Legacy ImageMagick Discussions Archive

I have one more question about the quantum:format=floating-point image attribute. Why isn't it always set when the source file is a floating point format? For example EXR images can contain it as well but it will never be set for them (I checked the source code and tried). Is this an oversight or an ...

This is mostly useful for Q16 HDRI builds where the storage type is float. By changing this you can then write 32bit float tiff files without issues. At least none that I found in my very limited testing.

In magick++/lib/image.cpp The depth method most likely incorrectly limits the max depth that can be set to MAGICKCORE_QUANTUM_DEPTH. Neither the c api or magic wand api does this. Likewise the Magick::Image::modulusDepth method doesn't limit it either. Most likely the correct solution is to remove ...

You forgot to recompile CORE_RL_magick_.dll (and possibly other files too) for the 6.9.0-4 windows binary release. The provided binaries are identical to 6.9.0-3 so the issue remains there.

I can confirm that it works when I compile my own version from source.

After a bit of pondering I remembered that you can easily get the name of the executable instead. You may want to change the line count=(ssize_t) GetModuleFileNameW(handle,wide_path,MaxTextExtent); to count=(ssize_t) GetModuleFileNameW(NULL,wide_path,MaxTextExtent); in the DllMain() call. This will ...

I agree. Not having the dllmain initialization enabled in the official binaries would also be an improvement.

If you use any of the ImageMagick dlls directly on windows (in my case through Magick++ but MagickWand will show the same issue) MagickCoreGenesis() will be called automatically in DllMain(). This is an issue for several reasons: 1. Since MagickCoreGenesis() is already called before any other code ...