[MPlayer-users] [PATCH] reworked video capture - testers needed

[Jukka Tastula]

On Sunday 11 August 2002 11:13, Jindrich Makovicka wrote:

> Things you could especially test are 1) trying various colorspaces
> (RGB15|16|24|32, YV12, YUY2, I420) - just to verify that they give the
> correct colors, there's no point in capturing in RGB24 into DIVX -
> and 2) capturing a bit longer video (about 2 hours) to verify the a/v
> sync.

outfmt=rgb15 exits with 

ioctl set picture failed: Invalid argument

Hardware limitation? Doesn't matter much, not planning on using it anyway :)

rgb16, rgb24, rgb32, yv12 and yuy2 all get correct colors now, not red and 
blue swapped :)

i420 works too but requires -vc rawi420 for some reason, otherwise I get 

======= Win32 (VFW) VIDEO Codec init =======
MPlayer interrupted by signal 11 in module: init_video_codec 

which I find rather strange but I don't see a reason to use i420 anyway.

Running cvs xfree86 with G450 dualhead enabled and the second screen has
no xv support so I'm stuck with -vo x11 for it. Both screens are running at 
16bpp and outfmt=i420|yv12 get the best results (~130% zoomed to 1152x864) 
and amazingly outfmt=rgb16 gets the worst result of ~300% 

outfmt=yv12 tells me 
SwScaler: using unscaled Planar YV12 -> BGR 16-bit special converter

This I can understand because my display is at 16bpp

but outfmt=rgb16 tells me
SwScaler: BICUBIC scaler, from BGR 16-bit to Planar YV12 using MMX2

This I don't. Why would I ever want to get the already 16bit video into yv12? 
It'd need to be converted again somewhere to actually get displayed right. 
Right?

And what is wrong with the deinterlacers other than lb? I get some frames a 
bit too blue, some a bit too green and some a bit too red. Looks really 
annoying. Known problem? Same effect with vertical resolution 288 or lower.
Using bttv driver 0.8.44, 0.7.94.

Anyway, great improvement, now its actually watchable fullscreen :)