After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 711242 - Different values for some metadata on GIMP (new metadata system) and exiftool
Different values for some metadata on GIMP (new metadata system) and exiftool
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: General
git master
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-11-01 01:34 UTC by Jehan
Modified: 2015-08-24 11:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jehan 2013-11-01 01:34:23 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.
Comment 1 Michael Natterer 2013-11-01 12:03:49 UTC
Nobody here is an expert, I suggest you become one and help us understanding
what the return values of gexiv2 really mean :)
Comment 2 Jehan 2013-11-01 21:14:05 UTC
Ahahaha. Good point. :-)
Well maybe later then. Metadata are not my biggest priority, though it is an interesting topic. :p
Comment 3 Michael Natterer 2013-11-03 14:52:05 UTC
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...)
Comment 4 Max Mustermann 2013-11-03 16:42:50 UTC
The exiv2 website is www.exiv2.org, but currently it's unreachable.
The GExiv2 bugtracker is here: http://redmine.yorba.org/projects/gexiv2/issues
Comment 5 Jehan 2013-11-04 05:58:21 UTC
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. :-)
Comment 6 Jehan 2013-11-08 06:49:15 UTC
Reported there: http://dev.exiv2.org/issues/935
Comment 7 Jehan 2015-08-22 10:25:56 UTC
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.
Comment 8 Jehan 2015-08-24 11:50:37 UTC
For info: after discussion, this is now fixed in Exiv2. :-)