Megui x264. Argument Error for every b-pyrimid option

[k2snowboards88]

I am using version 0.3.1.1056 of MeGUI. I tried updating to the newest version of x264 (1318) at x264.nl. I've been getting an argument error no matter what I set the b-pyramid option to. Here is an example:

An error occurred: x264 [error]: invalid argument: b-pyramid = --b-bias

Here is another:

An error occurred: x264 [error]: invalid argument: b-pyramid = --direct


Do you know whats wrong? Or even better, do you know a fix?

[XhmikosR]

You can use latest 0.3.1.1057 which has been updated to reflect the latest x264's changes, but it has a bug and will delete all your x264 profiles. The best would be to stop using MeGUI until it gets fixed, or use another GUI, or even better don't even use a GUI; encode via command line.

[k2snowboards88]

Is it worth updating to the latest version of x264? Are there substantial quality or speed gains? Aside from moving files around and compiling java applications, I don't have much experience in the DOS command line (i have some more experience in unix). Is there a good guide somewhere for the the command line version of x264?

[XhmikosR]

x264 IS a commandline application. MeGUI is a GUI for x264. Personally I always update to the latest version of x264. Not so many speed gains, since it's already optimized, but quality improvements. Take a look at some of the commits in the GIT repository (http://git.videolan.org/gitweb.cgi?p=x264.git;a=shortlog) to just get an idea of its development. First thing you should do if you want to encode via cmd, run x264 --help and you'll see all the various choices. You can even use the builtin presets to make things easier.

[Anacletus]

I am using version 0.3.1.1056 of MeGUI. I tried updating to the newest version of x264 (1318) at x264.nl. I've been getting an argument error no matter what I set the b-pyramid option to. Here is an example:

An error occurred: x264 [error]: invalid argument: b-pyramid = --b-bias

Here is another:

An error occurred: x264 [error]: invalid argument: b-pyramid = --direct


Do you know whats wrong? Or even better, do you know a fix?

That is happening because the newer builds of x264 use a different command line where you should pass a value for --b-pyramid (none, strict, normal) whereas MeGUI uses the old commandline where b-pyramid comes with no values.

So getting back to your example x264 is taking as value for --b-pyramid the next parameter in the commandline, in your examples "--direct" and "--b-bias" :mad:

[lnatan25]

So any idea when an update to 0.3.1.1057 will come out to fix x264 bugs and profile-removal bugs? :rolleyes:

[Dark Shikari]

So any idea when an update to 0.3.1.1057 will come out to fix x264 bugs and profile-removal bugs? :rolleyes:You could stop complaining and, in the meantime, switch to a GUI that sucks less and is actively maintained, like Staxrip, Handbrake, Ripbot264, HDConvertToX, and so forth.

[lnatan25]

Actually all the ones you mention suck a lot more than MeGUI when aesthetics are concerned, but whatever. Stop complaining yourself, just asked a question. Deal with it.

[Dark Shikari]

Actually all the ones you mention suck a lot more than MeGUI when aesthetics are concerned, but whatever. Stop complaining yourself, just asked a question. Deal with it.You asked an obviously rhetorical question which you don't expect to be answered, hence the eyeroll and trolling in your post.

[lnatan25]

Actually the eyeroll was because it's now 26/11 and last response here was 2/11, so it was more in the lines of "how longer do we have to wait". Check your trolling decoder for spec-violation bugs. http://www.nfohump.com/forum/images/smiles/face.gif

[Atak_Snajpera]

Actually all the ones you mention suck a lot more than MeGUI when aesthetics are concerned, but whatever.
I can't wait to see your gui amigo! We will judge later.

[prOnorama]

You could stop complaining and, in the meantime, switch to a GUI that sucks less and is actively maintained, like Staxrip, Handbrake, Ripbot264, HDConvertToX, and so forth.

You have a good point about the actively maintained part but if these alternative GUI's were better than MeGUI (better as in give full user control over x264 and other options) there wouldn't be so many ppl asking for MegUI to get fixed :)

It's not that I don't want to switch to another GUI but the GUI's mentioned above don't give me the amount of control I want (RipBot), or I don't like the way they work (StaxRip, HDConverttoX). Having said that I see there's a new version of Handbrake with the latest x264 build, I'll try that out again.

[MKVCrazy]

MeGUI doesn't suck. It's probably the best or if best is not a good word, then the most useful app than any other GUI I've seen on Doom9. It's really advanced and less CPU usage where others put things you don't know in the scripts and take more CPU usages. Super annoying. MeGUI is like set up the x264 you want, set up the script you want and go convert. Done!

I am also having that problem the b-pyramid -direct and please with respect do not reply here just to suggest another GUI. It's really not helping the problem. If x264 is too new for the MeGUI then will using an older x264.exe help? I'll try and see and reply back but I asked because I don't know how the details will be like if latest MeGUI is suppose to be used with one of the older x264.exe files or not etc.

[Atak_Snajpera]

Why don't you grab sources and fix this syntax error???? Everybody is crying but at the same time everybody has two left hands.

[lnatan25]

Why don't you grab sources and fix this syntax error???? Everybody is crying but at the same time everybody has two left hands.
You are 100% correct, will do that.

I can't wait to see your gui amigo! We will judge later.
Excuse me? So now anyone that doesn't have a GUI can't criticize? Yeah, that shows real maturity and real confidence in what you do. :rolleyes:

[prOnorama]

Why don't you grab sources and fix this syntax error???? Everybody is crying but at the same time everybody has two left hands.

Sadly I wil fully admit I do not have the knowledge for that, I'm not a programmer.

Still I'm hoping someone will take your suggestion at heart and pick up MeGUI development again :)

Would be sad to see this GUI go down the same path as GordianKnot which I liked in the past for Xvid encoding.

[crackerjohn]

http://s54.radikal.ru/i143/0911/bb/a52e83f1ae44.png

setting like this will avoid this error but it may has a big influence to quality....

[Schra]

Why don't you grab sources and fix this syntax error???? Everybody is crying but at the same time everybody has two left hands.

I have two left hands, too. But these hands tried to change a few things. Maybe it is helpful:
http://forum.doom9.org/showthread.php?p=1347860#post1347860

[thehurricane]

Regarding the error, the syntax mismatch in 1056 can easily be got around by unchecking 'Keep some B-Frames as reference' in Frame Type and entering a custom parameter for x264 in the Misc tab. For b-pyramid it would be --b-pyramid strict or --b-pyramid normal (depending on if u want a strictly hierarchical pyramid or not).

BTW is it really a bug in 1057 coz I compared the scratchpad profile xml in 1057 with a profile xml in 1056 and found that the elements for mixed frames and the value types for BFramePyramid were different. On changing those, 1057 accepted the profile as a valid one & didnt delete it.

Took me 6 days to encode an hr long video with 2pass insane settings in build 1057 (Yea I know I have a bad processor. Moreover, it's a laptop). Cool huh.

[lnatan25]

It's not a bug, the profiles just need to be updated for the new version.