Re: [Gimp-developer] xwd screen shot problems
it seems you are mistaken. What makes you think xwd can't capture TrueColor? How are you using the term 24-bit visuals here (24 bit color-depth or 24 bit aligned pixels) ? xwd: Warning. Error in XWD-color-structure (flag) xwd: EOF encountered on reading xwd: load_image (xwd): XWD-file /root/.gimp/tmp/gimp_temp.277523.xwd has format 2, depth 24 and bits per pixel 24. Currently this is not supported. This message was generated attempting to capture glxgears using Gimp (xwd). What do you suppose it means? Capturing motion video windows is really flakey with xwd. Usually it fails, but sometimes it doesn't. It seems to be influenced by what other windows are being displayed. Sven and GSR, any further thoughts? Cheers, Robin ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: current gimp status and a patch for apply_lens.
Hi, David Odin [EMAIL PROTECTED] writes: I'm using current HEAD cvs of the Gimp. I've seen that all the filter plugins which use a GTK interface are crashing. Is this a known bug and is this due to the switch to the version 2.0 of gtk+? Is there anything I can do to help fixing this? yes, clean up your gimp installation. You obviously have old plug-ins installed. I've notice that plugins use gtk_signal* fonctions while the gimp application (under the app directory) use g_signal* ones. This lets me think the plugins are not yet converted to use gtk+-2.0. those that are in the current Makefiles should work. The gtk_signal_* functions are still OK, we just decided to totally switch to g_signal_* in the core to avoid to gtk_signal_connect() to a GObject. The GUI code in the plug-ins can continue to use gtk_signal_connect(). To be more precise, here are the plugins I've seen crashed on invocation : - destripe, - NL filter, - gflare, - gimpressionist, - gfig, - gdyntext, - imagemap, - jpeg. I haven't checked them all, but I think they have not yet been converted. This means they won't get installed and you are calling old executable. I'll look into your patch later... Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Solaris 64bit compile
Hi, My question is, am I expecting too much from 64 bit? Does the C code actually have to change to get the benefit from 64 bit? Is this Sorry, youre expecting too much for an application like The GIMP to benefit from 64 bit. I'd say look for pure CPU speed and memory bandwidth, or SIMD/vector instructions if the code is optimized for it. 64 bit gives most for applications that handle giant amounts of data or very high precision. Jens ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: xwd screen shot problems
[EMAIL PROTECTED] (2001-08-27 at 0021.59 -0700): xwd: Warning. Error in XWD-color-structure (flag) xwd: EOF encountered on reading xwd: load_image (xwd): XWD-file /root/.gimp/tmp/gimp_temp.277523.xwd has format 2, depth 24 and bits per pixel 24. Currently this is not supported. This message was generated attempting to capture glxgears using Gimp (xwd). I used my script to capture it, it worked, but gears lost speed for 10 secs (first message always gives low speed, then it goes up, when I used the script, I lost like 30% for two messages, then back to full speed, each message cover 5 secs). What do you suppose it means? Reading problems, as Sven says. My script uses xwdtopnm as first step of conversion. Capturing motion video windows is really flakey with xwd. Usually it fails, but sometimes it doesn't. It seems to be influenced by what other windows are being displayed. I tried video, and I got a blue image... fun. I run with depth 24 and fbbpp 32, so I guess this has something to do about it, cos when moving the video window, I get blue areas (I am still discovering the nice and bad things of the new driver for my card). GSR ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: current gimp status and a patch for apply_lens.
David Odin [EMAIL PROTECTED] writes: On Sun, Aug 26, 2001 at 08:38:57PM +0200, David Odin wrote: Hi, I'm using current HEAD cvs of the Gimp. I've seen that all the filter plugins which use a GTK interface are crashing. Is this a known bug and is this due to the switch to the version 2.0 of gtk+? Is there anything I can do to help fixing this? I've notice that plugins use gtk_signal* fonctions while the gimp application (under the app directory) use g_signal* ones. This lets me think the plugins are not yet converted to use gtk+-2.0. If you can tell me what need to be changed for the migration, I'll be happy to fix all these plugins. To be more precise, here are the plugins I've seen crashed on invocation : - destripe, - NL filter, - gflare, - gimpressionist, - gfig, - gdyntext, - imagemap, - jpeg. Hi David, all the plug-ins you mention are currently excluded from CVS HEAD build because we didn't get around fixing them (mostly GtkText - GtkTextView migration needed). Seems you have old 1.2 plug-in binaries hanging around which badly crash... The ongoing presence og gtk_signal_foo() stuff in the plug-ins is however perfectly ok, since gtk 2.0 offers wrappers around the new GLib signal stuff. We will do some kind of perl mass processing of the plug-ins at some point to remove this Gtk 1.2 compat cruft. Any yes, patches to make them compile again are welcome :-) ciao, --Mitch ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: xwd screen shot problems
Guillermo S. Romero / Familia Romero wrote: I tried video, and I got a blue image... fun. I run with depth 24 and fbbpp 32, so I guess this has something to do about it, cos when moving the video window, I get blue areas (I am still discovering the nice and bad things of the new driver for my card). A modern video card includes hardware optimised for playing back YUV video data such as Motion JPEG, MPEG, MPEG2 etc. Rather than doing YUV - RGB - framebuffer in software these cards contain additional buffers and logic for displaying YUV data as chroma-keyed overlay onto the real RGB framebuffer. In X11 this is expressed through the Xv video port extension to the X11 protocol, in Windows there is an equivalent mechanism presumably. You draw a window in the chromakey color (often ~ #fe which is blue) and the video card paints your YUV data into the blue space! This has two visible effects 1. Video runs faster and more smoothly even on slower hardware 2. The video data is not in the framebuffer, so you can't screenshot it, and will see weird artifacts if you drag the video window too quickly This is perfectly normal. If you don't like it it's possible to disable the support for this feature on some hardware, but IMHO you don't know what you're missing :) So long as you only use Free Software you need not fear losing the ability to get frames out of movies, because the YUV data can be captured and re-processed to make a screenshot after the fact :) Nick. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: current gimp status and a patch for apply_lens.
On Mon, Aug 27, 2001 at 11:42:20AM +0200, Michael Natterer wrote: David Odin [EMAIL PROTECTED] writes: On Sun, Aug 26, 2001 at 08:38:57PM +0200, David Odin wrote: Hi, I'm using current HEAD cvs of the Gimp. I've seen that all the filter plugins which use a GTK interface are crashing. Is this a known bug and is this due to the switch to the version 2.0 of gtk+? Is there anything I can do to help fixing this? I've notice that plugins use gtk_signal* fonctions while the gimp application (under the app directory) use g_signal* ones. This lets me think the plugins are not yet converted to use gtk+-2.0. If you can tell me what need to be changed for the migration, I'll be happy to fix all these plugins. To be more precise, here are the plugins I've seen crashed on invocation : - destripe, - NL filter, - gflare, - gimpressionist, - gfig, - gdyntext, - imagemap, - jpeg. Hi David, all the plug-ins you mention are currently excluded from CVS HEAD build because we didn't get around fixing them (mostly GtkText - GtkTextView migration needed). Seems you have old 1.2 plug-in binaries hanging around which badly crash... Oops! You are right (Sven also is right). In fact, these were old 1.3 plugins (from the early stage of the 1.3 branch...) The ongoing presence of gtk_signal_foo() stuff in the plug-ins is however perfectly ok, since gtk 2.0 offers wrappers around the new GLib signal stuff. We will do some kind of perl mass processing of the plug-ins at some point to remove this Gtk 1.2 compat cruft. Ok. So we should let perl do this stuff. Any yes, patches to make them compile again are welcome :-) Well, at least to make the jpeg plugins to compile (and works!) again, I just had to remove the '#' in front of its definition in plugin-defs.pl. Did I miss something important? Regards, DindinX -- [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
