What kind of music do you play that needs this seemingly very complicated configuration.
I mean, I play in three bands, two of them doing some pretty sophisticated stuff and I don’t even use the global rackspace other than for final output and to manage controlling my sheet music ipad
I don’t think I have more than 15-20 widgets in my most complicated rackspace and often just 2-3
Obviously the needs must be different but you must have some extremely complicated need that I don’t understand
I am also a bit lost, what are your remaining “issues” if you still have any?
I have no remaining issues… I think my only issue was that I didn’t need the On Variation to be called during gig load at all, and now that I’ve figured out how to ignore it when it is, I’m all set. Further to that I was just exploring to try to understand the system better.
I don’t think the music I play is any more complicated than yours. I think it’s just my own predilection (as my friends and family can surely attest) to make things more complicated than necessary for my own amusement!
In my Global Rackspace I’ve built a user interface that includes a mixer for 8 patches (though in practice I only use 2 in most songs, sometimes 3-5 at most). The mixer mixes the 8 patches down to 2 buses. For each patch I have 12 parameters controlled by widgets that are set in the local rackspace (a bus selector, a toggle to allow the upper keyboard to control that patch, lower and upper boundaries for the zone of the upper keyboard, a transposition value, a toggle for the lower keyboard, with zone boundaries and a transposition, and three parameters for a compressor on each patch (pre-gain, ratio, and post-gain). So, that’s 96 widgets, plus another seven widgets to control other things: two bus gains, a toggle for the metronome sound, some parameters that control how my expression pedal affects the gain on one of the buses, and a master limiter threshold). It’s because of these 103 widgets that I wasn’t comfortable using global parameters for this, because I also have four instruments defined in the global rackspace which use a lot of global parameters themselves so that the local rackspace can control how they behave.
And it’s because of the need to read in all those widgets from the local rackspace that I needed to detect the rackspace name every time the user switches song part or rackspace or variation, which is what led to my original question.
Now that we have 256 global parameters to play with, I could rewrite all of this to use those, but for now I’m going to keep with my current path and see where it takes me. And besides, even with global parameters I still need the global rackspace to detect whether each widget exists in the local rackspace, because if a given global-parameter widget doesn’t exist in the local rackspace then the global rackspace script needs to reset the corresponding global widget to its default value or else it would retain whatever value the previous rackspace had set it to.
In practice my system is working very well. I acknowledge that it’s way more complicated than most keyboardists would want, but I’m enjoying the work. Thank you to all the GP devs for giving me this playground!
To follow a bit what your are explaining, it could be nice to have a few screenshots of you Local/Global Rackspaces and Panels/Wiring views… 
Okay I’m going to go this route. Thank you for the advice.
The last time I tried using OSC I had an issue where GP would sometimes start with OSC disabled and I had to enable it from the settings every time that happened. My fear in this case is that if that occurs, then my gig script will fail to send the osc message to my global rackspace script, and consequently my global rackspace script will never find out that the gig finished loading, and then I won’t be able to play. But perhaps that problem has gone away in the months that have passed since then.
That will happen when there are OSC port conflicts with other apps/instances. Make sure you are using unique addresses.
You are correct; as I recall, there was an error message to that effect. I never did figure out what app on my system might have been using that port. (To my knowledge, nothing else in my computer should be using OSC).
How do I go about selecting a port?
Seeing as you’re not (knowingly) using OSC for anything else, the choice is rather arbitrary.
if the default port used by GP wasn’t working for you, try incrementing it until you no longer receive any conflicts.
Actually, it might be good to beef up this page on this topic a bit for those with limited technical knowledge:
I seem to recall I did not understand how to create a handle, what to do if (as would be common) if you are using more than one plug in in the Global Rackpsace. (If I recall correctly, you need to have different handles(?))
Thankfully, David walked be through it. But, it might be helpful to walk through more details for people who do not even know what OSC is.
I found this also happens when you have to activate the license (I typically deactivate GPs’ license before applying OS updates, so I have to activate afterwards).