OK… according to my suggestion for using the setlist mode, i tried that approach myself and it works flawlessly! This is what i have done:
set up some rackspaces - each for one sound. I prefer to send the local rackspaces output through a separate gain block (for adjusting each rackspaces own volume) to the global rackspace, where i can have a “Global Volume” at the end of the chain…
The wiring of the local rackspace:
The panel of the local rackspace:
The wiring of the global rackspace:
The panel of the global rackspace:
The list of rackspaces/variations:
Go to the Options/Setlist menu and learn your MIDI-keyboard’s buttons to the corresponding “Song Part Selection” - the controller buttons should preferably be configured as “Momentary” (in the setlist options as well)!
Switch to Setlist mode and add a new song which will represent your whole set of the diffrent sounds you want to have available (i called mine “Settings 1”). Then add a song part for each sound (meaningful names will be useful, i.e. the instrument’s name) and connect this song part with the corresponding rackspace/variation. To do this, just activate first the song part in the list, then click on the rackspace/variation which you want to use… proceed with the next song part / Rackspace pairing until you’re done.
Schamass’s solution would also allow you to have patch persist, or overlapping midi/sound functionality without having to add scripting to achieve that which given your style of play would probably be an asset.
This is very similar to how I set up my system and I use Global Rackspace downstream of my local rackspaces to control mix and global effects like Leslie making it the last stop in the signal chain.
Since you have only VST sound sources you’d have no issues switching between sounds/rackspaces without interruption.
I just feel compelled to comment here… this is SO COOL how this community reacts to a question, particularly from a newbie to GP. And I’ve noticed whatever the solve ends up being, the most robust solution tends to come from the approach of exhausting the designed system of GP, before considering scripting. I do have a background in software development and new user support and this is VERY rare to find, most especially in music software. I am SO pleased I found Gig Performer.
Yeah, scripting was originally intended to allow us to experiment with features that might ultimately be integrated in to GP directly. As GP evolves, that continues to happen.
I seem to recall reading about how way back when ILM started doing motion control camera rigs using an Apple II to run its motors that Steve Wozniak said his mind was blown that people would use his little assemblage of salvaged HP boards to do something like that. I think you guys are guilty of implementing really good design.
Thank you so much for the detailed explanation. I will check tonight if the current setup works for me. If not, I’ll definitely dive into your solution!!!
It worked, but I think I’ll try the other option too.
Sorry for the late reaction, but as a newby I had to wait a day before I could reply again!