[MPlayer-dev-eng] What happened to deinterlacing?
Felix Buenemann
atmosfear at users.sourceforge.net
Tue Oct 16 16:50:26 CEST 2001
On Tuesday, 16. October 2001 16:08, Michael Niedermayer wrote:
> On Tuesday 16 October 2001 15:10, marpet at linuxpl.org wrote:
[snip]
>
> > :-)
> >
> > Question: is the postprocessing optionset going to standarize in some
> > way? Currently it is a bit messy - any ideas where it is going to go?
>
> no clue :)
> commandline options would be a nice thing, something like
> -deint=linblend
> -denoise=temp,25 (25 is the threshold to use)
> or
> -deint-linblend
> -denoise-temp=25
> or
> ...
hmm how about adding a function like getppmodebyname() that is fed with a
string from the commandline in the form of:
-pp deblock1,linblend,tmpdenoise:25,lumdering or something in that way?
Hmm, but it gets problematic the moment we use additional parameters (cause
we can't simply map a string to a pp value and add it to the flags) so maybe
it's a better idea to split it up like this:
-deinterlace linearblend
-dering luma,chroma
-deblock rk1v,rk1h
-levelfix
and we could define some defaults for each switch that are used when called
without paramters like only -deinterlace.
And another very cool thing would be to rate the pp's by quality and speed
and depending on free cpu time use the faster or the better looking
algorithmn (for -autoq).
>
> Michael
--
Best Regards,
Atmos
____________________________________________
- MPlayer Developer - http://mplayerhq.hu/ -
____________________________________________
Software is like sex: it's better when it's free.
- Linus Torvalds
More information about the MPlayer-dev-eng
mailing list