Hi Doug,
I just tried your patch with my Logitech 9000, and it crashes with
a segmentation fault, trying 800x600 resolution (MPEG4, large).
Output from vic is:
V4L: trying /dev/video0... ok, UVC Camera (046d:0990)
V4L: color; size: 48x32 => 960x720
V4L: ports:ioctl VIDIOCGCHAN: Invalid argument
V4L: depth=16, palette=yuyv422
V4L: ==> format { 411 422 cif } size { small large cif } port { } type
{auto pal ntsc secam}
Attached to V4L device: V4L-UVC Camera (046d:0990) /dev/video0
V4L2: trying /dev/video0... V4L2: ports: Camera 1:
V4L2: norms:
V4L2: ==> format { 411 422 cif } size { small large cif } port
{ Camera-1 } type { }
Attached to V4L2 device: V4L2-UVC Camera (046d:0990) /dev/video0
Device capture V4L2_PIX_FMT_YUYV (YUV 4:2:2)
Device capture V4L2_PIX_FMT_MJPEG
V4L2: fps 30
V4L2: start
V4L2: format cifdecimate: 1
V4L2: setting input port to 0
V4L2: failed to set format! requested 704x576, got 800x600
V4L2: falling back to resolution 800x600
V4L2: format cifdecimate: 0
V4L2: setting input port to 0
V4L2: setting format: width=800 height=600
V4L2: mmap()'ed buffer at 0x705ba000 (960000 bytes)
V4L2: mmap()'ed buffer at 0x704cf000 (960000 bytes)
Segmentation fault
A Logitech 5000 camera, which has a maximum resolution of 640x480,
works fine.
The segmentation fault could be caused by the MPEG4 encoder not being
able to handle resolutions where width and height are not divisible
by 16.
I modified my patch to use 960x720 with the Logitech 9000, and it
works. I changed it to use 800x600, and it segfaults.
Please let me know if I can get you more info.
Regards,
Claus.
On Mon, 2008-07-14 at 20:26 +1000, Douglas Kosovic wrote:
> Hi,
>
> I've SVN checked-in a variation of Claus's grabber-v4l2.cpp patch for VIC.
>
> New SVN snapshot VIC RPMs for RHEL/CentOS 5 and Fedora 8 & 9 are now
> available, just do a yum update. Let me know if you have any issues now with
> V4L2 and VIC.
>
> The V4L issue about not being able to open the device appears to be a bug in
> the bttv driver of later kernels.
>
>
> Cheers,
> Doug
>
> > Douglas Kosovic wrote:
> > Looks like vic's V4L2 'large' only works with 4:3 704x576 PAL input
> > sources, in the past the bttv driver would put a black border around a
> > 704x480 NTSC source, but now when vic requests it, it doesn't
> > succussed, vic's debug output:
> >
> > V4L2: failed to set format! requested 704x576, got 704x480
> >
> > I think I'll try and do a variation of Claus's patch (which doesn't
> > work with common UVC webcams that use 16:9 resolutions), so that it
> > selects the nearest working resolution to 704x576.
> >
> >
> > Cheers,
> > Doug
> >
> > > Claus Endres wrote:
> > >
> > > You might want to try the attached patch. It works for me for
> > > webcams with NTSC resolution.
> > >
> > > Please let me know if it solves your problem.
> > >
> > > Regards,
> > > Claus.
> > >
> > > Todd Zimmerman wrote:
> > > > Hey All,
> > > >
> > > > Not sure if it is a local configuration/driver issue or not, but I
> > am
> > > > having problems producing 'large' video sizes using my BTTV capture
> > > > card. It's a WinTV PCI card with a Sony handycam plugged into the
> > > > s-video input.
> > > >
> > > > I'm using vic-2.8ucl1.4.0beta
> > > >
> > > > Here are my settings::
> > > >
> > > > V4L2 (BT878), SVideo, NTSC, Mpeg4, Large. When I select
> > 'Transmit',
> > > > the stream 'info' still only indicates 352x288. If I change the
> > > > Signal to Auto (or PAL or SECAM) the picture goes green/pink but
> > the
> > > > resolution moves to 704x576.
> > > >
> > > > Is it _actually_ producing a larger video but the indication is
> > > > wrong, or is it not capable of going above 352x288??
> > > >
> > > > I'd test V4L, but for some reason vic indicates it cannot open the
> > > > device when trying to switch to v4l.
> > > >
> > > >
> > > > Any thoughts?
> > > >
> > > > Todd
