AVISynth and VirtualDubMod

RichLather · Post by **RichLather** » Wed Aug 09, 2006 8:51 pm

Wait, what? I know what those two things are, but danged if I know how to designate one or the other for DGIndex.

Rajin Recoil · Post by **Rajin Recoil** » Wed Aug 09, 2006 9:04 pm

Sorry, lack of information given on my part. In your AVS script, when you load the plug-ins, make sure that you're using dgdecode.dll. Since your using AVISynth 2.5.6, it should automatically load the plug-ins from the plug-in directory. So if you have both, mpeg2dec3.dll and dgdecode.dll in there. I would imagine that there would be a conflict for function names. That's why I have my functions as filename_function(parameters). For example dgdecode_mpeg2source(<PATH>).

But then again, AVISynth refuses to work with VDM for me, so I could just think I know what I'm talking about ^^;;

Qyot27 · Post by **Qyot27** » Wed Aug 09, 2006 10:36 pm

If MPEG2Dec3 is in AviSynth's plugins folder, move it out of there or delete it outright. It's outdated and only works with DVD2AVI, not DGIndex.

If you try to open the script that crashes VirtualDub through Windows Media Player instead, do you get an error? I also seem to remember that the filters collection that gets installed with the AMVapp sometimes causes problems and wonky behaviour on some computers, and that when I had that problem, all it took was going into AviSynth's plugins folder and moving/deleting plugins I didn't need. Eventually whatever it was got straightened out. My suggestion would be to move all the filters out, then put back only the ones that the problematic script in question depends on, and see if the crashing stops. If it does, then try to isolate which of the plugins you moved was the culprit (unless you feel confident enough to just go in and delete things you doubt you'll ever use and that ends up fixing the issue).

Rajin Recoil · Post by **Rajin Recoil** » Wed Aug 09, 2006 11:00 pm

Qyot27 wrote:If MPEG2Dec3 is in AviSynth's plugins folder, move it out of there or delete it outright. It's outdated and only works with DVD2AVI, not DGIndex.

It's gone now

Qyot27 wrote:If you try to open the script that crashes VirtualDub through Windows Media Player instead, do you get an error? I also seem to remember that the filters collection that gets installed with the AMVapp sometimes causes problems and wonky behaviour on some computers, and that when I had that problem, all it took was going into AviSynth's plugins folder and moving/deleting plugins I didn't need. Eventually whatever it was got straightened out. My suggestion would be to move all the filters out, then put back only the ones that the problematic script in question depends on, and see if the crashing stops. If it does, then try to isolate which of the plugins you moved was the culprit (unless you feel confident enough to just go in and delete things you doubt you'll ever use and that ends up fixing the issue).

I probably should've stated this before. But I don't have AMVapp. Instead I've just hunted down what I needed.

And as for the script, it runs in WMP and MPC. The strange thing is that it also opens in VirtualDub. It just seems to be VirtualDubMod that doesn't want to open the script in question, or any script I've made.

Gepetto · Post by **Gepetto** » Thu Aug 10, 2006 11:39 am

Then, as I have stated before, the problem is in VirtualDubMod. Install a different version, or re-download the one you have.

Melanchthon · Post by **Melanchthon** » Thu Aug 10, 2006 9:39 pm

What version of VDM do you have? The one that comes with the AMVApp is 1.5.4.1 b2066. I've had problems with 1.5.10.2 b2542 (which I installed only in an attempt to get tritical's cvs AviSynth build working. Didn't work). My problem was with it only displaying the first frame, but since it didn't give me the result I wanted I just went back to the one I knew worked with every script I've thrown at it.

Rajin Recoil · Post by **Rajin Recoil** » Thu Aug 10, 2006 9:52 pm

I've got both 1.5.4.1 b2066 and 1.5.10.2 b2542. They both produce the same error.

Gepetto · Post by **Gepetto** » Fri Aug 11, 2006 8:30 am

Rajin Recoil wrote:I've got both 1.5.4.1 b2066 and 1.5.10.2 b2542. They both produce the same error.

Would they by any chance be in the same directory? One corrupt DLL is enough to mess up every version of VD and VDM installed in the same place.

Rajin Recoil · Post by **Rajin Recoil** » Fri Aug 11, 2006 11:59 am

Nope, every version I have of VD and VDM has it's own directory. Another interesting thing that I just stumbled upon, is that I get the same error in VD if I try to open more than one script file. So If I load a script, make a change to it, then load it again, it'll create the error.

Gepetto · Post by **Gepetto** » Sat Aug 12, 2006 6:44 am

Well, that is odd. Since it crashes in every version of vdub, one would expect the problem to be in AviSynth, but it works with all the other players, so the problem should be in vdub. I'm way over my head here, but maybe Windows is just being a bitch about something?