[MPlayer-users] Re: Re: Re: tv:// Errors with DC10+ and playback on monitor

[Phil Bertram]

RC wrote:

> On Mon, 23 Oct 2006 17:41:59 +1300
> Phil Bertram <phil.bertram at clear.net.nz> wrote:
> 
>> mplayer tv:// -tv driver=v4l:outfmt=yuy2:width=300:height=200 I get
>> playback. However when I increase my size dimensions any further the
>> errors return.
> 
> 300 and 200 aren't exactly standard dimentions.  Try even multiples of
> 16:  320x240 for example.

Unfortunately the same errors occur with 320x240.
> 
> And does it work with v4l2 as well?

No. The errors are the same using v4l2 as they were in the begining 
i.e mplayer tv:// -tv driver=v4l2:outfmt=yuy2:width=320:height=240
v4l shows the most promise.

Gives .........

[snip]
Selected device: DC10plus[0]
 Capabilites:  video capture  video output  video overlay  streaming
 supported norms: 0 = PAL; 1 = NTSC; 2 = SECAM; 3 = Autodetect;
 inputs: 0 = Composite; 1 = S-Video; 2 = Internal/comp;
 Current input: 1
 Format RGB555 (16 bits, 15-bit RGB): BGR 15-bit
 Format RGB565 (16 bits, 16-bit RGB): BGR 16-bit
 Format BGR24  (24 bits, 24-bit RGB): BGR 24-bit
 Format BGR32  (32 bits, 32-bit RGB): BGRA
 Format YUYV   (16 bits, 4:2:2, packed, YUYV): Packed YUY2
 Format unknown (0x47504a4d) ( 0 bits, Hardware-encoded Motion-JPEG):
Unknown
 Current format: YUYV
v4l2: ioctl set format failed: Invalid argument
v4l2: ioctl set mute failed: Invalid argument
v4l2: 0 frames successfully processed, 0 frames dropped.
v4l2: up to 0 video frames buffered.


> You've certainly got some strange problem there...
You are right.