Identifying JPEGs give wrong results

Post any defects you find in the released or beta versions of the ImageMagick software here. Include the ImageMagick version, OS, and any command-line required to reproduce the problem. Got a patch for a bug? Post it here.
Post Reply
rwedrich

Identifying JPEGs give wrong results

Post by rwedrich »

Hi,

we use ImageMagick for identifying image metadata like size, resolution etc. in a database publishing system (by using identify -verbose). We have noticed that since some versions, IM gives the wrong resolution for jpegs saved by Photoshop CS2 (result is always 72 ppi). Photoshop, TheGimp or IrfanView give the correct resolution, so I presume that it is IM's fault.

Here are some examples:
http://www.lobster.de/testimages.zip

The correct resolution is indicated in the image's title.

Thanks for having a look (and, if possible, a quick solution...)

Rainer
User avatar
magick
Site Admin
Posts: 11064
Joined: 2003-05-31T11:32:55-07:00

Re: Identifying JPEGs give wrong results

Post by magick »

ImageMagick is picking up two EXIF resolution tags instead of one so for the 96 DPI case it picks up 96 then 72. We will have a fix for this problem in ImageMagick 6.3.6-2 Beta sometime tomorrow.
rwedrich

Re: Identifying JPEGs give wrong results

Post by rwedrich »

Thanks, it works fine with JPEGs and TIFF now. However, I just found found that the same Problem exists with PSD and EPS files.

Here are some test files, the Photoshop resolution ist given in the filename. Identify returns 72x72 in each case and no value for "units":

http://www.lobster.de/test_images.zip

Hopy you'll be able to fix this, too...
User avatar
mi
Posts: 123
Joined: 2005-01-25T14:14:43-07:00
Contact:

Re: Identifying JPEGs give wrong results

Post by mi »

This sounds important... Could you, please, publish a patch against 6.3.6-9? Thanks!
User avatar
magick
Site Admin
Posts: 11064
Joined: 2003-05-31T11:32:55-07:00

Re: Identifying JPEGs give wrong results

Post by magick »

Your images have an embedded XMP profile which is not properly being separated from its 8BIM wrapper. We will fix this problem but we currently do not have an ETA given that our list of things-to-do currently has several hundred items
Post Reply