Legacy ImageMagick Discussions Archive

I wish it did. I've since found a few other assets that have similar problems though corrupt in different ways than this one. Removing -type palettematte does not fix them and some of them have actual alpha layers. I can add them here or start a new thread but I imagine the advice will be the same ...

Is there anything I can do to help with this or is this just something that requires a moment of inspiration on some future date?

I have found a few additional examples of converting assets to indexed that cause similar but slightly different corruption but what I'm hearing is "Stop doing that, it's broken and won't be fixed soon." Does that about sum it up?

The reason I did not report just -colors 255 as the bug was because changing the resize/extent made the image properly (though kinda ugly) appear again. It seemed a useful place to start a diagnostic process but it looks like we're narrowing down the cause regardless.

I think the thing that confuses me the most and indicates that this is a bug is that the result is not consistent (I think alpha or not is a red herring). Just changing how big the extents are shouldn't lead to the kinds of corruption that this appears to cause. http://insidesystems.net/images ...

$ convert -version Version: ImageMagick 6.7.1-0 2011-08-03 Q16 http://www.imagemagick.org Copyright: Copyright (C) 1999-2011 ImageMagick Studio LLC Features: OpenMP $ uname -a Darwin Mactop.local 11.0.0 Darwin Kernel Version 11.0.0: Sat Jun 18 12:56:35 PDT 2011; root:xnu-1699.22.73~1/RELEASE_X86_64 ...