+ Reply to Thread
Results 1 to 13 of 13
Hmm maybe a problem with DEP or possible bad RAM stick.
Yes I don't understand why i just bought this 6 core computer and everything is set up correctly. A couple days ago the encodes were fine, i could finish an encode without errors in 20 minutes. Now the speed slowly goes down while processing until finally i get error under status tab in MeGUI.
maybe it's a problem with my avisynth script. Did i use avisynth_mt correctly in it?
# Set DAR in encoder to 4 : 3. The following lines are for automatic signalling
global MeGUI_darx = 4
global MeGUI_dary = 3
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\TIVTC.dll")
import("C:\Program Files (x86)\AviSynth 2.5\plugins\AAA.avs")
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\RemoveGrainS.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\FluxSmooth.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth 2.5\plugins\aWarpSharp.dll")
DGDecode_mpeg2source("C:\Users\Ryan\Desktop\VTS_01 _1.d2v", cpu=6)
why don't you copy/paste what it exactly says
you can always debug your problem starting from simple things to eliminate Avisynth or x264 first,
like just testing your script in VD or MPC-HC (sure it will be slow but just to check for errors) then you advance to very simple command line like: x264 --crf=25 --out.mp4 input.avs
---[Information] [9/28/2013 8:43:54 AM] encoded 1376 frames, 28.78 fps, 2217.98 kb/s
--[Error] [9/28/2013 8:43:54 AM] Process exits with error: 0xC0000005 STATUS_ACCESS_VIOLATION (-1073741819)
--[Warning] [9/28/2013 8:43:54 AM] The 64 bit mode of x264 is enabled. Depending on the error it may help to disable it in the MeGUI settings.
--[Information] [9/28/2013 8:43:54 AM] Job completed
Try running MeGui in administrator (right click on shortcut -> run as administrator).
I need to do this to allow updates and also to be sure there are no problems. 99% of errors disapeared for me when I do this. It's especially true when you are using programs installed in "Program Files" directory (like avisynth in your case)
Thanks guys! updating didn't help, but running the program as administrator worked. That would make sense considering its an access violation error.