MeGUI: General Questions and Troubleshooting Thread

[check]

trellis2 is better quality, but significantly slower. Which one is better depends on how you value 'time' and 'quality' relative to each other.

[((( atom )))]

Sorry, I am totally loosing track here..

I just updated megui again and now after loading the avs it opens the preview window and closes it itself after clicking "AutoEncode", so I assumed the bug is fixed and there is no reason for keeping the preview-window open. So i reloaded all my avs files again and set up new rips and the result is: all encodes are a looooong line. Display width / heigt in mkvmergegui is shown to be 1317966336 / 1684768 for all of these encodes.

So does this mean, that megui is totally unusable for the moment? I can somehow not believe that, but that is what it looks like to me...

?

[LOGiC]

trellis2 is better quality, but significantly slower. Which one is better depends on how you value 'time' and 'quality' relative to each other.


Thank you for your answer Sir. What I understood from this thread and other threads is that in the latest MeGUI build there is PSY-RDO 0.5 already integrated and enabled and therefore it is useless to select Trellis1 MB, as it definately will be switched off by MeGUI automatically. I think I read from Sharktooth that Trellis just can be 0 or 2 with Psy-RDO activated. My question therefore is, taking 2 for Trellis-always, does it have a senseful quality/time-ratio, in other words, is it worth the extra encoding time or is the result with 2 in comparison to 0 negligible ?

Thanks again for your help, I am trying to crouch in the way to set it up the best way for my personal use and I still need to learn.

[j8ee]

With megui 0.3.0.1020 and when having avs files using directshowsource for audio, ffdshow audio decoders remains loaded even though the files are closed. Is this a known problem? When there have become 20-30 ffdshow icons in the tray, I usually restart megui, but sometimes it's only the window that closes, and I have to manually kill the process.

[bottomsup]

Anyone know how to get M-JPEG in a .mov container to load in the AVISynth analyzer?

[Sharktooth]

Sorry, I am totally loosing track here..

I just updated megui again and now after loading the avs it opens the preview window and closes it itself after clicking "AutoEncode", so I assumed the bug is fixed and there is no reason for keeping the preview-window open. So i reloaded all my avs files again and set up new rips and the result is: all encodes are a looooong line. Display width / heigt in mkvmergegui is shown to be 1317966336 / 1684768 for all of these encodes.

So does this mean, that megui is totally unusable for the moment? I can somehow not believe that, but that is what it looks like to me...

?
there's still one bug concerning AR. the one you experienced and it doesnt always happen.

[check]

@logic: once again, it depends how you personally value time & quality. I generally use trellis 1 or 2.

@bottomsup: try directshowsource()

[LOGiC]

Good Morning all

after my first thirty hour x264 encoding I unfortunately had to notice that the Aspect Ratio is wrong and screwed up. Which is in your opinion a safe way to find out about the real aspect ratio ? MediaInfo didn't tell me, AVINaptic didn't. Is there any other program that tells me the real AR to use ?

Thanks.

Andy.

[Archimedes]

Lost in space. :rolleyes:

In the XviD configuration dialog I-Frame boost is set to 100 (default setting). But the default value of xvid_encraw is 10 (parameter kboost). Is the default setting in MeGUI correct this way?
What about this issue?

[check]

@logic: Remux the video with mkvmerge. You can specify the correct AR when doing so. (btw, mkvmerge has an included GUI tool called mmg).

[Sharktooth]

or with mp4box.
the AR is usually written on your DVD case.

[rack04]

Can someone explain the option "Force Decoding via Directshow"? I'm having some conflicts using this option and would like to know if I'm losing something by using NicAC3? Also what justifies using this setting in some audio presets and not others? Thanks.

[bottomsup]

@logic: once again, it depends how you personally value time & quality. I generally use trellis 1 or 2.

@bottomsup: try directshowsource()

Thanks. I'm not sure how to do that exactly. When I click the ellipse to load the video in the AviSynth creater I get this message.

http://img66.imageshack.us/img66/9174/capturesdfdwh1.jpg

The edit page looks like this...

http://img66.imageshack.us/img66/7783/captsdfdsurehl1.jpg

[((( atom )))]

there's still one bug concerning AR. the one you experienced and it doesnt always happen.

hmm, so how could I get rid of it? I can't actually encode a thing anymore :(

I /could/ set the correct ar in mkvmerge, but I am unsure, if that is the right method. I read somewhere, that the ar should be set in the videostream actually and not really in the container. Then again I read, that mkvmerge deletes the entry from the videostream and writes it in the container instead.

Which is true? If the latter, i could simply use mkvmergegui to fix the last 12 rips I made, that would be great!

[Sharktooth]

easy, if it works then its ok.
IIRC mp4box writes the AR in the bitstream so it's more "safe"... but mp4box is for mp4 not mkv.

[Sharktooth]

@bottomsup: DirectShowSource("") ?!?!??!? it cant work...
the error message it's quite clear... you miss the DS decoder.
install FFDShow. it should work.

[Sharktooth]

Can someone explain the option "Force Decoding via Directshow"? I'm having some conflicts using this option and would like to know if I'm losing something by using NicAC3? Also what justifies using this setting in some audio presets and not others? Thanks.
It uses DirectShow decoders installed on your system to decode the source audio file.
If you have an ac3 decoder (ac3filter, ffdshow, etc) it will use it.

[bottomsup]

@bottomsup: DirectShowSource("") ?!?!??!? it cant work...
the error message it's quite clear... you miss the DS decoder.
install FFDShow. it should work.

I have FFDShow "FULL" installed so that's not it. The AVI Script Creator doesn't even have .mov as an option so I have to select 'all files' This makes me think it isn't supposed to work with megui.

Any other pointers? Thanks for your help.

[Sharktooth]

try installing quicktime alternative. .mov files need a quicktime splitter and proper decoders depending on the stream contained in the .mov.

[bottomsup]

try installing quicktime alternative. .mov files need a quicktime splitter and proper decoders depending on the stream contained in the .mov.

I have that too :confused:

[Raere]

meGUI is crashing quite a bit for me since I've upgraded my computer. I'm now using Vista 64-bit. It mostly crashes when I try to enqueue two jobs in one session. I have to enqueue one job, close meGUI, open it again, and enqueue the second job. I'm willing to try to help debug this, is there a way to make meGUI dump a full logfile? It's actually freezing and Windows lists it as 'not responding', so I don't think a crash logfile would generate.

[corporalgator]

I'm getting a crash bug in megui ever since the preview windows were fiddled with. I'm not sure what exactly is causing it, but it happens when I am currently encoding with x264 and I then open another file which opens a preview window such as avisynth creator or loading .avs script to enque. I know the solution is to simply wait to start encoding after I have queued everything up....

Vista calls up data execution prevention and then closes megui, but does not terminate x264 so it continues to eat my cpu time. I am able to start another instance of x264 through megui and didn't notice x264 was already running until I tried to load that avisynth script that it crashed while encoding.

To clarify, I have several encodes in the queue, I start the encodes, then open another preview window, which then crashes once the preview window loads (it does not immediately crash but only once the preview windows flashes onto the screen after the load wait) and then vista brings the DEP window and acts like it somehow going to find a solution.... I then restarted megui, start the rest of my queue and went to reload the script it aborted on, and then received the error it was already in use and then loaded program manager to find x264 still running. I didn't feel like sitting around waiting to find out if x264 was actually going to finish that encode. I am also loathe to disable DEP for megui to test that.

Before, I was able to continue working and opening preview windows in megui at will. This only happened recently. At first, I figured it a freak occurrence, until I pinpointed exactly what was causing the crash, so I cannot tell you which version of the preview window change started the crash, but it think it was after the non-closeable preview window and may have started when the shrink option was added to it, although I cannot be sure. Sorry if my information is fuzzy.

Here is what the windows event viewer log states:

Faulting application MeGUI.exe, version 0.3.0.1020, time stamp 0x48885c42, faulting module DGDecode.dll, version 1.5.0.0, time stamp 0x487b4900, exception code 0xc0000005, fault offset 0x0001d1c0, process id 0xe1c, application start time 0x01c8efa84a70be24.

Another time was this:

Faulting application MeGUI.exe, version 0.3.0.1020, time stamp 0x48885c42, faulting module FFT3DFilter.dll, version 2.1.1.0, time stamp 0x45db414e, exception code 0xc0000005, fault offset 0x000118a8, process id 0xf70, application start time 0x01c8ef8527768264.

I was using FFT3Dfilter on one but not the other.

[Raere]

Interesting, mine always crashes after I load a script (thus popping up the preview window) so we could be having the same problem. The only difference is that meGUI just freezes for me; but I also don't have DEP enabled for all programs, it'd probably throw up an error if I had it enabled.

[check]

@raere: is it running out of RAM? It's a known memory leak with MeGUI

@corp: sounds like you are running out of memory again, but you can terminate DEP with extreme prejudice (at least temporarily) to confirm it's not a problem with DEP.

[tebasuna51]

Can someone explain the option "Force Decoding via Directshow"? I'm having some conflicts using this option and would like to know if I'm losing something by using NicAC3?
To decode ac3 the best method is use NicAc3Source.
You can obtain same results with DirectShowSource if you have the default DS filter (ffdshow, Ac3Filter, ...) for AC3 properly configurated (DRC, DialNorm, ...)

Use DirectShowSource is only recommended when the audio source don't have a dedicated avisynth decoder.

Also what justifies using this setting in some audio presets and not others?

Is used only for low quality downmix (mono, simple stereo) for mp3 low bitrate output (64, 96 Kb/s). DS filters have internal downmix simple methods to do the job.

[bluebebe]

i have a problem with latest megui, i tried to muxx a xvid avi with a mp3, the mp3 have i created using megui with lame abr 192 with a delay of -207ms, i think megui ignores this delay, when i add the source ac3 to the sound encoder, megui dont apply the delay to the new filename, so easyl:

source filename: VTS_03_1 T80 3_2ch 384Kbps DELAY -207ms.ac3

dest. filename: VTS_03_1 T80 3_2ch 384Kbps DELAY 0ms.mp3

megui removes the delay and so i think the program will ignore it, after remux with avimux the new avi is outsynched. the delay is from the latest dgindex. can anyone confirm this bug?

[corporalgator]

@raere: is it running out of RAM? It's a known memory leak with MeGUI

@corp: sounds like you are running out of memory again, but you can terminate DEP with extreme prejudice (at least temporarily) to confirm it's not a problem with DEP.

I am pretty sure it's not my ram as before I was able to have open at least 2 preview windows while running encode jobs, but I will check and see.

I have had freeze issues lately also, where my entire comp would free and nothing but a reboot could cure, no ctrl-alt-del possible, not even a bsod, but that has generally been in the middle of an encode and had nothing to do with preview windows. There's no log or error message for that since everything is frozen.

[Raere]

I'm pretty sure it's not a RAM problem as well - I have 4GB.

[toytown]

Raere,

The lockups in Megui happen if you have the multithreaded version of avisynth running. If you revert back to the normal builds then your problem with the freeze in the GUI will clear up.

I have had freeze issues lately also, where my entire comp would free and nothing but a reboot could cure

This is either overheating of your cpu, or 1 of your sticks of ram is bad. Run memtest overnight and see what results it gives. Also try running speedfan and monitor your temps midway through encodes.....finally if you have overclocked your computer this could also cause the issue.

[Raere]

Raere,

The lockups in Megui happen if you have the multithreaded version of avisynth running. If you revert back to the normal builds then your problem with the freeze in the GUI will clear up.



This is either overheating of your cpu, or 1 of your sticks of ram is bad. Run memtest overnight and see what results it gives. Also try running speedfan and monitor your temps midway through encodes.....finally if you have overclocked your computer this could also cause the issue.

Ah, I didn't think that could be a problem. I'll still stick with it though, the speed improvements are worth a little extra time queuing up jobs.

[((( atom )))]

@sharktooth: thanx, that helps for the moment. One mystery remains, though: if I have an idx-file with loads of subtitles, in autoencode mode only the first language is picked and muxed. That used to be different. Is anybody aware of this problem? I filed a bug weeks ago already..

[qpsl]

In P3 computer (1.26g), it took 13s to start up, it's too slow.

[Sharktooth]

vista 64bit is a memory hogger by nature. all problems with crashes when enqueuing multiple files are probably due to low amount of ram (4gb is just "ok i can start dont ask me to work hard").
learn the lesson, stick to XP and use only the official avisynth builds. avicvynth_MT is unstable.

[toytown]

vista 64bit is a memory hogger by nature. all problems with crashes when enqueuing multiple files are probably due to low amount of ram. (4gb is just "ok i can start dont ask me to work hard").

Thats simply not true, ive been encoding Bluray in 1080p and 720p on my HTPC which only has 2GB of ram. The locking up when trying to enque files is most likely from having the multithreaded version of Avisynth installed. As this was the problem on 3 of my machines and from reading on various posts in this thread is also how others have solved the problem.

I even just started up an encode from megui using bluray as the source, using avisynth to crop the blackbars. The HTPC has been on almost a month doing various encoding, so its not a fresh boot..........Total memory used 1116MB.......x264 is using 560MB of that for encoding. Still has almost 900MB free.

[Sharktooth]

oh yeah... while the system eats up almost 1GB of ram for doing what?
stick with XP or switch to linux.

[check]

oh yeah... while the system eats up almost 1GB of ram for doing what?I don't want to derail this thread any more so I won't reply further, but you will find that linux will happily eat 2gb of RAM on startup too, if you boot a modern GUI, like GNOME or KDE.

[toytown]

oh yeah... while the system eats up almost 1GB of ram for doing what?

The system has a total memory of 2GB
Total memory used 1116MB
.x264 is using 560MB of that for encoding

OS and other software running at the time was using 556MB!

Im not going to reply anymore but your blind hatred for an OS you dont understand is quite obvious and quite funny when you mention Linux as an alternative, which also consumes the full memory on bootup for things like caching etc .........just like Vista.

Fine if you dont like the OS dont use it, but dont try and turn everybody else off it because of your lack of understanding.

[Sharktooth]

linux caches. while vista eats. it has been proved superfetch kills the system performance. enabling the classic prefetch (like in XP - by editing a key in the registry) is much better (use google).
also there are heavy and lightweight linux distros. for example there are distros working with systems with less than 16MB of ram and still they have a graphic interface.

@toytown: did you use the task manager to report those values? coz the task manager is completely weird.
Use the perf. monitor. in the administrative tools.
however, even if it (the task manager) reported the correct values (which i highly doubt) more than 500MB for the system is just not acceptable.
oh wait, maybe i understand things a bit better than you and im trying to make you OPEN your eyes and think with your own mind.
is there a reson why EVERY professionist/analyst in any of the informatic fields, recommends sticking with XP and trash Vista? learn the lesson.

[toytown]

(4gb is just "ok i can start dont ask me to work hard").

oh wait, maybe i understand things a bit better than you and im trying to make you OPEN your eyes and think with your own mind.

The system has a total memory of 2GB
Total memory used 1116MB
.x264 is using 560MB that 1116MB for encoding at 1080p

Maybe its somebody else who needs to open there eyes. Im outta here anyways.

[Dark Shikari]

x264 does not use 560MB of memory.

Most of that is Avisynth. Add SetMemoryMax() to your script to limit it. x264 itself does not use much memory in normal situations.

[Sharktooth]

i hate fanboys... let him believe in his stupidity.
if he knows it all why he comes here asking for help?
i wonder why i still check this thread. i shuould not give support for free for an OS app. expecially for ppl like him.
if it doent work the sources are availabe... get them and fix it, if you're able. when you will see the problem is not the app but vista, then you might open your eyes.

[((( atom )))]

Maybe the stupid discussion about Vista - lol! - kicked my modest question about "what might be wrong with these subs?!" to a lower rank but I'd be very thankfull for help on this topic. ;)
Am I actually the only auto-encoder keeping more than one subtitle stream?

[Sharktooth]

it's a reported bug. im investigating.

[((( atom )))]

Ah, thx, I wasn't aware.. Didn't mean to bother..

[Sharktooth]

the report is here: http://sourceforge.net/tracker/index.php?func=detail&aid=2016031&group_id=156112&atid=798476

[((( atom )))]

I know, I actually filed that bug report! - But since no follow-up came up for long, I wasn't sure, if it is only my problem (still don't know) or just no one cared or whatever. So I thought, I just ask here again..

[Sharktooth]

ah ok. the report was anonymous so i couldnt know you were the author.

[((( atom )))]

Yeah, couldn't bother to sign up just for one report, sorry.. Anyway, I had just mentioned that I filed the report a while ago, guess you overlooked it. For the moment it doesn't matter (at least to me) anyway, since I went back to manual muxing due to the ar-problem.

[Sharktooth]

ill see if i can find the cause. however, yes, manual muxing is the workaround until we fix it.

[((( atom )))]

Sure, thx in any case!