The problem I have is that after a size conversion the XMP in the file is no longer recognized by other applications. The XMP in the original file is somewhat 'corrupt' with multiple empty XMP areas but nevertheless it seems that the XMP is touched in the convert process.
My own analyzis is this:
The original file has multiple XMP meta blocks. However between the end of one and the start of another the following characters appear
<?xpacket end='w'?>ÿá¬http://ns.adobe.com/xap/1.0/<?xpacket begin
In the result XMP the extra characters are washed away. I suspect that this means that applicatoins will look for XMP in the very last XMP block which is empty. In the original file I suspect that the extra characters are providing applications to think that the extra blocks in fact are XMP.
(I am not sure why the XMP looks like it does in the original, the file is going through a lot of workflows and my idea is that this workflow adds this and that this is an error, but still expect the XMP to be ok after the convert command)
Tests have been carried out on Mac OSX 10.6.8 with
ImageMagick 6.7.8-0 2012-07-17 Q16
The following files can be downloaded for test
Original Image (appr 5.4 MB)
http://www.laidbacksolutions.se/ImageMa ... iginal.JPG
Result Image (appr 500 kB):
http://www.laidbacksolutions.se/ImageMa ... result.JPG
The command that have been executed to test is the following
Code: Select all
convert 20120725-original.JPG -resize 25% 20120725-result.JPG