Date: Thu, 18 Apr 2002 09:34:50 +0300 (EEST) From: Juha.Nurmela@quicknet.inet.fi To: freebsd-multimedia@FreeBSD.ORG Subject: Quickcam 3000 usb trouble Message-ID: <Pine.BSF.4.10.10204180846150.6767-100000@lpr-621.cable.inet.fi>
next in thread | raw e-mail | index | archive | help
Hello, What could be the problem reading Logitech Quickcam Pro 3000 images from usb ugen device, when the transfer looks right in size (bytecount), but there are runs of zerobytes in the data ? Linux pwc-driver (Philips usb webcams, has qc3000 support) is used as reference. Userland simple hack with ugen. The other parts of the cam work (audio/led/button) and video sort of works too, but: Image data is sensible, but there are repetitive blocks of (mostly) 0x00, length 10 bytes inserted. The transfer consists 8 bytes header, yuv data (320x240 5fps) and 4 bytes trailer, 115212 bytes total. Last packet is shorter than normal (isochronous mode, packet size 582). The transfer of an image is not supposed to contain other framing bytes than the header/trailer. The header looks good, the trailer does not. Pixel-data extends into the trailer-part, but there is no more data- nor trailer-bytes coming. Another header and similarly corrupt image comes along nicely after the flagging short packet. Some pixels are missing too. Otherwise the image seems crisp and clear, obviously jagged and twisted. This is on not-quite-up-to-date -CURRENT, btw. Computer (Abit KT7) is fast enough to stay in pace with the circular buffer of ugen, reads 582 many times then 552 once. Ideas ? Going to try smaller resolutions, Juha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10204180846150.6767-100000>