Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify file names possibility #500

Closed
ronbruins opened this issue Nov 17, 2022 · 7 comments
Closed

Specify file names possibility #500

ronbruins opened this issue Nov 17, 2022 · 7 comments

Comments

@ronbruins
Copy link

I’m using icloudpd to download photos to my NAS and photoprism to make an album of it. Works great, except for the following:

icloudpd downloads Live Photos as following:
IMG_1234.HEIC / IMG_1234_HEVC.MOV

photoprism sees this as two separate times and doesn’t combine it into a Live Photo. My workaround is to copy all to IMG_1234.MOV so they match and ignore the HEVC in photoprism. However now I end up with twice the files.

Is there a way to include an option to have both the files be named identical, except for different extensions obviously.

@Soulplayer
Copy link

I'm having the same issue... This would be awesome to add!

@dtlics
Copy link

dtlics commented Mar 21, 2024

If one downloads the "original" version via iCloud API, xxx.HEIC and xxx.MOV is the files one gets, not sure why icloudpd decides to name is as xxx.HEIC and xxx_HEVC.MOV, this makes it complicated when one wants to use other iCloud functions based on the icloudpd results. What I do is I icloudpd once then do renaming via codes, then I have to stop using icloupd because it'll mess up the files

@dtlics
Copy link

dtlics commented Mar 21, 2024

would really appreciate it if icloudpd can get this corrected. I don't wanna fork my own icloudpd and do this cause I expect future versions of icloudpd will be needed when icloud updates its APIs...

@AndreyNikiforov
Copy link
Collaborator

would really appreciate it if icloudpd can get this corrected

That is not a bug. icloudpd adds extension of the image to the name of the video file for live photos. Without that you can have live photo and regular video competing for the name with .MOV extension. Example:

  • Live Photo Image1234 will be saved as a pair: Image1234.HEIC & Image1234_HEIC.MOV
  • Video Asset Image1234.MOV will be saved as Image1234.MOV without conflict

@dtlics
Copy link

dtlics commented Mar 22, 2024

would iPhone generate xxx.HEIC and xxx.MOV? it seems my iPhone would do something like IMG_0118.HEIC and then if i shoot a video it'll be IMG_0119.MOV, it increments the number by 1 automatically. I'm afraid worrying too much about avoiding duplicates adds too much complexity to using the tool with other softwares... I'd love to hear how your team think about this

@AndreyNikiforov
Copy link
Collaborator

would iPhone generate xxx.HEIC and xxx.MOV? it seems my iPhone would do something like IMG_0118.HEIC and then if i shoot a video it'll be IMG_0119.MOV, it increments the number by 1 automatically. I'm afraid worrying too much about avoiding duplicates adds too much complexity to using the tool with other softwares... I'd love to hear how your team think about this

Duplicate management needed for resolving updates over existing storage (to avoid re-downloading) as well. If you think it is worth supporting the case without _HEIC suffix for movies in live photos, feel free to write down expected behavior for all cases and then implement under its own flag.

@AndreyNikiforov
Copy link
Collaborator

added to 1.18.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants