Assuming you have AvsPmod (if not, you can grab it here), what does that say when you try to preview the avs? If it works there, then something fishy's going on with vdub, otherwise, AvsPmod might give us a clearer error.The avs code itself looks pretty much fine (you should crop a bit horizontally but it's nothing major and chances are that the DVD might actually have been done non-ITU, which seems depressingly common nowadays, so it might be better not to, oddly enough), and the vdub error doesn't say anything about missing plugins, so I'm kinda left wondering.

By opened, do you mean just open to check the code, or actually show the video preview (hit F5 in the program)? If you can actually view the latter, then the script is correct, and the issue is definitely lurking somewhere in VirtualDub or the VfW framework.

FFFFFFFFFFFFF.YOU DON'T DO THAT.THAT FUCKS WITH DIRECTSHOW.The problem was in the VfW framework, indeed.But installing random directshow filters will just make directshow worse and create conflicts. It's a very dangerous thing, I can't stress this enough, as in the worst case one won't be able to properly clean the register without formatting the system altogether.You should try to uninstall that as much as possible (or straight up do a system restore to before installing it) and just install cccp to keep directshow in order.

This afternoon I rolled back my system to this morning. I then installed CCCP. However, I'm back to square one with opening up AVS files in VirtualDub. I know you said there was something wrong with VirtualDub, so is there any other way I can get my footage?

I forgot to ask before, but you weren't using mismatching 32bit/64bit avs and vdub, right? Otherwise it wouldn't work out.Suggestions to bring forth in case you were already on matching 32bit (if you weren't just use the 32bit stable versions first):1) Try to update avisynth to the latest alpha version, currently 2.6.0 Alpha 4: http://sourceforge.net/projects/avisynt ... _Releases/2) Try to use the 1.10 experimental branch of virtualdub: http://virtualdub.sourceforge.net/Do make sure you use the 32bit version of everything, otherwise it's not gonna work.

Also, 19.189fps sounds suspiciously close (19.18081918081918..) to what you get if you try to "ivtc" on a 23.976. Perhaps you had force film selected in dgindex before you ivtc'd in avisynth? If that's the case, reindex with honour pulldown, and then ivtc like normal if it's less than FILM 99%, or force film again and don't IVTC in avisynth if it's over that.

It looks like uninstalling my AVISynth and reinstalling the newest one, as well as getting the 1.10.3 Vdub, has solved the issue at last for me. After I reindexed the footage, Vdub opened up the AVS file easily, and the clip pulling went smoothly. Thanks for all your help!