Avisynth error: LoadPlugin problem

[tcorr]

Hi all,

I'm trying to take material from my Philips set-top recorder and apply some avisynth filters to it. I've demuxed the material with DGIndex (DGMPGDec v1.4.9 RC2) and got my .d2v file, but when I try to run a very simple avisynth script through Quenc 0.72, I get the following error message:

Avisynth open falure:
LoadPlugin: unable to load "C:\Program Files\DGMPGDec\DGDecode.dll")
(C:\Documents and Settings\Trevor\Desktop\test2.avs, line1)

I've triple-checked that the DGDecode.dll is where I have specified it in the script. The script is simply:

LoadPlugin("C:\Program Files\DGMPGDec\DGDecode.dll")
mpeg2source(C:\demuxed\CSI.d2v")

I've searched the forums for the last two days trying to figure this out, and I've resintalled Avisynth 2.5.7, but to no avail. One topic in the myriad of posts I found while searching mentioned an older installation of Gordian Knot, which I do have, but DGMPGDec was still DVD2AVIdg at that time, so I don't see how that would be a problem.

Any ideas?

Thanks,
Trevor[/img]

[kevo777]

The DLL could be corrupt. Have you also re-installed DGDecode and QuEnc? I would experiment around with different install paths when doing so...especially since these apps aren't really "installed", but rather unzipped into specified folders.

[Alex_ander]

Maybe there's another copy of it in Avisynth 'plugins' folder (e.g. from some other program using Avisynth) and it is loaded by default?

[tcorr]

Thanks, Kevo.

I'll try reinstalling (unzipping) QuEnc again. The DGDecode.dll was taken from the most recent version of DGMPGDec downloaded just a couple of days ago, so if the .dll is corrupt, I'll need to find another source for it.

By the way, would you know if the RC2 (release candidate 2) version of the DGMPGDec is considered more of a "beta" than a true release? I was a bit confused as to what is the latest "stable" version. I checked out the website for the tool, but aside from the change history, I didn't see anything that spelled it out in black-and-white.

Trevor

[tcorr]

Maybe there's another copy of it in Avisynth 'plugins' folder (e.g. from some other program using Avisynth) and it is loaded by default?

That is a distinct possibility. I've been using QuEnc with DVD Rebuilder for a few years now, so I've had Avisynth on my harddrive for awhile. I guess the question is: which DGDecode.dll would be correct? The one from the DGMPGDecode download or the one in the Avisynth download? I guess I'll try both, in the Avisynth plugins directory, and see if that fixes the problem.

Thanks Alex

[FulciLives]

Maybe there's another copy of it in Avisynth 'plugins' folder (e.g. from some other program using Avisynth) and it is loaded by default?

That is a distinct possibility. I've been using QuEnc with DVD Rebuilder for a few years now, so I've had Avisynth on my harddrive for awhile. I guess the question is: which DGDecode.dll would be correct? The one from the DGMPGDecode download or the one in the Avisynth download? I guess I'll try both, in the Avisynth plugins directory, and see if that fixes the problem.

Thanks Alex

You need to match the DGDecode DLL with the version of DGIndex you used to create the D2V file. When you install DGIndex you should have one folder with all the needed files. When you use your LoadPlugin command make sure you point to the DLL in that same folder.

- John "FulciLives" Coleman

P.S.
I haven't used Quenc in a long while but in my opinion HCenc is the better encoder.

[tcorr]

You need to match the DGDecode DLL with the version of DGIndex you used to create the D2V file. When you install DGIndex you should have one folder with all the needed files. When you use your LoadPlugin command make sure you point to the DLL in that same folder.

That's the confusing part. The .dll that came with the version of DGIndex that I just downloaded is the one I'm pointing to in my avisynth script. To your knowledge, is there the possibility that, even though the script is specifying one location for the .dll, Avisynth is looking for it in another location?

I haven't used Quenc in a long while but in my opinion HCenc is the better encoder.

Up until now, I've never had problems with QuEnc, but I'm certainly open to trying another encoder to see if it will play well with Avisynth.

Thanks for the reply and for giving me more ideas to try.

Trevor

[manono]

To your knowledge, is there the possibility that, even though the script is specifying one location for the .dll, Avisynth is looking for it in another location?

Yes, if there's a different DGDecode.dll in your AviSynth Plugins folder or elsewhere in the path, like the System32 directory.

If I were you, I'd search for any and all DGDecode.dlls on your computer and toss them all out, just to be safe. Then start over and make a fresh D2V file from the most current DGIndex package, and then make sure you use the DGDecode.dll from the same DGMPGDec package, making sure to point the path to it correctly. I agree with everything FulciLives said (including the encoder suggestion).

[tcorr]

Thanks, manono. I've used some of your posts from 2006 Jun 07 as a guide in trying to figure some of this stuff out.

I will get rid of all DGDecode.dll files and start over, including trying out HCenc.

As a long-time lurker but a first-time poster, I really appreciate all the help the posters on this board provide. You guys rock

Trevor

[tcorr]

Just a quick follow-up to my problem...

I removed all dgdecode.dll files laying around on my harddrive, then I downloaded the most recent version of DGMPGDec (1.4.9) and tried again. I still recieved the same error message.

I then decided to download the previous release of the package ( 1.4.8 ) and I was successful.

I removed the 1.4.8 version and replaced with 1.4.9 again and I get the error message, so I think the dgdecode.dll in 1.4.9 is corrupt for some reason, as kevo777 thought it might be. I think manono's suggestion of clearing all of the old dll's (I had 5 of them) was also crucial to resovling this.

Thanks for all the help,
Trevor

[manono]

Interesting, and I'm glad that with a bit of ingenuity you solved your problem. I've been using 1.4.9 Final with no problems since it came out a couple of days ago. If that's newer and different from the one you tried without luck, you might give it a try.

I did, however, come across someone else having the exact same problem as you (I think):

http://forum.doom9.org/showthread.php?t=116841&page=16

[45tripp]

I had the problem with the last 1.4.9 beta. I reverted to 1.4.8
Haven't had a chance to try the final 1.4.9 yet.

[FulciLives]

I'm still using whatever version came with the last updated version of autoGK LOL

I guess I should download the 1.4.9 Final version, huh?

- John "FulciLives" Coleman

[Soopafresh]

Consider also upgrading to the latest 2.57 of Avisynth. Make a backup of your Avisynth.dll in \windows\system32 and replace it with this one:



avisynth_257_latest.rar

[Soopafresh]

Just learned something interesting re v1.49 of the DGindex package. It needs msvcr80.dll. Earlier versions didn't.

[FulciLives]

Just learned something interesting re v1.49 of the DGindex package. It needs msvcr80.dll. Earlier versions didn't.

What the hell is msvcr80.dll and where do I put it? Does it go in the "\windows\system32" folder?

- John "FulciLives" Coleman

[Soopafresh]

Hee hee. John, you have a way with words.... This is where it is located, but it ought to work just fine in the system32 folder under c:\windows



Hmm..actually, it might be better just to install the runtime library. Here's an alternate download location for it. Just unpacked the installer to make sure it was the real thing.

http://download.silicondust.com/vendor/dotnet/vcredist_x86.exe

[Alex_ander]

What the hell is msvcr80.dll...?

Google says:

msvcr80.dll is a process associated with Microsoft Visual Studio 2005 from Microsoft Corporation. It is the Microsoft C Runtime Library and is used by programs written with Microsoft Visual Studio 2005.

From what a M$ man (Martyn Lovell) says (http://www.dll-files.com/dllindex/dll-files.shtml?msvcr80),
this file shouldn't be copied to any system directory, it should come with the application that needs it.

[Soopafresh]

Right you are, Alex_ander. I posted a link above.