Hmm... I knew it was something obvious ;)

Ive changed the polling policy to wait policy and works very well.

Im curious abut the DC1394_NO_FRAME, How can I test that idea ?
Is only for handel errors?


On Mon, May 16, 2011 at 1:51 AM, Byron Guernsey <byron.guernsey@ikotech.com> wrote:
What is the value of err, is it by chance DC1394_NO_FRAME (-2 I believe)? the DC1394_ERR_CLN_RTN() macro won't exit if its a warning or info error, and anything < 0 is info/warning.

Since you are dropping your frame rate when the problem occurs, its possible that your main loop is running faster than the frame rate. If you don't want to check for DC1394_NO_FRAME, change your polling policy to DC1394_CAPTURE_POLICY_WAIT


On May 15, 2011, at 8:54 AM, Salvador Garcia Bernal wrote:

> in the capture section:
> err=dc1394_capture_dequeue(camera, DC1394_CAPTURE_POLICY_POLL, &frame);
> DC1394_ERR_CLN_RTN(err,cleanup_and_exit(camera),"Could not capture a frame\n");

Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
Mailing list for libdc1394-devel