[MPlayer-users] BUG: -ovc xvid -xvidencopts not working ?

[Martin Hoffmann]

I have just tracked down the problem a little bit further (unfortunately not 
solved yet :-( ):

It depends on the order of the parameters of -xvidencopts:
If i use -xvidencopts nodebug:br=1000000:mode=2pass-1 then every thing works 
fine !
If i put the mode=2pass-1 at the beginning of the line -xvidencopts 
mode=2pass-1:br=1000000:nodebug then everything behind mode is ignored ! Even 
unknown parameters ! Seems to have something to do with the subconfig for 
mode !???

Another "problem" in ve_xvid.c seems to be that br=nnnnn has to be specified 
in bits/s - no support for kbit/s like ve_divx4.c has it ! Is this intended ? 
I know that this is easy to implement, i just want to know if its intended 
this way ....

Martin

> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
>
> On Saturday, 19 October 2002, Martin Hoffmann wrote:
> > [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> > Hi,
> >
> > are the options specified via -xvidencopts already working ? It seems
> > they are completely ignored !?
> > I took a quick look into the source but couldn't find the cause - it
> > seems to me that the config (from commandline) is ignored - everything
> > that is set in the struct as default values overrides the commandline
> > parameters ! However the commandline paramters seem to be only parsed
> > correctly (error message for non existant -xvidencopts) when called
> > without input file ;-) If you specify non-existant -xvicencopts with real
> > input file and then no message is generated :-(
> >
> > I hope you understand what i meant!
>
> RTFbugreports.html. Does your mplayer have xvid support compiled in at all?