-
Notifications
You must be signed in to change notification settings - Fork 281
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
DNG: exiv2 vs exiftool previewimage inconsistency #2825
Comments
There appears to be another issue; when examinging the DNG file for previews, the In the use case above, we are able to use |
I wouldn't get hung up on the size per se, as they don't really disagree:
However, the preview not being detected as a JPEG might need looking into. |
So the Not sure if there's an actual bug here, just difference in behaviour: exiv2 decides to treat DNG/TIFF subimages as still valid TIFF images when possible, and doesn't necessary "unwrap" them unless they're specifically designated as preview/thumbnail images (using e.g. the JPEGInterchangeFormatLength tag instead of StripByteCounts, which in contrast seems to make |
I have a DNG generated from Halide IOS camera appl.
I use
exiftool
to update the previewimage following advice from Phil Harvey replacing the previewimage with afoo.jpg
. I can subsequently pull the image usingexiftool
and its identical to the preview image.However,
exiftool
andexiv2
(0.28.1) have inconsistencies:exiv2 -pt
reports aExif.Image.StripByteCounts
(viaexiv2 -t ...
) that is incorrect - I am expect this to be the exact size matching foo.jpg, the inserted preview imageexiv2 -pp
reports the preview image is aimage/tiff
(expect jpeg)exiv2 -ep1
extracts a corrupt imageRunning with
exiv2 0.28.1
built from source on linux/x64 andexiftool 12.69
To Reproduce
exiv2
andexiftool
disagree on preview image sizeExpected behavior
exiv2 -pp to reflect preview image size consistently.
The text was updated successfully, but these errors were encountered: