Hi all, 

comparing the V4L implementation of Wengophone classic 
(libs/webcam/src/v4l-driver/WebcamV4l.cpp)
and NG (libs/webcam/src/v4l/V4LWebcamDriver.cpp) I noticed a completely 
different architecture.
While classic makes use of a timer in order to trigger the capturing of a 
frame, the NG driver
consists of a loop that sleep for 1/fps seconds and then captures a frame. This 
rather simple
approach raises problems when trying to use higher frame rates (e.g. desired 
framerate = 25 fps,
resulting in a sleep of 40ms - however an additional execution time of 20 ms of 
the rest of the
loop results in a loop interval of 60ms on my machine, lowering the framerate 
to a jittery 15
fps).

I would like to ask about the motivation of leaving the more sophisticated 
(classic) approach in
favor of the new implementation which is not really usable for high bitrates 
and quite
undeterministic.

Thanks in advance
Matthias Schneider


                
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to