I am an idiot.

[OzzieAlThor79]

I used DGIindex, saved my d2v file. I have my roughly 170 kb .d2v file.

I have my separate AviSynth script file.

I go into VDB and choose "Open Video File", choose my script and it doesn't work. "There is no function named mpeg2source"

Should I just be using the VOB? (<-- I don't think so)

What am I missing in the guide?

[Kariudo]

if you got the amvapp, you shouldn't be having this problem.
If not, make sure that dgdecode.dll is in avisynth's plugins folder (..\program files\avisynth2_5\plugins\)

if dgdecode.dll is already in there, look for warpsharp.dll and take it out of the plugins directory

[OzzieAlThor79]

Followed instructions. Both files were there and I removed the second one. Same error.

Think I need to uninstall then reinstall the app again?

[mirkosp]

Try using the following code instead:

Code: Select all

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\DGDecode.dll")
dgdecode_mpeg2source("your file.d2v")

[OzzieAlThor79]

Try using the following code instead:

Code: Select all

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\DGDecode.dll")
dgdecode_mpeg2source("your file.d2v")

Thanks. That worked. Why did I need to do that? How can I fix it going forward?

[mirkosp]

Well your issue was at least one out of either of these things:
1) Autoloading didn't work. In this case, loading the plugin manually did the trick.
2) You also had another plugin that's called with mpeg2source (such as DVD2AVI's mpeg2dec3). In this case, the function call breaks since it doesn't know which one it's supposed to call, and specifying dgdecode_mpeg2source makes it know which one of the two should it be looking for.
See which of the two fits, but in the first case there's hardly anything you can do besides just giving in and loading the plugin manually each time. It'll work that way so it's not something to worry about. In the second case you can just delete or move the other conflicting dll and call it a day.

[OzzieAlThor79]

Thanks!

[Scintilla]

See which of the two fits, but in the first case there's hardly anything you can do besides just giving in and loading the plugin manually each time.

Actually, there is: make a .AVSI file in your plugins directory that contains the LoadPlugin line, so the line gets automatically called every time. That's what I do.

[OzzieAlThor79]

I decided to reinstall everything and see what I got.

It works automatically now.

I'll definetly save the info in this thread for future use. Tons of help.

[mirkosp]

See which of the two fits, but in the first case there's hardly anything you can do besides just giving in and loading the plugin manually each time.

Actually, there is: make a .AVSI file in your plugins directory that contains the LoadPlugin line, so the line gets automatically called every time. That's what I do.

/me facepalms
I can't believe I didn't think about that!