[Gimp-developer] Re: xwd screen shot problems

2001-08-27 Thread Guillermo S. Romero / Familia Romero

[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: xwd screen shot problems

2001-08-27 Thread Nick Lamb

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: xwd screen shot problems

2001-08-26 Thread Guillermo S. Romero / Familia Romero

[EMAIL PROTECTED] (2001-08-25 at 2218.12 -0700):
 Hi. Unless I'm mistaken xwd isn't capable of capturing 24-bit visuals. It
 seems almost useless on modern hardware. Is this an issue that has been
 discussed here before?

OOh, well, then my computer does magic. ;]

 Attempting to capture graphics-intense windows with xwd on x86-based XFree86
 3.x or 4.x just gives a misleading error message, extra confusing because
 other simpler windows on the same desktop will capture without trouble.

xwd worked here in 3.x and is working with 4.0.3. Can you define
intense? Tried with browsers with a anim playing and a OpenGL app to
test. Do you mean video playback windows?

 The ImageMagic import utility works consistently and writes directly to png.
 Is there any thought to switching Gimp screen capture to use import?

IIRC, ImageMagick writes to what you put as name, so if you say
foo.jpg, it writes a jpeg, and if you do not specify, you get a miff.
And import, at least when I tried with 3.x, had a bug that raised
windows even if you do not wanted.

GSR
 
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer