Doug Ames
Forum Enthusiast
I'm writing a utility to convert the camera data segment in my old Olympus D-320L files to EXIF format so that photo album programs can read it and index the files properly. In the course of doing this I've discovered a couple of bugs in EXIF handling in IrfanView 3.8 and ACDSee 5:
Viewing EXIF data in IrfanView 3.8 for Motorola-byte-order cameras like Olympus:
The Max Aperature value is calculated incorrectly; hence the sometimes odd numbers you see like "2.64" instead of exactly 2.8
The FileSource and SceneType values have incorrectly inverted byte order; hence they are shown as "other" instead of the correct types.
Editing EXIF data In ACDSee 5:
It inserts an APP0 (JFIF) segment before the EXIF (APP1) segment, which may confuse some software.
Also it always changes the EXIF byte alignment to Intel, even if it was Motorola before, but it fails to change the Maker Note section correctly, and therefore corrupts this data for camera models where the Maker Note was originally Motorola alignment.
Viewing EXIF data in IrfanView 3.8 for Motorola-byte-order cameras like Olympus:
The Max Aperature value is calculated incorrectly; hence the sometimes odd numbers you see like "2.64" instead of exactly 2.8
The FileSource and SceneType values have incorrectly inverted byte order; hence they are shown as "other" instead of the correct types.
Editing EXIF data In ACDSee 5:
It inserts an APP0 (JFIF) segment before the EXIF (APP1) segment, which may confuse some software.
Also it always changes the EXIF byte alignment to Intel, even if it was Motorola before, but it fails to change the Maker Note section correctly, and therefore corrupts this data for camera models where the Maker Note was originally Motorola alignment.
