[MEncoder-users] x264 questions
Rich Felker
dalias at aerifal.cx
Tue Nov 6 19:50:25 CET 2007
On Tue, Nov 06, 2007 at 09:14:32AM +0100, Reimar Döffinger wrote:
> Hello,
> On Mon, Nov 05, 2007 at 10:22:28PM -0500, Rich Felker wrote:
> > On Mon, Nov 05, 2007 at 08:37:32PM -0600, James Hastings-Trew wrote:
> > > Two separate questions regarding x264 encoding in mencoder:
> > >
> > > 1) does setting frameref to something other than 1 make a difference if
> > > there are no bframes? I've read the relevant section in the manuals and
> > > am still unclear.
> > >
> > > 2) This message has been a very long standing feature of Mencoder:
> > > > ** MUXER_LAVF
> > > > *****************************************************************
> > > > REMEMBER: MEncoder's libavformat muxing is presently broken and can
> > > > generate
> > > > INCORRECT files in the presence of B frames. Moreover, due to bugs MPlayer
> > > > will play these INCORRECT files as if nothing were wrong!
> > > > *******************************************************************************
> > > Is this going to be resolved? - i.e. will Mencoder ever be able to mux
> > > to an .mp4 container with a video stream that contains b-frames?
> >
> > Basically no one is working on mencoder and it's so broken that few of
> > us are interested in it unless it's greatly overhauled. I would
> > recommend just using it to do the video stream if you need the
> > powerful filtering it provides, then using the ffmpeg program for the
> > muxing and anything else.
>
> Regardless of this, are you sure the message above still applies? At
> least the i_certify_... option was removed so I assumed it was at least
> mostly fixed.
Nope, nothing was fixed. The files will still be horribly broken.
Someone just removed that option without asking me while I was away
over the summer and replaced it with the above warning banner... :(
Rich
More information about the MEncoder-users
mailing list