AviSynth 2.5.5 plugin path bug?

[hartford]

I uninstalled v 2.5.4 and installed v 2.5.5.

I wasn't asked about setting the plugin path as in previous versions.

I used regedit and found this this key:
HKEY_Local_Machine\SOFTWARE\AviSynth

Value C:\Program Files\AviSynth 2.5.5\plugins

So, the path seems to be set, but when I try to invoke a plugin
without the path, I get a "not found" error.

Does this happen to anyone else?

Thanks.

Build had this as part of the filename: 140304

[Fizick]

In Avisynth 2.5.3 I save such reg file:


REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
"plugindir2_5"="E:\\Program Files\\AviSynth 2.5\\plugins"

[hartford]

Thanks for the reply, but that doesn't answer my
question.

Does the release 2.5.5 alpha 140304 have a bug or not?

The problem is that 2.5.5 doesn't seem to "find" the
plugin path, eventhough it is specified in the registry.


I can't do:

LoadPlugin("Undot.dll")


I must do like:
LoadPlugin("c:\avisynth\plugin\Undot.dll")


I must do the full path, eventhough the plugin
path is in the registry.

That's the bug.

[Richard Berg]

The registry's plugin_dir doesn't affect the working directory of the application. (Otherwise you'd have to give full paths to your video files, too.) There is a SetWorkingDir function if you need it, but in general it's best to let autoloading work by itself.

Edit: perhaps your plugins are still in the old directory? (although, minor revs should use the same dir...)

[hartford]

Thanks for the reply.

No, I copied all my plugins to the new directory (old one still available.

I'm dropping this. It's just a minor inconvienence to include the
full path.

Apparently, I'm the only one having this problem. But, it's minor.
So...

Again, thanks.

[stickboy]

If your plugins are in the path specified by the registry, you shouldn't need to call LoadPlugin at all. :confused:

If you really want, you can do:
function MyLoadPlugin(string dllName)
{
LoadPlugin("c:\avisynth\plugin\" + dllName)
}

[Si]

As stickboy is saying - the plugin path is there to automatically load plugins so that if a plugin is in the specified folder, then you don't need to add a LoadPlugin command - the plugin is available to you as if it was part of Avisynth itself.

I don't know what happens if you effectively load the plugin twice but it can't be good ;)

regards
Simon

[hartford]

Dudes:

I know that it "should" work; but it doesn't.

I don't know why it doesn't.


I'm no longer willing to "fight" it. I'll just go the "long path"
route.

Please...drop it.


Maybe, when 2.5.5 is out of alpha it will work.

Not a major problem.

Thanks.

[Si]

Taken to PM

regards
Simon

[hartford]

Ok, peeps. The problem is fixed.

I don't know what caused it; whether it was a "bad" install
or something else, but the problem has been fixed.

I uninstalled date-coded build 140304-2.5.5 alpha
and installed build 200304-2.5.5 alpha.

Was there some problem with 140304? Beats me, since I seemed
to be the only one complaining .


But, now it works, and everything is happy in Guinea Pig land.


Thanks, siwalters, for your kindness.