Legacy ImageMagick Discussions Archive

Image: http://rvvs89.ucc.asn.au/stuff/huge/huge4.jpg Size: 30000x30000 Command: .\jpegtran.exe -crop 100x100+0+0 .\huge4.jpg output.jpg Failed: Insufficient memory (case 4) (even with maxmemory set to 500000) Well, with your huge4.jpg, ImageMagick (even stream) throws that error, too - at least on ...

Also remember the crop would be limited to multiples of 8. With lossless JPEG cropping, the size is not limited - but the starting point must be at a block boundary. Or, to put it in other words, the upper left point must be at a multiple of 8 or 16 (even bigger blocks are possible - but not widely...

Do not use "-define jpeg:size" - this is only good as a first step when drastically downsizing images, or when one only needs e.g. the metadata. You can use "-extract" as alternative to 'file[size]', but the extract option must be before the input image. With very large images, &...

Thanks! I didn't think of the background color. I wonder why IM sets such a random, non-grayscale background color in the first place. I already encountered other cases where the background color automatically changed to a strange value. Of course only a minor problem. The root cause of the failure ...

I created the chunks manually (with TweakPNG).
Thanks for the new patch!

If you still wonder why the combining of your original commands wasn't completely successful: As you first use a special compositing method, you have to change it back to the default ("-compose src-over") right before the second composite. Personally, I would also avoid nested parentheses ...

dfelder wrote:As it turns out, the [0] actually works with the old version, as well.

I see.. Interesting. (But still, the old versions had a bug there.)

@Glenn: I'll try to list only the PNG encoder problems. Unfortunately, the errors stayed the same in IM v6.6.8-2 (Q16, Win32). Now alpha channel disappearing (the tRNS chunk is missing): convert logo: -transparent white -define png:color-type=3 logo.png identify -format "%[channels]" logo....

The verbose messages look ok. But there's no file! And also no error message. Only in the debug messages, I see a "Cannot write PNG8 or color-type 3; colormap is NULL" line. The exception was being thrown into the encoder's temporary image structure (image) instead of into (IMimage). Fixe...

In ImageMagick-6.6.8-2 ou can use the "-define PNG:exclude-chunk=pHYs" option. Then the PNG encoder will fall back on writing a tEXt:density chunk in dots/inch units. Does this really work in IM v6.6.8-2? I don't find a successful command for that - e.g.: convert rose: -define png:exclude...

Another small thing.. 'identify -format "%x %y"' sometimes fails, too - at least with PNG files. Example - take this file: http://img651.imageshack.us/img651/5595/rosebc.png identify -verbose rosebc.png ... Resolution: 456x456 Units: PixelsPerInch ... identify -format "%[xresolution]x...

It works. Thank you! A small question regarding the handling of PSDs.. Is it supposed to be like that now (with the current IM): identify logo1.psd logo1.psd[0] PSD 267x136 267x136+0+0 8-bit DirectClass 830KB 0.000u 0:00.000 logo1.psd[1] PSD 194x116 194x116+35+6 8-bit DirectClass 830KB 0.000u 0:00.0...

What I'm expecting to see is this: ... identify -format %Wx%H offset. psd 400x400 FYI: It now works with IM v6.6.8-2. The windows binaries have been updated: http://www.imagemagick.org/script/binary-releases.php#windows Note that with PSDs, you now have to add the layer number 0 (for the composite ...

The reference.html file was not previously mentioned. I have fixed '-blackpoint-compensation' in that file. Thanks, Anthony! (I didn't even notice that "-blackpoint-compensation" was also in this file.) But yecril71pl probably meant that: At Operator Options Index : -draw Draw ~ Primative...

Hi, If you save as PNG, the density/resolution will be written into the "pHYs chunk" - but the unit there can only be pixels per meter or undefined, so ImageMagick has to convert the dpi values (see also here ). That means, the 72dpi can only be written as 28.34 PixelsPerCentimeter (71.983...