I’ve noticed that if I add all the available plugins supported by MM that some patches ‘Ambient Gen’ as an example, will drive the CPU > 100% and not run. Not sure why but I can imagine memory filling up and the CPU swapping.
So, since there is a manifest at the start of the .yml of which plugins are in use, can MM let me know? I can then load only the ones I need. You could even imagine and auto load feature (not the one at startup).
As an example, if I try and load something that requires Elastika, can MM tell me ‘Sapphire’ plugins are not loaded’. That way I can load only the plugins needed for a patch.
Conversely, since loading plugins can affect performance, and if you are switching patches in a live situation, can plugins be unloaded if not in use? I hate to have to isolate MM with a separate power supply in the rack to be able to reboot it without shutting down the whole setup.
I am still new to MM so if there are features for this already let me know.
Yeah, it would be great to have a pop-up that says “load all plug-ins needed for this patch?“ whenever I try to load a patch and don’t have all the necessary plug-ins loaded.
1 Like
an “autoload missing plugins” feature request was made some time ago (can’t seem to find that thread) and dan agreed it was worth implementing at some point. having that feature, along with “unique buffer/rate setting per patch” would be hugely helpful together.. just drop any patch on the mm and itll run immediately. no fuss.
I didn’t see it either. often ideas on forums are added to a topic with a totally unrelated title. glad ‘Dan’ (whom I’m now assuming is ‘the’ 4ms MM guy) has been thinking about it.
And as a now retired C/Python developer and project manager for f500 companies, I would be more interested in ‘feature solid’ rather than ‘feature complete’. And feature solid would also include the features that make the product solidly useful (as well as robust). MM is on its way to being solid!
Thanks.
.m
Right, these are both on the TODO list. We’ll get to them eventually!
CPU usage and RAM consumed by plugins are not related to each other (there’s no disk swapping or virtual memory or paging etc.) . So you can pre-load all available plugins without causing any issues — unless you are running low on memory. Running out of memory is pretty hard to do unless you are manually loading large wav files into your patch.