View Full Version : megui 0.3.1.1053 update broke x264: --no-mbtree doesn't exist anymore
florinandrei
30th August 2009, 05:54
Downloaded and installed megui 0.3.1.1053 from Sourceforge.
It prompted me to upload a bunch of things, including x264. I acknowledged the updates. It updated everything, including x264.
It restarted.
Now I'm trying to do an x264 encode, but it fails:
[NoImage] Standard error stream: C:\Program Files\megui\tools\x264\x264.exe: unrecognised option `--no-mbtree'
Obviously megui and x264 are out of sync now. Would be nice if everyone was on the same page w.r.t. to command-line options so that such a thing does not happen anymore. ;) Thanks!
Here's the Updater window, with the current versions of all important components after update:
http://imgur.com/VaOqa.png
MatLz
30th August 2009, 06:04
Hi. I didn't use this new build yet, but you can try the 1054 from here:
http://kurtnoise.free.fr/MeGUI/?M=A
florinandrei
30th August 2009, 06:23
Hi. I have not use this new but try the 1054 from here:
http://kurtnoise.free.fr/MeGUI/?M=A
I downloaded the core.....1054.zip, extracted the main megui.exe and used it instead of the one that caused the problem.
It works! I'm waiting to see the end result, but anyway, until then I'm happy it doesn't give the error anymore.
It's weird, but it encodes ~3x faster than megui 1051 (93 fps vs. 32 fps). I am using the Blu-Ray profile, modified for constant quantization = 25. Source is 480x480 SVCD MPEG2, I do deinterlacing with yadif+bob, rescale with spline36 to 640x480.
My guess: 1053 came with a newer x264 which is faster than the old x264, but couldn't run it because of the error, and now 1054 fixed the error and the new x264 is working faster than the old one. Is that correct?
MatLz
30th August 2009, 06:32
3x faster? Megui doesn't speed up the encoding, it's just a gui. I think your first pass is in "fast first pass" mode.
florinandrei
30th August 2009, 06:34
3x faster? Megui doesn't speed up the encoding, it's just a gui. I think your first pass is in "fast first pass" mode.
Actually, the profiles seem broken. I looked at the x264 options and that's definitely not the usual Blu-Ray profile. :(
florinandrei
30th August 2009, 06:36
Anybody has 1051 saved somewhere? It worked fine for me.
MatLz
30th August 2009, 06:49
I can't help you for profiles, I had never use it.
Ha, I forgot a thing with the update core:
Sometimes, you must delete the old folder with a config file from previous version.
For me it's in
C:\documents and settings\Mat\local settings\application data\ww.doom9.net\MeGUI.exe_Url_phe4d......\0.3.1.xxxx
I had a crash cause that one time.
florinandrei
30th August 2009, 07:18
I uninstalled megui.
I downloaded 1052 from sourceforge and installed it. I let it do all updates and restarted it.
I'm encoding now. There's no error, the encoding speed is normal. So far so good. If the video looks good then I guess it's fixed. Phew! :)
Dark Eiri
30th August 2009, 18:14
I downloaded the core.....1054.zip, extracted the main megui.exe and used it instead of the one that caused the problem.
It works! I'm waiting to see the end result, but anyway, until then I'm happy it doesn't give the error anymore.
It's weird, but it encodes ~3x faster than megui 1051 (93 fps vs. 32 fps). I am using the Blu-Ray profile, modified for constant quantization = 25. Source is 480x480 SVCD MPEG2, I do deinterlacing with yadif+bob, rescale with spline36 to 640x480.
My guess: 1053 came with a newer x264 which is faster than the old x264, but couldn't run it because of the error, and now 1054 fixed the error and the new x264 is working faster than the old one. Is that correct?
Are you sure you're using Constant quant. mode and not auto 2 pass?
Maybe the bug that set fast 1st pass settings for the 2nd pass still persists.
florinandrei
30th August 2009, 19:44
Are you sure you're using Constant quant. mode and not auto 2 pass?
Yes, I took the regular Blu-Ray profile and only modified it from 2-pass to CQ, then saved it to scratchpad, that's all.
I'm watching it as it's encoding, indeed it does only one pass.
Maybe the bug that set fast 1st pass settings for the 2nd pass still persists.
I have no idea whether that's the case, but it's good to keep in mind because for other projects I actually use the AVCHD profile in the default 2-pass mode. I guess I'll have a closer look at the settings next time I use 2-pass.
Thanks for the heads-up.
soso12
11th September 2009, 16:39
Hi. I didn't use this new build yet, but you can try the 1054 from here:
http://kurtnoise.free.fr/MeGUI/?M=A
Thank you, it's ok now ! :thanks:
fahim
16th September 2009, 11:39
Which version write x264 in library core 67 or 65??
n0an
20th September 2009, 00:45
Googled this and found a soltuion. Hope it works for you.
This is how I worked around it:
In the encoding-profile I enabled mbtree in the advanced settings. I saved the profile and closed megui.
In the megui-folder there is a folder named jobs. In it are the xml-files for the queued jobs (2 if your using 2-pass encoding)
Edit the xml-files, find the tag for mbtree and change the value within the tag from false to true.
Start Megui and go to the queue-tab. If you now start the jobs, things should work.
Credits: Kardargo
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.