[MPlayer-dev-eng] making -mc the default in mencoder
D Richard Felker III
dalias at aerifal.cx
Mon May 17 19:51:54 CEST 2004
On Mon, May 17, 2004 at 04:22:30PM +0200, Nico Sabbi wrote:
>
> >>Ivan Kalvachev
> >>
> >>p.s.
> >>If I understand correct "mc" is used to smooth dropping/dublicating.
> >>It's maximum value is maximum frame duration.
> >>
> >>
> >
> >mencoder uses a bad feedback system to measure A-V drift, because the
> >demuxers suck too bad to give correct pts which could be used
> >directly. The -mc option specifies how much the measured "A-V" value
> >is allowed to change each frame. Using high values for -mc means trust
> >the demuxer's pts, whereas low values will cause correction to take
> >place only when there is prolonged desync in the source. But skips &
> >duplicates for adjusting framerate (including inverse telecine) will
> >always take place immediately, regardless of -mc, unless -noskip is
> >also used.
> >
> >Rich
> >
> >
> >
> >
> >
>
> is it better to use -mc 0 or -mc some_large_value when the demuxer gives
> correct
> PTS that wrap around (mpeg ps/ts ) ?
If mc!=0 worked, it would be better to use large value for mc. But
since it _doesn't_ work (broken preload/buffering measurement), mc!=0
will always give wrong results (at least slightly). mc==0 will work
exactly if the source material is ok (even if it has resetting
timestamps), but not if it has "missing" segments of audio (supposedly
common for dvb).
Rich
More information about the MPlayer-dev-eng
mailing list