[MPlayer-dev-eng] comprehensive lavcopts test - in progress.

[Roman Gaufman]

Well, again, in this case I need info about what options depend on what 
options.

On Monday 14 June 2004 15:11, Michael Niedermayer wrote:
> Hi
>
> On Monday 14 June 2004 16:59, Romain Dolbeau wrote:
> > Roman Gaufman wrote:
> > > So what we end up is: 99 lavcopts
> > > 			       3 preopts for each lavcopt
> > > 			       4 files (2 pass each)
> > > 			       2 vbitrate settings (900kbit ad 1600kbit)
> > > 				= 2376 tests
> > >
> > > Not too many, but seems quite comprehensive. Just to explain in words,
> > > 99 lavcopts will be tested with 3 preopts for EACH lavcopt. Those 297
> > > tests will be tested for 4 files with 2 different video bitrate
> > > settings (once with 900kbit and once with 1600kbit), this makes a total
> > > of 2376 tests.
> > >
> > > cmd="mencoder %s %s -nosound -ovc lavc -lavcopts
> > > vcodec=mpeg4:vbitrate=%s:psnr:autoaspect:vb_strategy=1:vratetol=32000:v
> > >pa ss=%s: %s -o videoout/%s-%s-%s'             % (x,z,y,i+1,opt,n,x,y)"
> >
> > I'm missing something here. You're only going to test one option
> > at a time ? In that case, I believe results won't mean much,
> > as in many cases one option may change the usefullness of another.
> > For instance, in my experiment, the order of quality for
> > *cmp is 6>2>3 w/o qpel and mv0, but 3>2>6 w/ qpel and mv0.
> > So testing those 3 separately won't make sense.
>
> btw, it would be interresting to know how many local minima are there in
> your results
> i mean cases where no single changed option leaded to an improvement