search

iMediaSandboxing / iMedia

The Karelia iMedia Browser, framework and application for browsing media on Mac OS X
http://www.karelia.com/imedia/
Other
18 stars 12 forks source link

Transcoded Apple Media images are unreliable? #95

Open danielpunkass opened 6 years ago

danielpunkass commented 6 years ago

Has anybody else noticed problems with images from Apple Media Library that originated from e.g. a new iPhone X? The HEIC format of the image seems to cause them to be transcoded by Apple, such that a cached copy is actually supplied to iMedia. This works for many images but:

  1. The image is often supplied with a long uuid-style name as opposed to the real logical name on the photo.

  2. The image is sometimes considered to be not found because a cached copy is apparently not present in Apple's internal transcoding cache.

I haven't received specific bug reports about this, so I'm not sure how common this problem, or whether I've gotten my own Photos installation into an unusual predicament. I suspect that at a minimum the unfortunate image names are being generated for these images.

Screen shot from MarsEdit but is probably representative of standalone iMedia Browser behavior as well.

2018-01-22 at 10 51 am

iljaiwas commented 6 years ago

Will try to replicate once I've become a super successful Mac indie/podcaster, who's able to afford an iPhone X. 😘

danielpunkass commented 6 years ago

Hahaha! Touché. FWIW I think I misunderstood the new codecs, and they are being used on all iOS 11 devices. So ... perhaps it's more widespread than just iPhone X?

danielpunkass commented 6 years ago

I think point #1 about the image name can be disregarded. It's my own bug interpreting the name as the file name of the supplied URL. Obviously iMedia has the name right as it's displayed in the thumbnail view.

So it seems there is just an issue, possibly rare, where an MLMediaObject has a URL attribute referencing a cached transcoded file that doesn't actually exist.

danielpunkass commented 6 years ago

Depending on how common it is to encounter this scenario, I think the fix is probably for iMedia to be resilient to missing assets at "URL" and to resort to transcoding ourselves, if needed, the asset at "originalURL".

danielpunkass commented 4 years ago

For what it's worth I haven't noticed this lately or heard complaints from customers along these lines. Maybe it was a fleeting issue at the time which has been addressed in subsequent OS updates?