Log in

View Full Version : Annoying MeGUI behaviour


MKVCrazy
8th November 2011, 16:22
I'm not sure how to describe it so I created a thread. I'm sorry if I've posted in the wrong section but I posted here because a I see a bunch of MeGUI related threads but did not wish to hi-jack other people's threads.

So the problem is, I use One-Click Encoder. I have setup the One-Click Encoder profiles to the way I want so that in the future, I can quickly load each file and then assign each file to different works and start all workers at the same time by hitting the "START" button in Queue tab. Everything turns out as planned but when I got to the part, where all workers finish the Indexing part, FFMSIndex or something, after that stage, everything just freezes and MeGUI crashes everytime at that point. I reset every file and their settings and still crashes at that point. So I did a search on here and on Google. I think Sharktooth said that it's probably hardware related, CPU overheating problem. That might be the case but my CPU is a monster, E3-123 @ 3.2Ghz (8 cores). I only started 4 workers at the same time.

So far, my situation is that I've found how to have multiple files encoding at the same time. I just have to wait each worker to reach the audio encoding stage before starting another worker. This is fine if the clips I encode are 1-2 minutes as MeGUI will quickly finish the FFMSIndexing part (in less than 5 seconds) but since each clip is about 40-50 mins. I have to wait about 3-5 minutes in front of the computer to start another worker, and it's just not productive when I want to batch convert 14 clips before I got to work or bed.

Anyone have a better suggestion or something that you think I should try?

PS: The fault module says it's Kernelbase.dll. This is what I see in the App crash box, that pops up. Does that ring a bell? I can reproduce this crash every time, using any test clips or files. So I don't think it's the files that are causing the crash.

Regards,
I really appreciate your time for reading this.

Zathor
10th November 2011, 22:21
Please post (a link to) the full log file so that I can investigate the issue.