I am using exiftool to parse files from the Panasonic GH6, released a few weeks ago, and it is giving some very mixed up data.
The image shows some of the relevant source code, and the output from Sony cameras, and the problematic output from the GH6. As I said, deleting the output and running it again seems to solve the problem. Sometimes.
Strangely enough, it seems to work sometimes, and not others.
exiftool -fast -T -aperture -cameratemperature -datetimeoriginal -daylightsavings -directory -directorynumber -filename -filenumber -focallength -fov -imagesize -iso -keywords -lensid -lightvalue -model -modifydate -orientation -rating -serialnumber -shuttercount -shutterspeed -subject -timezone -filesize\#
This is the only exiftool-specific code being used.
As you can see, the order of fields in the output is not showing up right.
Not sure if this will help, but this is an example GH6 file.
I think this is a problem with your parsing of the ExifTool output.
- Phil
That's entirely possible, although the software that's parsing of EXIF output from exiftool has worked for millions of images from a huge number of camera models in the past 20 years with not a glitch in many years.
It looks like the direct output from exiftool (which is in those files) is not in the order specified in the command line. These are programs within programs within programs, so it's possible that something is mangling it somewhere. The only common factor we've been able to identify is the GH6.
Figured it out. You're right, it's not exiftool causing a problem, although there are some fields unsupported it appears.
macOS 12.3 from March 14th apparently stopped following the traditional POSIX specification and/or some legacy/deprecated command-line tool options were broken, so there's some code for merging the exif data from recently modified files and the exif data from previously parsed files that needs to be rewritten. This just happened to be almost the same time that some GH6 files showed up for the first time in our databases.