Weird MeGUI error

[MixMasters]

Whenever I try to encode with x264 i get this error


[NoImage] Standard error stream: C:\Program Files\megui\tools\x264\x264.exe: unrecognised option `--no-mbtree'


i tried with XviD also, when i tried i got this

--[Information] [8/20/2009 3:49:46 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [8/20/2009 3:49:46 PM] Job completed


it was working with fine couple of days ago, don't know what happend how to fix this issue? :confused:

My MeGUI version 0.3.1.1053

[AKarpo]

Having the EXACT same problem. I haven't changed anything either with any of my encoding settings. Something is up.

[MatLz]

Update your X264.exe.

[AKarpo]

Update your X264.exe.

Using the Win32 build from here - http://forum.doom9.org/showthread.php?t=89979

yields the same error.

Tried using 1217 from x264.nl - same error.

[MatLz]

Sorry, I don't know, it works fine for me. I use X264 r1214 and same Megui as you.

[AKarpo]

Sorry, I don't know, it works fine for me. I use X264 r1214 and same Megui as you.

Are you using MeGUI 1053?

[MatLz]

Are you using MeGUI 1053?

Yes, 0.3.1.1053.

[AKarpo]

Yes, 0.3.1.1053.

Weird. Well I'm not doing anything crazy, just using the AVCHD preset. Wonder why it is now suddenly broken after working all this time.

[MixMasters]

any idea how to fix this problem
it all started suddenly

[AKarpo]

any idea how to fix this problem
it all started suddenly

I'm guessing it's some sort of incompatibility between x264 and the presets in MeGUI. A bunch of functions in the AVCHD preset that I use aren't being recognized by x264.

[MatLz]

Or in 1217 mbtree has been disabled by default so --no-mbtree has been removed?
Don't know, wait a moment for an experts answer. They will come soon. Good luck

[MixMasters]

i tried in in Command Prompt also
but it was no use as you said need some experts help

EDIT ::

I downloaded revision 1217 from here (http://mirror01.x264.nl/x264/?dir=./revision1217)
that mb-tree problem is gone an another problem is started


-[Information] Log for job1 (video, Shangri-La 20.avs -> Shangri-La 20.mp4)
--[Information] [8/20/2009 6:50:52 PM] Started handling job
--[Information] [8/20/2009 6:50:52 PM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --profile high --level 3.1 --preset fast --pass 1 --bitrate 860 --stats "E:\test.stats" --thread-input --bframes 0 --ref 1 --no-mbtree --me dia --subme 2 --partitions none --trellis 0 --no-mixed-refs --output NUL "E:\test.avs"
--[Information] [8/20/2009 6:50:54 PM] Encoding started
--[NoImage] Standard output stream
--[NoImage] Standard error stream
--[Information] [8/20/2009 6:50:54 PM] Job completed


The encoding starts and closes with an unknown error :confused:
what to do?
the same thing started with xvid also

EDIT 2 ::
Re-Installed to Vista
still have the same problem

[tasusq]

Getting the same problem here. Whenever i try to open bitrate calculator after opening MeGUI or Whenever i click on Video Encoding>Enqueue i get an error.

This happened after i installed and updated MeGUI 0.3.1.1053. I am using Windows XP SP3 32bit.

I can no longer use MeGUI not for any encoding using any codec.
Here is a screenshot of the error i get:
http://i25.tinypic.com/1118prd.jpg

I also attached the .txt file created after the error. I also attached the AVS script i was using.

In the script i tried removing fft3dGPU filter and the problem was gone. But it was working fine with the same script.

[florinandrei]

Uninstall it. Download 1052 from sourceforge (look for the megui-development section on the Files page) and install it. It should work - at least, it does for me.

http://forum.doom9.org/showthread.php?t=149223

[dbzj14]

Had the same exact problem, I fixed it but selecting MB Tree in the config menu for the codec I was using. In one of the advance menu tab's(I cant remember off hand which one) look near the right. In one of the tabs you should see something that say's "use MB TREE" or something to that effect, select that option. Sorry this is vague, I am not infront of my computer with the program but I remember this fixing the problem.