Legacy ImageMagick Discussions Archive

I'd like to thank everyone for humoring me. My impatience as well as my assumptions about a library I know very little about, got the best of me. Your responses have been very informative. I basically threw everything out and started over again based on your feedback. This did exactly as I expected ...

By all means, stick your nose in. :) I think the part I was missing is Q32 does not mean single precision float. It means uint32_t. Or is that wrong as well? Admittedly, I was being a 'bit' presumptuous in my original post. Pun intended. I have textures comprised of signed floating point values that ...

Ok. Maybe I should start a new thread. My main concern is Q32 because of what I'm seeing in the results of some simple pixel arithmetic. HDRI is secondary only in that I have other applications that link to IM and require HDRI enabled. If I trying something like this in my current setup (HDRI/Q16 ...

Thanks for such a quick reply. I guess I'm confused though about what building imagemagick with a fixed quantum depth of 16 means. I'm a 3D artist and work with floating point and 16-bit UINT displacement maps (height field maps essentially) and sometimes I need to convert 32-bit files to 16-bit by ...

I would like HDRI support AND 32-bit quantum depth. Is this not possible at this time? The configure script is hard-wired to force Q16 when HDRI is enabled.