GeoTagging of JPEGs broken in most recent versions?
Wed, 01/06/2010 - 01:23 — mplusplus
Anyone experiencing problems with geotagging functionality in the most recent versions of bt747? in particular "save tagged files" seems to be broken in 2.x.1630 and 2.x.1636. 2.x.1618, 2.x.1624 work fine with the same set of pictures.
I confirm the issue. I fixed it and added a test case for it in the regression. The build should be online in about 20 minutes and be called 2.X.1637 or later.
I've tried the version 1637 and the reported issue has been fixed (I think, I had a similar problem where the file seemed to be renamed before being modified), but then I get a new problem: the created JPEG files are seen as being broken by all utilities I tried under Linux (at least ImageMagick, GIMP and KDE viewer, using imlib). Here the error message from ImageMagick (exists also for Windows):
display: Corrupt JPEG data: 952 extraneous bytes before marker 0x01 `8984_IMG_tagged.JPG'.
display: Corrupt JPEG data: 23 extraneous bytes before marker 0x7f `8984_IMG_tagged.JPG'.
display: Unsupported marker type 0x7f `8984_IMG_tagged.JPG'.
(other programs give a very similar error message)
In that case, can you send me a sample image file. Some makers add extra stuff in the EXIF data that is not really foreseen in the EXIF specification and I need to improve BT747 for that - or maybe it is a bug.
I'll check in more detail with the JPG files I have already. The 'self-tests' I wrote for checking the tagging are working but not 'exhaustive'.
Thanks for the note, I'll
Thanks for the note, I'll check this out in +/- 19 hours ;-).
Hi I confirm the issue. I
Hi
I confirm the issue. I fixed it and added a test case for it in the regression. The build should be online in about 20 minutes and be called 2.X.1637 or later.
Kind regards
Mario
Hello, I've tried the version
Hello,
I've tried the version 1637 and the reported issue has been fixed (I think, I had a similar problem where the file seemed to be renamed before being modified), but then I get a new problem: the created JPEG files are seen as being broken by all utilities I tried under Linux (at least ImageMagick, GIMP and KDE viewer, using imlib). Here the error message from ImageMagick (exists also for Windows):
display: Corrupt JPEG data: 952 extraneous bytes before marker 0x01 `8984_IMG_tagged.JPG'.
display: Corrupt JPEG data: 23 extraneous bytes before marker 0x7f `8984_IMG_tagged.JPG'.
display: Unsupported marker type 0x7f `8984_IMG_tagged.JPG'.
(other programs give a very similar error message)
Thanks, Eric
Hi Eric In that case, can you
Hi Eric
In that case, can you send me a sample image file. Some makers add extra stuff in the EXIF data that is not really foreseen in the EXIF specification and I need to improve BT747 for that - or maybe it is a bug.
I'll check in more detail with the JPG files I have already. The 'self-tests' I wrote for checking the tagging are working but not 'exhaustive'.
OK, I created a bug report
OK, I created a bug report and attached the stuff to it: https://sourceforge.net/tracker/?func=detail&aid=2928890&group_id=196368&atid=957176
Thanks, Eric