On Thu, Jan 10, 2013 at 11:53 PM, Nicolas Robidoux
wrote:
> I replied privately that VIPS/NIP2 and ImageMagick talks probably would be
> more appropriate, providing contacts.
For GIMP itself it makes sense to present now, given that it is
gaining the needed numeric fidelity. April might however b
On Saturday, January 12, 2013, 22:32:15, pavel wrote:
> The idea about creating my own installer came from some forums where
> I've got an impression that there is no 64bit version of Gimp for
> Windows at the moment, or is unstable or buggy. Then I realized that
> there is something, so I will po
Hi Sven,
thank you for your e-mail. I'll not go back to previous paragraphs and
try to explain something here.
The idea about creating my own installer came from some forums where
I've got an impression that there is no 64bit version of Gimp for
Windows at the moment, or is unstable or buggy. The
Hi Sven,
thank you for your e-mail. I'll not go back to previous paragraphs and
try to explain something here.
The idea about creating my own installer came from some forums where
I've got an impression that there is no 64bit version of Gimp for
Windows at the moment, or is unstable or buggy. The
On Sat, Jan 12, 2013 at 4:43 PM, Elle Stone wrote:
> The fits format supports 32- and 64-bit integer and floating point;
As Mitch said, the newly ported FITS loader is a straightforward port
of the legacy plug-in, it only deals with 8bit data, not 16, 32 and
64bit integers or floats. Someone woul
On Sat, Jan 12, 2013 at 4:43 PM, Elle Stone wrote:
> Is the Gimp/babl 16-bit floating point the same as OpenExr 16-bit
> floating point? Is there a Gimp OpenExr plugin?
There's a plug-in that uses GEGL loaders and savers fir multiple file formats.
http://git.gnome.org/browse/gimp/tree/plug-ins/c
On 11/29/12, Øyvind Kolås wrote:
> On Fri, Nov 30, 2012 at 7:28 AM, Elle Stone wrote:
>> So gathering the gist of this discussion, it would be useful to add
>> the code for 16-bit floating point and 32-bit integer to the lcms
>> plug-in?
>>
>> And presumably if/when the lcms.c plug-in disappears,
