mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
iOS live photos uploaded via photosync. mov.jpg is set to primary, not HEIC.jpg #1139
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#1139
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ferronand on GitHub (Oct 4, 2021).
When uploading to originals folder via photosync, a jpg of the live photo is created(filename.mov.jpg) based on the first frame of the live photo, and a jpg of the actual photo is created(filename.HEIC.jpg). The mov.jpg is then set to primary in the stack. How can we instead make sure the HEIC.jpg is set as primary? Changing the primary manually is not an option for me, as I have about 2 thousand photos.
@graciousgrey commented on GitHub (Oct 5, 2021):
Could you send us an example file for testing to hello@photoprism.app ?
@lastzero commented on GitHub (Oct 5, 2021):
Duplicate of #926
@lastzero commented on GitHub (Oct 5, 2021):
We'll implement this, but I need to look after a few other important issues first. In particular multi-user support as everyone and his dog is waiting for this. Setting the best available JPEG can easily be implemented later based on the existing index. In addition, we need to set a flag when the primary was changed manually so that PhotoPrism doesn't change it automatically. Not everyone might want to use the file with the highest resolution by maybe a crop.