Does anyone know how I can recreate the “defer patch change” setting from Mainstage in GP5?
What does that defer do?
When you press the button to trigger a patch change (or in GP I guess song part change), it waits until all the midi notes have been turned off before changing. Meaning you can then essentially have the release of the notes trigger the change. Allows for smoother transitions.
Reminds me to patch persist
Did you try patch persist?
What is that? And how do I find it? I literally just got GP the other day - still very much learning!
This was possible starting with Gig Performer v1! 
1 Like
Patch persist means that sound you are playing remain as long as note off is missing or sustain is pressed.
Is is an option of a rackspace
Is it possible to do it on a per variation/song part basis?
You can try this: [Gig] Plugin Persist 2.0
1 Like
Thanks! Is there any documentation to go with it?
The real patch persist mechanism depends on the plugins in the “old” rackspace continuing to run temporarily (until you release held notes,etc) after you switch to a new rackspace.
Variations don’t give you that facility because you are still using the same rackspace. However, some rather clever users have developed scripts in Gig Performer’s scripting language that can emulate the behavior of patch persist in a single rackspace. They called that effort Plugin Persist 2.0
There’s no official documentation since those scripts were not developed by the company. But there are plenty of discussions about it on these forums.
Well, welcome. You’ll find lots of great resources around here and on the gig performer website (documentation, videos and so forth). The thing be careful of though - do not try to force Gig Performer to behave as it if was MainStage (or another channel strip model). While you can pretty much do everything (and more) in GP that you could do in other environments, the approach/paradigm is different.
1 Like