Can't open AVS files anymore suddenly

[Brakus]

I'm at the end of my rope here, or so it seems.
For some reason, I can't open any of my AVS files anymore in VirtualDub. I keep getting the error:

Avisynth open failure:
MPEG2Source: couldn't open file
(N:\BASARA\MainMovie\SENGOKU_BASARA_D1\VIDEO_TS\SB1-7.avs, line 1)

After I create the d2v file, I usually open the AVS file that's been created, which simply has 1 line:

Mpeg2source("N:\BASARA\MainMovie\SENGOKU_BASARA_D1\VIDEO_TS\VTS_01_1.d2v",cpu=0)

I've had to install DGIndex manually and made sure I copied the DGDecode.dll file from that installation into the plugin directory. I've rebuilt the d2v file several times and that damn error keeps popping up.

There's got to be some step or two that I've been leaving out somehow. Please help!

[Cannonaire]

Try:

Code: Select all

DGDecode_Mpeg2source("N:\BASARA\MainMovie\SENGOKU_BASARA_D1\VIDEO_TS\VTS_01_1.d2v",cpu=0)

[Brakus]

BINGO! That worked. Thanks!

[Pwolf]

Try:

Code: Select all

DGDecode_Mpeg2source("N:\BASARA\MainMovie\SENGOKU_BASARA_D1\VIDEO_TS\VTS_01_1.d2v",cpu=0)

Is that new in the newer version of dgdecode? Never seen it used that way.

[LantisEscudo]

Try:

Code: Select all

DGDecode_Mpeg2source("N:\BASARA\MainMovie\SENGOKU_BASARA_D1\VIDEO_TS\VTS_01_1.d2v",cpu=0)

Is that new in the newer version of dgdecode? Never seen it used that way.

I've seen it before, usually when there's a function name collision with two plugins. The portion before the underscore tells AVS which library to use the specified function from. (mpeg2source is the one I've seen it most often with, between mpeg2dec* and dgdecode both being present so often.)

[Pwolf]

ah, that makes sense.

[Mister Hatt]

What LantisEscudo said. It's an AVS intrinsic to specify which lib you want to load the function from. It usually happens in dgmpegdec vs mpeg2dec3, multiple versions of vsfilter, and different warpsharp plugins. You can also specify versions. You need to know the internal name of the plugin lib though iirc, not the filename, but that might have changed in 2.5.8 or so.