Not correctly parsing exif files from Olympus camera

hypertex avatarhypertex created an issue

There might be something weird about my Olympus camera generating strange files. They have a "PrintIM" tag, which is a proprietary standard that cannot be decoded as far as I know. This tag may or may not be causing the problems.

from what I can tell, the IFD[0] is correctly parsed, but IFD[1] is not. According to the IFD[0], the next IFD offset is 1174 (absolute position 1186). However, hachoir is parsing IFD[1] beginning at 578. The resulting data makes no sense, for example, this camera has no GPS capability, but hachoir is telling me that it has GPS tags.

I will attach an example file. I get the same results with all files from this Camera, so it's not just one corrupt file.

Comments (3)

  1. nneonneo

    I've got an EXIF rewrite in the works which parses your file (and several more broken ones) correctly. I'll hopefully get that committed this weekend, if there aren't any complaints.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.