Link: Questions about rackspaces and variations - Gig Performer®
–
Other useful posts:
[1] You could have thousands of rackspaces - LINK
[2] Creating rackspaces along with Rig Manager aliases without a MIDI controller attached - LINK
[3] How to use GPScript to set explicit widget values in different variations - LINK
[4] A plugin in a non active rackspace might consume a certain amount of RAM but shouldn’t use much CPU power. Same as a bypassed plugin - LINK
[5] Is it better to use variations or rackspaces for your patch? → Solid tip to help you decide - LINK
[6] Putting the same plugin in multiple rackspaces does not significantly increase physical RAM because the DLLs are shared – only the instance data is duplicated. - Mute vs. BlockNoteOn for CPU Usage - #8 by dhj
[7] How to change the underlying MIDI Input device for all MIDI In Blocks in all Rackspaces → LINK
[8] Every time you leave a variation, Gig Performer captures the current widget values so that it can reset them back when you return to that variation. → LINK
–
How to set up a keytar to change rackspaces - link