Gig Performer | How to create two Gig Performer instances with a single client ASIO Driver on Windows
Gig Performer is a cross-platform (Mac/Windows) audio plugin host for both live performance and session musicians (keyboard players, guitarists, singers, drummers) looking for an intuitive fast and flexible VST/VST3/AU plugin hosting environment for their software synths and effects.
Audio Plugin Host, Audio Unit, VST, VST3, Live Performance, Session Musician, Performing Musician, MIDI Instruments, OSC, Musicians, Stage, Keyboard Players, Guitarists, Synths, Vocalists, Mainstage, Freestyle, Cantabile Performer, Patchworks, Rack Performer, Plugins, Live Sound, Modular
18342
bp-legacy,post-template-default,single,single-post,postid-18342,single-format-standard,ajax_fade,page_not_loaded,,qode-theme-ver-13.1.2,qode-theme-bridge,wpb-js-composer js-comp-ver-5.4.5,vc_responsive,no-js
 

How to create two Gig Performer instances with a single client ASIO Driver on Windows

How to create two Gig Performer instances with a single client ASIO Driver on Windows

Creating a second GP instance is easy. Just select File->Create new instance (or open an existing one) and you’re all set. This works great on OSX and on many Windows machines without further tweaking.

Unfortunately, some Windows ASIO drivers still allow only one application (Gig Performer with two instances counts as two applications) 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 are still many drivers out there that do not allow you to use the same audio device with more than one audio application at a time. This  also prevents your second GP instance from using the audio interface.

If you find yourself in this situation, the first thing you should do is to see if there is an update for your audio device driver available that does in fact support multiple applications simultaneously. Consider also complaining to the company providing the driver, if they hear from enough people, perhaps they’ll fix it.

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 go to its Audio Options
  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 GP instance to another – you can use install a virtual MIDI port driver (NB, if you happen to be reading this but are using an Apple Macintosh, virtual MIDI ports are built-in to OS X and are called IAC 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 http://www.tobias-erichsen.de/software/loopmidi.html

Once installed and configured if necessary, virtual MIDI ports simply show up in GP as another input or output midi device. Just send any midi data you want from one GP instance into a MIDI Out block for LoopBe1 and receive it in your other instance using a MIDI In block.

One caveat. Make sure you are not using any MIDI In OMNI blocks if you’re doing this. Otherwise you will set up an infinite feedback loop because Midi In OMNI blocks will receive all incoming MIDI data, including data you just sent out.

No Comments

Sorry, the comment form is closed at this time.

Help-Desk