AVISynth Access Violation? o.O

[Lady Brick]

I'm about halfway through editing a new video and when I went to build a new preview of the last 10 seconds or so of clips I had added, instead of the clips, I got a black screen with the following message:

Avisynth: caught an access violation at 0x0d912d85,
attempting to read from 0xffffffff

I thought perhaps there had been a problem building the preview, so I rebooted, wiped all my preview files out, and rebuilt the whole thing. The first 1:40 or so came up fine, while those last bunch of clips came up with the same error. The AVISynth file played fine in Premiere (I was able to find the clips perfectly fine) and they are from varous places in the footage. This was during a long editing run, so no computer settings or files were changed. Any ideas on how to fix this?

[Garylisk]

It happened to me, too. Appearently sometimes it will do that if you slow a clip down to insanely slow. And then sometimes it just happens for no reason at all.

Just reboot and open premiere again, then re-encode. That worked for me anyway. Just a flaw in Avisynth.. one of many.

[ErMaC]

AVISynth + Premiere sorta has a memory leak that crops up if you lave Premiere open too long. You see, AVISynth will decode a frame on the fly when you request it, but it then caches the result to Virtual Memory (you can see it do this if you open Task Manager in Win2K, go to processes, and see how everytime you see to a new frame the VMSize of premiere.exe increases, but old frames do not cause an increase). Essentially this will cause you to run out of space in virtual memory, and then AVISynth wil attempt to write to Virtual Memory that doesn't exist, and crap out.

Restart Premiere or better yet reboot your machine and start fresh. I periodically close and reopen premiere when the Virtual Memory footprint of premiere.exe exceeds about 1.5GB. I currently have around 2GB of swap space allocated. You can allocate more by going Control Panel->System->Performance->VirtualMemory.

[Lady Brick]

It's still doing the same thing, even starting fresh in the morning right after booting. Any other ideas as to what could be causing this?

[Lady Brick]

To add injury to insult, I reinstalled Premiere and the AVISynth plugins, and it's STILL doing it. It will sometimes let me do one good preview build before it craps out -_-

[klinky]

Iam gonna go out on a limb here and say, either your source is corrupt. A avisynth file is corrupt(unlikely), a windows file is corrupt, or your computer is sucking....


What to do:

Try the file in VirtualDub, does it do the same thing?
re-install AviSynth <---already did that.
Re-rip footage.
remake d2v file.
Try a <a href="http://home.concepts.nl/~hzon00008/bin/ ... zip">later version(Beta6)</a> of avisynth.
make sure you have the latest drivers for video/sound/motherboard.
re-install directX
huck the computer out the window... :p

Maybe DVD2AVI/AviSynth doesn't like your DVD, try a different one, see if the same thing happens.

~klinky

[Lady Brick]

I figured it out. There was a clip I had slowed down a bit earlier in the video and forgot about it. When I saw that also had the error, I replaced it, and everything works fine. I had only noticed the error in the later clips and didn't make the connection. Thanks for everyone's help ^^