Do you know why?
Do you need instant access to every rackspace? If you don’t, or if you do but you follow a setlist, then predictive loading might help you.
Do you know for sure that your plugins accept program changes? Many don’t.
If you don’t need immediate switching, you could try the new (but experimental) GP Script function
**LoadGPPreset(*p: Block*, *presetName: String* )**
It’s still marked as experimental but so far nobody has reported any issues with it.
To use this, click on the Save GP User Preset… in the plugin editor menu
and give the preset a name.
Do this for each of the presets you want.
Then create a rackspace script that looks something like this: (If you’re not familiar with GPScript, please take a look at the manual) – in this example, I have a synth with the GPScript handle “Legend”
Whenever the variation changes, we select the desired preset.
Obviously this can easily be extended but the concept works fine — the caveat is that you are now dependent on the plugin’s ability to load new state on the fly (make sure you test carefully) as well as any delays introduced by the plugin while changing its state — so you can’t leverage GP’s Patch Persist.
But it does work and should work with any well-implemented plugin – here’s a simple GIF demoing it
