Maximum number of plugins?

[bcn_246]

Ran into some issues with TTempSmooth... initially I thought that it was the filter, however AVSMeter is showing problems with a range of plugins (alphabetically from T to V). Renaming TTempSmooth.dll to aTTempSmooth.dll got it working again.

I have about 250 dlls in my C:\Program Files (x86)\AviSynth+\plugins directory, along with about another 150 avsi scripts. Is there some sort of limit on how many plugins can be used?

http://i.imgur.com/GBW17YA.png

[mariush]

Yeah, there's limitations of the operating system and runtimes used

see https://blogs.technet.microsoft.com/markrussinovich/2009/07/05/pushing-the-limits-of-windows-processes-and-threads/ and https://stackoverflow.com/questions/1437422/working-around-fls-limitations-with-too-many-statically-linked-crts

[bcn_246]

Thanks, will have to go through and delete some... bit of a pain as most are the dependencies of my avsi scripts

[GMJCZP]

What happens is that most load all the plugins by default; What I do in my case is to do what Gordian Knot does, use LoadPlugin from a different folder, so I do not have to worry about how many plugins I have in one place. In Avisynth normal/MT if memory fails me can load up to 50 plugins.

By default I only load the source plugins and some script.

[Groucho2004]

Thanks, will have to go through and delete some... bit of a pain as most are the dependencies of my avsi scripts
Since you're using Avisynth+ you might consider splitting your plugins/avsi's into logical groups (directories) and make use of the "AddAutoloadDir (http://avisynth.nl/index.php/AviSynth%2B#New_Functions)" functionality.

[real.finder]

What happens is that most load all the plugins by default


yes, since avs+ don't unload the loaded plugins after autoload


In Avisynth normal/MT if memory fails me can load up to 50 plugins.


the non plus avs set limit for loaded plugins, yes, but you can have like 1,000 dll in autoload plugins folder and you will not get any problem unless your encode script use more than 50 plugins then you will get error message for the 50 limit

anyway, avs+ behavior now is bad, it must unload plugins like normal avs, see here https://forum.doom9.org/showthread.php?p=1641891#post1641891

[hello_hello]

the non plus avs set limit for loaded plugins, yes, but you can have like 1,000 dll in autoload plugins folder and you will not get any problem unless your encode script use more than 50 plugins then you will get error message for the 50 limit

Ahhhh.... that explains why I can have around 80 dlls in the auto-loading plugins folder without an issue (Avisynth 2.60) even though AVSMeter's -avsinfo gets upset when it hits the 50 plugin limit.

Maybe in a perfect world AVSMeter would load and unload each plugin one at a time?

[Groucho2004]

Maybe in a perfect world AVSMeter would load and unload each plugin one at a time?
That is easily done but the plugin testing will take a lot longer since I would have to create/destroy the IScriptEnvironment for each plugin. No big deal for 10 plugins in the auto-load directory but it could take a minute or so with 250 plugins and a slow CPU.

Edit: I could of course create/destroy the IScriptEnvironment in larger intervals, I'll look into it.

[real.finder]

That is easily done but the plugin testing will take a lot longer since I would have to create/destroy the IScriptEnvironment for each plugin. No big deal for 10 plugins in the auto-load directory but it could take a minute or so with 250 plugins and a slow CPU.

Edit: I could of course create/destroy the IScriptEnvironment in larger intervals, I'll look into it.

what about make it every 50 plugins rather than every 1 :rolleyes:

and aren't you fix this before?

[Groucho2004]

and aren't you fix this before?No, that was a different issue.

[real.finder]

if someone need a solution for this aside from removing some dlls then maybe use or take some ideas from https://forum.doom9.org/showthread.php?t=181989 since this problem not fixed until now in avs+