Live Photo Support
steilerDev opened this issue · 7 comments
Syncing Live Photo's video portion as a separate file.
I would love to help you on this one. I've looked at the postman collection and I think I found the live video, which is at resOriginalVidComplRes I believe. For HEIC, I don't see the sidecar file though, do you know where that is located?
I'm not sure if this is available through the API - why would the sidecar file be important?
I have some comments across the code where changes need to happen for this. Generally speaking loading the local and remote library needs to support this.
I had a think about this, and other future additional assets associated to a picture - we should consider using an extensible container format for storing those assets in a single location.
A couple of options I've been investigating:
- Have a directory per picture, with different versions (original, edited, live, ...) in there
- Use a standardized container format, like TIFF or matrovska - however it seems none of them supports both video and images. Matrovska is very much focused on audio and video, while tiff only seems to support pictures
I'm a little bit torn between the options and would love to have your opinion on this
I'm not sure if this is available through the API - why would the sidecar file be important?
I am using PhotoSync and it provides the adjustment data if the image is adjusted, and some of my photos are.
I had a think about this, and other future additional assets associated to a picture - we should consider using an extensible container format for storing those assets in a single location.
A couple of options I've been investigating:
- Have a directory per picture, with different versions (original, edited, live, ...) in there
- Use a standardized container format, like TIFF or matrovska - however it seems none of them supports both video and images. Matrovska is very much focused on audio and video, while tiff only seems to support pictures
I'm a little bit torn between the options and would love to have your opinion on this
The preference I have would be to have the additional files with the same name and since they will differ on file type, it should not be an issue. At least PhotoSync does it that way and would be nice to keep it consistent. Having a separate folder per image would create a management hell in my opinion. In terms of a container format, I haven't seen anything that would be able to cover the set of files in this case.
I've created a separate issue (#354) to explain my proposal - would love to get your input on my ideas there / alternative ideas.
For the sidecar files - if the API allows me to pull them I'm happy to work them into the new library structure - if we add many additional files without separating them in folders, the folders themselve could become very cluttered, very quickly - we need to find a good balance.
Closing this in favor of #354