hi mathieu,
thank you for your answer ...
[quickcam pro 5000 with uvc]
driver. The uvc driver is still very new, and last time I checked, it seemed a bit flaky, though maybe this has already changed (?).
it seemed to be quite stable with the few applications that support its v4l2-interface - namely, ekiga and its very own uvcview.
[v4l/v4l2]
redefining ioctl to be something else, so as far as V4L2 goes, there's no difference between the user and the userspace, because it's just a kernel interface.
This basically means that V4L2 is difficult to support because one is supposed to be supporting all of its color models. (Is it me, or the smiley makes it sound worse than without a smiley?)
phew, that might be okay from a kernel programmers viewpoint - it really sucks for anyone else. as long as there is no tried-and-tested middleware that does color conversations, decodes mjpeg streams and all those things, it's up to the developers of v4l2-applications to reinvent those wheels for every usb camera and every colour space out there. that's plain - inefficient. gstreamer might be able to do exactly this one day, hopefully. the loopback device for v4l looked promising as well, but is not maintained anymore.
The quickcam 4000 pro stops at 15 fps for that resolution. At 320x240 it goes up to 30 fps but limited to increments of 5 fps.
blimey. i kind of came to terms with using a dv cam already and live with the 50% performance penalty ...
with kind regards, thoralf.
___________________________________________________________ What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship. http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk