Gig Performer is designed to be a very flexible host to allow you not only to create your sounds but also to perform, in real time, on stage or in a studio. We’re not talking about playing 8 bars with one sound, stopping to switch...
For users coming to Gig Performer from other hosts, there is some confusion as to how to configure Gig Performer so you can use the same set of Program Change (PC) or Control Change (CC) messages for different parts of a song, no matter what...
Gig Performer’s MIDI In Block is not just your everyday block for receiving MIDI events. It can do much more than just receive MIDI messages from an external device and feed them to connected soft-synth plugins. It has important other functionality that often relieves you from...
Omnisphere supports a mode where it can load several sounds simultaneously so that you can switch from one to another with no delay and with the ability to leave the old sound audible until you release all notes. Of course, Gig Performer's Patch Persist™ facility...
Gig Performer 2 introduced a programming language, GP Script which, while still evolving, will allow users to extra add functionality into Gig Performer. Let’s see a simple example of GP Script in use. Gig Performer supports Tap Tempo, the ability to measure a sequence of taps and...
By default, Gig Performer saves the values of all widgets using a "last value" algorithm. That means that when you change a widget value and save your gig, then when you reload your gig, that widget will have the same value. This is very convenient but...
The normal way to use Gig Performer™ is to create rackspaces each of which contains a collection of plugins connected together as desired. A rackspace might contain everything needed for a single song or you might use several rackspaces during a single song, switching from...