Mencoder and XVID with Large Files

[RickG8]

Hi,

I'm using Mencoder to produce XVID files (overnight with a scheduled task). I've tried using 2-pass, fixed_quant, get decent results all through with just one big problem - if the output goes over 1GB, it won't play in WMP or any other player I've tried (VLC, DIVX Player etc.). The player either just doesn't display or I get errors that it cannot be played. I've tried the DivX, Xvid and FFDSHOW decoders.

Anyone have any ideas why the files won't play? G-Spot thinks that they are fine...

Thanks,
Rick

[haubrija]

I beleive I'm having the same issue. Anyone got any advice on this?

[mcqweb]

I'm also having the same problem, I think it might be to do with openDML, not had a chance to try yet but I believe mencoder has this option -noodml to turn it off

[celtic_druid]

Should work, as long as you don't go above 2GB's. By default mencoder inserts a new RIFF chunk every 1023MB's, once that happens I guess a lot of things can't read the resulting avi. Maybe try remuxing with AVIMuxGUI? Perhaps it creates openDML files that are more compatible?

[stephanV]

Not being playable at all is weird, since at least the first RiFF chunk should be able to be parsed i think by standard AVI parsers.

Since you created the files with mencoder, you should at least try mplayer first before you start remuxing and trying other stuff. (but VLC not working is not a good sign)

[RickG8]

Thanks for the suggestions. So is it possible to tell mencoder not to chunk RIFFs (whatever the hell that is!!). :)

[Pookie]

Perhaps running Avimaster on the XVID files ?

http://www.thozie.de/avimaster/

[ChronoCross]

I'm going to confirm this bug as well. The resulting avi is unreadable by anything. I can't remux it into something else and it's nothing but a black screen when trying to play. it's 1.3GB of blackspace.


EDIT: Also tried remuxing with avimuxgui and it gives a cannot read from video source error. MKV and MP4 muxing produces 4kb files. Any suggestions?

[RickG8]

I've tested this out now, and I can confirm that the -noodml argument fixes this problem. Thanks guys!

Rick