Log in

View Full Version : megui will not set "-max_bframes 0" in xvid_encraw


Blue_MiSfit
5th February 2007, 04:24
Hey everyone,

So a friend of mine has me working up a procedure for him to put his DVDs on his iPod, so that he can take them with him, and play them on a TV with the video out dock.

Anyway, he has a 5g (not a 5.5), so that means for good resolution (over 320x240) vanilla MPEG-4 is required, no more than 1500kbit, and no bframes, CQMs, or other advanced settings. Fine.

I decided to shoot for a 640x_ resolution, as this is a good compromise between 320 and 720, and is pretty "standard" - whatever that means. 1500kbit should ensure good quality with this resolution for most material.

Indeed when I do a 2 pass encode with either vdub or megui (xvid_encraw) everything looks great. Very watchable, albeit not quite what I'm used to with full resolution high bitrate x264 with ffdshow's lanczos + noise.

The strange thing is that even though the output of both encoders (vfw and xvid_encraw) plays just fine on my PC, and even in quicktime, no matter what settings I use for xvid_encraw, I cannot get it to play correctly on the iPod.

Whatever I use, playback is totally b0rked, with green evilness all over the place, and frames decoding out of order... hard to describe, but violently evil. Then, the same settings (encoded with vdub and muxed to mp4 with yamb) work perfectly.

I'm wondering if anyone else had run into this, and if a solution is known. I taught my friend how to use MeGUI, and it's a lot simpler than doing everything manually with vdub.

~MiSfit

Blue_MiSfit
5th February 2007, 04:29
*Update

I ran both mp4s through gspot, and the one created using xvid_encraw has bframes, even though I explicitly set bframes to 0 in megui. Is this a bug? Title edited to respect this, original post below.

Here's the command line for first pass:

encoder commandline:
-i "E:\Closer\Closer.avs" -pass1 "E:\Closer\Closer.stats" -bitrate 1204 -kboost 100 -overhead 0
-max_key_interval 240 -nopacked -closed_gop -lumimasking -threads 1


and second pass

encoder commandline:
-i "E:\Closer\Closer.avs" -pass2 "E:\Closer\Closer.stats" -bitrate 1204 -kboost 100 -overhead 0
-max_key_interval 240 -nopacked -closed_gop -lumimasking -threads 1 -o "E:\Closer\Closer.m4v"

squid_80
5th February 2007, 04:38
Looks like "-max_bframes 0" is missing.

Blue_MiSfit
5th February 2007, 04:47
So that would be an issue with MeGUI right? Because I definitely set max bframes to 0 in there! :)

I setup another encode on another machine (my main rig) with MeGUI, setting max bframes to 0, and get the same behavior - it seems consistent.

Thanks for the reply squid_80.

~MiSfit

Sharktooth
5th February 2007, 14:57
Please report megui bugs to the sourceforge bugtracker or they will get easily ignored...
http://sourceforge.net/tracker/?atid=798476&group_id=156112&func=browse

squid_80
5th February 2007, 15:00
Foxyshadis already has. (I could have sworn he had a post here too, where'd it go?)

Sharktooth
5th February 2007, 15:01
you mean this? http://sourceforge.net/tracker/index.php?func=detail&aid=1652312&group_id=156112&atid=798476

squid_80
5th February 2007, 15:12
Yes. His post here was worded slightly better: "The bug is that megui incorrectly assumes the xvid_encraw default is 0 b-frames, not 2 b-frames."

Blue_MiSfit
5th February 2007, 21:37
Thanks for updating the bug report sharktooth.

I just wanted to make sure my logic was correct before submitting an incorrect bug report :)

foxyshadis
5th February 2007, 21:55
Yes. His post here was worded slightly better: "The bug is that megui incorrectly assumes the xvid_encraw default is 0 b-frames, not 2 b-frames."

I delete my posts when I notice someone else answers first, don't want to be redundant. :p Sorry for causing a head trip, but I figured I'd take it right to the source anyway.

Blue_MiSfit
6th February 2007, 01:49
Thanks to you all! :)

And "His post here" would be "her post here" if memory serves, right foxy? ;)

foxyshadis
6th February 2007, 07:36
Thanks to you all! :)

And "His post here" would be "her post here" if memory serves, right foxy? ;)

NO GRRLZ ON TEH INTERBUTTS

I'll usually give it a o.ô and move on, it seems rude to correct people. ^^;

I'd better stop before some mod strikes me for off-topic...

squid_80
6th February 2007, 14:56
Bah. Thread's virtually finished, not like we're hijacking it.

http://en.wiktionary.org/wiki/he
Definition 3: Another (person or animal) whose gender is unknown (with animals this includes dogs, rodents; see she).
Note: This usage is considered sexist by some. Compare he/she, s/he and they.

If anyone considers it sexist, I guess I'm just going to have to start calling everyone "it". :sly: