Hi, On Wed, 2007-01-02, Andy Brown wrote: > So from what you explain, I cannot stop this from causing the device to > stop delivering the data and require the device to be closed then re-opened?
You don't need to close it, you just need to re-queue the frame for capture. I.e., your _application_ is responsible for handling te capture error. The driver doesn't crash or anything, it simply returns an error on he sync call, because the next frame could not be delivered (it got lost), probably along with a whole bunch of more frames if the interference is really bad. Simply discard them and continue queueing frames for capture and you should be fine. (Note, however, that this is the theory; in practice, we never actually test that. If you want, we can add a --ignore-frame-errors or so to lavrec and see if it really actually works, and fix possible driver errors, but that will require some small testing + patching from your side.) HTH, Ronald ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
