How to use the Monitoring Mission with multiple VST Host (amp simulation software) and a DAW for rehearsal and/or recording purposes.

Here is an advanced use case which will show you how to use ANUBIS with the Monitoring Mission to then be able to monitor independent VST Host from individual ASIO / Core Audio machines + a DAW to ensure stems playback and/or record the VST Host outputs like it was a real amplifier.

Before constructing the overall workflow, make sure to tune the OS and Network configuration as recommended.

Windows Optimization guide:

https://merging.atlassian.net/wiki/spaces/PUBLICDOC/pages/4817977

Network adapter config (Win):

https://merging.atlassian.net/wiki/spaces/PUBLICDOC/pages/4817173

OSX Optimization guide:

https://merging.atlassian.net/wiki/spaces/PUBLICDOC/pages/4820445

This workflow can fit in studio environnement or in rehearsal environment. We do not recommend it for live purposes, as VST Host based on convolution tends to be CPU intensive. This is why each machine is ensuring its very own task as unique VST Host or DAW.

Please also rely on the system recommendation from the VST Host manufacturer website.

The example below is done at 48kHz without oversampling. Some machine can handle higher sample rate but it can then result to audio artefact and or CPU spike as each time the sample rate is doubled, the needed CPU resources will be doubled too.

Current limitations (1.5.6):

Source selection is independent on CUE, volume of each source is global. (already a part of the feature request)

No delay on source > DI signal from local input & Process signal from VST Host cannot be aligned from ANUBIS. (already a part of the feature request.

As we are using multiple driver at once, UNITE mode is not compatible with such workflow also with the Music Mission.

Workflow:

 

From ANUBIS:

Create dedicated sources: (From Settings>Monitoring>Sources)

  1. DI 1 (Mono > Inst Line 3)

  2. DI 2 (Mono > Inst Line 4)

  3. Neural Gojira (Stereo)

  4. Neural Granophyre (Stereo)

  5. DAW playback

 

Create dedicated Monitor as CUE for the performer: (From Settings>Monitoring>Monitors):

  1. Guitar Player 1 (Stereo>Mode as “CUE”> Button “Heaphone 1”> Patched to Heaphone 1 Left and Right)

  2. Guitar Player 2 (Stereo>Mode as “CUE”> Button “Heaphone 2”> Patched to Heaphone 2 Left and Right)

  3. Optional Main Monitor as Speaker Set if using the workflow in studio.

Network Latency:

From both driver (MAD/VAD) and device side, set the network latency at 48 (AES67) or 64 (RAVENNA) samples as a starting point. Keep in mind that when operating an ASIO device, the latency must be identical in terms of multiple/denominator (48 sample based or 64 sample based).

Lower latency settings are possible on devices but not recommended on driver.

On devices this parameter is accessible from:

  • Anubis: Settings > General > Frame mode > Latency

  • Horus/Hapi : Setup > System > Latency (if also having/using Horus/Hapi in the ecosystem)

 

Setup consideration:

From below, there is multiple devices in the workflow, ANUBIS SPS can act as a Network switch for 2 Merging Devices / Driver. If using ANUBIS single port or if wishing to add a 3rd machine (e.g. as a DAW or additional IO), please consider to use a qualified Network switch.

Routing from ANEMAN:

From ANEMAN, Create a New Zone, Sample Rate Zone.

Once done place the device as below. As there is many computer, having ANUBIS as SR master (on the crown icon) is then more convenient.

  • An ASIO Machine is running Neural DSP Gojira’s plugin

  • A Core Audio Machine is running Neural DSP Granophyre

  • An ASIO Machine is running a DAW

 

Sending DI signal to AMP simulation plugin (and DAW optional if recording DI signal*):

  • ANUBIS is sending audio to ASIO - Neural Gojira : DI signal > Line 3 to ASIO IN 1

  • ANUBIS is sending audio to CoreAudio - Neural Granophyre DI signal > Line 4 to Core Audio IN 1

  • *Both source from local input are also sent to ASIO DAW: Line 3 and Line 4 to ASIO DAW IN 1 & 2

Sending playback signal from VST Host to ANUBIS (on previously created sources), (Playback from DAW is optional*)

  • ASIO - Neural Gojira is sending audio back to its dedicated source on ANUBIS : ASIO OUT 1-2 to the source “Neural Gojira” on ANUBIS.

  • CoreAudio - Neural Granophyre is sending audio back to its dedicated source on ANUBIS : CoreAudio OUT 1-2 to the source “Neural Granophyre” on ANUBIS.

  • * ASIO - DAW is sending its playback to the dedicated source “DAW return”: ASIO OUT 1-2 to “DAW Return” on ANUBIS.

Sending processed signal from the VST Host to the DAW.

To record signal from the VST Host in the DAW like real amp, you will have to send both ASIO - Neural Gojira and CoreAudio OUT - Neural Granophyre OUT to ASIO - DAW IN.

Additional note: When recording on a DAW, you’ll have to mute the sources in the DAW to avoid them being a part of its playback playback.

 

Here below is how should look the complete ANEMAN Matrix View:

From Both Neural Granophyre and Neural Gojira’s VST Host, select our driver and perform the corresponding channel IN-OUT assignment

Select the Merging Audio Device as “Master ASIO host” as the sample rate change is driven by ANUBIS as SR Master if using our MAD driver on a Windows based machine. (such settings are not applicable for CoreAudio machines)

 

ASIO - Neural Gojira:

Select Merging RAVENNA/AES67 as both Audio Input and Output Device

Set the corresponding channel mapping. Audio output channels 1 & 2 as the playback source is stereo and already patched to ASIO out 1-2 & Audio Input channels 1 as the line 3 is mapped to ASIO IN 1.

 

CoreAudio - Neural Granophyre:

Select Merging RAVENNA/AES67 as both Audio Input and Output Device

Set the corresponding channel mapping. Audio output channels 1 & 2 as the playback source is stereo and already patched to CoreAudio out 1-2 & Audio Input channels 1 as the line 4 is mapped to CoreAudio IN 1.

Adapt the buffer size to a decent value in conjunction with the processing resources at disposal. This point must be benchmarked by the end-user.

ASIO - DAW

Select the Merging Audio Device as “Master ASIO host” as the sample rate change is driven by ANUBIS as SR Master if using our MAD driver on a Windows based machine. (such settings are not applicable for CoreAudio machine)

Select Merging Audio Device as driver for your DAW.

Dial the gain from the preamp page

 

Monitor From ANUBIS:

The setup is now ready to rock and each source can be selected & monitored from their monitor page on ANUBIS.

Engage the SUM function to then be able to monitor multiple sources at once.

To tweak panning from stereo sources coming out of the VST Host, please use the built in panner from the VST Host.