Fix CR3 detection #310
Merged
Fix CR3 detection #310
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sylikc
added
the
format support
|
hmm, i wonder if this is what has caused problems when i'm opening CR3 files... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#261 broke CR3 detection. CR3 uses the HEIF container, so it gets detected as a HEIF before checking the file extension.
I added a check for the "crx " major brand and moved the unspecified encoding fallback after the file extension check. I moved TIFF detection here as well, which currently won't really do anything since it just goes to GDI+ anyway. I also added the
.HIFextension used by newer Canon cameras (https://github.com/lclevy/canon_cr3/blob/master/heif.md)