$ 0 0 I can confirm this is a bug in ImageMagick and it will be fixed in the next release of Magick.NET.