AviSynth plugin support failure with AMVapp 3.0b

[dowhatnow]

I just tried opening some older projects in Premiere Pro 2.0, and the first thing it asks is: "Where is the file 'insertnamehere.avs'?" I lead the program in the right direction, and it does three things:

1. Tells me that I have a "DGDecode/DGIndex version mismatch".

I figure this should be fixed with a complete re-indexing of all my projects, saving them as the same file name referenced in the .avs files. No harm done, or so I hope.

2. Tells me that it I have an Avisynth error and that it couldn't import "C:\blankclip.avs"

I'm going to take a guess and say that it's an interconnected problem stemming from thing 1 as mentioned above.

3. Gives the "File Import Failure" dialog box and lists the path of the .avs file and gives the error "Unsupported format or damaged file."

The obvious final blow in this 3-hit combo.

All I did to correct this was do exactly what I thought I needed to do: re-index my indexes. Just overwrite the existing .d2v file that I had, and go back to working on whatever I was doing at the time.

Obviously, it's a beta for a reason, but I for one like to be on the leading edge of software. I'm posting this in the hopes that people who are transitioning to AMVapp 3.0b from the previous version read it, and hopefully eliminate the same problem I had, regardless of their video editing software. Not only that, I'm hoping to at least slow down the flood of "It's not working like it's supposed to, please help" threads.

Another thing I noticed is that while indexing new .vob files, and while d2v file was created, a .avs file was not. In the previous version, .avs files were created with every .d2v, but does not occur with this one. Simple fix: make one. That, or wait until it's no longer a beta.

The one question I do have is this: Just what is blankclip.avs and where is it? If it's nothing terribly important, just tell me to disregard it.

[Scintilla]

I'd suggest going to your AVISynth plugins folder and looking through any and all .AVSI files (auto-loading helper scripts) for any mentions of <b>Import("C:\blankclip.avs")</b>, because that's the only thing I can think of that would be causing problem #2. If you find any such lines, get rid of them.

[Zarxrax]

I also have no idea what could cause problem number 2. I don't believe it's related to amvapp in any way, but maybe I'm wrong.

As for the dgindex files not working without reindexing, that's the reason that every single version of the amvapp has always had a big fat warning before you install it saying that amvapp should never be installed while you are in the middle of projects. The developer of DGindex continues to break backwards compatibility with each new release, which means your old d2v files wont work.

I wasn't aware that the older versions of amvapp were set up to automatically generate avs scripts. I might see about adding that back, or maybe not. In any case, you can enable it yourself within dgindex.