linux-uvc-devel Mailing List for linux-uvc (Page 352)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi all,

can anyone tell me where can I find this uvcview thing everyone keeps 
mentioning? google only pointed me to a microsoft program, I guess this 
must be something else...

TIA

br

Szo

how to subscribe ?

On Thursday 19 January 2006 15:36, Steven Coutts wrote:
> Ok, compiled the software and loaded the kernel module, everything seems to
> be recognised -:
>
> usb 1-6: USB disconnect, address 5
> usb 1-1: new high speed USB device using ehci_hcd and address 6
> usbvideo: Probing device 1
> Format MJPEG found
> Format Uncompressed found
> usbvideo: Found a Status endpoint (addr 87).
> usbvideo: Found UVC device (1.00)
> usbvideo: Scanning UVC chain: OT 5 <- Unit 4 <- Unit 3 <- Unit 2 <- IT 1
> usbvideo: Found a valid video chain (1 -> 5).
> usbvideo: UVC device initialized.
>
> However, uvcview doesn't work -:
> uvcview verion 0.1.3
> Video driver: x11
> A window manager is available
> video /dev/video0
> Unable to set format: 5.
>  Init v4L2 failed !! exit fatal
>
>
> Any ideas?

If I unplug the device then plug back in and try again I get a black video 
windows breifly then it fails -:

uvcview verion 0.1.3
Video driver: x11
A window manager is available
video /dev/video0
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  141 (XVideo)
  Minor opcode of failed request:  19 ()
  Serial number of failed request:  23
  Current serial number in output stream:  24

Regards

-- 
Steven Coutts B.Sc.(Hons) MBCS
sc...@bc...

PGP Public Key
<http://stevec.couttsnet.com/scoutts.asc>

On Thursday 19 January 2006 13:50, Steven Coutts wrote:
> Hello,
>
> Is the driver usable with a Quickcam Pro 5000 yet?
>
> Regards

Ok, compiled the software and loaded the kernel module, everything seems to be 
recognised -:

usb 1-6: USB disconnect, address 5
usb 1-1: new high speed USB device using ehci_hcd and address 6
usbvideo: Probing device 1
Format MJPEG found
Format Uncompressed found
usbvideo: Found a Status endpoint (addr 87).
usbvideo: Found UVC device (1.00)
usbvideo: Scanning UVC chain: OT 5 <- Unit 4 <- Unit 3 <- Unit 2 <- IT 1
usbvideo: Found a valid video chain (1 -> 5).
usbvideo: UVC device initialized.

However, uvcview doesn't work -:
uvcview verion 0.1.3
Video driver: x11
A window manager is available
video /dev/video0
Unable to set format: 5.
 Init v4L2 failed !! exit fatal

Any ideas?

-- 
Steven Coutts B.Sc.(Hons) MBCS
sc...@bc...

PGP Public Key
<http://stevec.couttsnet.com/scoutts.asc>

Hello,

Is the driver usable with a Quickcam Pro 5000 yet?

Regards

-- 
Steven Coutts B.Sc.(Hons) MBCS
sc...@bc...

PGP Public Key
<http://stevec.couttsnet.com/scoutts.asc>

Hi all,

Please find attached a patch to MythTV / MythPhone to
support MJPEG and UVC.  This patch should apply
cleanly against Myth SVN version 8626.

Some outstanding problems / concerns with this patch:

1) The webcam does not turn off when exiting out of
mythphone. This seems to be a problem with the
VIDIOC_STREAMOFF ioctl() and/or the munmap() functions
of the uvc driver...

2) There's a complete lack of testing for other camera
types besides the Logitech Quickcam Fusion.

Other than that, I'm really happy with how it works. 
:)

Hopefully I can get more people playing with this
patch, and sending me feedback / code.

UVC folks:  I would appreciate it if you could add
this patch to your collection.  Hopefully soon, I'll
be submitting it to the mythtv folks.  I want to wait
until my problems shutting down the webcam are solved
first...

Take care,
-- Nick

Le Lundi 16 Janvier 2006 22:31, Marc Dumontier a écrit :
> Hi,
>
> I was trying to see if my webcam would work with this driver (it's a
> quickcam for notebook deluxe)
>
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 004: ID 046d:08a9 Logitech, Inc.
> Bus 003 Device 001: ID 0000:0000
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
>
>
> I loaded up the driver,
>
> dmesg output:
>
> usbcore: registered new driver usbvideo
> USB Video Class driver (v0.1.0)
> usb 3-2: new full speed USB device using uhci_hcd and address 4
> usb 3-2: USB disconnect, address 4
> usb 3-2: new full speed USB device using uhci_hcd and address 5
>
>
> I don't have a /dev/video* file or anything
>
> where do i go from here to see if my camera works?
>
> thanks,
> Marc
Marc,
Your webcam is supported by the spca5xx driver 
Your chipset vimicro zc0302 sensor  Hv7131from Hynix is not UVC compliant.
look here
http://mxhaard.free.fr/spca5xx.html
regards
-- 
Michel Xhaard
http://mxhaard.free.fr

Hi,

I was trying to see if my webcam would work with this driver (it's a 
quickcam for notebook deluxe)

Bus 004 Device 001: ID 0000:0000
Bus 003 Device 004: ID 046d:08a9 Logitech, Inc.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

I loaded up the driver,

dmesg output:

usbcore: registered new driver usbvideo
USB Video Class driver (v0.1.0)
usb 3-2: new full speed USB device using uhci_hcd and address 4
usb 3-2: USB disconnect, address 4
usb 3-2: new full speed USB device using uhci_hcd and address 5

I don't have a /dev/video* file or anything

where do i go from here to see if my camera works?

thanks,
Marc

I have successfully used tvtime to view images from my webcam.
I was never able to do it while using the Fedora 4 2.6.14_1653 kernel.
I obtained a current kernel from kernel.org version 2.6.15. Customized it
for my hardware. I then recompiled tvtime, with your patch, and the
usbvideo drivers. 

The webcam images are now passed to tvime with only some problems
around the tv standard. Using pal works where ntsc does not. I have
only tried brightness, contrast settings so far, and they have worked.

James

--
James Spring

This might be worth checking, it has some v4l2 viewer, streamer and 
other soft.

http://www.linux-projects.org/modules/mydownloads/

Update
The driver works correctly wen I run the current
uvcview.

James W. Spring wrote:

> After starting tvtime --norm=NORM
> It starts sucessfully
> I then change to PAL and restart.
> It can see the camers for a second then it aborts.
>
> Restarting tvtime.
> Reading configuration from /etc/tvtime/tvtime.xml
> Reading configuration from /home/jwspring/.tvtime/tvtime.xml
> videoinput: Driver won't tell us its norm: Invalid argument
> videoinput: Can't get tuner info: Invalid argument
> videoinput: Driver won't tell us its norm: Invalid argument
> videoinput: Can't get tuner info: Invalid argument
>
>    Cannot allocate enough off-screen video memory.  This may be fixed by:
>
>      1. Closing or restarting large X applications.
>      2. Lowering the input width of tvtime (--inputwidth parameter).
>      3. Lowering your colour depth or highest configured resolution.
>      4. Increasing the amount of video memory in your X config file
>         (for example, if you are using the i810 XFree86 driver.)
>
>    See http://tvtime.net/ for more information.
>
> videoinput: Can't read frame. Error was: Invalid argument (0).
> videoinput: Can't read frame. Error was: Invalid argument (0).
> videoinput: Can't read frame. Error was: Invalid argument (0).
> videoinput: Can't read frame. Error was: Invalid argument (0).
>
>    Cannot allocate enough off-screen video memory.  This may be fixed by:
>
>      1. Closing or restarting large X applications.
>      2. Lowering the input width of tvtime (--inputwidth parameter).
>      3. Lowering your colour depth or highest configured resolution.
>      4. Increasing the amount of video memory in your X config file
>         (for example, if you are using the i810 XFree86 driver.)
>
>    See http://tvtime.net/ for more information.
>
> Thank you for using tvtime.
>
>

After starting tvtime --norm=NORM
It starts sucessfully
I then change to PAL and restart.
It can see the camers for a second then it aborts.

Restarting tvtime.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/jwspring/.tvtime/tvtime.xml
videoinput: Driver won't tell us its norm: Invalid argument
videoinput: Can't get tuner info: Invalid argument
videoinput: Driver won't tell us its norm: Invalid argument
videoinput: Can't get tuner info: Invalid argument

    Cannot allocate enough off-screen video memory.  This may be fixed by:

      1. Closing or restarting large X applications.
      2. Lowering the input width of tvtime (--inputwidth parameter).
      3. Lowering your colour depth or highest configured resolution.
      4. Increasing the amount of video memory in your X config file
         (for example, if you are using the i810 XFree86 driver.)

    See http://tvtime.net/ for more information.

videoinput: Can't read frame. Error was: Invalid argument (0).
videoinput: Can't read frame. Error was: Invalid argument (0).
videoinput: Can't read frame. Error was: Invalid argument (0).
videoinput: Can't read frame. Error was: Invalid argument (0).

    Cannot allocate enough off-screen video memory.  This may be fixed by:

      1. Closing or restarting large X applications.
      2. Lowering the input width of tvtime (--inputwidth parameter).
      3. Lowering your colour depth or highest configured resolution.
      4. Increasing the amount of video memory in your X config file
         (for example, if you are using the i810 XFree86 driver.)

    See http://tvtime.net/ for more information.

Thank you for using tvtime.

> I'm not able to understand what I can` do to with this error
> I have the latest version of your driver
> The test code does run and capture frames correctly.
>
> kernel 2.6.14-1.1653_FC4 on a labtop with integrated video
>
> Running tvtime 1.0.1.
> Reading configuration from /etc/tvtime/tvtime.xml
> Reading configuration from /home/jwspring/.tvtime/tvtime.xml
> videoinput: Driver won't tell us its norm: Invalid argument
> videoinput: Can't get tuner info: Invalid argument
>
>    Your capture card driver: usbvideo [/0000:00:1d.7/256]
>    does not support full size studio-quality images required by tvtime.
>    This is true for many low-quality webcams.  Please select a
>    different video device for tvtime to use with the command line
>    option --device.

Try to set the video standard to PAL (right-click on the tvtime window, select 
'Input configuration' and 'Television standard'). Please let me know if it 
helps.

Laurent Pinchart

I'm not able to understand what I can` do to with this error
I have the latest version of your driver
The test code does run and capture frames correctly.

kernel 2.6.14-1.1653_FC4 on a labtop with integrated video

Running tvtime 1.0.1.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/jwspring/.tvtime/tvtime.xml
videoinput: Driver won't tell us its norm: Invalid argument
videoinput: Can't get tuner info: Invalid argument

   Your capture card driver: usbvideo [/0000:00:1d.7/256]
   does not support full size studio-quality images required by tvtime.
   This is true for many low-quality webcams.  Please select a
   different video device for tvtime to use with the command line
   option --device.

James

> the attached patch fix mjpeg2jpeg.py to prevent file corruption when the
> input file has already the huffman table.

Thanks. Applied.

Laurent Pinchart

Hello,

the attached patch fix mjpeg2jpeg.py to prevent file corruption when the
input file has already the huffman table.

Have a nice day.

        Olivier
-- 
Olivier Bornet, IDIAP, CP 592, CH-1920 Martigny
http://www.idiap.ch/~bornet/
http://www.idiap.ch/~bornet/pgp/
PGP-key: 0xC53D9218

Hi Luc,

> I've removed some code from my project that extract Jpeg image from an Avi
> file. Feel free to adapt it. The code is in attachement and written in
> python. Just parse the jpeg chunck and if we didn't found the Huffman
> table, add it when writting the file.

Thanks for the code. I renamed the file to mjpeg2jpeg.py, modified it a bit, 
and commited it to svn at  
http://svn.berlios.de/svnroot/repos/linux-uvc/uvc-utils/trunk

Laurent Pinchart

Thanks!

With this program, I was able to confirm that my camera takes nice
pictures of me!

/Mikael

tis 2006-01-10 klockan 17:52 +0100 skrev Luc Saillard: 
> On Tue, Jan 10, 2006 at 05:21:08PM +0100, Mikael Nilsson wrote:
> > 
> > I'd prefer interpreted, so python would suit me...
> > 
> I've removed some code from my project that extract Jpeg image from an Avi
> file. Feel free to adapt it. The code is in attachement and written in
> python. Just parse the jpeg chunck and if we didn't found the Huffman table,
> add it when writting the file.
> 
> Luc
-- 
Plus ça change, plus c'est la même chose

On Tue, Jan 10, 2006 at 05:21:08PM +0100, Mikael Nilsson wrote:
> 
> I'd prefer interpreted, so python would suit me...
> 
I've removed some code from my project that extract Jpeg image from an Avi
file. Feel free to adapt it. The code is in attachement and written in
python. Just parse the jpeg chunck and if we didn't found the Huffman table,
add it when writting the file.

Luc

tis 2006-01-10 klockan 15:26 +0100 skrev Laurent Pinchart:
> The MJPEG files contains standard JPEG data without the Huffman tables, so you 
> won't be able to open them in your regular image tools. I posted a patch to 
> the video4linux mailing list some time ago to add MJPEG support to Qt (so 
> most Qt/KDE based applications will be able to open MJPEG images).
> 
> I will create a simple script to add the Huffman tables to an MJPEG image. 
> Should I write it in C or in Python ?

I'd prefer interpreted, so python would suit me...

> 
> > I have not gotten xawtv or tvtime to work (xawtv does not like my Xorg
> > server: XF86DGANoDirectVideoMode, and tvtime complains about not having
> > studio quality capture). Other tips on applications I should try?
> 
> tvtime should work with the patch I posted on the linux-uvc mailing list. Try 
> with PAL if NTSC doesn't work (the video standard is irrelevant, but tvtime 
> will use another resolution with PAL).

Will try again. It seems xawtv wants DGA, which is disabled in newer
nvidia drivers. with -nodga it at least launches, but I get 

ioctl: VIDIOC_G_STD(std=0x2a00060b7c58414 [PAL_G,PAL_I,PAL_Nc,?,SECAM_B,SECAM_G,SECAM_L,?ATSC_8_VSB,ATSC_16_VSB,(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)]): Ogiltigt argument
ioctl: VIDIOC_S_STD(std=0x0 []): Ogiltigt argument
no way to get: 384x288 32 bit TrueColor (LE: bgr-)
no way to get: 384x288 24 bit TrueColor (BE: rgb)

Ogiltigt argument = Illegal argument.

and I get no pic whatever I try. It that again because of the USB1
situation? Can I tell xawtv to use MJPEG somehow?

/Mikael

-- 
Plus ça change, plus c'est la même chose

Dne úterý 10 leden 2006 15:12 Laurent Pinchart napsal(a):
> Hi Libor,
>
> > i have logitech quickcam chat, is it uvc device?
>
> No, the device is not UVC compliant. You need the spca5xx driver available
it' a pity ;) i thought that all usb2 cameras will be uvc compliant (well 
manufactuer says it's usb2 device, when i connect it, it has only 12Mbits 
speed (port is ok, when i plug usb disk, it reports as usb2 device and has 
480Mbits speed))

> at http://mxhaard.free.fr/spca5xx.html
yes i know about this driver, i use it now, but image is not ... great , but 
is getting better in last release ;)

thanks for info

cu

libor

>
> Laurent Pinchart
>
> _______________________________________________
> Linux-uvc-devel mailing list
> Lin...@li...
> http://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Hi Mikael,

> I wanted to report a partial success with my new QuickCam Fusion.
[...]
> Anyway, trying the test program I get
>
> Device /dev/video0 opened: .
> Unable to set format: 22.

As you mention later, your laptop doesn't support USB 2.0, so uncompressed 
image formats are not available (YUYV). You must instead use the MJPEG 
format, as you found out by yourself.

> Trying instead using
>
>         fmt.fmt.pix.width = 640;
>         fmt.fmt.pix.height = 480;
>         fmt.fmt.pix.pixelformat = V4L2_PIX_FMT_MJPEG;
>
> it seems to work: it creates a number of files that "file *" tells me
> are JPEG files, but I cannot view them using regular image tools. Tips
> for checking them?

The MJPEG files contains standard JPEG data without the Huffman tables, so you 
won't be able to open them in your regular image tools. I posted a patch to 
the video4linux mailing list some time ago to add MJPEG support to Qt (so 
most Qt/KDE based applications will be able to open MJPEG images).

I will create a simple script to add the Huffman tables to an MJPEG image. 
Should I write it in C or in Python ?

> I have not gotten xawtv or tvtime to work (xawtv does not like my Xorg
> server: XF86DGANoDirectVideoMode, and tvtime complains about not having
> studio quality capture). Other tips on applications I should try?

tvtime should work with the patch I posted on the linux-uvc mailing list. Try 
with PAL if NTSC doesn't work (the video standard is irrelevant, but tvtime 
will use another resolution with PAL).

Laurent Pinchart

Hi Libor,

> i have logitech quickcam chat, is it uvc device?

No, the device is not UVC compliant. You need the spca5xx driver available at 
http://mxhaard.free.fr/spca5xx.html

Laurent Pinchart

hello,
i have logitech quickcam chat, is it uvc device?
I attached output of lsusb.

i tried (naivelly) to add

       /* Logitech Quickcam Chat */
        { .match_flags          = USB_DEVICE_ID_MATCH_DEVICE
                                | USB_DEVICE_ID_MATCH_INT_INFO,
          .idVendor             = 0x046d,
          .idProduct            = 0x092c,
          .bInterfaceClass      = USB_CLASS_VENDOR_SPEC,
          .bInterfaceSubClass   = 0,
          .bInterfaceProtocol   = 0 },

to list of ids, it finds camera (when .bInterfaceSubClass is 1, it doesn't 
load uvcvideo module on device connection) but dmesg contains

usb 3-1: new full speed USB device using uhci_hcd and address 18
usbvideo: Probing device 1
usbvideo: Found UVC device (0.00)
usbvideo: No valid video chain found.
usbvideo: UVC device initialized.
usbcore: registered new driver usbvideo

can i help somehow? (i'm not kernel hacker ;)

cu

libor

tis 2006-01-10 klockan 13:07 +0100 skrev Mikael Nilsson:
> Hi!
> 
> I wanted to report a partial success with my new QuickCam Fusion.
> 
> Bus 002 Device 002: ID 046d:08c1 Logitech, Inc.
> 
> I'm running Debian unstable, using kernel 2.6.15. 
> 
> Compilation works, the module is however installed
> in /lib/modules/2.6.15 and not /lib/modules/2.6.15-1-686 as it should,
> and it seems to be because Debian stores the EXTRAVERSION in
> $KSRC/.extraversion, and I don't really know a general way around it...

See:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345918

(short version: will probably be fixed in Debian soon)

Quick fix for debian users:

cd /usr/src/linux-headers-2.6.15-1-686   # or wherever...
cp .extraversion localversion

Done!

/Mikael
-- 
Plus ça change, plus c'est la même chose

2006	Jan (183)	Feb (152)	Mar (69)	Apr (65)	May (57)	Jun (38)	Jul (109)	Aug (77)	Sep (85)	Oct (72)	Nov (149)	Dec (68)
2007	Jan (183)	Feb (143)	Mar (84)	Apr (120)	May (109)	Jun (68)	Jul (88)	Aug (150)	Sep (124)	Oct (182)	Nov (131)	Dec (175)
2008	Jan (195)	Feb (260)	Mar (167)	Apr (150)	May (101)	Jun (129)	Jul (245)	Aug (64)	Sep (72)	Oct (75)	Nov (152)	Dec (135)
2009	Jan (72)	Feb (93)	Mar (107)	Apr (35)	May (59)	Jun (127)	Jul (91)	Aug (73)	Sep (79)	Oct (82)	Nov (84)	Dec (104)
2010	Jan (61)	Feb (44)	Mar (81)	Apr (74)	May (50)	Jun (58)	Jul (31)	Aug (66)	Sep (83)	Oct (68)	Nov (61)	Dec (23)
2011	Jan (88)	Feb (81)	Mar (101)	Apr (95)	May (21)	Jun (147)	Jul (56)	Aug (121)	Sep (66)	Oct (54)	Nov (119)	Dec (50)
2012	Jan (54)	Feb (67)	Mar (24)	Apr (72)	May (134)	Jun (64)	Jul (105)	Aug (50)	Sep (38)	Oct (38)	Nov (53)	Dec (43)
2013	Jan (69)	Feb (15)	Mar (25)	Apr (14)	May (10)	Jun (13)	Jul (31)	Aug (30)	Sep (44)	Oct (12)	Nov (29)	Dec (19)
2014	Jan (18)	Feb (42)	Mar (25)	Apr (11)	May (20)	Jun (15)	Jul (2)	Aug (3)	Sep (10)	Oct (22)	Nov (27)	Dec (18)
2015	Jan (19)	Feb (17)	Mar (12)	Apr (10)	May (12)	Jun (22)	Jul (7)	Aug (12)	Sep (2)	Oct (16)	Nov (3)	Dec (30)
2016	Jan (19)	Feb (10)	Mar (20)	Apr (2)	May (3)	Jun (3)	Jul (4)	Aug (5)	Sep (14)	Oct (1)	Nov (7)	Dec (19)
2017	Jan (4)	Feb (4)	Mar (5)	Apr (3)	May (1)	Jun (8)	Jul (4)	Aug (7)	Sep	Oct (4)	Nov (7)	Dec (2)
2018	Jan (11)	Feb (5)	Mar (4)	Apr (6)	May (6)	Jun (4)	Jul (6)	Aug (2)	Sep (3)	Oct (6)	Nov	Dec (2)
2019	Jan (2)	Feb (10)	Mar (6)	Apr	May (6)	Jun (6)	Jul (2)	Aug (4)	Sep (2)	Oct (11)	Nov (1)	Dec (1)
2020	Jan (4)	Feb (1)	Mar (5)	Apr (19)	May (18)	Jun (5)	Jul (13)	Aug (12)	Sep (7)	Oct (4)	Nov	Dec (1)
2021	Jan	Feb (2)	Mar (2)	Apr (1)	May (3)	Jun (2)	Jul	Aug	Sep	Oct (3)	Nov (12)	Dec (1)
2022	Jan (2)	Feb (2)	Mar (6)	Apr (1)	May	Jun (1)	Jul (1)	Aug	Sep	Oct	Nov	Dec
2023	Jan	Feb (1)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2024	Jan	Feb (1)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

linux-uvc-devel Mailing List for linux-uvc (Page 352)

Linux UVC driver and tools

linux-uvc-devel — Linux UVC development