-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Better support for HEIC/HEIF files created by iOS #269
Comments
Thanks for opening this issue. Once exiftool adds support for HEIC files we should update the Readme to say something similar as it says for videos with regard to the minimum version of exiftool needed. |
I'm not having any luck getting elodie to recognize & process HEIC files. When I run exiftool on the files, I get a full dump of the exif data, but it's not clear to me from the exiftool history notes whether write support exists. Is elodie currently still unable to read and categorize HEIC files? |
One suggestion - perhaps have elodie mark HEIC files as an error? Right now, it appears to just be taking no action on that file type (success=0, errors=0). In my case Elodie is called by a Hazel rule, so in the absence of an error I had no idea those files weren't being successfully processed. |
(As a Windows user I'd never heard of Hazel "Automated Organization for Your Mac".) |
Unfortunately there's no good support for detecting HEIC files in Instead, for now, I've created #320 to special case HEIC by extension. |
…nd add HEIC support (#320) Fixes #281 and #269 When elodie imports images, imghdr.what is used to determine the image type. imghdr implementation won't support all JPEG variants. Because of this, even for a valid JPEG file, imghdr.what returns None causing elodie to skip the image during import. This commit adds a fallback mechanism which uses PIL(pillow) library to identify image formats. When imghdr fails, elodie uses pillow to identify image format. When pillow is unavailable, it will be treated as an invalid media file. Pillow is imported only when imghdr fails.
…nd add HEIC support (#320) Fixes #281 and #269 When elodie imports images, imghdr.what is used to determine the image type. imghdr implementation won't support all JPEG variants. Because of this, even for a valid JPEG file, imghdr.what returns None causing elodie to skip the image during import. This commit adds a fallback mechanism which uses PIL(pillow) library to identify image formats. When imghdr fails, elodie uses pillow to identify image format. When pillow is unavailable, it will be treated as an invalid media file. Pillow is imported only when imghdr fails.
…nd add HEIC support (#320) Fixes #281 and #269 When elodie imports images, imghdr.what is used to determine the image type. imghdr implementation won't support all JPEG variants. Because of this, even for a valid JPEG file, imghdr.what returns None causing elodie to skip the image during import. This commit adds a fallback mechanism which uses PIL(pillow) library to identify image formats. When imghdr fails, elodie uses pillow to identify image format. When pillow is unavailable, it will be treated as an invalid media file. Pillow is imported only when imghdr fails.
Marking this as closed as HEIC support is now available in master. |
…nd add HEIC support (#320) Fixes #281 and #269 When elodie imports images, imghdr.what is used to determine the image type. imghdr implementation won't support all JPEG variants. Because of this, even for a valid JPEG file, imghdr.what returns None causing elodie to skip the image during import. This commit adds a fallback mechanism which uses PIL(pillow) library to identify image formats. When imghdr fails, elodie uses pillow to identify image format. When pillow is unavailable, it will be treated as an invalid media file. Pillow is imported only when imghdr fails.
HEIC support requires |
It looks like Elodie is unable to currently process HEIC files coming from modern iPhones.
This seems to be an exiftool issue, which currently has Read Support, but does not currently have write support yet. They are making progress though.
The text was updated successfully, but these errors were encountered: