|
From: Jan P. <pa...@pi...> - 2006-04-15 19:19:23
|
John, I just commited a fix (in exif-loader.c) to CVS at sf.net. The problem was that APP2 marker with ICC profile was not correctly skipped by libexif. The ICC profile was stored after the EXIF data in the original file. However, the modified file has ICC before EXIF. -- Jan > http://www.jetmore.org/john/pics/IMG_1309_orig.JPG > http://www.jetmore.org/john/pics/IMG_1309_edit.JPG > > I built _edit from _orig with the command: > > convert -resize 576x576 -rotate +90 IMG_1309_orig.JPG IMG_1309_edit.JPG > > (convert is from the ImageMagick package). > > Thanks > --John > > On Sat, 15 Apr 2006, Jan Patera wrote: > >> Hi John, >> >> could you please send me such transformed image via the >> www.yousendit.com service (or some other download link)? >> Thanks. >> >> -- Jan >> >> > Thanks for these tools, very helpful. >> > >> > I have images from a Canon camera that exif (and therefore libexif) >> reads fine. However, when I transform the files using tools from >> the ImageMagick package the exif tool can no longer find the exif >> info in the transformed image. At first I thought ImageMagick >> stripped the exif data out of the saved file, but now it looks like >> it just moves it far enough into the file that libexif doesn't see >> it. I the original file the EXIF tag is about 2 bytes into the >> file. In the transformed file, the EXIF tag is about 1346 bytes >> into the file. FWIW, other apps (specifically Grafic Converter and >> Preview on MacOSX) can read the EXIF data in the transformed file. >> > >> > I can work around this by updating the EXIF tags before I do the >> transformations (specifically, setting the orientation tag and the >> rotating the image), I just found it odd that libexif had this >> limitation and wondered if I was missing some obvious setting. >> > >> > Thanks >> > --John |