-
Notifications
You must be signed in to change notification settings - Fork 685
How To support Apple's Live Photo? #578
Comments
Hello @satifanie |
Reading the documentation: https://developer.apple.com/library/prerelease/ios/releasenotes/General/WhatsNewIniOS/Articles/iOS9_1.html#//apple_ref/doc/uid/TP40016572-DontLinkElementID_2 Looks like that if we export the photos on the Photo Live format the photos are not JPG or PNG so the only devices that could see the pictures will be other iPhones 6s or 6s Plus... I think that it is a bad idea support Live Photo 😞 |
I think it's possible. A live photo is comprised of two simple files. A jpg and a mov file. Please note: I am no expert here and I haven't used PhotoSync - I just have been doing some research on this topic because I am hoping to cancel my apple iCloud subscription after sorting out these types of challenges. Anyway, this is what I found about the live photos: The two files are related together with an asset identifier in the form of a a UUID as a string in the metadata.
Timed Metadata track with ["com.apple.quicktime.still-image-time" : 0xFF]; The actual still image time matches up to the presentation timestamp for this metadata item. The payload seems to just be a single 0xFF byte (aka -1) and can be ignored. If using an AVAssetReader you can use CMSampleBufferGetOutputPresentationTimeStamp to get this time. The assetIdentifier is what ties the two items together and the timed metadata track is what tells the system where the still image sits in the movie timeline. |
By now this became feasible again, as Apple now released a SDK to embed Live Photos into Websites - https://developer.apple.com/live-photos/ The most important thing is, that both files are uploaded, the image and the adjacent movie file. If they are not modified, uploading them as-is is sufficient. In case there's a conversion, the metadata needs to be adjusted. |
I had tried, but the live phone after uploaded turned to be a normal one when I downloaded it again .
Can live photo be supported?
The text was updated successfully, but these errors were encountered: