[MPlayer-dev-eng] 3 pass encoding syntax poll
Alexander Strasser
eclipse7 at gmx.net
Fri Feb 11 19:21:04 CET 2005
Diego Biurrun wrote ( On Fri, Feb 11, 2005 at 06:34:33PM +0100 ):
> Martin Drab writes:
> >
> > On Fri, 11 Feb 2005, Diego Biurrun wrote:
> >
> > > Martin Drab writes:
> > > >
> > > > Even better and IMHO clearer:
> > > >
> > > > 1 First pass (only generate log file)
> > > > 3 N-th pass (read, refine, and write log file)
> > > > 2 Last pass (only read log file)
> > > >
> > > > This fits to all cases.
> > >
> > > Boulderdash. Then 2 would come _after_ 3. How much sense could that
> > > make? None at all.
> >
> > The number cannot be swapped without breaking backwards compatibility.
> > Although I have nothing against that. I just think this expressing is the
> > one, that makes the stuff most clear. It really is like that, when you
> > want to do a 3-pass encode, you really have to do pass=1, then pass=3, and
> > then pass=2 !!
>
> Look, I don't know what kind of definition of clarity you have, but
> let me assure you that the rest of the world just expects 1, 2 and 3
> to come in ascending order.
>
> Perhaps using numbers is not a good idea in the first place and
> something like "first", "middle", "last" would be better.
I came up with the same words when thinking about it.
What about supporting 1 and 2 as we always did, drop 3 and additionaly
support first, middle, last.
But besides all names and stuff, examples in the man page and maybe
in the xml docs, are the way to go ( there would be also room for a
little chapter about 2+ pass encoding i think ).
Just a suggestion...
Alex (beastd)
More information about the MPlayer-dev-eng
mailing list