Hi, On Monday 28 June 2010 22:17:54 seno wrote: > Laurent Pinchart <laurent.pinchart <at> ideasonboard.com> writes: > > Thank you. The descriptors expose pan, tilt and zoom controls. That looks > > a bit weird for an integrated webcam. Could you try to modify them and > > see if they have any influence on the picture ? > > Let's first check if the pan/tilt and zoom controls have any influence on > > the image. > > Hello, > > it took me a while to find a way to set tilt/pan on a webcam, but finally I > found luvcview offers that options :) > > Result: > Image does not change at all. > > console output: > ioctl querycontrol error: Invalid argument > Set Pan up error > > ioctl querycontrol error: Invalid argument > Set Pan down error > > Same output for tilt and gain.
No very surprising. I wonder how hard it could be for vendors *not* to expose controls that they don't support. I would imagine that such things would not pass the most basic UVC test suite. They probably have none. > Setting brightnes, contrast, saturation, sharpness, gamma, exposure and > white balance works > > > Do you get 15 fps in Windows in 1280x1024 ? The camera seems to capture a > > full resolution image even when you select a lower resolution, and that > > might have an influence on the frame rate. > > The Windows BisonCam application doesn't show fps, so I opened the cam with > VLC Player and that reported 15 fps at 1280x1024 what might be correct as > the video runs smooth. Other resolutions run at 30 fps on windows. > > > You can ignore the video transfers (isochronous), but I'll need all > > control transfers from as early as possible until you start the video > > capture. > > > > As the camera is integrated in the laptop the initialization sequence > > performed at bootup won't be easy to capture, but with a little luck that > > won't be needed. > > The cam is integrated, but can be dis-/enabled by pressing Fn+F10. > So I did > - one USB trace while 'hotplugging' the cam and > - one trace when the cam already was connected and I started the BisonCam > application; I snipped the isochronous traces > > camera hotplug trace: http://www.loaditup.de/files/511048.txt > > start camera application trace: http://www.loaditup.de/511049.html > > I hope that helps for further investigation, please reply if you need > anything else... Thanks a lot for the information. Looking at the traces, the Windows driver sends lots of vendor-specific requests to the device. Even worse, it sends no UVC request at all. This means the device is handled by the driver in a vendor-specific way, and UVC compatibility is just a façade, probably to get some sort of certification for the device. That's pretty bad news, the vendor is cheating, and there's not much I can do on the UVC side. The device needs a device-specific driver that talks its proprietary protocol. It should be possible to support it in the gspca driver, but that will require someone developing support for it (don't look at me :-)). -- Regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
