Setting up avisynth for speed

[smartel]

Filters that are in the plugin directory are loaded up by default at startup and eating memory !
Is that right ?

is there any optimal way to setup avisynth to loadup just the required ones ?

i have a bunch of plugins (useful and not) just for trying them up
and i just read that it may decrease it's speed when accumulated by default in memory

can i make a folder with my video source and the necessary filters
and just delete it when finish and keep my original avisynth folder with my bank of filters ?

How have you setup your Avisynth ?

and sorry if it has been already covered

[Chris K]

Filters that are in the plugin directory are loaded up by default at startup and eating memory !
Is that right ?

It doesn't eat memory. It only slows down the startup procedure.

At startup all plugins in the "Plugins" folder are loaded to find out in which plugin the requested commands reside. When Avisynth doesn't find the command it unloads the plugin again. Finally only the plugins that are needed are kept in memory.

can i make a folder with my video source and the necessary filters
and just delete it when finish and keep my original avisynth folder with my bank of filters ?

One option would be to create a second plugins folder like e.g. "plugins2", then move all your plugins to it and always load them manually in your script. But as said, this would only speed up the Avisynth startup procedure.

[smartel]

so .. the only thing influencing the speed is the choice of filters themselves (and the avisynth version) !?

[Chris K]

Basically, yes! But the flow of the script may also influence speed a bit. Colorspace conversion seems to slowdown but if you can avoid this with a different command order depends on the script. The manual mentions this somewhere.

[Gavino]

At startup all plugins in the "Plugins" folder are loaded to find out in which plugin the requested commands reside. When Avisynth doesn't find the command it unloads the plugin again. Finally only the plugins that are needed are kept in memory.

More or less right, but more accurately what happens is this.

At startup all plugins in the "Plugins" folder are loaded to find out which commands they contain. (At this point the script has not been read, so Avisynth does not know which commands will be requested.) After noting this information, each plugin is unloaded again. Then when the script is processed, only the plugins containing the requested commands will be loaded again (and retained in memory) the first time they are needed.