Q) Why do I get a bunch of errors like:
   v4l1_core_next(595): New frame out of sequence - ignoring3 Warp: 0 Drop: 0
   nvcore_main(422): Error getting more video data. Trying to continue.

A) These errors are caused by the timing info of the frame disagreeing with
the time the frame _should_ have.  There are two main causes of this:
1) You are using a v4l1 driver in a non-PAL country - The v4l1 driver does not
report the video standard or frame rate to the application, so it needs to
be set explicitly with "-norm NTSC".
2) A few of these errors are bound to occur anyway due to clock jitter.  The
problem is slightly improved with v4l2, but is impossible to alleviate
entirely, unless the capture card has clock recovery...

