Help center


Practical applications - Routing multiple inputs to stage sources

The multi-channel capability in Inspirata Professional and Immersive Editions is not only for supporting surround output options: multi-channel inputs are also important when you are working in stereo. The more individual input paths the plugin has, the more individual track or material can be treated as independent sound sources with their own position, gain, apparent source width etc. Let us imagine a scenario where you have the following tracks that you would like to place in a space:

  • A mono lead vocal track

  • A mono backing vocal track

  • A stereo piano track  

  • A stereo percussion track

  • A mono guitar track

That is 7 channels in total. You should create a 7.0 FX track with its output sent to your stereo master buss (downmixing is done by your DAW) and initialize Inspirata. The only thing to do now, is to route all your 7 tracks to 7 different inputs of the 7.0 FX track. The way this is done depends on the DAW, but it can be done via surround panning (for example, in Steinberg Nuendo, Cubase), pre-defining Sub-paths (for example, in Avid ProTools) or by routing (e.g., in Reaper).

Nuendo

In Nuendo you have multiple possibilities to work with a multichannel INSPIRATA. The most common case is you have an INSPIRATA on a multichannel FX Channel or on a Group Track. For example you have a 7.0 FX Channel with an INSPIRATA instance. If you want to send multiple Input Channels to this FX Channel and you want to route each input to individual sources you have to use panning. If the channel you want to send the INSPIRATA has more than one channel the Position Channels Independently feature can be very useful.

ProTools

If you have an INSPIRATA instance in an AUX track with a Bus input (e.g InspirataBus), you can predefine Sub-Paths in the I/O Setup to route the tracks to a specified input of the plugin.


You can send the Audio Tracks to the listed Bus Sub-Paths.


Reaper

In Reaper you can easily route track channels to an arbitrary plugin input as you can see in the figure below.