GNOME Bugzilla – Bug 711242
Different values for some metadata on GIMP (new metadata system) and exiftool
Last modified: 2015-08-24 11:50:37 UTC
In bug 710937, a user provided a jpeg straight out a Canon camera. It loads fine but the metadata seems wrong, when I compare to `exiftool -a -u -g1 IMG_4810.JPG`. For instance exiftool says (which corresponds to what the user says. Photo taken with long exposure in bulb mode): Shooting Mode : Bulb Shutter Speed : 60.5 I can't find a shooting mode tag in our metadata window, but there is for instance Exif.Photo.ExposureMode which is "Manual" and Exif.Photo.ExposureTime is 61s. I imagine they may be the same. But we should display "Bulb". And why do we approximate the shutter speed to integer if it is a float? I don't know if the bug is in (G)Exiv2 or GIMP though. I'll let the metadata expert take care of it, and eventually report a bug upstream if we end up not being responsible for this. :-) The attachment is too big for the tracker. The user provided an upload there: https://app.box.com/s/3j2u9nu7hcr9fgpz1two Please download IMG_4810.JPG.
Nobody here is an expert, I suggest you become one and help us understanding what the return values of gexiv2 really mean :)
Ahahaha. Good point. :-) Well maybe later then. Metadata are not my biggest priority, though it is an interesting topic. :p
the exiv2 command line tool says: Exposure time : 61 s So GIMP is simply using what it gets from there, closing as NOTGNOME (we should probably figure how to submit bugs against exiv2 now...)
The exiv2 website is www.exiv2.org, but currently it's unreachable. The GExiv2 bugtracker is here: http://redmine.yorba.org/projects/gexiv2/issues
Hmmm... I actually managed to connect this morning to exiv2.org (though not anymore), but I couldn't on dev.exiv2.org (where there is supposed to be their bugtracker, it seems), even after several tries all along the day. Anyway I hope you won't mind if I reopen this only until we manage to report the problem upstream. That makes it a reminder. Otherwise I will forget. As soon as someone can report the bug upstream, let's close again as NOTGNOME. :-)
Reported there: http://dev.exiv2.org/issues/935
For info: they considered that the bug is not to be fixed because it may break scripts out there relying on it. I am trying to get it reopened and also submitted a patch to Exiv2.
For info: after discussion, this is now fixed in Exiv2. :-)