Patch : load plugin automatically

currently,
if you load a patch that references a plugin thats not loaded, the module is just omitted from the patch.
basically, you have to either manually load the plugin, or have it set as auto-load.
(at least this is what happened for me… unless there is a bug?)

what id like is IF the plugin is present on the sdcard, then meta module automatically loads its when the patch is loaded. (ofc, assuming its on the sdcard!)

Im assuming the load/auto load is to save memory, only having the plugins you are using in memory.

the issue is, you may well only use a particular plugin for a few patches, for a specific use.
so you want have it loaded when you load the patch, and frankly, you’ll probably have forgotten you used it… and the patch will just not work, and you wont know why.

ofc, this brings up the ‘issue’ that if you keep loading new patches, with different plugins - you’ll end up loading a lot of plugins.

so perhaps, in this use-case, MM could, when switching patches, unload all modules that have not been explicitly loaded or loaded via auto-load.
( I guess you could ask user … but its probably ok to just do it)

as a bonus , lol… (but somewhat related)
it might be useful to somewhere detail modules that were missing when loading a patch - this will be useful if users start sharing patches.
or perhaps even just have a blank panel/module, with name of the module in patch view, so you know something is missing.

Yeah, I thought about having a pop-up if modules are not found, that lists what the modules are and asks if you want to search and load plugins on disks. It can take a few seconds to load a plugin and a patch might need to load a few plugins.

Yeah, auto-unloading would be useful. Right now you load all the plugins and not be anywhere near the limits. But eventually that won’t be the case…

I like the idea for a blank module with the name of it.

yeah, perhaps if you have the blank module … you could then click on it to attempt to load it?

though Id still prefer it to just load :wink:

I can see in live performance you might not want that pause… but then presumably you already have pre-loaded… since otherwise the patch (currently) would not work anyway.
i.e. auto-load becomes an ‘optimisation’ / cache

perhaps call it ‘pre load’ to make it clear !?

btw: good to know, you can load all currently… so this is ‘future problem’

does the ‘system dialog’ currently detail how much mem is free? might be useful in this area for the future. esp. if you start loading samples etc!