Legacy ImageMagick Discussions Archive

This is expected behavior. Instead try this command:

We'll add a 565 coder within a day or two:

Assume 8-bits per pixel, so -depth 8 is required. Even so, with a width of 800 pixels (e.g. -size 800x600), thats 2400 bytes of RGB per scanline. With a file length of 960000, the pixels are consumed after 400 rows, although you are asking for 600-- thus an exception is thrown. How many rows and col...

-48 will be released today. Nudge Arch to upgrade or build -48 from source.

With PerlMagick you can read an image, resize it, and get the pixels all in memory. See https://imagemagick.org/script/perl-magick.php for example PerlMagick scripts.

Thanks for the problem report. We can reproduce it and will have a patch to fix it in GIT master branch @ https://github.com/ImageMagick/ImageMagick later today. The patch will be available in the beta releases of ImageMagick @ https://www.imagemagick.org/download/beta/ by sometime tomorrow.

Thanks for the problem report. We can reproduce it and will have a patch to fix it in GIT master branch @ https://github.com/ImageMagick/ImageMagick later today. The patch will be available in the beta releases of ImageMagick @ https://www.imagemagick.org/download/beta/ by sometime tomorrow.

Convolution in IMv7 had a bug when dealing with alpha channels. The bug is fixed in -47. Using -channel RGB tells IM to ignore the alpha channel when blurring. It should, as Fred suggests, fix the problem you reported.

Use -scale rather than -resize. Resizing is a two pass process that causes ImageMagick to read pixels in a non-optimal manner, column-wise rather than row-wise. That's fine for memory, but as you found, very slow on disk.

Not a bug. ImageMagick is behaving properly. It does not support high bit-depth images exported by Gimp 2.10 and alerts you when you try to read the image. Two solutions. One, save your image in the Gimp 2.8 compatible format or wait for a patch to the XCF reader in ImageMagick. We do not have an ET...

Try now. We built a new Beta release.

Post a link to your Loading Default.2rawdata image file. We need to reproduce the problem before we can comment.

Grab the latest beta (building now). This command works for both IMv6 and IMv7: convert text.png -alpha deactivate -blur 0x6 -shade 135x5 -normalize +level 30% -alpha activate shaded7.png There is a slight difference in shading. You can change the intensity to Rec609 and the results should match.

@hairykid shows the filename as msvg:... which suggests the renderer is MSVG, the internal ImageMagick SVG renderer.

We're not getting extra space in the ampersand with ImageMagick 7.0.8-46, the current release. Can you try with -46 and see if the problem persists for you?