MeGUI has basically stoped working

[saint-francis]

I have been successfully using MeGUI for about a half of a year now and just recently my average FPS while encoding went from about 8 to between 3 and .2. The encoding starts out at about 2.4 FPS and when I check on it 12 hours or so later it will be going at less than .2 FPS and the cpu usage for x.264 is o but it still seems to be using a decent amount of memory. I have wiped MeGUI and all of it's components and reinstalled all to no avail. Is this a problem any one has seen before? Any one have any ideas?


Screenshot of the issue

http://img176.imageshack.us/img176/3078/untitledtc6.th.jpg (http://img176.imageshack.us/my.php?image=untitledtc6.jpg)

[mitsubishi]

Does this occur with all codecs or just x264?
Is there any chance it could be a hard drive/file access issue?

Try going to the log, copying the command line and executing it straight at a command prompt (putting "C:\Program Files\megui\tools\x264\x264.exe" infront)

So something like this:

"C:\Program Files\megui\tools\x264\x264.exe" --pass 1 --bitrate 3220 --stats "W:\final.stats" --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --threads 2 --thread-input --progress --no-dct-decimate --no-psnr --no-ssim --output NUL "W:\final.avs"

[lpvtech]

It has nothing to do with MeGUI or x264. Its a problem with your computer. Afterall, they are just programs with some instructions to carry out. The program never changes.. What changes is the ability of the OS to allot the CPU a specific timing. Mostly, it can't be a problem with your HDD.. Since even an extremely slow HDD which is worn and torn, can do so much more even a 100 fps.It lies in the CPU's power.. x264 is harder to encode and 8 fps is resonable. May be your system is now junked with a lot of software that wasn't there a year ago. There might be more programs running in the background (even hidden) than before, which clearly explains the reason for the drop of speed. I would seriously recommend a format and clean install and then bring your dead system back to life. It is really a good habit to format and make a clean install atleast once a year. Actually, I do it every month or two... But that's not something one would suggest... Do it atleast once a year and avoid all junk programs that you don't need and pick a tool like say, CCleaner that keeps your system free from junky temporary files. I have scheduled CCleaner to run about every day.It just takes 5-10 secs to run...

And by the way, from your snapshot, I would never run it with HIGH Priority - Normal or Low is suggested.

[check]

@temporary files are unrelated to this (also, use some bloody paragraphs! :p)

It sounds like a problem with either the encoder (x264) or the decoder (avs) if x264 is just sitting there using no CPU. Try mitsubishi's strength and report back.

[saint-francis]

I tried mitsubishi's plan for encoding through the command prompt and I got the same problem. Speeds a little slower than usual at first and then slowly (over about 10 minutes) x.264 begins to just sits there and eventually uses 0% cpu but continues to use memory. I am using staxrip right now and having no trouble with x.264 what so ever.

And I'm working on a pretty fresh install of windows (about 1 1/2 months) so I don't think that's it. And I am also pretty sure that all of my hardware is in top condition as it's also pretty new.

[check]

could be an x264 bug, but it's certianly an x264 problem or input problem. What happens if you use the same input file with megui to encode an xvid or something?

[Adub]

make sure you update to the latest version of x264. I had the same exact problem once, and an update fixed it.

[saint-francis]

make sure you update to the latest version of x264. I had the same exact problem once, and an update fixed it.

Well I used the MeGUI update function. Is it out of date? Is there a discrepancy between that version and the one from Check's source? It has always worked up until now.

could be an x264 bug, but it's certianly an x264 problem or input problem. What happens if you use the same input file with megui to encode an xvid or something?

I have tried this with several different sources recently and always gotten the same issue. Although I have never tried using MeGUI for xvid at all. But I can and will if it is still believed to provide useful information.

[check]

it is :)

[Adub]

yeah, just update the x264 file manually.

I recommend Cef's builds. You can actually find them in Sharktooth's sticky now.

[saint-francis]

OK. I uninstalled MeGUI and avisynth and everything else on my pc that has any codecs. I then reinstalled MeGUI. I encoded the same source with xvid flawlessly. I then tried it with x.264 and I got the same problem. I also am using the latest x.264 build from cef found right where merlin7777 told me it would be. The weird thing is that at first x.264 is using almost 100% of the cpu (which is usually doesn't do) and then after about 2 minutes this time the cpu usage went to 0 but it still kept using memory. I was using the maxspeed profile. The fps slowly begin sinking from about 100 after x.264 stops using the cpu.

Here is a screenshot.

http://img293.imageshack.us/img293/58/badmeguimemorypy0.jpg

[ChronoCross]

run x264 from command line. Something has to be happening externally of MEgui. it's almost as if there is a thread lock somewhere

[saint-francis]

Earlier I tried it from a command prompt and I had the same issue. I just tried it again and got the same problem. I also got a weird error this time which I got once yesterday.


Sorry I cropped it poorly. I tried to replicate it and couldn't.

http://img246.imageshack.us/img246/520/memerrorly7.jpg


The weirdest thing is that I used x.264 with staxrip the other day and didn't encounter this problem at all.


I'm going to run memtest 86+ for a couple hours and see what comes up.

[Adub]

It's weird. Your problem sounds exactly like what mine was. I didn't get that last error, but I did have the dropping frame rate problem and 0% processor usage problem. The even weirder thing is that it went away when I update my X264 build. Atleast, that was the only thing I changed and the problem went away.

Edit: Oh yeah, post your script. It seemed I had the problem when I used MT() functions in my script and the older version of x264. Also, if you are using MT, which version?

[saint-francis]

Here is my script. I am not using MT.


# Set DAR in encoder to 47 : 20. The following line is for automatic signalling
global MeGUI_darx = 47
global MeGUI_dary = 20
DGDecode_mpeg2source("C:\MY_MOVIE\VIDEO_TS\VTS_02_1.d2v")
#Not doing anything because the source is progressive
crop( 4, 60, -4, -60)

BicubicResize(720,368,0.333,0.333) # Bicubic (Soft)
mergechroma(blur(1.3)) # Little Noise

[saint-francis]

Well I decided to format the C; drive and that took care of the problem. I had tried everything else I could think of. I rebuilt my user account, used every malware scanner known to man. I tried it all; and to no avail. The format worked though. Still I am curious what the issue was.

Thank you everyone for your help.