I have a rackspace that I duplicate all the time, changing only the preset that’s loaded into the main plugin. Obviously I can’t do this using variations, which all have to share the one plugin preset that was saved with the rackspace. But the proliferation of rackspaces with identical plugins and patch layouts can be problematic. Questions:
Do each of these rackspaces take up additional memory, or are the patch layout and plugins shared in memory somehow?
Having multiple “identical” rackspaces is fine when each one is for a separate song, but I have another gig file set up as a sort of demo for various plugins - for example, the 25 synth plugins in Arturia’s V Collection. I’ve ended up with several rackspaces for each plugin, giving me different classic preset examples for that plugin, and my gig file has gotten unwieldy with over 100 rackspaces. It would be nice if there was a way to at least group these rackspaces by plugin.
When I play live, I’m glued to my MIDI keyboard, playing right hand and bass, working both pedals, and singing, so there’s no way I can interact with on-screen widgets, which is why the MacBook is not positioned next to me. My keyboard sends a program change to GigPerformer to select the rackspace for a song, and the keys, pedals, wheels and knobs send any needed controller message to G.P. So I haven’t needed to set up any widgets/panels on my rackspaces, making Variations kind of useless for my purposes. But if there was a way to learn everything about a plugin’s current state, and somehow save that in a Variation (I suppose that would require a widget for each setting?), then I would be able to use variations to effectively change the plugin’s preset. Is this a completely crazy idea?