Legacy ImageMagick Discussions Archive

Which version of ImageMagick are you using?

Woops seems I made a mistake, I will try to fix this before the next release.

You can increase the memory limit with Image::cacheThreshold(bytes). The documentation says megabytes but it really is bytes, I already patched this comment in the svn repository. You can read more about memory limits on windows here: http://msdn.microsoft.com/en-us/library/aa366778.aspx.

You are better of using GetImageChannelDistortion with MetricType=RootMeanSquaredErrorMetric

I just copy pasted into the command line and that didn't work. It works when I run it from a batch file, I will investigate it further.

I get an error when I run your command:
convert.exe: invalid argument for option `sparse-color': Invalid number of Arguments @ error/mogrify.c/SparseColorOption/522.

My mistake I read that the image should be darker. Can you post 'twoGrad2.png' somewhere snibgo?

It seems that ImageMagick sets the colorspace to sRGB instead of RGB. Not sure if this is a bug. Changing the colorspace to RGB fixes the problem.

I am working on some changes to fix the problem with the compression. I agree with you that the compression of the source image should not be used in the output image. The default compression that is used normally should be used. We had had the same problem with the quality setting a while back (htt...

The problem probably the amount of pixels in your image. At some point ImageMagick will use your disk to store its pixels and reading/writing that is really slow. Maybe you can switch your application to 64 bit? This will allow you to allocate more memory at once.

I just tried it with the latest beta of ImageMagick. With Q16 and x64 I am able to create multiple output images. They all have one/two colors, not sure if this is the expected result. I did have to add '-define registry:temporary-path=' because the image is ridiculously large.

Libtiff checks if a certain value will fit in an int32 and for this image that won't fit. You should use the x64 version of ImageMagick and not the x86 version.

I can confirm this is a bug in Magick++, it will be fixed in a couple of days.

Edit: I have committed my changes, this will be fixed in the next version of ImageMagick.

Can you please post your IM version and platform?

I prefer bit-depth, it will be available in the next release of ImageMagick.