Hi,
Stephen J Baker [EMAIL PROTECTED] writes:
So, I was pointing out that floating point imagery is soon going to
be important to many other user communities outside of the film industry
and it follows that floating point images ought to be loadable, editable
and save-able from within
On 10-Dec-2002, Sven Neumann wrote:
the plan is not to have 16 bit or 32 bit or floats but to offer a
framework that allows to handle image data more or less independently
of its representation. GEGL is the framework and it already supports
floating point, 8bit and 16bit integer. Adding more
On Fri, 29 Nov 2002, Sam Richards wrote:
I would like to stress that some of the film-industry interest in
filmgimp is as much for the floating point as the 16 bit. The need for
floating point is for High Dynamic Range imagery which is used as a
lighting tool, and not for final delivery. So
On 09-Dec-2002, Stephen J Baker wrote:
On Fri, 29 Nov 2002, Sam Richards wrote:
I would like to stress that some of the film-industry interest in
filmgimp is as much for the floating point as the 16 bit. The need for
floating point is for High Dynamic Range imagery which is used as a
On 09-Dec-2002, Stephen J Baker wrote:
I'm not suggesting that this would be useful to GIMP - but that other
developers who are working in 3D using modern rendering hardware will
soon need support for 32 bit floating point texture maps.
So, I was pointing out that floating point imagery is
Hi,
Sam Richards [EMAIL PROTECTED] writes:
I would like to know what the roadmap for gimp is after 1.4? When is
the merge for GEGL? Are you planning 16 bit support as a separate
thing to GEGL? Are there any design docs for 1.3? How much work was
it porting to GTK2.0?
This document is
Hi,
I am one of the developers of filmgimp, although really I am mostly
bug-fixing and packaging it at the moment. While I'm not going to
comment on accuracies of the web site, thats Robins area, but I would
like to address some of the other issues raised...
Firstly, like everybody else, I
