[Originally posted by bozi on 2007-03-25 18:05:57-07]
Hi phil,
I have Problems with the Makernotes in 6.83, stable version is hmmm sometimes OK.
Im mostly using a template-file with -p ... an often Tag values appears as "0". At commandline
sometimes warnings like
[minor] Adjusted MakerNotes base by 33
Invalid CanonCameraSettings data
[minor] Tag 'ImageStabilizer' not defined
are displayed.
The best Version for me seems to be the 6.68
2 template lines:
Cam: $Model (${ShutterCount}) ... Linse: ${Lens} @ ${FocalLength}
${ShutterSpeed} s ... F $Aperture ... ISO $ISO ... EV: $ExposureCompensation ... Focus: $focusmode
thnx, bozi
[Originally posted by exiftool on 2007-03-25 23:40:14-07]
Hi Bozi,
I just made a change in 6.83 to automatically fix Canon maker notes,
but apparently it isn't doing the right thing for your image, which is
surprising. Could you send me a sample? (my email is
philharvey66 at gmail.com) Also, what utilities did you use to edit
the image before you used ExifTool?
Thanks.
- Phil
[Originally posted by bozi on 2007-04-05 21:10:22-07]hi phil,
sorry for the late reply.
here are 2 examples of those jpegs:
jpeg1 jpeg2 my template-file consists of 2 lines:
Cam: $Model ($ShutterCount) ... Linse: $Lens @ $FocalLength
$ShutterSpeed s ... F $Aperture ... ISO $ISO ... EV: $ExposureCompensation ... Focus: $focusmode
This template worked with older exiftool versions (7.6.x) with those files too.
In newer Versions some (unused) Tags of the template stops the whole decoding.
I think these tags doesnt exist in those "crippled" files (Warning: [minor] Tag 'ShutterCount' not defined - ...)
hmmm, its only a warning, but exiftool aborts the process. I found the -m parameter (for errors)
My solution is the -m parameter, so exiftool doesnt abort when warnings appearing *wondering*
alfterall, my
now working command is
exiftool -m -p e.tpl ...
cu, bozi
[Originally posted by exiftool on 2007-04-05 23:13:21-07]Hi Bozi,
Sorry for not recognizing the problem sooner (especially sorry
because I reverted the automatic makernote fixing in case
this feature was causing problems).
The new behaviour is as designed, and is due to a feature that
was added in version 6.69 which gives you more flexibility over
how the missing tags are handled. From the history:
Jan. 8, 2007 - Version 6.69
- The -p option no longer suppresses error and warning messages
And to quote the new
-p documentation:
If a tag does not exist, the output value is set to '-' if the -f option
is used. Otherwise a minor warning is issued and the line with the missing
tag is not printed. However, if the -m option is used, minor warnings
are ignored and the line is printed with an empty tag value.
So now you get a choice of 3 ways to handle missing tags.
- Phil