i know we have the ‘last patch we were running for about a minute = startup patch’ feature but that might not be the patch we want to have at startup. or the last patch we were experimenting with might freeze at startup, or use a lot of samples and take forever to load, etc. could be useful if a startup.yml file is in the root folder, the mm would only ever autoload that. and if startup.yml isn’t present, it would just use current behavior and auto load the last patch we were fooling around with. or perhaps we could set the startup patch from the settings menu?
setting a startup.yml would also be useful if, say you’re on tour and have a series of patches you need to switch and perform with throughout the set and so you always need to be able to startup the rig and have it just running a specific patch no matter what. without being able to set a default startup patch, you would then need to manually reload the 1st patch of the set, every single time…