[MEncoder-users] Strange things when encoding with libx264: B frames, threads

[Etienne Buira]

On Sun, Oct 11, 2009 at 04:34:42PM +0200, Grozdan wrote:
> 2009/10/11 Etienne Buira <etienne.buira.lists at free.fr>:
> > Hello.
> >
> > I have troubles when encoding with libx264.
> >
> > I use mencoder SVN-r29766, and libx264 git
> > 39f6499e3abcf473bdcbade38aba9a7490470e6a (both updated at the same
> > time).
> >
> > When using a command line not specifying "bframes=0" in -x264encopts, B
> > frames are generated, despite the man page says that default bframes
> > value is 0.
> > However, if I specify "bframes=0", no bframes are generated. What's
> > wrong? My cmdline? man page? bug?
> >
> > Also, without specifying "threads=1" (like manpage says it is the
> > default), mencoder process uses more than 300% CPU (quad core). I have
> > the same questions about this issue.
> >
> > My typical command line is 'mencoder -o dest.avi -hr-edl-seek -edl
> > edl-file -oac faac -faacopts br=128 -ovc x264 -x264encopts
> > frameref=7:direct_pred=auto:partitions=all:8x8dct:me=umh:subq=7:mixed_refs:trellis=2:crf=21
> > source.ts'
> 
> Man page is highly outdated. Bframes are on by default if you don't
> specify anything. Threads is set to auto which will use all available
> cores

OK, so is there an accurate documentation somewhere? Or should we fall
back to the source (yeah, most accurate doc ever, but needs to be used
to mplayer source architecture, what I always failed to do).