On Tue, 2007-05-22 at 22:44 -0600, Richard wrote:
In article <000f01c79cf1$65f0cdc0$1402a8c0@eyx2>, "Edwin Young" <edwin@bathysphere.org> writes:
While you're at it, why not just go straight to 16-bit or floating-point?
Because that's a far more invasive change to the code.
I can imagine. Like I said, it's just a thought. Maybe you could create a color_t typedef or something to make it easier down the line.
Currently the DAC is always passed around as an array of 256 entries of 3 bytes each. However, there is fudging around with the actual values that restricts them to the range 0-63 instead of 0-255. I never quite realize that fractint cheaped out on the 256 color colormap in this way until I started digging in the code.
I noticed this when parsing the color strings in .par files, which have the same issue.
Do you have a URL for the specification of OpenEXR? I've never heard of it before.
http://www.openexr.com/documentation.html To be honest, actually outputting fractals to that is almost certainly overkill and useful only for bragging rights. The only fractal-related program I know which supports it is Fyre (http://fyre.navi.cx/).