Error loading DGIndex-made avs scripts into VDubMod

qzxy · Post by **qzxy** » Wed Oct 03, 2007 4:54 am

Hi! I've been trekking through the AMVapp guides (AMAZING WORK!!), trying to get started in vidding, but I've come to a snag. For some reason I'm unable to import the avs files created by DGIndex into VirtualDubMod. I get the MPEG2Source: unable to load file "somethingorother.d2v" in something.avs, line something error, which the guide says "will occur if your MPEG2Source command isn't pointing to a d2v file or you've made a typo." I don't think there's a typo, since I haven't touched what DGIndex generated (accept to add a resize command, but when I took it out, I still got the same error) and the d2v file definitely does exist, so I'm not sure what this means or how I would fix it.

This poster seemed to be having a similar problem, but I don't understand the solution (search for all instances of MPEG2Dec3.dll in my system and replace with DGDecode.dll? Don't want to try that unless this is definitely the same thing and that's definitely what I'm supposed to do!).

Thank you for any help!

Gepetto · Post by **Gepetto** » Wed Oct 03, 2007 8:47 am

Yes, that's the same problem, go ahead and switch them.

Don't worry about replacing the file just because it ends with .dll - it's not a Windows system file, all it does is decode .d2v and other mpeg-2 videos in AviSynth.

Scintilla · Post by **Scintilla** » Wed Oct 03, 2007 5:09 pm

Gepetto wrote:Don't worry about replacing the file just because it ends with .dll - it's not a Windows system file, all it does is decode .d2v and other mpeg-2 videos in AviSynth.

It's not the fact that it ends with .dll; it's the fact that it <i>begins</i> with MPEG2Dec3.

Qzxy, you said you had used DGIndex to make the D2V files. In that case, yes, you should get rid of MPEG2Dec3.dll and/or MPEG2Dec3DG.dll from your AVISynth plugins directory and replace them with whatever version of DGDecode.dll came with your copy of DGIndex.

qzxy · Post by **qzxy** » Thu Oct 04, 2007 12:30 am

OK, I'm in my Avisynth plugins folder (Program Files/Avisynth 2.5/plugins) and there's no MPEG2Dec3.dll or MPEG2Dec3DG.dll, while there is a DGDecode.dll. I searched my system for the first two and none were found.

Gepetto · Post by **Gepetto** » Thu Oct 04, 2007 7:32 am

Perhaps it's a different version from the DGindex build you're using?

qzxy · Post by **qzxy** » Thu Oct 04, 2007 12:56 pm

Well, I downloaded them both at once from the AMVapp, so would that have happened? And how would I know if they were different?

I've uninstalled and reinstalled the entire AMVapp thinking maybe I changed something that wasn't supposed to be changed during the install, but I tried to open the d2v file in VDubMod and got the same error.

Unless I need to remake the d2v file after the reinstall?

Sereenie · Post by **Sereenie** » Thu Oct 04, 2007 1:53 pm

Did you maybe move the d2v file after it was created?

S.

qzxy · Post by **qzxy** » Thu Oct 04, 2007 2:04 pm

Nope, the vob files, the d2vs, and their avisynth scripts are in all the folder where they were originally created. I checked the filenames in the scripts just in case and they're right.

Man, I thought this was going to be one of those dumb, easily fixable questions.

I haven't gone through the whole Guide yet (I stopped at the indexing when that didn't work), but is the indexing absolutely necessary? Are there ways to process the files with avisynth scripts (like resizing fixes) without using d2v files? In case the problem isn't fixable...

Gepetto · Post by **Gepetto** » Thu Oct 04, 2007 3:15 pm

There are ways to edit directly from the VOB files but they're very very buggy and frame-innacurate.

.d2v files are very emo, so if you so much as sneeze near your keyboard they'll stop working. Try making new ones.

Sereenie · Post by **Sereenie** » Fri Oct 05, 2007 10:01 am

Just another idea: is a relative path used in the script, or put the whole path? I think I remember there being a problem when relative paths are used.

S.