Plugins cannot be loaded anymore

[papcom]

I have the problem that my plugins are not anymore loaded when I run a script., which worked perfectly yesterday.

The problem occured after I made a re- install of avisynth 2.5.8, although all the Plugins DLLs are there and the plugins Sources are there, and the pathes are the same as they were before.

(I did first a correct de-install of avisynth, restarted the PC and mad the new install of 2.5.8)

Can anyone help me?

[StainlessS]

Was previous install v2.6 Avisynth ?
2.6 plugins dont work in 2.58.

[videoh]

clsid:

"You need to add the [VideoFred] plugin dir to %PATH% environment variable."

http://forum.doom9.org/archive/index.php/t-166492.html

You're getting thwarted by safe DLL loading.

[papcom]

clsid:"You need to add the [VideoFred] plugin dir to %PATH% environment variable."
.

thanks - I just installed AVS258 on a clean WIn7 PC and installed videofreds scripts and plugins and guess what : it works there.

The Explanation lies in the article you mentioned. Thank You ...I have to go through all of this in order to do the right Thing which keeps me on track also in the future.

[videoh]

Maybe safe DLL loading is not enabled on the win7 machine.

[raffriff42]

Verify Avisynth is using the correct plug-in folder. Check the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth
Perhaps the re-install changed it.

[papcom]

Verify Avisynth is using the correct plug-in folder. Check the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth
Perhaps the re-install changed it.
All is very strange:


as written before, I have installed AVS258, VirtualDub1.10.4 and my videofred scripts, plugins and sources on a new WIN7 installation on a different PC. On this new installation everything works without any problems !

On my usual PC I have both VirtualDUB 1.9.11 und 1.10.4 installed. Also I have AVS258 and my videofred scripts. On this machine the script only runs with VDUB1.9.11 BUT NOT with 1.10.4. --- I have to mention that on this PC I have FFMpegInputDriver Plugin installed with VDUB 1.10.4. probably this plugin is responsible for the problems with the AVS scripts.

Also it is not possible at all to import ProRes MOVs with my AVS Scripts

My goal is to be able to import MOV Files with ProRes422HQ into Vdub AND the AVS Scripts. I am able to open ProRes Movs in my VDub1.10.4 where the ffmpegplugin is installed , but I cannot openProRes files in my VDub1.9.11 where no ffmpeginputdrivers are present.

[raffriff42]

I have the problem that my plugins are not anymore loaded when I run a script., which worked perfectly yesterday.

The problem occured after I made a re- install of avisynth 2.5.8, although all the Plugins DLLs are there and the plugins Sources are there, and the pathes are the same as they were before.

(I did first a correct de-install of avisynth, restarted the PC and mad the new install of 2.5.8)

Can anyone help me?Let's not bring VirtualDub, VideoFred, ProRes or different PCs into this - let's concentrate on resolving the problem you stated in your original post.

Where are your plugins?
Where does Avisynth look for its plugins?

EDIT Can you post a simple example script with AviSource or DirectShowSource, that fails?

[papcom]

as I wrote before:

My Scripts run without Problems as long as I use a clean installed Virtual Dub1.x.x for the AVS Script.

I noticed after all, that my Problem had no direct relation to the avisynth Installation, but to something how DLL's are controlled and assigend in a Windows System. Thatz's why the path's of the plugins were not found anymore. (Probably the ffmpeginputdriver plugin of virtualdub is culprit.)

Actually I do not yet have a final Explanation to the problem

Read more regarding this problem here:

http://forum.doom9.org/archive/index.php/t-166492.html

[foxyshadis]

Your VirtualDub 1.10.4 is 64-bit. Get the 32-bit version.