[MEncoder-users] Problems when creating video dvd

Oded Shimon ods15 at ods15.dyndns.org
Mon Jan 16 18:26:55 CET 2006


On Mon, Jan 16, 2006 at 06:21:17PM +0100, Guillaume POIRIER wrote:
> Hi,
> 
> On 1/16/06, Sebastian <sebastian_ml at gmx.net> wrote:
> > On Mo, Jan 16, 2006 at 12:39:04 -0400, Giacomo Comes wrote:
> > > Using -nosound is also a bad idea. In order to test stuffs (options,
> > > dvdauthor, mplex, etc) I would suggest you to encode only a small
> > > portion of the movie. You can use -frames 10000 in order to encode
> > > few minutes. Test the results and when you have found a working
> > > command line, encode the whole movie.
> >
> > You're right, will do. I just get this feeling that this is all about
> > "harddup". I left it out because I didn't see it in the guide ->
> > http://www.mplayerhq.hu/DOCS/HTML/en/menc-feat-vcd-dvd.html
> > It definitely is in there, but too late, in the "Putting it all
> > Together" section. It should be mentioned early on (with a short explanation
> > of its meaning, what it does and why one needs it for mpeg encoding).
> >
> > Anyone cares to change that? :)
> 
> I could change it, but I need to be dead sure that this option is
> absolutely necessary. Nico, can you confirm?

I can confirm - without harddup, MEncoder uses "0 byte frames" to make a 
fake delay, to constrain to fixed fps. 0 byte frames are legal in AVI, but 
the are completely illegal in MPEG and will most likely even make the mpeg 
muxer fail, as it has a framer that reads the frames given it.

it's either harddup, or -mc 0 -noskip, or just pure luck that mencoder for 
this specific file didn't give you any duplicate frames.

- ods15




More information about the MEncoder-users mailing list