snibgo

This issue relates to a problem raised in https://github.com/ImageMagick/ImageMagick/discussions/5186 Two of the major limitations in coders\vicar.c are: 1. The coder assumes there is only one image. 2. The coder assumes...

The problem seems to occur when we have a small component at top-left. For example (Windows scripts): ``` %IMG7%magick ^ -size 300x300 xc:#0f0 ^ -fill Black ^ -draw "rectangle 0,0,10,10"...

In my x3.png above, the bottom-right black square was correctly removed, but the top-left square was not removed. A workaround for this image (not a general workaround) is "-virtual-pixel Tile"...

> I suppose it is easy enough either for the code or for the user to just include -virtual-pixel none. That would solve the merging issue in x3.png, but sadly...

"-virtual-pixel None" doesn't fix the problem with spm_hue_4a.png in the OP. For the component at top-left, there are no components above or to the left to merge into. For this...

``` magick y1.miff y2.miff y3.miff -compose over -composite xx7b.png ``` The problem is that y3.miff has an alpha channel. This is entirely opaque (alpha=100%), but the presence of the alpha...

With IM 7.1.0-42, your command gives a (bad) gray result. To get a (good) result of the jigsaw over Lena, remove the second "-channel rgb". Windows syntax: ``` %IMG71042%magick tmpA17.miff...

The problem seems to be in statistic.c, function ApplyEvaluateOperator(): ``` case PowEvaluateOperator: { if (pixel < 0) result=(double) -(QuantumRange*pow((double) -(QuantumScale*pixel), (double) value)); else result=(double) (QuantumRange*pow((double) (QuantumScale*pixel), (double) value)); break; }...

I suggest using a "-quality" setting, like this: ``` magick abcmlad.jpg -quality 40 out.pdf ```

> My aim is to have identical images, ... I don't think IM can do that. IM reads your input files into memory, decompressing each image into pixels. Then it...