Is it possible to create a common user interface (like Mainstage does) for a GP file for about 50 keyboard patches (with a variety of plugins used)? I’d rather not spend time building the “perfect” interface first, I’d prefer to be able to make tweaks at any point.
I know Mainstage does this, can GP?
That’s the curse of maximum flexibility.
What would be the use of a user interface, made by someone else, which wouldn’t suit your personal needs?
You can do almost everything in Gig Performer, but if you want it to be the way you like, you most probably have to make it yourself.
Our you crawl through the pool of ready made rackspaces which you can find in the respective subforum… lot of stuff to “tweak”!
I guess I didn’t make myself clear. I do want to build my own user interface, but I only want to build it once, not for each song patch. And if I want to modify it in the future, I want to modify it once, not for each song patch. Thanks, Jeff
you could do that with the global rackspace
I have seen users build a single rackspace with huge numbers of plugins. You could do that.
But, obviously you do not want to hear them all at the same time. So, you would need “variations” where some of the plug ins are bypassed.
Of you could put them all in the Global Rackspace. But, I think you would have to go through a similar process of bypassing the ones you are not using.
Jeff
If I built an audio mixer in my Global Rackspace, would it be able to control different plugins for different songs?
For example song 1 - Kontakt piano - mixer channel 1, other plugins into other channels
song 2 - Omnisphere - mixer channel 1, other plugins into other channels
Or do I need a huge mixer with all the plugins and turn off what’s not being used in the song?
You should download the fully functional trial version of GP, and see for yourself all the different ways there are to build whatever infrastructure you want to build. You’ll find there are many ways to accomplish the same task, which gives you a lot of flexibility to customize your setup just how you like it.
Trial Version - I have been a user for years. I always end up spending so much time on pre-building the user interface, it never gets done. 
As I understand it, you would need a widget for each patch/sound that would allow you to bypass that patch/sound.
If you used more than one patch/sound form Omnisphere, I think it is recommended that you set up another instance of it. This is because it is generally not a good idea to change sounds that that are not loaded on the fly. I would think this would especially apply to Ominisphere, which I think can use a lot of ram (and cpu as well).
I don’t know that the Global Rackspace is the way to go with all those instruments. I am not sure if it does much for you.
You could just set up a single giant (regular) rackspace with all the patches/sounds you want and then use “variations” to bypass (or not bypass) particular patches/sounds.
I think you need to try to get an understanding of the difference between a “rackspace”, a rackspace “variation”, and “songs” and “song parts” in setlist mode (personally, I almost always use setlist mode).
Frankly, I tend to be an advocate of “taking it slow” and not trying to do everything at once. That’s the approach I took. But, maybe I am on the opposite extreme because my priority was being able to continue using my hardware keyboards as I always had while I slowly started using GP for some sounds (and expanding from there).
It is amazing software that will grow with you. And the people who are available in this forum are great (most know much more than I do).
Jeff
You can route audio from a specific local rackspace to generic global rackspace where you have a mixer plugin and where you route your audio to an audio interface. In the local rackspace you can control the mixer of the global rackspace.
With a bit of GPScript I even go further. See the following animated gif, I have a local rackspace where I can enable/disable my plugins, give them a name and control their volume locally (first panel). The control is local, but it acts on a 32-mixer in the global rackspace (third panel). In the second panel I have a GP widget of my control surface, from where I can control the 32-mixer of the third panel. This only to show that with GP you are virtually not limited.
That’s very close to what I need. Is it possible to get that GPScript to see what you are doing? Thanks, Jeff
If you consider only the first and third panel, it doesn’t necessitates any GPScript. You have got everything in GP to control a mixer in the global rackspace from the local rackspace.
The GPScript is only there to control everything with the control surface and it is not yet clean enough to be shared. I hope I will have time during holidays to finish it and make it cleaner…
Out of curiosity: that keyboard: 88 shape widgets?
Some patience you’re showing 
It is part of the GP4 templates, it is the “illuminated keyboard”.
This same exact topic came up in disguise in another recent “feature request” topic. What you want already exists. You can have your “common interface” in either a song rackspace, global rackspace, or both, which you can tweak to your heart’s content.
All you need is something you create or that someone else creates/created and you save it as a template. The proper term from the menu description is import and/or export, panels differ a little bit in terminology but the idea is the same. It makes it infinitely reusable, changeable, adaptable, collaboration friendly, and can include the backend scripting and automation limited only by your imagination. With abilities like that, you don’t need hardcoded interfaces which is what Erik (@schamass) was alluding to. It takes a little more effort - but not a lot - to figure out how to do it, but the tradeoff is the most flexible live performance software that I know of.
Hey Jeff 
You can see many community created gig and rackspace files here: Gig and Rackspace Files - Gig Performer Community
Everything is downloadable, free, and all scripts (for stuff that have them) are free to edit and adjust to your needs.
Jeff is a long-time Gig Performer user. See here.
I do not get it.
In my rackspaces I have different widgets to control different plugin parameters.
Somestime I only need a Master Volume, in other rackspaces I need others to control for example pitchbend or trigger on shot samples.
When I would build a common interface, most of the controls do not make sense for a particular song.
Yes you can absolutely do this and I just played a gig wtih 22 songs where i only used one rackspace.
I used variations instead of rackspaces to change between states.
Totally doable. I like you want minimal rackspace designs… I want to see all my tools in one spot.
I found a way to ‘grey out’ the items that are not active in that particular variation too… so they are still part of the UI but obviously have no effect.
You can work however you want in GP
I have just done this. I created a single rackspace with all of the different front facing controls i would want and then attached them to specific widgets
I wanted to be able to quickly see the instrument mapping (like the NI light guide) so included the illuminated keys script…
In my case i allowed for up to 6 instances of kontakt but only used three in the example.
By using the midi controller input widget as a bypass option and a channel mixer as the volume option then it doesnt matter which vst you place in the chain. (I have increased the usability of this by also adding min and max keys dials but am not at ny computer for the screenshot)
I also wanted buttons to allow .my second keyboard to control any one of 16 parts of the Modx so that patch and variation editing was easy.
Finally i also wanted an audio player for stems so that at a practice we could have an individual part playing of they were absent.
Once i had everyting i though i would need then i saves this as a rackspace and then for each song i started with this and changed the vsts, programme changes and tracks on the player. But the controls srayed rhe same. Have included a screenshot of the rackspace and wiring for clarifcation… but planning is key as it is harder to add a “template” item one you have 20 songs built
