[MPlayer-dev-eng] [PATCH] v4l2 interface

[Arpi]

Hi,

> On Mon, Jan 13, 2003 at 11:42:14PM +0100, Arpi wrote:
> > if you don't report or report bad/inaccurate timestamps, it will think
> > the streams are desynced and tries to correct it...
> 
> Ok, just two more questions to be sure, because I don't want to do
> unnecessary work:
> 
> Is this also true, if just one ore two frames have an incorrect
> timestamp and the next one is ok again,

no
it averages timestamps over time, so small errors are ok.

> as in the example I gave?  Or
> is it then just a theoretical possibility not worth bothering?
> 
> Is all of this also true for TV input?  I don't know what
> `default_max_pts_correction = 0;' means.

max_pts_correction sets the upper limit of timestamp correction per frame,
in seconds. if you set it to 0, you disable this correction (see -mc 0),
but i don't recommend that. maybe set to something lower than default 0.01,
for example 0.001 (+-1ms/frame correction allowed)


A'rpi / Astral & ESP-team

--
Developer of MPlayer, the Movie Player for Linux - http://www.MPlayerHQ.hu