|
Tip: Creating Two Instances of Gig Performer with a Single Client ASIO Driver |
Scroll Prev Top Next More |
Creating a second instance of Gig Performer is easy. Just select (or open an existing one) and you’re all set. This works great on OS X and on many Windows machines.
Unfortunately, some Windows ASIO drivers still allow only one application to use the audio interface at a time. These are known as single-client drivers. Multi-client audio drivers started coming out years ago, but, sadly, there still are many single-client drivers in place.
Two instances of Gig Performer count as two applications, which is a problem when running on a single-client driver.
If you find yourself in this situation, first check whether there is a multi-client update for your audio device driver available. Consider also contacting the company providing the driver; if they hear from enough people, perhaps they’ll fix the issue.
If there is no update, there’s still a way — just follow these instructions:
1. Install the ASIO4ALL drivers on your computer http://www.asio4all.org
2. Open a second GP instance and choose to open the Audio preferences tab.
3. Select the ASIO and ASIO4ALL driver matching the sample rate of your main instance.
4. Click on the “Control Panel” button once you have switched to the ASIO4ALL driver and make sure that your real audio interface is selected within the ASIO4ALL driver.
That’s it. Your second instance will remember the audio settings and will now always open using the correct driver.
Should you need to route MIDI from one Gig Performer instance to another you can install a virtual MIDI port driver (Virtual MIDI ports are built-in to OS X as IAC – InterApplication Communication - ports.)
LoopBe1 is a free MIDI loopback driver for personal use. You can download it here http://www.nerds.de/en/loopbe1.html
There is also loopMIDI from Tobias Erichsen
https://www.tobias-erichsen.de/software/loopmidi.html
Once installed and configured, virtual MIDI ports simply show up in Gig Performer as input or output MIDI devices. Just send any MIDI data you want from one Gig Performer instance into a MIDI Out block for LoopBe1 and receive it in your other instance using a MIDI In block.
CAUTION: Do not use any MIDI In OMNI blocks if you’re using this method. Otherwise you will set up a feedback loop because MIDI In OMNI blocks receive all incoming MIDI data, including data you just sent out.
