from:"Martin"


Hello people,

First of all, happy new year to everyone reading this, since i'm new  
here :)
i have discovered the linux uvc project for a few days now, i have  
been looking for a good quality, supported webcam under linux, and i  
have to admit, the documentation lacks a lot...


So here is what i want to achieve:
We need a software which takes a snap of 5 connected webcams (The  
snapshots will then be used to make an accurate 3D mesh of the shooted  
object).


My first attempt was on Labtec webcam pro, which were working pretty  
well under linux with gpsa.
i have made a little application with C++ / Qt 4.3, which just calls  
vgrabbj on /dev/video* in a process. After the process ends, the  
pictures were retrieved and displayed...


The problem with this solution, was the resolution... 640x480 was not  
enough, the people told me that they need at least 1024x768.
So i have searched the internet, posted on forums, no one answered  
me... So i bought several QuickCam 9000.
Now, i'm trying to make them work the same way... And surprise: they  
can't work with my previous application, because vgrabbj can't handle  
the format in /dev/video*...


So i have looked at luvcview, and v4l also (i dont really understand  
what v4l has to do with everything here, i have never played with  
that). The result is, that i'm having several issues with both of them.


So my question is simple...
Is there any program, shell script, magic carot command which i can  
use to get a SIMPLE single shot on this device?


i'm on this project for a week now, i thought it would take a few  
hours to make... But the lack of doc / people on the net made me take  
a serious delay on the thing, so this request is kind of urgent...


Thanks a lot for your time, i hope that my request is clear. If not,  
feel free to tell me that my english is really bad, and you need some  
explaination about this or that :D


PS: Below is an email sent to the maintainer of luvcview, it is more  
precise about what i need to achieve... The email is in french.


Kind regards,
Pierre.


Bonjour,

Je m'appelle Pierre, et j'ai trouvé votre site en faisant des  
recherches à propos de ma problématique...
J'ai actuellement un projet en cours, et j'aimerais vous demander un  
petit coup de main (Ceci n'est pas une requête de support, si la  
partie descriptive vous embête, passez directement à la fin).


Voilà l'idée:
Je dois créer un petit soft (Je fais le dev sous macosx avec comme  
target linux) permettant de commander 5 webcams simultanément (donc  
branchées sur la même machine).
J'ai déja quelque chose de fonctionnel, basé sur du QT et des appels à  
vgrabbj... Cela fonctionne parfaitement avec des webcams labtec, mais  
il se trouve que les personnes me demandant cette application ont  
besoin d'obtenir des clichés de 1024x768 au minimum...


J'ai donc été chercher des Quickcam Pro 9000, webcam qui m'a semblé  
être une des seules disponibles et compatible linux, avec comme  
résolution du xga.


Une fois les drivers UVC compilés et installés, j'essaye mon appli, et  
là je me rend compte que vgrabbj n'a pas l'air de comprendre ce qu'il  
voit dans /dev/video0... Aucune erreur, mais une image verte en sortie.


Je m'orriente alors vers des recherches sur internet (Le sujet n'est  
vraiment pas assez documenté pour le grand public je trouve) et là je  
tombe donc sur votre application, luvcview.


LUVCView fonctionne environ une fois sur 3 quand je la lance à partir  
d'un xterm (sous XFCE). Les autres fois j'obtiens ceci:


luvcview version 0.2.1
Xlib: connection to :0.0 refused by server
Xlib: XDM authorization key matches an existing client!
Couldn't initialize SDL: Couldn't open X11 display

Quand l'application fonctionne, elle fonctionne bien, sauf au premier  
lancement où la palette semble brulée.


Si je liste les modes possibles, j'obtiens:

/dev/video0 does not support read i/o
{ pixelformat = 'MJPG', description = 'MJPEG' }
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 320, height = 240 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 352, height = 288 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 640, height = 480 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 800, height = 600 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 960, height = 720 }
Time interval between frame: 1/15, 1/10, 1/5,
{ pixelformat = 'YUYV', description = 'YUV 4:2:2 (YUYV)' }
{ discrete: width = 160, height = 120 }
Time interval between frame: 1/30, 1/25, 1/20, 1/15, 1/10, 1/5,
{ discrete: width = 176, height = 144 }
Time interval between frame: 1/30, 1/25, 1/20,

Re: [Linux-uvc-devel] Little questions about uvcvideos... And possible solutions to my problem.

Hello List,

Thomas:
i have just finished to compile the mjpg_streamer package, and i have  
started a testing session.
it seems to perfectly work, and most important: FIT WHAT I NEED :D
i will use curl or directly Qt to download the pictures.

But there is a little problem, i hope someone knows the what or the why:
The pictures shown are totally wrong on colors. i believe the palette  
is not correctly set, all seem red, dark areas are almost pure blue...

Anyway thanks a lot for all these directions, i am very happy with  
this solution, and i discovered this tool which i will probably use  
for other purposes later.

Kind regards,
Pierre.

P.S.: i really believe that the main digests of this mailing list  
should be formated with eye candy and placed in a well known website  
(understand: well known for end users without any technical knowledge  
at all), it took me days to find the list and the archive!

On 28 janv. 08, at 13:59, Tom St wrote:

 Perhaps you also just want to use the plugin as it is.
 It would just be necessary to write the right interface, but all you
 need is already in the shared object input_uvc.so. Its job is to  
 take
 snapshots and store those pictures in a global buffer. Images are
 already/converted-to in JPEG-format.
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Little questions about uvcvideos... And possible solutions to my problem.

Ok my misstake (Maybe?):
After unplugging and replugging the webcams, both pictures are GOOD :)

Thanks for this cool tool, i'll give feedback if i encounter issue for  
my personnal use.

Pierre.


On 28 janv. 08, at 14:24, Tom St wrote:

 Hi Pierre,
 But there is a little problem, i hope someone knows the what or the  
 why:
 The pictures shown are totally wrong on colors. i believe the palette
 is not correctly set, all seem red, dark areas are almost pure  
 blue...


 Can you verify this erroneous behaviour also with a browser like  
 firefox?

 Have you activated YUYV mode? This would capture YUYV images from the
 webcam and convert it using libjpeg. Surely this will increase your  
 CPU
 usage a lot. Perhaps you need to check out the current snapshot from
 subversion-repository, because i discovered issues with the buffer  
 sizes
 a few days ago.

 Regards,
 Tom


 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Little questions about uvcvideos... And possible solutions to my problem.


Hello Tom,

Here is the output of my listening MJPG Streamer:
./myStart.sh
MJPG Streamer Version.: 2.0
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1600 x 1200
 i: Frames Per Second.: 1
 i: Format: YUV
 i: JPEG Quality..: 100
 o: www-folder-path...: disabled
 o: HTTP TCP port.: 8080
 o: username:password.: disabled
 o: commands..: enabled

The mode is YUYV unless the -y switch doesnt work, but according to  
the console output, i think it's good.
You give me the advice to use the svn snap, but this is already what i  
have done... Revision was 54, am i good with this one?


The picture in firefox is wrong too.

Also i have tried the output_file plugin, and set up with the --folder  
thing after looking at the sources to know the parametters to use. But  
this output plugin gives a segmentation fault.


Also a fast question:
in the sources, i see a resolution table which only goes to 1280 x  
1024 (Which is SUFFICENT for me, no problem). Does it mean that the  
1600 x 1200 is software-side interpolated? What if i add UXGA 1600  
1200 in the table? :)


For now, i would be more than happy if the HTTP output plugin can give  
me real colors. Any clue for this please?


Thanks a lot for your support, for now you're the only person who  
provided me with a fast solution... So i place my hope in your  
knowledge now :D


Pierre.


On 28 janv. 08, at 14:24, Tom St wrote:


Hi Pierre,
But there is a little problem, i hope someone knows the what or the  
why:

The pictures shown are totally wrong on colors. i believe the palette
is not correctly set, all seem red, dark areas are almost pure  
blue...



Can you verify this erroneous behaviour also with a browser like  
firefox?


Have you activated YUYV mode? This would capture YUYV images from the
webcam and convert it using libjpeg. Surely this will increase your  
CPU

usage a lot. Perhaps you need to check out the current snapshot from
subversion-repository, because i discovered issues with the buffer  
sizes

a few days ago.

Regards,
Tom


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Little questions about uvcvideos... And possible solutions to my problem.


Ooops... #2

After starting two instances of the program, it appears that it works  
for the 2nd webcam (on port 8081)...

So the ugly colors are only on the 1st cam...

What can be causing this?

Pierre.

On 28 janv. 08, at 14:42, Pierre MARTIN wrote:


Hello Tom,

Here is the output of my listening MJPG Streamer:
./myStart.sh
MJPG Streamer Version.: 2.0
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1600 x 1200
 i: Frames Per Second.: 1
 i: Format: YUV
 i: JPEG Quality..: 100
 o: www-folder-path...: disabled
 o: HTTP TCP port.: 8080
 o: username:password.: disabled
 o: commands..: enabled

The mode is YUYV unless the -y switch doesnt work, but according to  
the console output, i think it's good.
You give me the advice to use the svn snap, but this is already what  
i have done... Revision was 54, am i good with this one?


The picture in firefox is wrong too.

Also i have tried the output_file plugin, and set up with the -- 
folder thing after looking at the sources to know the parametters to  
use. But this output plugin gives a segmentation fault.


Also a fast question:
in the sources, i see a resolution table which only goes to 1280 x  
1024 (Which is SUFFICENT for me, no problem). Does it mean that the  
1600 x 1200 is software-side interpolated? What if i add UXGA 1600  
1200 in the table? :)


For now, i would be more than happy if the HTTP output plugin can  
give me real colors. Any clue for this please?


Thanks a lot for your support, for now you're the only person who  
provided me with a fast solution... So i place my hope in your  
knowledge now :D


Pierre.


On 28 janv. 08, at 14:24, Tom St wrote:


Hi Pierre,
But there is a little problem, i hope someone knows the what or  
the why:
The pictures shown are totally wrong on colors. i believe the  
palette
is not correctly set, all seem red, dark areas are almost pure  
blue...



Can you verify this erroneous behaviour also with a browser like  
firefox?


Have you activated YUYV mode? This would capture YUYV images from the
webcam and convert it using libjpeg. Surely this will increase your  
CPU

usage a lot. Perhaps you need to check out the current snapshot from
subversion-repository, because i discovered issues with the buffer  
sizes

a few days ago.

Regards,
Tom


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel




___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] ekiga fails to open camera on second run

2007-12-08 Thread Martin Ebourne

Hi,

I have a Logitech Quickcam Pro for Notebooks (046d:0991) which works
with ekiga (3.0 svn) the first time I run it, but on subsequent runs
ekiga fails to open the camera and gives an error 'Your driver doesn't
seem to support any of the colour formats supported by Ekiga.'

If I unplug and reinsert the camera ekiga works again for one more run.
These are the messages when the camera is inserted:

usb 1-6: new high speed USB device using ehci_hcd and address 3
usb 1-6: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device unnamed (046d:0991)
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)

These errors appear when ekiga loads and the camera works:

uvcvideo: Failed to query (135) UVC control 2 (unit 2) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 7 (unit 2) : -110 (exp. 2).
uvcvideo: Failed to query (135) UVC control 3 (unit 2) : -110 (exp. 2).

These errors appear when it doesn't work:

uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).
uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -32 (exp. 26).
uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -32 (exp. 26).
uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -32 (exp. 26).

I've asked over in the ekiga list
http://mail.gnome.org/archives/ekiga-devel-list/2007-December/msg00029.html
and they think it is a linux-uvc bug.

I'm using r148 of linux-uvc and kernel-2.6.23.8-63.fc. I've also
attached a debug log from ekiga when it didn't work.

Cheers,

Martin.


fails.log.gz
Description: GNU Zip compressed data
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] ekiga hang cancelling druid

2007-12-08 Thread Martin Ebourne

When I run ekiga, open the configuration druid and then cancel it, most
times ekiga locks up.

I'm using r5776 and the backtrace is below.

Cheers,

Martin.

Program received signal SIGINT, Interrupt.
[Switching to Thread 46912516974944 (LWP 15824)]
0x00376160a8f9 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
(gdb) thread apply all bt

Thread 23 (Thread 1107339600 (LWP 15869)):
#0  0x0037606cddf2 in select () from /lib64/libc.so.6
#1  0x2ac4aec5 in PSocket::Select (read=value optimized out, 
write=value optimized out, except=value optimized out, 
[EMAIL PROTECTED]) at socket.cxx:319
#2  0x2ac5ec94 in PSocket::Select ([EMAIL PROTECTED], 
[EMAIL PROTECTED]) at ../common/sockets.cxx:1031
#3  0x2ac66077 in PMonitoredSockets::ReadFromSocket (this=0xd49450, 
[EMAIL PROTECTED], buf=0xf3d770, len=2000, [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED])
at ../../ptclib/psockbun.cxx:564
#4  0x2ac6638d in PSingleMonitoredSocket::ReadFromBundle (
this=0xd49450, buf=0xf3d770, len=2000, [EMAIL PROTECTED], [EMAIL 
PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED])
at ../../ptclib/psockbun.cxx:1084
#5  0x2b391d33 in OpalListenerUDP::Accept (this=0xcfd7d0, 
[EMAIL PROTECTED])
at /usr/src/debug/opal-3.1.0/src/opal/transports.cxx:757
#6  0x2b396e2c in OpalListener::ListenForConnections (this=0xcfd7d0, 
[EMAIL PROTECTED]) at /usr/src/debug/opal-3.1.0/src/opal/transports.cxx:416
#7  0x2ac55ba3 in PThread::PX_ThreadStart (arg=value optimized out)
at tlibthrd.cxx:804
---Type return to continue, or q return to quit---
#8  0x003761606407 in start_thread () from /lib64/libpthread.so.0
#9  0x0037606d4b0d in clone () from /lib64/libc.so.6
Current language:  auto; currently c

Thread 22 (Thread 1085827408 (LWP 15868)):
#0  0x0037606cddf2 in select () from /lib64/libc.so.6
#1  0x2ac59374 in PThread::PXBlockOnIO (this=0xcfdd10, handle=43, 
type=2, [EMAIL PROTECTED]) at tlibthrd.cxx:896
#2  0x2ac4cf0a in PChannel::PXSetIOBlock (this=0xcfd8a8, 
type=PChannel::PXAcceptBlock, [EMAIL PROTECTED]) at channel.cxx:119
#3  0x2ac48e6e in PSocket::os_accept (this=0xcf1470, 
[EMAIL PROTECTED], addr=0x40b85da0, size=0x40b85d9c) at socket.cxx:197
#4  0x2ac60860 in PTCPSocket::Accept (this=0xcf1470, [EMAIL PROTECTED])
at ../common/sockets.cxx:2231
#5  0x2b394ee1 in OpalListenerTCP::Accept (this=0xcfd850, 
timeout=value optimized out)
at /usr/src/debug/opal-3.1.0/src/opal/transports.cxx:661
#6  0x2b396e2c in OpalListener::ListenForConnections (this=0xcfd850, 
[EMAIL PROTECTED]) at /usr/src/debug/opal-3.1.0/src/opal/transports.cxx:416
#7  0x2ac55ba3 in PThread::PX_ThreadStart (arg=value optimized out)
at tlibthrd.cxx:804
#8  0x003761606407 in start_thread () from /lib64/libpthread.so.0
#9  0x0037606d4b0d in clone () from /lib64/libc.so.6

---Type return to continue, or q return to quit---
Thread 16 (Thread 1107605840 (LWP 15858)):
#0  0x0037606cddf2 in select () from /lib64/libc.so.6
#1  0x2ac56049 in PThread::Sleep ([EMAIL PROTECTED])
at tlibthrd.cxx:672
#2  0x004c58f9 in GMAccountsEndpoint::Main (this=0xd4ae00)
at endpoints/accountshandler.cpp:163
#3  0x2ac55ba3 in PThread::PX_ThreadStart (arg=value optimized out)
at tlibthrd.cxx:804
#4  0x003761606407 in start_thread () from /lib64/libpthread.so.0
#5  0x0037606d4b0d in clone () from /lib64/libc.so.6

Thread 14 (Thread 1107073360 (LWP 15856)):
#0  0x00376160ab7d in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib64/libpthread.so.0
#1  0x2ac55041 in PSyncPoint::Wait (this=0x2af0fa88, 
[EMAIL PROTECTED]) at tlibthrd.cxx:1434
#2  0x2ac66a7d in PInterfaceMonitor::UpdateThreadMain (
this=0x2af0fa00) at ../../ptclib/psockbun.cxx:236
#3  0x2ac55ba3 in PThread::PX_ThreadStart (arg=value optimized out)
at tlibthrd.cxx:804
#4  0x003761606407 in start_thread () from /lib64/libpthread.so.0
#5  0x0037606d4b0d in clone () from /lib64/libc.so.6
Current language:  auto; currently asm

---Type return to continue, or q return to quit---
Thread 12 (Thread 1074538832 (LWP 15854)):
#0  0x00376160cef4 in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x003761608915 in _L_lock_102 () from /lib64/libpthread.so.0
#2  0x003761608390 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x004ad84c in gnomemeeting_threads_enter () at gui/misc.cpp:65
#4  0x004b7731 in PVideoInputDevice_Picture::GetFrameDataNoDelay (
this=0xce2000, frame=0x2aaab571f010 '� repeats 200 times..., 
i=value optimized out) at devices/fakevideoinput.cpp:270
#5  0x004b7673 in PVideoInputDevice_Picture::GetFrameData (
this=0xce2000, a=0x2aaab571f010 '� repeats 200 times..., i=0x400c1f5c)
at devices

[Linux-uvc-devel] New QuickCam Team website for video developers

2007-10-11 Thread Martin Rubli

Dear all,

The Logitech video team is proud to present the new QuickCam Team website,  
a resource targeted at webcam developers for all platforms as well as  
power users of Logitech video hardware on popular operating systems and  
hardware platforms.

This new website contains documentation and links related to developing  
webcam software and using Logitech webcams on platforms like Linux,  
Solaris as well as others, answers to frequently asked questions, and a  
forum platform to discuss related topics. You can find it at the following  
address:

http://www.quickcamteam.net/

Contributions and comments are welcome. If you think that a particular  
section is missing or if you have something you would like to contribute,  
please drop us a note in the forum.

Note that the QuickCam Team website is not meant to be a replacement for  
the official customer support. However, you are welcome to post developer  
or Linux questions that may be out of the scope of ordinary customer  
support. Please also take a minute to read the introduction page  
(http://www.quickcamteam.net/about/) before visiting.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Which cameras really work with linux-uvc?

2007-10-03 Thread Martin Rubli

On Fri, 28 Sep 2007 15:49:35 +0800, Michel Xhaard [EMAIL PROTECTED] wrote:

 Martin,
 Can you change spca5xx on quickcamteam.net by gspca. spca5xx is now  
 deprecated and did not work for a lot of Logitech webcams
 Bests regards

Sure, I'll update it. But can you clarify a few things for me? On your  
compatibility list (http://mxhaard.free.fr/spca5xx.html) there are a few  
cameras that have spca5xx, others have gspcav1 or gspca v4l1/v4l2.

1. What's the difference between  gspcav1 and gspca v4l1/v4l2?

2. What is the status of the spca5xx driver? Is it obsolete and 100%  
replaced by gspca? Or are there certain devices for which people have to  
keep using spca5xx because gspca doesn't support them yet?

I'd like to explain those things on quickcamteam.net when I do the update.

Thanks!
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Control the status LED?

2007-09-27 Thread Martin Rubli

Jörg, Laurent,

On Thu, 27 Sep 2007 04:45:20 +0800, Laurent Pinchart  
[EMAIL PROTECTED] wrote:

 does the uvcvideo module export some controls that can be set via the  
 sysfs filesystem? I'm looking for a way to toggle the status LED on and  
 off. Or is this directly controlled my the hardware?

 My cam is the Logitech QuickCam Sphere MP.

 The LED is directly controlled by the hardware. There is no way to turn  
 it on or off from the computer.

What Laurent said is partially true, the LED is by default controlled by  
the hardware. However, there is a way of influencing the behavior of the  
LED. There is an extension unit control that allows to set the LED to  
states like On, Off, Blinking, and Auto. The latter one is just the  
default.

I'll try to write up the necessary information in a quick spec and then  
post it. I may take me a few days though before I'll get around to do it,  
so if you're in a hurry feel free to drop me a quick e-mail and I can give  
you some raw information.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Which cameras really work with linux-uvc?

2007-09-27 Thread Martin Rubli

On Tue, 25 Sep 2007 04:26:28 +0800, Laurent Pinchart  
[EMAIL PROTECTED] wrote:

 Hi Tom,

 On Monday 24 September 2007, Tom St wrote:
 Hello Listmembers, Hello Laurent,
 What about the idea to add another column to the list of supported
 devices, which shows some kind of ranking like:

 * works for most users (++),
 * some issues (+),
 * no issues reported (+++)?

 Would also be an idea to have such a list in the wiki and include hints
 for workarounds like initialize audio modules first, then load video
 modules for certain webcams.

 What do you  think?

 The boundary between works for most users and some issues is  
 difficult to
 define. I added a Status column to the supported devices list. The  
 device
 is either supported (green check mark) or supported with some issues the  
 user
 should be aware of (warning sign with footnote links).

 Please let me know what you think of this new supported devices list.

Good list! A few small comments:

1. The camera with VID/PID 046C/09B0 is based on the Sonix SN9C21x chip  
and isn't affected by the bugs. I think it deserves a green checkmark. :-)

2. Your list is missing some Logitech cameras. You may want to sync it  
with this one:
http://www.quickcamteam.net/hcl/linux/logitech-webcams

3. There's some information on the mentioned Logitech hardware bug here:
http://www.quickcamteam.net/documentation/faq/logitech-webcam-linux-usb-incompatibilities
Would you mind adding the link to footnote 1 in your device compatibility  
list?

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] invalid module format uvc

2007-08-25 Thread Martin

Am Thu, 2 Aug 2007 22:31:30 schrieb Laurent Pinchart:
 On Thursday 02 August 2007, helico unitemoyenne wrote:
  i am not sure that the problem is with mandriva.

I am not sure, too...

 I'm pretty sure I'm not adding 'custom' to '2.6.17-10mdv'. You should
 try to investigate with your kernel sources where this comes from. It
 seems to definitely be a build issue.

I'm sure, this is true, also.

Well, the Makefile uses `uname -r` as the kernel version. This should
be the current running one. Just to be sure do some...

$ cd /lib/modules/2.6.17-10mdv/build
$ make menuconfig

Please tell us, what is in General Setup --- Local version - append
to kernel release? Is there some custom around?

If not, what is `uname -r` in your case?

Hope to have given some useful hints...

Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Fwd: Orbicam - 046d:09b0 Logitech, Inc

2007-05-08 Thread Martin Rubli

Last time I checked Camorama was a V4L1-only application. Have you tried  
with luvcview? If you do, remember to use the -f yuv switch as your  
camera does not support the MJPEG format, which is luvcview's default.

I tested your Orbicam with both, the main trunk and the dynctrls branch,  
and both of them work fine. No crash, even when trying to launch Camorama.

Cheers,
Martin


On Mon, 07 May 2007 06:30:05 +0800, Domijor [EMAIL PROTECTED] wrote:

 Always I remove the old driver.
 # rm /lib/modules/2.6.18-4-686/usb/media/uvcvideo.ko

 Now show:

 # rmmod uvcvideo
 Show dmesg:  usbcore: deregistering driver uvcvideo

 # modprobe uvcvideo trace=255

 # dmesg | tail
 uvcvideo: Adding mapping Brightness to control
 ----0101/2.
 uvcvideo: Adding mapping Contrast to control
 ----0101/3.
 uvcvideo: Adding mapping Hue to control
 ----0101/6.
 uvcvideo: Adding mapping Saturation to control
 ----0101/7.
 uvcvideo: Adding mapping Sharpness to control
 ----0101/8.
 uvcvideo: Adding mapping Gamma to control
 ----0101/9.
 uvcvideo: Adding mapping Backlight Compensation to control
 ----0101/1.
 uvcvideo: Adding mapping Gain to control
 ----0101/4.
 uvcvideo: Adding mapping Power Line Frequency to control
 ----0101/5.
 uvcvideo: Adding mapping Hue, Auto to control
 ----0101/16.
 uvcvideo: Adding mapping Pan (relative) to control
 63610682-5070-49ab-b8cc-b3855e8d2256/1.
 uvcvideo: Adding mapping Tilt (relative) to control
 63610682-5070-49ab-b8cc-b3855e8d2256/1.
 uvcvideo: Adding mapping Pan/Tilt (reset) to control
 63610682-5070-49ab-b8cc-b3855e8d2256/2.
 uvcvideo: Adding mapping Exposure, Auto to control
 ----0001/2.
 uvcvideo: Adding mapping Exposure (Absolute) to control
 ----0001/4.
 uvcvideo: Adding mapping White Balance Temperature, Auto to control
 ----0101/11.
 uvcvideo: Adding mapping White Balance Temperature to control
 ----0101/10.
 uvcvideo: Probing generic UVC device 4
 uvcvideo: Found format Uncompressed.
 uvcvideo: - 640x480 (15.0 fps)
 uvcvideo: - 352x288 (30.0 fps)
 uvcvideo: - 320x240 (30.0 fps)
 uvcvideo: - 176x144 (30.0 fps)
 uvcvideo: - 160x120 ( 30.0 fps)
 uvcvideo: - 1280x960 (8.0 fps)
 uvcvideo: - 1280x1024 (8.0 fps)
 uvcvideo: Found a Status endpoint (addr 83).
 uvcvideo: Found UVC 1.00 device unnamed (046d:09b0)
 uvcvideo: Added control ----0101/2 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/3 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/7 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/8 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/9 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/1 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/4 to device  
 4
 entity 3
 uvcvideo: Added control ----0101/5 to device  
 4
 entity 3
 uvcvideo: Added control ----0001/2 to device  
 4
 entity 1
 uvcvideo: Added control ----0001/4 to device  
 4
 entity 1
 uvcvideo: Added control ----0101/11 to  
 device 4
 entity 3
 uvcvideo: Added control ----0101/10 to  
 device 4
 entity 3
 uvcvideo: Scanning UVC chain: OT 2 - Unit 3 (- 4 13 12 10) - IT 1
 uvcvideo: Found a valid video chain (1 - 2).
 uvcvideo: UVC device initialized.
 usbcore: registered new driver uvcvideo
 USB Video Class driver (v0.1.0)

 # lsmod | grep uvcvideo
 uvcvideo   37156  0
 compat_ioctl32  1472  1 uvcvideo
 videodev   21120  1 uvcvideo
 v4l1_compat12036  2 uvcvideo,videodev
 v4l2_common20448  2 uvcvideo,videodev
 usbcore   112644  5 uvcvideo,usbhid,ehci_hcd,uhci_hcd

 # ll /dev/vid*
 crw-rw 1 root video 81, 0 2007-05-06 22:46 /dev/video0

 # chmod a+r /dev/video0

 # ll /dev/vid*
 crw-rw-r-- 1 root video 81, 0 2007-05-06 22:46 /dev/video0

 $ camorama
 Windows error: Could not connect to video device (/dev/video0). Please  
 check
 connection

 # dmesg | tail
 uvcvideo: uvc_v4l2_open
 uvcvideo: uvc_v4l2_ioctl
 v4l1 ioctl VIDIOCGCAP, dir=r- (0x803c7601)
 v4l2 ioctl VIDIOC_QUERYCAP, dir=r- (0x80685600)
 v4l2 ioctl VIDIOC_ENUMINPUT, dir=rw (0xc04c561a)
 v4l2 ioctl VIDIOC_ENUMINPUT, dir=rw (0xc04c561a)
 v4l2 ioctl VIDIOC_ENUM_FMT, dir=rw (0xc0405602)
 v4l2 ioctl VIDIOC_TRY_FMT, dir=rw (0xc0cc5640)
 uvcvideo: Trying format 0x56595559 (YUYV): 1x1.
 uvcvideo: Using default frame

Re: [Linux-uvc-devel] (no subject)

2007-04-09 Thread Martin Rubli

On Tue, 27 Mar 2007 23:09:37 +0800, [EMAIL PROTECTED] wrote:

 is it possible to set some capture properties with modprobe while
 loading the driver ? Capture image size and framerate would be
 interesting for webcams. (quickcam pro 5k is able to capture at about  
 1200x900 which is not allways desired, especially in the field of real  
 time object
 recognition) The capturing takes about 41% of cpu power on an athlon 64  
 bit 3700+ processor which is quite a bit.

How do you get this high resolution? The camera only has a VGA sensor. I'm  
assuming you're using the Windows driver, which might allow for software  
upscaling. If so, did you measure the CPU usage on Windows or Linux?

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] How to reset Quickcam Fusion if it locks up (USB timing bug in hardware)?

2007-04-09 Thread Martin Rubli

On Fri, 06 Apr 2007 06:28:09 +0800, Ian Latter  
[EMAIL PROTECTED] wrote:


 Can I add one thought to the root cause;  I haven't seen
 this problem and I'm stuck on USB 1.1.  Since the problem
 is believed to have been traced back to a timing issue - is
 it possible that this is a USB 2.0 issue (as in, those seeing
 the problem are using USB 2.0, and could make the
 problem go away if they connected the same device to a
 hub, on the same PC, that forced the interface/speed down to
 USB 1.1)?

Yes, it's pretty much confirmed to be a USB 2.0 only issue. Running the  
camera on a USB 1.1 port or unloading the ehci_hcd driver before plugging  
it is a feasible workaround, i.e. if you can do without some of the higher  
YUYV resolutions that require USB 2.0 throughput.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] LQC Pro 5000 picture quality settings

2007-04-09 Thread Martin Rubli

On Tue, 27 Mar 2007 20:31:36 +0800, Ian Latter
[EMAIL PROTECTED] wrote:

I hadn't heard of Bayer mode before. Seems the PWC
project has support for Bayer decoding in pwc-dec23.c;
http://iphitus.loudas.com/beyond/2.6.17/2.6.17-beyond3/patches/pwc-2.6.18-backport-fixed.patch

Bayer mode is an image encoding standard that's not currently supported by
the UVC specification, which is one of the reasons why it probably won't
make its way into the UVC driver.

Another one is that V4L2 drivers are not supposed to decode the image
data. There was a lot of discussion on that topic in the past and the
bottom line is that even though there's no unified V4L2 library that could
take care of this, drivers are not supposed to do it. This leaves it up to
the app to do any sort of decoding.

That being said, the UVC driver doesn't really care about the video data
that it relays to the app. In the case of some Logitech cameras you can
switch them to Bayer mode and then do the decoding in user space. I posted
a quick how-to on this topic a while ago, you should be able to find it in
the archives.

.. and makes mention of this special case;
/* special case: VGA @ 5 fps and snapshot is raw bayer mode */

I take it this is the single image capture mode that
UVC doesn't support yet?

Still image capture is indeed not supported yet. It shouldn't be too
difficult to implement but the main question to resolve is: How do you get
the still image to the app? V4L2 has no support for this today, so you'd
have to come up with another interface. My favorite is dd if=/dev/video0
of=mypic.jpg but nobody's had time to implement that so far. :-)

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] UVC Non-module patch

2007-03-06 Thread Martin Rubli

On Tue, 06 Mar 2007 18:59:52 -0800, Ian Latter  
[EMAIL PROTECTED] wrote:

 We will do much better than that. The plan is to get the Linux UVC  
 driver
 integrated in the mainline kernel. This isn't a straightforward  
 process, as I
 need to have a few V4L2 controls standardised first.

 Thanks Laurent -- in the mean time tho .. Gnu style tarballs
 (uvc-version.tar.gz) would be handy.

I agree, with all the people who keep having problems to download the  
driver it couldn't hurt. :-)

 Thanks, now that I've been through the workings of the luvcview
 code, I'm feeling pretty confident.  Last night I produced a basic
 library based on the luvcview v4l2 code .. it looks promising.  If I get
 my camera running, I'll give you the USB id's, because it shows up as
 unknown.

The device showing up as unknown is not a problem, it just means that  
you have a generic UVC device that doesn't need any special treatment  
(unlike the few Logitech ones that are hardcoded). Unfortunately the  
driver usually has no way of reading a descriptive name from the device.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Quick Cam Pro 5000 046d:08ce don't run on Ubuntu Feisty Fawn

2007-02-23 Thread Martin Funk

it works now!

And I'm a little ashamed of why it didn't before:

svn diff -r HEAD
Index: Makefile
===
--- Makefile(Revision 89)
+++ Makefile(Arbeitskopie)
@@ -1,6 +1,6 @@
  KERNEL_VERSION := `uname -r`
  KERNEL_DIR := /lib/modules/$(KERNEL_VERSION)/build
-INSTALL_MOD_DIR:= usb/media
+INSTALL_MOD_DIR:= kernel/ubuntu/media/usbvideo

  PWD:= $(shell pwd)


adding the trace messages showed me, that I wasn't using the downloaded 
module at all, but the
module provided by ubuntu.

If you don't mind I'll drop a bugreport at https://launchpad.net/ 
telling em that the uvcvideo module they provide is outdated.

Martin


Laurent Pinchart schrieb:
 On Tuesday 20 February 2007 22:05, Martin Funk wrote:
 Hi Thomas,

 verry same output of v4l-video here, just the bus_info differs.
 It also makes no difference if the given uvc_ids is added to the code or
 not.
 
 Here's what bothers me in your kernel log:
 
 [  284.165685] uvcvideo: uvc_v4l2_ioctl
 [  284.165691] v4l2 ioctl VIDIOC_STREAMON, dir=-w (0x40045612)
 [  284.165967] uvcvideo: uvc_v4l2_ioctl
 [  284.165970] v4l2 ioctl VIDIOC_DQBUF, dir=rw (0xc0585611)
 [  284.166061] uvcvideo: Dequeuing buffer 0.
 [  284.171785] uvcvideo: Dropping packet (out of sync).
 [  284.171788] uvcvideo: Dropping packet (out of sync).
 [  284.171790] uvcvideo: Dropping packet (out of sync).
 [  284.171791] uvcvideo: Dropping packet (out of sync).
 
 Right after started streaming, the application tries to dequeue the first 
 buffer using VIDIOC_DQBUF. The ioctl checks the first buffer in the queue 
 (which is buffer 0) and blocks until the buffer is filled with image data. It 
 seems from what you reported that this never happens.
 
 The driver keeps printing out-of-sync messages, and that shouldn't happen. An 
 out-of-sync message can happen from times to times, but definitely not at the 
 very beginning. Could you hack uvc_video.c to print more information in the 
 out of sync message, such as the buffer number (buff-buf.index) and state 
 (buff-buf.index) ?
 
 Best regards,
 
 Laurent Pinchart
 

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Quick Cam Pro 5000 046d:08ce don't run on Ubuntu Feisty Fawn

2007-02-20 Thread Martin Funk

Hi,

sorry for reheating my question, but I'm still in search of the 
component to blame, that the cam is not working. I understand that the 
Linux distro I'm using is in alpha state so problems have to be expected.
It's a Ubuntu Feisty Fawn on a amd64 dual core and uname -a tells me:
Linux fnk64-desktop 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 
x86_64 GNU/Linux

Maybe someone can give me a hint on where to tweak the logging to get 
more information.
I'm not much of a c-programmer and far off understanding the 
architecture of the uvcvideo module, but I should be able to add another 
uvc_trace here or there.

Kölle Alaaf,

Martin Funk

Martin Funk schrieb:
 I dug a little deeper into this.

 Before I this I didn't know how to set the trace level for a kernel 
 module, but now I think I do.

 At least this
  sudo modprobe uvcvideo trace=0x
 made the module very talkative:

 The first messages seem to belong to the startup phase of the driver.
 At [284.099774] i started luvcview

 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790239] uvcvideo: Probing 
 generic UVC device 4.4
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790251] uvcvideo: Found 
 format MJPEG.
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790253] uvcvideo: - 160x120 
 (30.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790256] uvcvideo: - 176x144 
 (30.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790258] uvcvideo: - 320x240 
 (15.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790261] uvcvideo: - 352x288 
 (15.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790263] uvcvideo: - 640x480 
 (15.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790265] uvcvideo: Found 
 format Uncompressed.
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790267] uvcvideo: - 160x120 
 (30.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790269] uvcvideo: - 176x144 
 (30.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790272] uvcvideo: - 320x240 
 (15.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790274] uvcvideo: - 352x288 
 (15.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790276] uvcvideo: - 640x480 
 (15.0 fps)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790283] uvcvideo: Found a 
 Status endpoint (addr 87).
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790286] uvcvideo: Found UVC 
 1.00 device unnamed (046d:08ce)
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790288] uvcvideo: Scanning 
 UVC chain: OT 5 - Unit 4 - Unit 3 - Unit 2 - IT 1
 Feb 14 23:54:47 fnk64-desktop kernel: [  244.790293] uvcvideo: Found a 
 valid video chain (1 - 5).
 Feb 14 23:54:48 fnk64-desktop kernel: [  244.799665] uvcvideo: UVC 
 device initialized.
 Feb 14 23:54:48 fnk64-desktop kernel: [  244.799725] usbcore: registered 
 new interface driver uvcvideo
 Feb 14 23:54:48 fnk64-desktop kernel: [  244.799797] USB Video Class 
 driver (v0.1.0-c)
 Feb 14 23:54:48 fnk64-desktop NetworkManager: debug 
 info^I[1171493688.045799] nm_hal_device_added (): New device added (hal 
 udi is 
 '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_video4linux').
 Feb 14 23:55:14 fnk64-desktop kernel: [  255.904563] usbcore: 
 deregistering interface driver uvcvideo
 Feb 14 23:55:14 fnk64-desktop NetworkManager: debug 
 info^I[1171493714.727154] nm_hal_device_removed (): Device removed (hal 
 udi is 
 '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_video4linux').
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.893769] Linux video capture 
 interface: v2.00
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895334] uvcvideo: Probing 
 generic UVC device 4.4
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895347] uvcvideo: Found 
 format MJPEG.
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895349] uvcvideo: - 160x120 
 (30.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895352] uvcvideo: - 176x144 
 (30.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895354] uvcvideo: - 320x240 
 (15.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895357] uvcvideo: - 352x288 
 (15.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895359] uvcvideo: - 640x480 
 (15.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895361] uvcvideo: Found 
 format Uncompressed.
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895363] uvcvideo: - 160x120 
 (30.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895365] uvcvideo: - 176x144 
 (30.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895368] uvcvideo: - 320x240 
 (15.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895370] uvcvideo: - 352x288 
 (15.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895372] uvcvideo: - 640x480 
 (15.0 fps)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895381] uvcvideo: Found a 
 Status endpoint (addr 87).
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895384] uvcvideo: Found UVC 
 1.00 device unnamed (046d:08ce)
 Feb 14 23:55:33 fnk64-desktop kernel: [  263.895387] uvcvideo: Scanning 
 UVC chain: OT 5 - Unit 4 - Unit 3 - Unit 2 - IT 1
 Feb 14 23:55:33 fnk64

Re: [Linux-uvc-devel] Quick Cam Pro 5000 046d:08ce don't run on Ubuntu Feisty Fawn

2007-02-20 Thread Martin Funk

Hi Thomas,

verry same output of v4l-video here, just the bus_info differs.
It also makes no difference if the given uvc_ids is added to the code or 
not.

Martin


Thomas Schlesinger schrieb:
  Original-Nachricht 
 Datum: Tue, 20 Feb 2007 09:56:15 +0100
 Von: Martin Funk [EMAIL PROTECTED]
 An: linux-uvc-devel@lists.berlios.de
 CC: 
 Betreff: Re: [Linux-uvc-devel] Quick Cam Pro 5000 046d:08ce don\'t run on 
 Ubuntu Feisty Fawn

   
 Hi,

 sorry for reheating my question, but I'm still in search of the 
 component to blame, that the cam is not working. I understand that the 
 Linux distro I'm using is in alpha state so problems have to be expected.
 

 Hi,

 I've bought this Webcam yesterday, too, in trust of 
 http://linux-uvc.berlios.de/#devices.

 I want to add the output of v4l-video here, hoping it helps somehow ;-)

 I've modified the usb_driver.c of uvc, like mentioned in another posting:

 static struct usb_device_id uvc_ids[] = {
 { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
 | USB_DEVICE_ID_MATCH_INT_INFO,
 .idVendor = 0x046d,
 .idProduct = 0x08ce,
 .bInterfaceClass = USB_CLASS_VENDOR_SPEC,
 .bInterfaceSubClass = 1,
 .bInterfaceProtocol = 0
 },
 [..]

 This is the output of v4l-info:

 [EMAIL PROTECTED]:~$ v4l-info

 ### v4l2 device info [/dev/video0] ###
 general info
 VIDIOC_QUERYCAP
 driver  : uvcvideo
 card: USB Video Class device
 bus_info: :00:1d.7
 version : 0.1.0
 capabilities: 0x401 [VIDEO_CAPTURE,STREAMING]

 standards

 inputs
 VIDIOC_ENUMINPUT(0)
 index   : 0
 name: Camera
 type: CAMERA
 audioset: 0
 tuner   : 0
 std : 0x0 []
 status  : 0x0 []

 video capture
 VIDIOC_ENUM_FMT(0,VIDEO_CAPTURE)
 index   : 0
 type: VIDEO_CAPTURE
 flags   : 1
 description : MJPEG
 pixelformat : 0x47504a4d [MJPG]
 VIDIOC_ENUM_FMT(1,VIDEO_CAPTURE)
 index   : 1
 type: VIDEO_CAPTURE
 flags   : 0
 description : Uncompressed
 pixelformat : 0x56595559 [YUYV]
 VIDIOC_G_FMT(VIDEO_CAPTURE)
 type: VIDEO_CAPTURE
 fmt.pix.width   : 160
 fmt.pix.height  : 120
 fmt.pix.pixelformat : 0x47504a4d [MJPG]
 fmt.pix.field   : NONE
 fmt.pix.bytesperline: 0
 fmt.pix.sizeimage   : 38400
 fmt.pix.colorspace  : SRGB
 fmt.pix.priv: 0

 controls
 VIDIOC_QUERYCTRL(BASE+0)
 id  : 9963776
 type: INTEGER
 name: Brightness
 minimum : 0
 maximum : 255
 step: 1
 default_value   : 127
 flags   : 0
 VIDIOC_QUERYCTRL(BASE+1)
 id  : 9963777
 type: INTEGER
 name: Contrast
 minimum : 0
 maximum : 255
 step: 1
 default_value   : 32
 flags   : 0
 VIDIOC_QUERYCTRL(BASE+2)
 id  : 9963778
 type: INTEGER
 name: Saturation
 minimum : 0
 maximum : 255
 step: 1
 default_value   : 32
 flags   : 0
 VIDIOC_QUERYCTRL(PRIVATE_BASE+0)
 id  : 134217728
 type: INTEGER
 name: Backlight Compensation
 minimum : 0
 maximum : 2
 step: 1
 default_value   : 1
 flags   : 0
 VIDIOC_QUERYCTRL(PRIVATE_BASE+1)
 id  : 134217729
 type: MENU
 name: Power Line Frequency
 minimum : 0
 maximum : 2
 step: 1
 default_value   : 2
 flags   : 0
 VIDIOC_QUERYCTRL(PRIVATE_BASE+2)
 id  : 134217730
 type: INTEGER
 name: Sharpness

Re: [Linux-uvc-devel] Quick Cam Pro 5000 046d:08ce don't run on Ubuntu Feisty Fawn

2007-02-14 Thread Martin Funk

Hi Laurent,

 luvcview

response with this on the shell:

luvcview version 0.2.0
Video driver: x11
A window manager is available
video /dev/video0


a new window with the title LUVCview(c)Laurent Pinchart  Michel Xhaard
is opened.
The green light on the cam is turned on.
There are no messages in any log file, but: No pictures to be seen 
nowhere :-(

luvcview seems to see the device though, since:
 luvcview -L
luvcview version 0.2.0
Video driver: x11
A window manager is available
video /dev/video0
/dev/video0 does not support read i/o
{ pixelformat = 'MJPG', description = 'MJPEG' }
{ pixelformat = 'YUYV', description = 'Uncompressed' }

Also uvcvideo seems to see something of the device, since a push on the 
cam button leads to this entry:
Feb 14 10:41:52 fnk64-desktop kernel: [ 1505.024051] uvcvideo: Button 
event (1).
Feb 14 10:41:52 fnk64-desktop kernel: [ 1505.123872] uvcvideo: Button 
event (0).
in the syslog.

The XWindow can't be closed either. luvcvideo responses with Stop 
asked but doesn't close the window.
To close the window I do a kill -9 on luvcvideo.

By the way Ekiga can't drive the video either, but it can drive the 
cam's microphone.

Anything else, I can do to assist?

Martin

Laurent Pinchart schrieb:
 Hi Martin,

   
 I just got myself a QuickCam Pro 5000 046d:08ce
 it runs using Windows, but using Linux I have problems

 When I plug in the cam ist is recognized by lsusb:
 Bus 002 Device 019: ID 046d:08ce Logitech, Inc.

 
 [...]
   
 Linux video capture interface: v2.00
 uvcvideo: Found UVC 1.00 device unnamed (046d:08ce)
 

 This line is good news, it means the driver recognised your webcam and 
 initialised it successfully.

   
 usbcore: registered new interface driver uvcvideo
 USB Video Class driver (v0.1.0-c)

 and a
 crw-rw 1 root video 81, 0 2007-02-13 17:43 /dev/video0
 is created.
 

 That's good too.

   
 Unfortunately when I start

  xawtv

 The little green lamp is turned on but I see this on the shell
 

 xawtv is not known to work the the Linux UVC driver. Could you try luvcview 
 and see if you're more successful ?

 Best regards,

 Laurent Pinchart

   

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] Quick Cam Pro 5000 046d:08ce don't run on Ubuntu Feisty Fawn

2007-02-13 Thread Martin Funk

Hi,

I just got myself a QuickCam Pro 5000 046d:08ce
it runs using Windows, but using Linux I have problems

When I plug in the cam ist is recognized by lsusb:
Bus 002 Device 019: ID 046d:08ce Logitech, Inc.

I got
URL: svn://svn.berlios.de/linux-uvc/linux-uvc/trunk
in
Revision: 88

I made the little:
 make all
 sudo make install

I think I also made
 sudo modprobe uvcvideo

anyway when I plug the cam out/in
i find this in the syslog


Feb 13 17:43:06 fnk64-desktop kernel: [ 5558.432070] usb 2-4.4: new high 
speed USB device using ehci_hcd and address 23
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.425407] nm_hal_device_added (): New device added (hal 
udi is '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.494433] nm_hal_device_added (): New device added (hal 
udi is 
'/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_alsa_capture_0').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.572748] nm_hal_device_added (): New device added (hal 
udi is 
'/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_oss_pcm_0').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.705243] nm_hal_device_added (): New device added (hal 
udi is 
'/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_oss_pcm_0_0').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.722874] nm_hal_device_added (): New device added (hal 
udi is 
'/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_oss_mixer__1').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.730878] nm_hal_device_added (): New device added (hal 
udi is '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_if3').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.732857] nm_hal_device_added (): New device added (hal 
udi is '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_if2').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.734673] nm_hal_device_added (): New device added (hal 
udi is 
'/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_if2_alsa_control__1').
 

Feb 13 17:43:06 fnk64-desktop kernel: [ 5558.526977] usb 2-4.4: 
configuration #1 chosen from 1 choice
Feb 13 17:43:06 fnk64-desktop kernel: [ 5558.680078] Linux video capture 
interface: v2.00
Feb 13 17:43:06 fnk64-desktop kernel: [ 5558.681719] uvcvideo: Found UVC 
1.00 device unnamed (046d:08ce)
Feb 13 17:43:06 fnk64-desktop kernel: [ 5558.710975] usbcore: registered 
new interface driver uvcvideo
Feb 13 17:43:06 fnk64-desktop kernel: [ 5558.710981] USB Video Class 
driver (v0.1.0-c)
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.852581] nm_hal_device_added (): New device added (hal 
udi is '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_if1').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.899166] nm_hal_device_added (): New device added (hal 
udi is '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_if0').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.927331] nm_hal_device_added (): New device added (hal 
udi is 
'/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_video4linux').
Feb 13 17:43:06 fnk64-desktop NetworkManager: debug 
info^I[1171384986.927850] nm_hal_device_added (): New device added (hal 
udi is '/org/freedesktop/Hal/devices/usb_device_46d_8ce_DD8DC2A1_usbraw').

and a
crw-rw 1 root video 81, 0 2007-02-13 17:43 /dev/video0
is created.

Unfortunately when I start
 xawtv
The little green lamp is turned on but I see this on the shell

This is xawtv-3.95.dfsg.1, running on Linux/x86_64 (2.6.20-8-generic)
/dev/video0 [v4l2]: no overlay support
v4l-conf had some trouble, trying to continue anyway
Warning: Cannot convert string 
-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-* to type FontStruct
ioctl: VIDIOC_G_STD(std=0x7fff55eeb4a4 
[PAL_G,PAL_D,PAL_K,PAL_Nc,NTSC_M,NTSC_M_JP,?,SECAM_D,SECAM_G,SECAM_H,SECAM_K1,SECAM_L,?ATSC_8_VSB,ATSC_16_VSB,(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)]):
 
Invalid argument
Xlib:  extension GLX missing on display :0.0.
ioctl: VIDIOC_S_STD(std=0x0 []): Invalid argument
v4l2: oops: select timeout


and this in the kern.log


Feb 13 17:48:56 fnk64-desktop kernel: [ 5734.284810] uvcvideo: Failed to 
query (130) UVC control 1 (unit 0) : -32 (exp: 26).
Feb 13 17:48:56 fnk64-desktop kernel: [ 5734.288033] uvcvideo: Failed to 
query (1) UVC control 2 (unit 0) : -32 (exp: 26).


I don't have no good questions on the problem no more

by the way:
 uname -a
Linux fnk64-desktop 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 
x86_64 GNU/Linux

Tell me where to be more specific to help to solve this.

Martin

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de

Re: [Linux-uvc-devel] (no subject)

2007-02-09 Thread Martin Rubli

On Thu, 08 Feb 2007 14:19:18 -0800, Laurent Pinchart  
[EMAIL PROTECTED] wrote:

 Hi David,

 I bought a Logitech Quickcam Pro 5000 today and tried to use
 it with ekiga.  Sometimes it works and other times I get this
 error at the beginning or in the middle of a session:

 Your driver doesn't seem to support any of the color formats supported  
 by Ekiga.
 Please check your kernel driver documentation in order to determine  
 which Palette is supported.

 I have to unplug the camera and plug it in again to get it to work
 again.  The log shows  this:

 It seems you are experiencing the dreadful Logitech hardware bug :-( I  
 don't think you can do much here. Martin, can you confirm ?

It does indeed look like it. Ekiga has always been very good at triggering  
it ...

 uvcvideo: UVC device initialized.
 usbcore: registered new interface driver uvcvideo
 USB Video Class driver (v0.1.0)
 uvcvideo: Trying format 0x56595559 (YUYV): 720x480.
 uvcvideo: Using default frame interval 3.3 us (30.0 fps).
 uvcvideo: Trying format 0x56595559 (YUYV): 1x480.
 uvcvideo: Using default frame interval 3.3 us (30.0 fps).
 uvcvideo: Control 0x00980903 not found.
 uvcvideo: Control 0x00980903 not found.
 uvcvideo: Control 0x00980909 not found.
 uvcvideo: Failed to resubmit video URB (-1).
 uvcvideo: Failed to resubmit video URB (-1).
 uvcvideo: Failed to resubmit video URB (-1).
 uvcvideo: Failed to resubmit video URB (-1).
 uvcvideo: Failed to resubmit video URB (-1).
 uvcvideo: Failed to resubmit video URB (-1).
 uvcvideo: Failed to resubmit video URB (-1).

 This puzzles me as well. Those errors are probably not fatal to the  
 problem you are experiencing, but they still should not happen.

Agreed. I've seen these before, they were always harmless, but I never  
really found the connection to the other problem. I think I saw them  
happen independently, but I'm not sure anymore ...

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] green screen

Does your Proscope work with any other applications like luvcview? If so,  
there might be a bug in the Ekiga decoder, in which case you should take  
your request to the Ekiga developers.

Cheers,
Martin


On Sat, 27 Jan 2007 10:48:16 -0800, Gene Imes [EMAIL PROTECTED] wrote:

 My Bodelin ProScopeHR renders a green screen in Ekiga. I can see video.
 A screenshot is here:

 http://ozob.net/luvc/ekiga-screen-shot.jpg

 Thanks for any help,


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Jumbled images from Logitech Quickcam 5000

Hi Lee,

I don't see your point, the landscape and the colors in your pictures look  
perfectly fine. ;-)

On a more serious note, I haven't seen anything similar myself. Could you  
check your camera with luvcview to see if the pictures are also jumbled  
up? If yes, I would be very surprised. If not, can you try if you can get  
Motion to use the YUV format instead of MJPEG (which it seems to be using  
now)? You may also want to capture some raw frames with luvcview (check  
the -h option) to analyze them--or have the Motion people analyze them.  
The driver really does nothing to the image data, so image corruption is  
rarely the driver's fault.

Let us know if you find something ...

Cheers,
Martin


On Mon, 29 Jan 2007 07:28:38 -0800, Lee Wild [EMAIL PROTECTED] wrote:

 Hi

 I'm running a Logitech Quickcam Pro 5000 webcam from a machine
 installed with Fedora Core 6. I built the linux-uvc drivers, and am
 running Motion webcam software.
 It's been a long road to get everything to build correctly and get
 this far, however

 My problem is that the majority of images being output are jumbled up,
 a bit like some sliding-block puzzle, here are a couple of examples:
 http://ukselfbuild.com/webcam/2007/January/29/cam2/2007-01-29-15-00-00-snapshot.jpg
 http://ukselfbuild.com/webcam/2007/January/29/cam2/2007-01-29-08-00-00-snapshot.jpg

 I first asked for support from the people behind Motion, but they are
 thinking the issue is to do with the linux-uvc driver.

 Does anyone have any ideas what might be causing this, and how I might
 get around it ?

 Many thanks
 Lee
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

[Linux-uvc-devel] Sony Vaio VGN-SZ3VWP/X built-in laptop webcam

Hi Daniel,

Unfortunately, this camera isn't a UVC webcam either. Below are instructions
how you can find out ...

Unless you know what kind of chipset the camera uses you might have a hard
time finding a driver. Maybe you can tell from the Windows driver?

Cheers,
Martin


Use the lsusb tool and look for video class interfaces like this: (In this
example, the VID is 046d and the PID is 08cb.)

lsusb -d 046d:08cb -v | grep 14 Video

If your device is a UVC device, you should see a number of lines that look
like this: 
bFunctionClass 14 Video
bInterfaceClass14 Video
bInterfaceClass14 Video
bInterfaceClass14 Video

In this case the Linux UVC driver should recognize your camera when you plug
it in. 

If there are no such lines, your device is not a UVC device.



 -Original Message-
 From: Daniel Storm [mailto:[EMAIL PROTECTED]
 Sent: Monday, January 29, 2007 9:54 AM
 To: [EMAIL PROTECTED]
 Subject: [Linux-uvc-devel] HP Pavillon dv6000 built-in laptop webcam
 
 Hi Martin,
 
 Apologies for the direct mail, rather than to the uvc-devel list (I'm
 not a member right now).
 
 Here's another Ricoh built in webcam from a Sony Vaio PCG-6N1M (or
 VGN-SZ3VWP/X if you prefer). It's a different model to the one you
 listed in your post.
 
 I don't know whether this card is already supported by the uvc driver,
 the source didn't build or mention Ricoh, so I hope this mail isn't a
 waste of your time.
 
 Please feel free to pass my details to anyone constructing a letter to
 Ricoh requesting technical details (as long as my email isn't
 published).
 
 Dan
 
 # lsusb -v -s 005:003
 
 Bus 005 Device 003: ID 05ca:1830 Ricoh Co., Ltd
 Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass0 (Defined at Interface level)
   bDeviceSubClass 0
   bDeviceProtocol 0
   bMaxPacketSize064
   idVendor   0x05ca Ricoh Co., Ltd
   idProduct  0x1830
   bcdDevice1.00
   iManufacturer   0
   iProduct0
   iSerial 0
   bNumConfigurations  1
   Configuration Descriptor:
 bLength 9
 bDescriptorType 2
 wTotalLength   78
 bNumInterfaces  1
 bConfigurationValue 1
 iConfiguration  0
 bmAttributes 0x80
   (Bus Powered)
 MaxPower  100mA
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   0
   bNumEndpoints   2
   bInterfaceClass 6 Imaging
   bInterfaceSubClass  0
   bInterfaceProtocol  0
   iInterface  0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x81  EP 1 IN
 bmAttributes3
   Transfer TypeInterrupt
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0040  1x 64 bytes
 bInterval   1
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x86  EP 6 IN
 bmAttributes1
   Transfer TypeIsochronous
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x  1x 0 bytes
 bInterval   1
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   1
   bNumEndpoints   2
   bInterfaceClass 6 Imaging
   bInterfaceSubClass  0
   bInterfaceProtocol  0
   iInterface  0
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x81  EP 1 IN
 bmAttributes3
   Transfer TypeInterrupt
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0040  1x 64 bytes
 bInterval   1
   Endpoint Descriptor:
 bLength 7
 bDescriptorType 5
 bEndpointAddress 0x86  EP 6 IN
 bmAttributes1
   Transfer TypeIsochronous
   Synch Type   None
   Usage Type   Data
 wMaxPacketSize 0x0c00  2x 0 bytes
 bInterval   1
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   2
   bNumEndpoints   2
   bInterfaceClass 6 Imaging
   bInterfaceSubClass  0
   bInterfaceProtocol  0
   iInterface

Re: [Linux-uvc-devel] Automatic Gain Control

Hi Michel,

On Thu, 11 Jan 2007 00:07:46 -0800, Michel Xhaard [EMAIL PROTECTED] wrote:

 The zero step size for the absolute exposure time is obviously wrong. I
 don't currently have my USB analyzer to check what's going on there.

I found the problem in the driver. There is a bug in the uvc_get_le_value  
function, which leads to wrong values when reading 32-bit wide controls. I  
have a patch and I'll submit it to Laurent. The control now looks as  
follows:

   Exposure (Absolute)
 ID  : 17,
 Type: Dword,
 Flags   : { CAN_READ, CAN_WRITE, IS_CUSTOM },
 Values  : [ 1 .. 1, step size: 1 ],
 Default : 166

 Also, I get errors when I try to read these controls. This seems to be  
 why the
 controls don't work in luvcview.

Another bug in the control definition in the UVC driver. Certain controls  
were accidentally marked as write-only, which explains the error. It's  
part of the patch that I mentioned, it should be fixed soon in the  
repository.

 Yes luvcview used the step value.

We'll post a message to the list as soon as the patch is committed. It  
would be great if you could retest it ...

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] -Werror fixes for uvcvideo

On Thu, 01 Feb 2007 12:12:00 -0800, Luigi Rizzo [EMAIL PROTECTED] wrote:

 one reason of concern is a note about future support that i misread
 in http://gcc.gnu.org/onlinedocs/gcc/Unnamed-Fields.html:

   ... For example, this structure:
   ...
   It is ambiguous which a is being referred to with `foo.a'.
   Such constructs are not supported and must be avoided.  In
   the future, such constructs may be detected and treated as
   compilation errors.

 maybe the note on treating these as errors in the future
 refers only to ambiguous constructs and not to all unnamed unions.

Yes, indeed. In our case there is no ambiguity. The whole struct becomes  
much easier to read if the unions are anonymous.

 the other reason for concern is ease of porting to other systems --  
 things like pragmas and attributes are easy to remap with a one time
 #define, but unnamed extensions are a pain to handle because you
 have to modify all references to the fields in the source.

 and of course - there is the issue of code safety, because
 1)this feature can cause ambiguous constructs, and 2) it doesn't
 suggest the programmer that multiple items are sharing the same
 memory location. The union name at least gives you some hints,
 especially if you call it 'u' ...

I somewhat agree with the portability part. However, these Linux system  
structures (they're part of V4L2 and, therefore, the official Linux  
kernel) are not designed to be portable. And given the wide availability  
of gcc I think you'd have a hard time finding a platform to port V4L2 to  
that doesn't support these constructs.

If you want, you can raise the discussion on the V4L2 mailing list. When  
we proposed the changes we were really just trying to fit in to what was  
already there.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Automatic Gain Control

Hi all,

On Mon, 08 Jan 2007 12:08:38 -0800, Laurent Pinchart  
[EMAIL PROTECTED] wrote:

 The thing is that I am trying to disable the camera auto gain.

 Martin, by the way, is it necessary to put the webcam in bayer mode to  
 disable the auto-exposure ? Or would the auto-exposure mode control do  
 the job
 alone ?

I think what you're doing by enabling raw Bayer mode shoots way over the  
top of what you want. Have you checked out this one here?
https://lists.berlios.de/pipermail/linux-uvc-devel/2006-December/001099.html

This disables auto gain/exposure mode and should be what you're looking  
for.

 That's right. The Quickcam Ultra Vision might have slightly different
 controls. I have no such model here, so I can't test the patch. Maybe  
 Martin could have a look.

This control is the same for the Ultra Vision as for the other controls.  
IIRC we're talking about a standard UVC control here anyway.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Automatic Gain Control

Jose,

On Tue, 09 Jan 2007 06:53:29 -0800, Jose Luis Landabaso  
[EMAIL PROTECTED] wrote:

 I have arrived to a point in which I'm very confused.
 I have learnt that you can only turn off the color processing when the
 camera is not capturing.

True.

 So, I stop the capture program, and then run bayer.
 If I disable color processing I cannot run my capture program again  
 since.
 I always get:

 select timeout
 VIDIOC_DQBUF error 11, Resource temporarily unavailable

 When I turn again the video processing on then the program works fine  
 again.

 Any ideas?

I'm assuming you're not using any of the native resolutions for which raw  
mode works. Quoting from the FAQ entry:

For 1.3 MP cameras raw mode may only work in the camera's native  
resolutions, which are 960x720 or 1280x960. If color processing is  
disabled and streaming is started in a not supported resolution, the  
camera sends no data and the application may appear to hang.

This would certainly explain the timeout. What camera are you using and at  
which resolution?

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Automatic Gain Control

Michel,

On Mon, 08 Jan 2007 12:30:05 -0800, Michel Xhaard [EMAIL PROTECTED] wrote:

 I just upload a new revision of luvcview with pan/tilt fix, a lot of
 improvements.

Cool! :-)

 Seem strange that we cannot change the exposure in manuel
 mode ?

There should be a control to set the absolute exposure time ...

 Is there a way to set/reset the autowhite balance too ? a lot of
 robotic project need these features

... and one for white balance temperature. I'll double check tomorrow on  
my Linux machine but those are standard UVC controls that our cameras  
support.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] QuickCam Fusion lockup

Brian,

On Tue, 09 Jan 2007 15:46:37 -0800, Brian  
[EMAIL PROTECTED] wrote:

 Disappointing, can firmware be uploaded to webcams?

No, sorry, the only way to update the firmware is a soldering iron. :-|

 My webcam appears to be working fine, I have tested it by leaving it
 running for extended periods. The only thing that 'seems' to trigger the
 problem is if I stop and start it several times.

The problem never occurs during simple streaming, it is triggered only by  
control requests.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] QuickCam Fusion lockup

 Given that a good chunk of cameras people are using are sometimes not
 functional,
 i think it would be good to put something on the website about this. I
 own two
 webcams that exhibit these problems regularly, and have been messing
 with various
 versions of the reset patch, trying to get better behavior.

 (Discussed here:
 http://www.mail-archive.com/linux-uvc-devel@lists.berlios.de/msg00322.html  
 )

 What is the opinion on putting some version of this hack in trunk? (even
 if temporarily)

Evgeny mentioned about a month ago that he was about to publish a new  
patch that should improve the behavior on most machines. I don't know the  
state of that. Any updates, Evgeny? :-) Basically, we were waiting for  
that, but the plan is indeed to either integrate such a hack into the  
trunk or, at least, put it up for download.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Automatic Gain Control

2006-12-20 Thread Martin Rubli

Hey,

Actually, it couldn't be much simpler. I think what you're looking for is  
the Exposure, Auto control, which looks something like this:

   Auto-exposure mode
 ID  : 15,
 Type: Choice,
 Flags   : { CAN_READ, CAN_WRITE },
 Values  : { 'Manual'[1], 'Aperture priority'[8] },
 Default : 8

Setting the control to 1 disables auto-gain and setting it back to 8  
reenables it. If you look at the UVC specification you'll see the meaning  
of the different bits, but 1 and 8 are the only values supported by the  
Logitech cameras.

Cheers,
Martin


On Wed, 06 Dec 2006 11:12:15 +0100, andrea giachetti [EMAIL PROTECTED] wrote:

 Hi
 Is there a way tro disable the automtic gain control
 of Logitech QuickCam Fusion webcams using
 linux-uvc? Thanks in advance
 andrea giachetti
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] max fps that can be achieved using logitech fusion webcam

2006-12-20 Thread Martin Rubli

Streaming VGA at 30 fps definitely works. The problem is that many  
applications can't or don't set the frame rate correctly when they start  
the stream. So what happens is that the driver just takes a default frame  
rate, which is not necessarily the highest possible.

GStreamer's v4l2src plugin can set the frame rate, so you may want to try  
something like:
 gst-launch v4l2src ... ! xvimagesink
and give the correct arguments to v4l2src. You should be able to capture  
video into a file at 30 fps using a more sophisticated pipeline.

Cheers,
Martin


On Wed, 20 Dec 2006 19:28:57 +0100, Francisco Vera [EMAIL PROTECTED] wrote:

 I need to know what is the max fps for the logitech fusion.

 In the past days I have read almost all the messages fron the last two  
 months
 from this list, the discussion on the thread Trouble recording from two
 webcams was illuminating, and the table from
 http://www.mail-archive.com/linux-uvc-devel%40lists.berlios.de/msg00306.html
 from logitech, it is clear that 30 fps can be achieved in mjpeg and yuv  
 modes,
 real tests with other logitech cameras report 15 fps at 640x480 and 10  
 fps at
 960x720.

 When I installed the fusion on my windows xp using the software bundled  
 with
 this camera, one can record video at a resolution of 640x480, but when
 playing this video on linux one can see that the video is only at 15 fps.

 Yesterday I got the uvcvideo driver from cvs (split branch) and  
 installed in
 my debian sid pc. Luvcview works at 640x480 15 fps in mjpeg mode and  
 1024x576
 10 fps in yuv mode.

 I can record video using:
  ffmpeg -an -r 50 -y -vd /dev/video0 -sameq -t 4 -s 1024x576  test.avi
 and ffmpeg say:
 -
 [video4linux2 @ 0xb7ef0610][4]Capabilities: 401
 Input #0, video4linux2, from '':
   Duration: N/A, bitrate: N/A
   Stream #0.0: Video: rawvideo, yuv422, 1024x576, 471859 kb/s, 50.00  
 fps(r)
 Output #0, avi, to 'test.avi':
   Stream #0.0: Video: mpeg4, yuv420p, 1024x576, q=2-31, 200 kb/s, 50.00  
 fps(c)
 --

 But this video has duplicate frames (5) so in reality it is only 10 fps,
 trying other frame rates also produce duplicated frames and 10 fps  
 effective.

 I can also view video with mplayer using (in a window or full window):
 ffmpeg -an -vd /dev/video0 -s 1024x576 -r 10 -b 5000 -y -vcodec mpeg4 -f
 avi - | /usr/bin/mplayer -

 If someone find how to record video un mjpeg mode with ffmpeg, please  
 post to
 this list.

 installing: apt-get install libpt-plugins-V4L2 allows ekiga to works,  
 but it
 is inestable.

 installing v4l2ucp-1.2 allows to change some parameters for the camera

 I have looked into the code but appears like the code automatically  
 detect the
 best frame rate for the camera?.

 Does someone knows if it is possible to capture 30 fps with these  
 cameras in
 640x480?

 I need this information urgent because if it is possible, in these days  
 I will
 buy 3 more of these cams. if not I will have to go to plan B, and buy a  
 non
 expensive digital cameras (not a webcam) that can grab video at 640x480  
 and
 30 fps.

 I really appreciate the work from the people involved in this driver,

 Regards,

 Francisco
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Integrated HP dv6000 laptop webcam

2006-12-12 Thread Martin Rubli

Hi Federico,

It seems the HP dv6000 comes with different webcam modules and we're  
trying to find out a little more about it. Would you mind posting the  
output of:

lsusb -d 0c45:62c0 -v

(Or whatever VID/PID your webcam has ...) That would really help us a lot!

Thanks,
Martin


On Tue, 28 Nov 2006 16:58:46 +0100, Federico Quagliata  
[EMAIL PROTECTED] wrote:

 So far I managed to get it working only in Ekiga.

 Kopete shows a green screen, and both xawtv and mplayer complain about  
 ioctl
 invalid arguments errors.

 Here's mplayer (green screen too) output:

 
 $ mplayer tv:// -tv driver=v4l2
 MPlayer 1.0rc1-4.1.2 (C) 2000-2006 MPlayer Team
 (...)
 Playing tv://.
 TV file format detected.
 Selected driver: v4l2
  name: Video 4 Linux 2 input
  author: Martin Olschewski [EMAIL PROTECTED]
  comment: first try, more to come ;-)
 v4l2: ioctl get standard failed: Invalid argument
 Selected device: USB 2.0 Camera
  Capabilites:  video capture  streaming
  supported norms:
  inputs: 0 = Camera;
  Current input: 0
  Current format: YUYV
 v4l2: ioctl set format failed: Invalid argument
 v4l2: ioctl set format failed: Invalid argument
 v4l2: ioctl set format failed: Invalid argument
 v4l2: ioctl enum norm failed: Invalid argument
 Error: Cannot set norm!
 Selected input hasn't got a tuner!
 v4l2: ioctl set mute failed: Invalid argument
 FPS not specified in the header or invalid, use the -fps option.
 No stream found.

 v4l2: ioctl set mute failed: Invalid argument
 v4l2: 0 frames successfully processed, 0 frames dropped.

 Exiting... (End of file)
 

 Output from dmesg:
 
 uvcvideo: Found UVC 1.00 device USB 2.0 Camera (0c45:62c0)
 usbcore: registered new driver uvcvideo
 uvcvideo: Failed to query (1) UVC control 2 (unit 3) : -32.
 uvcvideo: Failed to query (1) UVC control 6 (unit 3) : -32.
 uvcvideo: Failed to query (1) UVC control 2 (unit 3) : -32.
 uvcvideo: Failed to query (1) UVC control 6 (unit 3) : -32.
 (and so on...)
 

 Greetings,
 Federico


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Automatic Gain Control

2006-12-07 Thread Martin Rubli

The only way I can think of is to completely disable the color processing.  
This gives you access to the raw Bayer data, therefore disabling any (!)  
sort of automatic adjustments. If that sounds like something you want to  
try, let me know and I'll post some doc on how to do that. Also, I'll ask  
around a bit and see if there are any other ways ...

Cheers,
Martin


On Thu, 07 Dec 2006 09:21:11 +0100, Andrea Giachetti [EMAIL PROTECTED]  
wrote:

 Hi
 Thanks for the quick answer.
 I bought two webcams for a gesture tracking system, but, using  
 thresholding and color segmentation
 I'd lile to disable the automatic adjustments.
 isn't there any way?
 regards
 andrea

___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Automatic Gain Control

2006-12-07 Thread Martin Rubli


Hi Evgeny,


Is this possible for Logitech QuickCam 5000? Accesing raw data is really
important for me.


Yes, it should work with all current Logitech UVC cameras.

I've attached a few instructions and files that should help you. Sorry for  
the poor layout, I just extracted it from the Wiki I'm currently  
preparing. A nicer version will be publicly available soon ...


Cheers,
Martin

quickcam-raw.tar.gz
Description: GNU Zip compressed data
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] unstable pictures with logitech pro 5000

2006-12-07 Thread Martin Rubli

Hi Simon,

I did a little testing with linphone. I downloaded 1.5.1 and enabled  
HAVE_LINUX_VIDEODEV2_H by hand. Is that supposed to be this way? (In the  
future, please specify the version you work with.)

After I got it running I had very different runs:

1. Sometimes it worked fine, the video seemed okay, no errors, etc. I  
still got a lot of errors, though. See trace 1 (taken with --verbose)  
below.

2. Usually when I ran it without --verbose it crashed when I enabled video  
with Xlib: unexpected async reply (sequence 0x3a12)! (different numbers  
each time). It crashed more often than not but for the times it didn't,  
the traces looked like trace 2 below.

3. One time I was able to reproduce the screwed up pictures you mentioned.  
IIRC --verbose was disabled.

My ideas:

I would first try to analyze where the VIDIOC_QBUF failed: Invalid  
argument comes from. Something's really wrong there.

Also, the Xlib errors you get, the different behavior with --verbose  
enabled/disabled, as well as the screwed up picture might hint at some  
synchronization issues in your program. I've seen those in the past when I  
wrote webcam software.

It's unlikely that the errors you see are actually the camera's fault. The  
EOF in empty packet. are harmless and if you use a newer driver version,  
they shouldn't appear anymore (except in debug mode, but as I mentioned,  
that's harmless).

If you really think the MJPEG stream is broken, try to use the YUV mode  
instead and see what it gives you. If your picture has green areas or  
spots, the data gets corrupted somewhere.

Cheers,
Martin


*** Trace 1 **

ortp-message-v4l_start: open, fd=28
ortp-message-v4lv2: MJPEG choosen
ortp-message-ms_filter_link: MSV4l:0x81dad40,0--MSMJpegDec:0x81f91f0,0
ortp-message-ms_filter_link: MSMJpegDec:0x81f91f0,0--MSSdlOut:0x81e46b0,0
ortp-message-v4l_thread starting
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-warning-VIDIOC_QBUF failed: Invalid argument
[mjpeg @ 0xb6c9d9a8]only 8 bits/component accepted
ortp-warning-ms_AVdecoder_process: error -1.
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-message-Using yuv overlay.
ortp-message-YUV overlay using hardware acceleration.
ortp-warning-We are late of 73 miliseconds.
[mjpeg @ 0xb6c9d9a8]only 8 bits/component accepted
ortp-warning-ms_AVdecoder_process: error -1.
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-warning-VIDIOC_QBUF failed: Invalid argument
[mjpeg @ 0xb6c9d9a8]mjpeg: unsupported coding type (cf)
[mjpeg @ 0xb6c9d9a8]invalid id 255
ortp-warning-ms_AVdecoder_process: error -1.
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-warning-VIDIOC_QBUF failed: Invalid argument
[mjpeg @ 0xb6c9d9a8]only 8 bits/component accepted
ortp-warning-ms_AVdecoder_process: error -1.
ortp-warning-VIDIOC_QBUF failed: Invalid argument
ortp-warning-VIDIOC_QBUF failed: Invalid argument


*** Trace 2 **

[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]only 8 bits/component accepted
[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]only 8 bits/component accepted
[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]mjpeg: unsupported coding type (c8)
[mjpeg @ 0xb6cc49a8]huffman table decode error
[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]only 8 bits/component accepted
[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]only 8 bits/component accepted
[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]only 8 bits/component accepted
[mjpeg @ 0xb6cc49a8]invalid id 255
[mjpeg @ 0xb6cc49a8]only 8 bits/component accepted



On Thu, 07 Dec 2006 14:31:16 +0100, Simon Morlat  
[EMAIL PROTECTED] wrote:

 Hello,

 I've bought a Logitech Quickcam Pro 5000 (Bus 004 Device 003: ID  
 046d:08c5
 Logitech, Inc.), and I've got some problems with it and the uvc driver.
 I use linphone (a sip video phone I'm the maintainer). The picture is  
 grabbed
 using mmap v4lv2 standart method with MJPEG format, then passed to  
 ffmpeg to
 decode it as YUV420P and then displayed.

 Sometimes (quite often), it works well.
 Sometimes, despite pictures display correctly, ffmpeg complains

Re: [Linux-uvc-devel] Automatic Gain Control

2006-12-06 Thread Martin Rubli

No, there isn't. But if you tell us a little more about the requirement  
behind it, we might be able to suggest something else. :-)

Cheers,
Martin


On Wed, 06 Dec 2006 11:12:15 +0100, andrea giachetti [EMAIL PROTECTED] wrote:

 Hi
 Is there a way tro disable the automtic gain control
 of Logitech QuickCam Fusion webcams using
 linux-uvc? Thanks in advance
 andrea giachetti
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Logitech Orbit Mp Stability problems, is a recent camera stable ?

2006-11-29 Thread Martin Rubli

 When I plug the camera I get :

 [17204020.156000] 13:3:1: cannot set freq 0 to ep 0x86
 [17204021.156000] 13:3:2: cannot set freq 0 to ep 0x86
 [17204022.168000] 13:3:3: cannot get freq at ep 0x86

These three lines come from the USB audio driver and have nothing to do  
with uvcvideo, so no need to worry.

 But if I try with luvcview it works properly,,, the problem is that after
 starting stopping the camera a few times (10-20 times,,,) I get :

 [17204111.756000] uvcvideo: Failed to query (130) UVC control 1 (unit 0)  
 : -32.
 [17204114.36] uvcvideo: Failed to query (1) UVC control 1 (unit 0) :  
 -32.
 [17204115.508000] uvcvideo: Failed to query (1) UVC control 1 (unit 0) :  
 -110.

 messages like these :( , and the camera stops working

 I've found
 http://developer.berlios.de/bugs/?func=detailbugbug_id=7605group_id=5681

 That seems to be similar,, it states hardware problems... but I'm not  
 sure it's the case here since if I remove the driver and reload it,, it  
 will work again..

It's indeed a hardware problem. If you're browsing through the mailing  
list archive you'll find quite a few threads about that problem. We're  
still looking for a good workaround for the UVC driver.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Trouble recording from two webcams

2006-11-15 Thread Martin Rubli

Hey Vidar,

I just did a little testing with two cameras, a QuickCam for Notebooks Pro  
(2006 model) and a QuickCam Orbit MP/Sphere MP (2006 model).

Using two instances of luvcview the following combinations work (only  
tested at the default resolutions):

MJPEG:
All combinations up to 2 x 640x480 (15 fps).
2 x 960x720 (theoretically 15 fps but my old laptop didn't manage to  
decode more than about 2 x 10 fps).

YUY2:
All combinations up to 2 x 640x480 (15 fps).
960x720 (10 fps) + 640x480 (15 fps).
1280x960 (7.5 fps) + 640x480 (15 fps).

The following failed with error -28:

YUY2:
2 x 960x720 (10 fps).
1280x960 (7.5 fps) + 640x480 (15 fps).
1280x960 (7.5 fps) + 960x720 (10 fps).

That should give you some indication of what you should be able to achieve  
with ffmpeg in terms of resolutions.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Trouble recording from two webcams

2006-11-15 Thread Martin Rubli

Ok, another interesting test with the same cameras. This time I used  
luvcview for one camera and another program for the second that allows me  
to select the frame rate.

1st camera: YUY2 960x720 @ 10 fps
2nd camera: YUY2 640x480 @ 15 fps works but fails with error -28 at = 20  
fps.

So you see that the bandwidth does indeed depend on the frame rate.

Also quite interesting

1st camera: YUY2 960x720 @ 10 fps
2nd camera: YUY2 960x720 @ 5 fps

Streaming starts but the picture of the second camera is completely messed  
up (the upper half is okay but the lower half is green and flickering)  
because packets are lost. I'll post more information as soon as I know  
where exactly the packets get lost but it might be a while ...

Cheers,
Martin


On Wed, 15 Nov 2006 11:13:54 +0100, Martin Rubli [EMAIL PROTECTED] wrote:

 Hey Vidar,

 I just did a little testing with two cameras, a QuickCam for Notebooks  
 Pro
 (2006 model) and a QuickCam Orbit MP/Sphere MP (2006 model).

 Using two instances of luvcview the following combinations work (only
 tested at the default resolutions):

 MJPEG:
 All combinations up to 2 x 640x480 (15 fps).
 2 x 960x720 (theoretically 15 fps but my old laptop didn't manage to
 decode more than about 2 x 10 fps).

 YUY2:
 All combinations up to 2 x 640x480 (15 fps).
 960x720 (10 fps) + 640x480 (15 fps).
 1280x960 (7.5 fps) + 640x480 (15 fps).

 The following failed with error -28:

 YUY2:
 2 x 960x720 (10 fps).
 1280x960 (7.5 fps) + 640x480 (15 fps).
 1280x960 (7.5 fps) + 960x720 (10 fps).

 That should give you some indication of what you should be able to  
 achieve
 with ffmpeg in terms of resolutions.

 Cheers,
 Martin
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Experimental patch for USB problem with Logitech webcams

Hey Vidar,

Could you try changing the line that reads

if(ret = 0 || ret != -EPIPE)

to

if(ret = 0 || (ret != -EPIPE  ret != -ETIMEDOUT))

to see if the camera recovers from error -110 (ETIMEDOUT) in the same way  
as it does from -32 (EPIPE)?

I don't know much about store return policies but from my past experience  
some shops are pretty nice about that. Especially if you pretend to be an  
unexperienced user and tell them that the camera just doesn't work. ;-)  
Anyway, we're obviously trying our best to come up with something that  
will save you from returning your camera.

Cheers,
Martin



On Wed, 08 Nov 2006 20:06:08 +0100, Vidar Normann [EMAIL PROTECTED]  
wrote:

 On 11/7/06, Martin Rubli [EMAIL PROTECTED] wrote:
 Hi all,

 Attached is a rather ugly patch that has proven to make the Logitech UVC
 cameras work fine for some people. It works around the USB errors by
 retrying control requests up to three times.

 We would like to get as much feedback as possible, so if you try it out,
 please let us know whether or not it works for you.


 I'm using the patch and on one camera it is able to record 20+
 times before I start seeing this error in dmesg:
 uvcvideo: Failed to query (1) UVC control 1 (unit 0) : -110 (exp. 26).

 As this is for a surveillance system I need these cameras to work all
 the time, and I probably won't be allowed to return them to the store
 since I've used them - My only hope is that Logitech fixes this or
 that you uvc-developers have a functional workaround. :)

 Is there anything I should post or do to help you (and myself) out?

 Regards,
 Vidar
 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel


___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Experimental patch for USB problem with Logitech webcams

Hey George,

 I am also a victim of this issue... FWIW i found the patch worked fine
 last time I tried it (i have since updated from SVN, and as I run
 motion which just opens the camera and keeps it open, the bug doesnt
 hit me that often, so I havent bothered to reapply. However, if my nfs
 drive goes down, motion crashes, and it needs to be re-opened, and
 sometimes I therefore have the problem, hence my interest.).

Just to make sure I understand you right: For you, the bug appeared both  
during opening and capturing but the retry patch fixed the capturing  
problem?

 My question is - even though this is a (nescesary) ugly workaround,
 will it ever be merged into the 'offical' driver?

Absolutely. We still want to find the nicest possible workaround, but  
_something_ will be integrated in the official driver.

 im guessing the 'offical' windows driver must have something similar
 in it to overcome the hardware bug...
 has anyone tried sniffing a windows session on the USB to see if does
 anything like these resets?

That's the thing. On Windows, the hardware bug simply isn't triggered. The  
timing of the USB packets is slightly different on Linux and Windows and  
apparently that's enough to trigger the problem.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Experimental patch for USB problem with Logitech webcams

On Fri, 10 Nov 2006 17:05:59 +0100, Evgeny [EMAIL PROTECTED] wrote:

 Other errors that were reported to occur are EOVERFLOW and EPROTO but  
 those are pretty rare and therefore more difficult to test.

 Martin, is there good reason why not to resend USB control message in  
 case of
 EOVERFLOW, EPROTO or any other error?

Only because I wasn't able to test it; they don't happen on my machine. If  
you get these errors and can test if retrying helps, please let us know  
the results ...

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Experimental patch for USB problem with Logitech webcams

On Sat, 11 Nov 2006 00:06:17 +0100, Nick Wiltshire [EMAIL PROTECTED]  
wrote:

 On Friday 10 November 2006 06:04, Martin Rubli wrote:
 That's the thing. On Windows, the hardware bug simply isn't triggered.  
 The timing of the USB packets is slightly different on Linux and  
 Windows and apparently that's enough to trigger the problem.

 Is this something that should be addressed in the USB subsystem? Is  
 either the Linux or Windows way right or wrong, or just different?

Just different, unfortunately. The error is clearly in the hardware and  
there isn't much the USB subsystem can do about it since the EHCI driver  
just programs the controller and the actual timing depends on the  
controller. At which point the difference springs into existence is  
something I haven't understood yet and nobody was able to tell me.

We were talking to the Linux USB stack developers a few weeks ago but  
there was no conclusion about this particular problem.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Non-Logitech UVC cameras.

On Fri, 10 Nov 2006 21:27:31 +0100, Laurent Pinchart  
[EMAIL PROTECTED] wrote:

 are there any non-Logitech UVC cameras, which do not experience control
 request problems?

 None that I know of. On the good side, newer Logitech webcams will  
 (Martin might be able to confirm) either implement a workaround in the  
 firmware, or use a different chipset with no hardware bug (or at least  
 not that particular bug :-)).

I can't confirm anything at this point but the next generation of Logitech  
cameras are extremly unlikely to contain the same bug for the very reasons  
that Laurent mentioned. Obviously, now that we know about the problem, we  
will keep an eye on the bug for future cameras.

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Logitech Orb won't pan/tilt in 704x576 resolution

Hi,

As a certain other company would put it: This behavior is by design. ;-)

If you try the same thing on Windows, you will see that the pan/tilt
buttons are disabled for resolutions higher than VGA. It's a limitation of
the hardware.

Cheers,
Martin


On Thu, 02 Nov 2006 15:41:44 +0100, Noble Pepper
[EMAIL PROTECTED] wrote:

 Hello again.

 I just installed a USB2.0 interface in my desktop box so I am playing  
 with
 the higher resolutions available with the Orb.

 In 320x240 and 640x480 resolutions, the pan/tilt operates fine in both
 luvcview and motion.

 When I go to 704x576 I get errors and the camera doesn't move

 In luvcview I get:
 ioctl pan updown control error
 Set Pan up error
 ioctl tiltupdown control error
 Set Tilt up error

 In motion I get:
 [0] Failed to move camera!: Input/output error
 [0] httpd - Read from client: Input/output error

 Since both apps have similar problems I am assuming this is a driver or
 hardware problem.

 Is this a known issue?

 Are you interested in pursuing this?

 I am going to try to get more detailed info but any tips would help at  
 this
 point.



 ___
 Linux-uvc-devel mailing list
 Linux-uvc-devel@lists.berlios.de
 https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Changing and Jumbled picture from uvcvideo driver using Logitech 046d:08c2 USB Webcam

Hi Larry,

 3.  But all the video producing applications I've tried so far,  produce
 a jumbled picture such as this 7 kB sample viewable at

 http://foxgulch.com/Miscellaneous/snap.jpg

 If you look closely, you can see parts of my face,  but not in the
 sequence my Mother intended. {;-)

Does this happen in JPEG and YUV mode? You can test this with the help of
the -f option when launching luvcview.

What about different resolutions? It would be great if you could post some
more samples. I've never seen anything like this, although it reminds me
of some pictures where the Y, U, and V channels were screwed up. (But that
couldn't possibly occur in JPEG mode.)

 4.  That  above jpg was produced with uvccapture.   Under
 luvcview20060920,  I can control the pan/tilt etc of the 046d:08C2
 logitech orbit/sphere usb web camera.  However the fps number shown at
 the top constantly varies and the picture is repeatedly  similarly  
 jumbled.

Again, rather strange behavior. Does your camera work on Windows, just to
be sure?

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] HP dv2000 laptop

On Wed, 25 Oct 2006 21:07:17 +0200, Laurent Pinchart
[EMAIL PROTECTED] wrote:

 Your webcam might not have sound support.

 uvcvideo is a video-only driver anyway, I don't know much about USB audio
 support. You could try asking the snd-usb-audio developers, but if the  
 driver doesn't recognize the webcam, it probably doesn't have sound  
 support.

Indeed. Webcams built into laptops are very unlikely to have audio support
because laptops already have mic and speakers. I would check out some of
the Linux compatibility websites to see if you can get the built-in audio
to work on Linux.

http://www.linux-laptop.net/
http://tuxmobil.org/

(I'm sure there are others ...)

Cheers,
Martin
___
Linux-uvc-devel mailing list
Linux-uvc-devel@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel

Re: [Linux-uvc-devel] Maximum framerate with multiple USB 2 cameras?