How to avoid penalty of Q16/HDRI while maintaining support?

[TheArcaneBrony]

Hi,

I was wondering how one would go about avoiding the penalty of using HDRI builds of Magick.NET, while still being able to support HDR/16 bit image inputs/outputs?

I've noticed that under some parameters, for example, resizing a short GIF can take minutes.
One solution I could do, is have a separate build of my application for each build of Magick.NET and somehow splitting load based on the input image, but that seems like a maintenance hazard to me? I'm not sure I see a benefit of using floating point operations on a gif, though.