Hello GP newbie here,
I’m on GP 5 and was wondering what the best approach for using two different audio interfaces, one for home and the other a smaller compact interface for live use. I do all of my programming and set list maintenance at home using an Apollo x8 then use a small Steinberg UR22mkII for live compact set up.
Create a new instance either for home or for live and start it by script/shortcut etc.
Are you on Windows or Mac?
→ [blog] How to use multiple instances in Gig Performer 4 still valid for GP 5 
I’m on Mac.
When you say create a new instance do you mean, create two aliases/shortcuts with the name of a startup script? Does GP accept an argument for a startup script or config file?
Ah! I saw the link for mutilple instances.
Besides the stuff in the links, and just one more option: I use shortcuts (“Kurzbefehle” in German) on my Mac for some time:
Also very useful
That’s really cool. I’m a software developer by day and a musician by night. I’m going to learn how to code note on/off events for various operations.
So, with these instances, I’m hoping I can use my existing racks global racks and song lists across both instances with the only thing different being the audio interface I would be using for home programming and live stage performance?
I’ll be getting into scriptlets and the GP programming language. I’m guessing that scriptlets are a high level wrapper around GP language? I looked at a video the other day and seems like scriptlets are intended for non-coders who know little about variables, loops, and event-driven paradigms.
I do this, and I dont do it correctly lol.
I use a UR22-C at home, and a Arturia MiniFuse 1 (very small, but has meters on the front which I really like) for gigs.
I dont do anything special. I had thought of having 2 instances, but I make a lot of tweaks when playing and not sure how id keep the two in sync any faster than just booing up with a different interface at a gig or home. To me its less work to just change them over in GP than it is to have two identical GP files kept in sync.
I also wouldn’t see the need for two instances…
What i would do: Put the final output block in the Global Rackspace and then send the audio from each local rackspace to the global rackspace via “To Global” bocks and receive it in the global rackspace with a “From Local” block.
Those blocks can be set to the number of channels you want to use.
That way you wouldn’t have to change the audio routing of your local rackspaces at all - no matter what interface you use, because this only affects the one and only out-block which resides in the global rackspace.
So if you change the interface with a diffrent number of channels, the only change you’d have to make is in the global rackspace. If the number of used outputs stays the same, there will be nothing to do at all.
Now, THAT makes a lot of sense. I love that idea! Thank you so much!
This also gives you the possibility to set a gain block before the “To Global” block in your local rackspaces, so you can adjust the output for every local rackspace separately, so you can even out the input level for the “From Local” block in your global rackspaces.
Not too bad if all the sounds come into the global rackspace as loud as you need them!
In addition to that, you could also put another gain block before the final out, so you easily can adjust your outgoing “Main Volume” without having to juggle with a particular (local) rackspace.
Or you can just mute everything with just one widget, or…
This approach seemed to me the most useful, that’s why i’ve built all my rackspaces like this. 
Exactly how i set mine up. I have a fader far left on my controller to control the main output fader from the Gain block in the Global rack space. I also have a knob assigned to the overal gain control of GP, just in case i start clipping. Normally i don’t need to touch it and leave to set at -3db.
I’m sure that’s duplicating things but I’m happy to have both.
I do nearly the same, but I also use differnt instances when trying out stuff (interfaces, buffer sizes, OSC etc.).
“Safe” main instance and testing environment, that’s why I brought up instances above
My mind exploded on your first reply. I’m a newbie so I’m still getting my feet wet. There is soooo much functionality with this deep feature rich tool. I love it!!
I implemented the multi-instance thing yesterday using the Mac script editor. I found it a bit too much for my specific use case. Each new instance (2) had to rescan all of my plugins (pretty lengthy process). Initially, I didn’t expect that but it makes perfect sense if you want a totally clean and isolated environment. Thanks for the tip! I’m sure I’ll come across a scenario where that will be useful down the line and thank you so much for the tip! I’m glad to have learned how to do this 
Is there a way of setting GP to use a certain freq and buffer size no matter what interface is used, by default.
As i posted above, i can use two interfaces without any real issues, but whenever i change interfaces GP seems to default to 44.1 KHZ (which is what i want to use) and 512 samples. I want to use 128, and while i can change it easily enough, i then have to wait for GP to reconfigure.
Just wondering how to avoid this bit. For reference im nor using Arturia MiniFuse 1 and Minifuse 2.
It wasn’t yet mentioned in this thread, but I would definitely recommend setting up Rig Manager as soon as possible, and then use aliases in all of your Rackspaces. If your home and live MIDI devices differ, then you can quickly change rigs to handle both scenarios.
Even if your gear were identical, it’s good practice. Gear choices can evolve over time.
I recently rebuilt my (multi-instance) Gig Performer setup from scratch. Step 1 was to set up the Options. Step 2 was to set up Rig Manager. Only then did I get into the Rackspaces and Songs.
And, yes, put your audio interface connections (and GP Relayers) in the Global Rackspace as noted above.
Currently not.
Dito, best way.
And save and load audio settings for different devices.
