AviSynth Script Generator Won't Open .d2v

[doucrix]

AviSynth script error:
MPEG2Source: couldn't open file

http://img132.imageshack.us/img132/5729/avisynthscripterror1bd.jpg

I can't find the exact reason, I have installed
everything that the 'sticky guide' instructed. this seems
like something easily fixed. help appreciated.

[ChronoCross]

make sure that DGdecode.dll is in your avisynth plugins directory (the version that corresponds to the version of DGIndex your using). Also make sure your opening a .d2v file.

[doucrix]

the DGDecode.dll is in my AviSynth plugins folder and it's
the same version I am running. Directory paths check
out okay in the MeGUI settings. I don't know what is wrong
with my setup and my .d2v files are legit. do tha Hamma! omfg.

[berrinam]

the DGDecode.dll is in my AviSynth plugins folder and it's
the same version I am running. Directory paths check
out okay in the MeGUI settings. I don't know what is wrong
with my setup and my .d2v files are legit. do tha Hamma! omfg.
Grab the newest version of DGMPGDec, and as ChronoCross said, put the DGDecode.dll that comes with it in your AviSynth plugins folder. Recreate the d2v file with your new version of DGIndex (through MeGUI if you want) and try loading the new d2v file. The new version should have more informative debuggin information.

[doucrix]

and thats not the problem.
the log said at the bottom - couldn't force film

[berrinam]

What log, where?

If you want help, please try to make it easier for us. Provide details. Have a look at the MeGUI Bug Reporting Guidelines (http://forum.doom9.org/showthread.php?t=105160). In particular, post your entire log, not just your summary of it.

Now, you're saying there was a problem with force film'ing. Have you made sure that you are running the newest version, as I said?

If so, see if you get the same error if you turn off automatic force film in the MeGUI settings (not that you should actually do that). Please post your log file in both situations (auto FF on and off) so we can see if there is some problem here.

[doucrix]

running the newest version my DGDecode.dll is in my AviSynth plugins folder.
this left me nothing new, and is the same result i started with before any advice.

PAL DVD::

MeGUI settings::force film off/on
http://img352.imageshack.us/img352/2149/autoforcefilm0hc.jpg

MeGUI's d2v creator::force film warning no matter what setting i chose
http://img397.imageshack.us/img397/2561/forcefilmwarning5ye.jpg

MeGUI's log::same error auto FF/none
http://img352.imageshack.us/img352/7866/d2vlog2ul.jpg

NTSC DVD

MeGUI's d2v creator::auto ff setting::force film warning
http://img397.imageshack.us/img397/2561/forcefilmwarning5ye.jpg

MeGUI's log::No force film settings d2v creator works without errors
http://img395.imageshack.us/img395/1493/logok2jx.jpg

load .d2v above with Avisynth Script Creator:: same error again
http://img361.imageshack.us/img361/3475/avserror4or.jpg

[berrinam]

Well, can you do what I asked please? Post your d2v file?

[ChronoCross]

because you CANNOT run forcefilm on your source even if it is detected as FILM. because DGINDEX is not built to do 25->24fps transform. it's probably corrupting the bitstream. try not running force film.

[doucrix]

the ntsc forced film that didnt error using MeGUI d2v creator but wouldnt load in avisynth script creator and the pal none-forcedfilm that MeGUI retardedly wanted to forcefilm on even though my settings were off and had to do manually and of course wont load in avs creator either.

[berrinam]

Ok, there's nothing wrong with your d2v per se. The force film issue with PAL is simply due to the fact it can't open the d2v file -- if it could, it wouldn't try to force film it. I would say that you either have some files missing/relocated, or AviSynth is using the wrong dll. Check your AviSynth plugins to see if you have mpeg2dec.dll there. It may be overriding DGDecode.dll's mpeg2source function.

[gbates]

I'm almost sure that the problem is with mpeg2dec(3).dll as berrinam said.
Yesterday I was fighting with meGUI for 3 hours because of this problem.

[doucrix]

FIXED
http://img74.imageshack.us/img74/6520/thnku9fo.jpg
thank you for figuring out this problem. thanks everyone who
posted to this thread. thanks berrinam for your time. taking out
the MPEG2Dec3dg.dll in my AviSynth plugins folder worked. i don't
know if i read somewhere to do that or I copy/pasted too much.
my mistake to have more than what was stated in the guide.

[dimzon]

Ok, there's nothing wrong with your d2v per se. The force film issue with PAL is simply due to the fact it can't open the d2v file -- if it could, it wouldn't try to force film it. I would say that you either have some files missing/relocated, or AviSynth is using the wrong dll. Check your AviSynth plugins to see if you have mpeg2dec.dll there. It may be overriding DGDecode.dll's mpeg2source function.
AFAIK fresh AviSynth supports DllName_FunctionName syntax to avoid such collisions.
Maybe it's time to use DGDecode_Mpeg2Source...

[berrinam]

AFAIK fresh AviSynth supports DllName_FunctionName syntax to avoid such collisions.
Maybe it's time to use DGDecode_Mpeg2Source...
I was thinking the same thing.... but it's ugly. Perhaps an option in the settings? Or maybe just a note in the Guide?

[dimzon]

but it's ugly.
I really doesn't think it's ugly at all. Anycase it will be more stable solution IMHO.

[berrinam]

I will update MeGUI to use that syntax for DGDecode.

EDIT: Done.