Dirk Lemstra

There were some issues the last time we tried to upgrade it but we will check it again in a couple weeks.

I can reproduce this issue and it looks like we made a mistake when adding support for MPF. I am working on a fix and it looks like this file...

Yeah that embedded thumbnail is causing ImageMagick to think that there are 3 images instead of two. I will need to redesign how we are attempting to read the MPF...

This issue should be fixed in the next release. We will no longer try to read the MPF image. We will only do that if the extension of the image...

Probably but this feels like something that should be decided on the RMagick side. Maybe `GetColorTuple` should be used instead of `QueryColorname` to make sure you always get a hex...

You will need to set the compression during writing. The compression on the image should not have a setter because this is not used when writing the image. I think...

Might be a good idea to share a sample image that can be used for this?

No idea why this works in a unit test but you are setting `Format` to `MagickFormat.Png` in the `umlClassSettings`. This means the `Read` method expects to read an image in...

I just pushed some patches to resolve this issue. The image is still slightly larger but you can now convert into another png without the requirement to do a reduction...

The problem here is that the `webp` encoder does a call to `-coalesce` and when this is done twice the output is incorrect. We have removed the call to `-coalesce`...