Legacy ImageMagick Discussions Archive

Missed that in your original post or did you add that after the edit? No working on adding support for libraw to my build script and I use the following to compile libraw (only tested on Linux yet): autoreconf -fiv export CFLAGS="-O3 -fPIC" export CXXFLAGS="-O3 -fPIC" ./configure...

It looks like you want to do a `SubImageSearch` instead of a `Compare`?

Maybe this script can help you: https://github.com/dlemstra/Magick.NET/ ... S/Build.sh. I use it to statically build ImageMagick on macOS.

The clip path is stored in a vector format and the positions are relative to the 0x0 position of the image. And that does not change when you resize the image. The relative position is still the same. But this changes when you extent the image. The start position of the clipping path is no longer at...

This is not a bug but the expected result. The clipping path is never resized. Sometime you are lucky and you get the correct clip path because of how it stored in the image profile. I don't think we will be able to add support for this anytime soon.

Looks like the same issue has been reported and fixed here: https://github.com/ImageMagick/ImageMagick/issues/1343

The JSON looks correct to me. You probably need to report this to the MiniMagick team.

Did you only copy paste part of the json data that you get from minimagick? If this is all then this looks like an issue in that library.

Can you share your EPS file?

No idea where you downloaded ImageMagick but our version contains that .xml file.

We did not create that file so we cannot tell you where to download it.

Pango is included in the Windows installation of ImageMagick.

IM7 is more strict about the order of the arguments. You will need to move -auto-orient after reading the first image:

Are you using the latest version of Magick.NET? A similar issues was solved in: https://github.com/dlemstra/Magick.NET/issues/307

I suspect that your issue is the way your file explorer shows the file information due to exif information. The following happens with a resize: identify * b3skpyik.jpg JPEG 4128x2322 4128x2322+0+0 8-bit sRGB 2.12903MiB 0.016u 0:00.016 c4ldzu3g.jpg JPEG 4128x2322 4128x2322+0+0 8-bit sRGB 2.19882MiB ...