by David Jameson | Aug 4, 2019 | Gig Performer Blog, Tips
Input and output ports in Gig Performer blocks . If you’re already a Gig Performer user, you know that you can easily route audio and MIDI between AU (Mac only), VST3 and VST plugins by just connecting them visually. However, you may have wondered why some plugin...
by David Jameson | Jun 30, 2019 | Gig Performer Blog, Knowledge Base Articles, Tips, Tutorials
For users coming to Gig Performer from other audio plugin 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 song you’re...
by David Jameson | Feb 23, 2019 | Knowledge Base Articles, Tips, Troubleshooting
It’s usually convenient to have Gig Performer load the last gig file automatically at startup and there’s a general option that controls this behavior. However, occasionally you may need to temporarily prevent automatic gig file loading. One reason is...
by David Jameson | Dec 23, 2018 | Gig Performer Blog, GP Script, Tips
Gig Performer is pretty efficient in terms of CPU cycles but sometimes plugins use up a lot of cycles even when they’re (apparently) not doing anything. In a traditional channel strip model, it’s pretty straight forward to automatically bypass plugins when...
by David Jameson | Jul 25, 2018 | Gig Performer Blog, MS Windows, OS X, Tips
You may be wondering how to implement side-chaining in your audio plugin host. Quick answer: if you’re using Gig Performer, it’s pretty trivial. I never used side chaining myself. In fact I wasn’t even sure what it was for a long time. But I got forced into finding...
by David Jameson | Jan 29, 2018 | Gig Performer Blog, Tips, Tutorials
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™...
