Log in

View Full Version : Crash when running Megui


bira
26th August 2006, 15:22
****** Please keep reading. Thread subject was edited. ****

I tried to search but could not find an answer.

Latest MeGui with auto updated files.

Avisynth Creator
Input DAR ITU 16:9
Clever anamorphic enconding = resize to mod 16
no crop
resize 720x480

# Set DAR in encoder to 37 : 20. The following line is for automatic signalling
global MeGUI_darx = 37
global MeGUI_dary = 20
DGDecode_mpeg2source("J:\Movie.d2v",info=3)
ColorMatrix(hints=true)
#blank deinterlace line
#crop
LanczosResize(720,480) # Lanczos (Sharp)
#denoise



Codec: x264
Container: mkv
Video Profile: HQ-Slow

Hit 'Enqueue' and then 'start'

x264 crashes and log says

The current job contains errors. Skipping chained jobs
Starting job job2-1 at 11:15:19 AM
encoder commandline:
--pass 1 --bitrate 1000 --stats "J:\Movie.stats" --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --merange 12 --threads 2 --thread-input --progress --no-psnr --output NUL "J:\Movie.avs"
successfully started encoding
Processing ended at 11:15:23 AM


If I choose Xvid instead of x264 it goes fine.

Any help?

bira
26th August 2006, 15:37
Quick update,

Working Profiles:
CQ-ASP_Q2_equiv
CQ-ASP_Q2_eq(crf)
1P-Goodquality

With every other profile x264 crashes.

Doom9
26th August 2006, 15:56
And why did you write anything about anamorphic? Have you tried the same source but without anamorphic signalling? Only if that works then I'd even bring up anamorphic.

bira
26th August 2006, 16:15
Thanks for your attention, Doom9.

Input DAR ITU 16:9
Without checking Clever anamorphic enconding
no crop
resize to 720x384 (suggest resolution checked)

Profile HQ-Slow

It works beautifully!

Doom9
26th August 2006, 17:28
that kinda suggests an x264 problem though. Take the commandline megui gives you (you posted it above), and run it from the commandline, and tell us what happens.

bira
26th August 2006, 19:36
It works running from the command line.

I believe I found the problem.

Look, this does not work:

--pass 1 --bitrate 1327 --stats "I:\Movies Original\DVD_VIDEO\VIDEO_TS\no crop non anamorphic.stats" --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --merange 12 --threads 2 --thread-input --progress --no-psnr --output NUL "I:\Movies Original\DVD_VIDEO\VIDEO_TS\no crop non anamorphic.avs"

This works:

--pass 1 --bitrate 1327 --stats "I:\Movies Original\DVD_VIDEO\VIDEO_TS\test.stats" --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --merange 12 --threads 2 --thread-input --progress --no-psnr --output NUL "I:\Movies Original\DVD_VIDEO\VIDEO_TS\test.avs"

Notice the lenght of the the path? I just changed the name of the .avs file. All other settings are the same.

bira
26th August 2006, 20:16
One more example:

First Pass *No Crash (309 characters)

--pass 1 --bitrate 1327 --stats "I:\Movies Original\DVD_VIDEO\VIDEO_TS\bs.stats" --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --merange 12 --threads 2 --thread-input --progress --no-psnr --output NUL "I:\Movies Original\DVD_VIDEO\VIDEO_TS\bs.avs"


Second Pass *Crash (391 characters)

--pass 2 --bitrate 1327 --stats "I:\Movies Original\DVD_VIDEO\VIDEO_TS\bs.stats" --ref 3 --bframes 3 --b-pyramid --weightb --direct auto --filter -2,-1 --subme 6 --trellis 1 --analyse all --8x8dct --vbv-maxrate 25000 --me umh --merange 12 --threads 2 --thread-input --progress --no-psnr --output "I:\Movies Original\DVD_VIDEO\VIDEO_TS\bs.mkv" "I:\Movies Original\DVD_VIDEO\VIDEO_TS\bs.avs"

Sharktooth
27th August 2006, 16:22
I smell a system unstability...

bira
28th August 2006, 03:09
I smell a system unstability...

My system? Is there anything I can do?

Carpo
28th August 2006, 11:49
run av progs, spyware progs, just to check system is clean (not saying it isnt but you never can tell these days) defrag drive(s) and run chkdsk x: /f on all the drives (x being the drive letter - e.g chkdsk d: /f) this will check the drive and fix any errors, keep doing this (from commandline) till you can see that is says it has found no problems with the disk

get all the updates for OS

then try - also try not to use paths with spaces in them - sometimes that can have an adverse effect on things

Sharktooth
28th August 2006, 12:32
get some burn-in tests like memtest86 let them run...

bira
28th August 2006, 20:01
I am sorry, but how come system stability can be picky on filenames.

Here the facts:

Naming the script as swst.avs instead of sst.avs crashes x264 using Megui, but when running x264 directly from the command line it runs ok.

Shouldn't it crash by running from the command line too??

Also, XVID does not crash.

*** Note: thread subject should be altered as the problem has nothing to do with anamorphic enconding.

bira
29th August 2006, 13:49
Well, I'm lost.

It's working fine now. At least for now.

And I did not change anything. In fact, I just started the queue again with the same files.

Sharktooth, it appears you're right. :o It's a system unstability, although it does not seems to be a hardware problem (everything else is running fine).

bira
29th August 2006, 15:00
Ok, I believe I found the problem (again).

It has nothing to do with hardware.

It was a conflict with a software I was using.

Thanks everybody for your patience! :D

Sharktooth
29th August 2006, 15:34
it may be useful for other users if you tell us what software was causing the conflict.

bira
31st August 2006, 21:52
DVD Region+CSS Free 5.9.8.3

bira
1st September 2006, 04:54
Well,

I had three softwares that were not going along well. They are:

Megui - DVD Region+CSS Free - and the main culprit MICROSOFT CTMON.EXE.

Just got rid of CTMON.EXE and it's all good (for) now.
"Ctfmon.exe activates the Alternative User Input Text Input Processor (TIP) and the Microsoft Office Language Bar. Ctfmon.exe monitors the active windows and provides text input service support for speech recognition, handwriting recognition, keyboard, translation, and other alternative user input technologies. Removing the Ctfmon.exe might cause problematic behavior in your Office XP programs, so removing it is not recommended. To prevent Ctfmon.exe from running, follow the steps on the attached link to MSKB."

Read more about CTMON.EXE here:
http://www.neuber.com/taskmanager/process/ctfmon.exe.html
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q282599