[MPlayer-users] Comparison of different deinterlace and denoise filters
Matthias Wieser
mwieser at gmx.de
Wed Oct 15 11:21:29 CEST 2003
Am Mittwoch, 15. Oktober 2003 02:11 schrieb D Richard Felker III:
> > Results:
> > - no visible difference between denoise3d and hqdn3d
>
> Agree. But...does the difference affect encoding quality?
I don't know. But even after Gimps "equalize" on the denoise3d PNGs I
could hardly see any relevant difference.
> > - pp=tn affects color ?!
>
> This filter is brain damaged by design and should never be used.
I know, but it's fast and because of it's description in "mplayer
-pphelp", some people will use it.
> It
> can and will ADD blocking artifacts to your movie (since it switches
> itself on and off on a per-block basis).
Woult it help, if the tn filter would fade out the denoising near the
edges of the blocks?
> > - pp=md looks similar to pp=fd
I found, that md produces jagged edges on interlaced parts. Does md use no
filter after deinterlacing?
> This is true for your test case. Not true at all in general. pp=fd
> will create ghosts for the same reason pp=lb does, however its ghosts
> come in the form of outlines rather than solid ghosts. Try a scene
> with motion.
I think, this effect is only visible, if you know, what you are looking
for.
Where can I find more information about how pp=md and pp=fd work?
> > - pp=lb is horrible for fast movements or moving text
>
> Agree mostly. Basically all deinterlacers are horrible...
50Hz (60Hz) Avis rock! ;-)
More information about the MPlayer-users
mailing list