You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I traced through this library and it looks like the child IFD for Tag::GPSInfoIFDPointer has a next_ifd_offset of -1 (i.e. 0xFF_FF_FF_FF) instead of 0, which causes this library to fail with InvalidFormat("Unexpected next IFD").
The file is able to be parsed using exiftool. I traced through its Perl code and it seems like exiftool only parses the next IFD if the tag is known to have a next IFD. So maybe it's safe to just ignore the next IFD offset for child IFDs instead of validating the offset? That would allow this library to read EXIF metadata from files like this one. What do you think?
The text was updated successfully, but these errors were encountered:
I've noticed, that someone already hacked a solution for this problem : vabock@76ee369
This solved my similar problem, maybe you can merge this fix, and release the library. What do you think?
I have a JPEG image generated by a FLIR camera:
I traced through this library and it looks like the child IFD for
Tag::GPSInfoIFDPointer
has anext_ifd_offset
of -1 (i.e.0xFF_FF_FF_FF
) instead of 0, which causes this library to fail withInvalidFormat("Unexpected next IFD")
.The file is able to be parsed using
exiftool
. I traced through its Perl code and it seems likeexiftool
only parses the next IFD if the tag is known to have a next IFD. So maybe it's safe to just ignore the next IFD offset for child IFDs instead of validating the offset? That would allow this library to read EXIF metadata from files like this one. What do you think?The text was updated successfully, but these errors were encountered: