viragoboy schrieb:
I purchased the same webcam on woot several weeks ago and I've been
watching this group hoping to get the thing working. Right now I'm
getting the same results as Scott, and I thought that maybe I could
help out a bit since I know how to code in C and C++.

If anyone could point me in the right direction about what section of
code causes the effect that Scott described then I can toy around with
it.


--~--~---------~--~----~------------~-------~--~----~
Lets make microdia webcams plug'n play, (currently plug'n pray)
To post to this group, send email to [email protected]
Visit us online https://groups.google.com/group/microdia
-~----------~----~----~----~------~----~------~--~---


The situation is this:
We've given up on image decoding in the driver and used libv4l to move that part into userspace. All we do is try to give libv4l a correctly labeled image stream that will be decoded and passed on to the application.

The only part way something like this can happen is if we give libv4l other data than we promised.

The causes for that can be various:
- Wrong settings in the cam (sensor or/and bridge chip)
- bad transmission from webcam to pc (bandwidth problems, etc.)

I think something like that is happening but I currently don't have the time or ideas on how to investigate this remotely.

GWater

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to