Floats (was Re: [Gimp-developer] Dreamworks, etc.)
On Fri, Nov 01, 2002 at 06:35:10PM +0100, Guillermo S. Romero / Familia Romero wrote:
some places use 32 bit float
This probably ought to be on our horizon too. Modern FPUs are very fast
and RAM gets ever cheaper. Are there any concrete advantages (other than
the 50% saving on storage) for 16-bit integers vs 32-bit float? We can't
actually /display/ either of these things on conventional hardware so
there's no difference there.
Naive tests suggest that floats are significantly faster for a compositor
or similar code { i.e. R' = R * (1-a) + r * a } on commodity x86 CPUs.
Has anyone with better profiling knowledge than me tried this kind of
thing inside an actual working image app ?
Nick.
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] linux-graphics-dev
On Sat, Nov 02, 2002 at 06:28:11AM +, Tor Lillqvist wrote: Does GIMP use the X clipboard at all, BTW? I think the Windows version uses its internal clipboard, at least (which is quite annoying :-) For text or images? Annoying that it does, or doesn't? It uses the Windows clipboard for text when you use the normal Control-C, V and X keys. Would you prefer it not to? For images. It's very annoying at times that it doesn't... (The problem is a lot bigger under Windows than on Linux, since I don't normally cut-and-paste image data into other programs on Linux.) Images have to be copied to/from the clipboard using the Edit:Copy to Clipboard and Paste from Clipboard menu entries. (Which you can of course bind to keyboard shotcuts if you like.) Hmm, very useful. Thanks. I was only aware of the Import - From clipboard menu entry. :-) /* Steinar */ -- Homepage: http://www.sesse.net/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Floats (was Re: [Gimp-developer] Dreamworks, etc.)
Hi, Nick Lamb [EMAIL PROTECTED] writes: On Fri, Nov 01, 2002 at 06:35:10PM +0100, Guillermo S. Romero / Familia Romero wrote: some places use 32 bit float This probably ought to be on our horizon too. Modern FPUs are very fast and RAM gets ever cheaper. Are there any concrete advantages (other than the 50% saving on storage) for 16-bit integers vs 32-bit float? We can't actually /display/ either of these things on conventional hardware so there's no difference there. that's why GEGL supported floats from the very beginning. Looking at the current code in CVS I see: gegl-color-model-gray-u16.h gegl-color-model-gray-u8.h gegl-color-model-gray.h gegl-color-model-rgb-float.h gegl-color-model-rgb-u16.h gegl-color-model-rgb-u8.h gegl-color-model-rgb.h Looks like something to start with. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: Floats (was Re: [Gimp-developer] Dreamworks, etc.)
On Sat, Nov 02, 2002 at 08:16:37AM +, Nick Lamb [EMAIL PROTECTED] wrote: This probably ought to be on our horizon too. Modern FPUs are very fast and RAM gets ever cheaper. And caches get slower... and RAM is _slow_. I don't say not to also support float, I just wanted to point out that performance is very much dependent on cache optimizations, as every fortran programmer knows ;) the 50% saving on storage) for 16-bit integers vs 32-bit float? We can't actually /display/ either of these things on conventional hardware so there's no difference there. I think that we very well can display 16 bits or higher, after all, we can have 16 bit linear and output 8 bit gamma-corrected. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] OS/2 compatibility
Is OS/2 compatibility (via #ifdef __EMX__) still a desired goal? -- Robert Krawitz [EMAIL PROTECTED] Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net Linux doesn't dictate how I work, I dictate how Linux works. --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] OS/2 compatibility
Hi, Robert L Krawitz [EMAIL PROTECTED] writes: Is OS/2 compatibility (via #ifdef __EMX__) still a desired goal? a good question that also came to Mitchs' and my mind up lately when working on GIMP code. Does it work at all? Do we have OS/2 users? Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] OS/2 compatibility
From: Sven Neumann [EMAIL PROTECTED] Date: 02 Nov 2002 18:10:46 +0100 Hi, Robert L Krawitz [EMAIL PROTECTED] writes: Is OS/2 compatibility (via #ifdef __EMX__) still a desired goal? a good question that also came to Mitchs' and my mind up lately when working on GIMP code. Does it work at all? Do we have OS/2 users? I suspect that the print plugin is broken. I've been doing some cleanup on the print plugin, and there's some code that just looks wrong. I'd rather get rid of it. -- Robert Krawitz [EMAIL PROTECTED] Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gimp Print --http://gimp-print.sourceforge.net Linux doesn't dictate how I work, I dictate how Linux works. --Eric Crampton ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
