[MPlayer-users] Re: [-] Re: [-] TV-recording with mencoder, "video-buffer full"

[D Richard Felker III]

On Mon, Feb 28, 2005 at 10:26:39PM +0100, Matthias Wieser wrote:
> Am Montag, 28. Februar 2005 17:01 schrieb D Richard Felker III:
> > On Mon, Feb 28, 2005 at 12:23:50PM +0100, Matthias Wieser wrote:
> >
> > > You could try pp=fd instead of pp=lb. The former should give a
> > > sharper image quality.
> >
> > Bad suggestion, IMO. If you're going to use pp=fd, just capture a
> > single field (height=288) instead. The quality will be comparable
> > either way,
> 
> My tests show the opposite. (http://home.knuut.de/MWieser_/index.html)

The opposite of what? I didn't say pp=lb looks good (in fact it's very
bad). What I said is that pp=fd essentially throws away a whole field,
and it has other flaws, so it should never be used.

> > since pp=fd essentially throws away one whole field
> 
> ..only when it actually needs to deinterlace. Static scenes show much 
> better quality than pp=md, pp=ci, and so on.

pp=md or perhaps kerndeint throws away the least for static scenes.
But both still have underirable side effects. It's impossible to fix
the fact that interlacing is fundamentally mathematically flawed. All
you can do is lessen the ugliness.

> > (but also adds edge ghosting from the other field -- very ugly!)
> 
> I have never seen those edge ghosting. Do you have screenshots?

Yep, I'll make one right now:

http://brightrain.aerifal.cx/~dalias/lavcdeint_sucks.jpg

This shows 3 frames from telecined content, so you see how the 'ghost'
of one appears in another. Also notice how bad the thin nearly
horizontal lines get aliased by the filter.

> > and single-field capture will use a LOT less cpu time
> 
> ...and give a LOT less quality. If someone has a >2GHz Athlon, kerndeint 
> should be worth a try. It's imho the only deinterlace included in 
> Mplayer, that does not decrease the quality of static scenes.

The only remotely correct deinterlacer in MPlayer is vf_tfields. :)
But it's only usable with MEncoder, and requires nasty hacks to trick
to make it get the framerate right.

In case you don't know, tfields deinterlaces to 60fps (or 50fps for
PAL) output, so you actually get the full advantage of the high
fieldrate rather than throwing half the information away
(essentially).

Rich