Olympus (E-1 and E-300) makernote flavour not supported: libexiv2 destroy some exif data on write
Writing a tag to a immage destroy some olympus exiv data.
I found this bug using digikam an report it. See https://bugs.kde.org/show_bug.cgi?id=225272
In this report are example data for verification.
I reporduce the bug using $exiv2 -M "set Exif.Image.Artist Ascii nobody" image.jpg
Updated by Andreas Huggel about 11 years ago
- Priority changed from Urgent to Normal
This is the result of missing support for this particular version of the Olympus Makernote.
The following comment from exiftool explains in detail:
# # Olympus really screwed up the format of the following subdirectories (for the # E-1 and E-300 anyway). Not only is the subdirectory value data not included in # the size, but also the count is 2 bytes short for the subdirectory itself # (presumably the Olympus programmers forgot about the 2-byte entry count at the # start of the subdirectory). This mess is straightened out and these subdirs # are written properly when ExifTool rewrites the file. (This problem has been # fixed in the new-style MakerNoteOlympus2 maker notes since a standard SubIFD # offset value is used.) - PH #
Exiv2 currently only supports the newer Olympus Makernotes that use standard SubIFD offset values for these subdirectories (called 'MakerNoteOlympus2' in exiftool and the comment above). As a result, Exiv2 does not decode the directories
and they are potentially corrupted when Exiv2 attempts to write to the Exif data (only in case of non-intrusive writing).
Changing Priority to 'Normal', this issue affects only specific Olympus camera models as it seems and is a feature, rather than a bug.
Updated by Robin Mills about 5 years ago
- Status changed from New to Assigned
- Assignee set to Robin Mills
This issue has been in the database for 5 years and nobody else has requested progress with this matter. So, unless you engage to persuade me to keep this matter alive, it will be closed on April 30 as "no longer needed/wanted".