Log in

View Full Version : avisynth unblock help


whiteshark99
21st November 2014, 12:09
I'm getting errors any help out there.

---------------------------
Video Player Error
---------------------------
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
---------------------------
OK
---------------------------


---------------------------
Video Player Error
---------------------------
As a result during this session the option "Improved AVS opening" in the settings is now disabled. Please disable it there completly if necessary.
---------------------------
OK
---------------------------

StainlessS
21st November 2014, 14:26
Cannot assist, but I think I'm correct in saying that MeGUI switches back ON the "Improved AVS opening" when you update, gives me trouble too.

EDIT: IIRC, I have most problems with "Improved AVS opening" on old P4 XP32.

hello_hello
22nd November 2014, 02:15
The "improved AVS opening" thing is returned to normal after MeGUI is restarted, or you can go into MeGUI's preferences and re-enable it yourself.
I find the way MeGUI automatically disables "improved AVS opening" a bit frustrating at times. I can disable it myself if need be, but maybe many users wouldn't know to do so. Disabling it doesn't block Avisynth, it opens a script for previewing at the beginning instead of in the middle.

If you're indexing h264 video with ffms2, try switching to the portable version of Avisynth+ in MeGUI's preferences. For some reason there's an issue causing those sorts of problems if you crop or resize too quickly in MeGUI's script creator, but the portable Avisynth+ and ffms2 seem to play a nicer together in that respect.

Having said that, I've been having problems with scripts containing complex filtering at times. Filtering more complex than any MeGUI adds to a script itself, at least. Using SRestore in a script seems like a sure-fire way to end up with the same "attempted to read or write protected memory" error if I preview the video and let it play for too long, and it's been happening occasionally when using QTGMC. I don't know why.

I'm running XP if it makes a difference.

whiteshark99
23rd November 2014, 09:51
thanks guys.