Log in

View Full Version : meGui crashed, trying to figure out what happened.

mitsubishi
12th July 2007, 13:26
I set up a job for x264 to do the video and Nero AAC to do the video. Pressed start and they both started at once as I have two workers set up.

I think when the audio finished, a popup announced megui had encountered a problem and needed to close. The video carried on encoding, but I saw in the queue list the audio status was error. The GUI locked up when I tried to switch to log. So I pressed OK on the popup.

In the folder there was no audio, I had to "unlock" the video to be able to delete it. So I tried just audio, no problem. Tried both again, this time it worked, although I realised it was running slow, there was a ghost x264.exe sharing the CPU, so I stopped it and started again.
check
13th July 2007, 04:53
You didn't have both encoders set to output to the same file did you? This can happen if both have MP4 output set and you don't change the default filenames.
mitsubishi
13th July 2007, 10:21
You didn't have both encoders set to output to the same file did you? This can happen if both have MP4 output set and you don't change the default filenames.LOL no, not this time, although I've done that many times before with mp4's, had a long video encode wiped out by the subsequent audio :(

Tried to recreate it, but no joy. There's no log with it crashing either. I'll keep starting encodes the same way and see if it happens again.
mitsubishi
14th July 2007, 13:46
Managed to get another error. I added an audio, then a video, went to jobs and pressed "start". This time, the audio went through and seems to be fine, the video instantly errored though.

Starting job job10 at 13:33:25
Starting preprocessing of job...
Preprocessing finished!
Job not started. Reason: Calling setup of processor failed with error 'The file Y:\te\sg.avs cannot be opened.
Error message for your reference: Script error: there is no function named "DGDecode_mpeg2source"
(Y:\te\sg.avs, line 1)'

That line break is shown as the little square in the log window and this job is above the audio "job9" in the log window. I simply changed status to waiting from error the job then started normally.