Here is an advanced use case which will show you how to use ANUBIS with the Music 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):

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.

No POST FX patching option available from the Generic AES67 channel → Feature request pending

Workflow:

For this specific workflow, we will not use the usual Auxilary DAW playback to ensure VST Host playback but Generic AES67 channels. This is needed for recording purposes, as Aux playback cannot be patched back to an input channel if you would record the output of the VST Host.

The fist step is then to add Generic AES67 channel from ANUBIS. (Settings>Audio inputs>Generic AES67 stream), once added, the device must be reboot from the “Exit” menu.

Open

Generic AES67 input channel will only show up in the ANUBIS Mixer once being patched.

It is also needed to run the Music Mission in Advanced mode to then have access to multiple CUE mix

Rename the CUE 1 & CUE 2 with the name of role of the performer. (e.g. Guitar Player 1, Guitar Player 2)

Select the CUE layer, reclick on it and select “NAME”

Open

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 AES67 stream 1-2 on ANUBIS.

• CoreAudio - Neural Granophyre is sending audio back to its dedicated source on ANUBIS : CoreAudio OUT 1-2 to AES76 stream 3-4 on ANUBIS.

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

From ANUBIS, link AES67 1-2 and 3-4 to make them stereo, rename them. (e.g. Gojira / Granophyre)

Click on them to access to the “link with right” and “name” option

It should look like the following below.

From the Buss Routing Menu, make sure the HP 1 and HP 2 are patched to Guitar Player 1 and Guitar Player 2 cue mixes.

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.

You’ll also may want to mute DI signal from the mixing/cue layers in ANUBIS to avoid them being a part of the CUE / MIX. This must be done independently for each mixing layer (Guitar Player 1, Guitar Player 2, and MIX)

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

Monitoring from ANUBIS:

The setup is now ready to rock, select the corresponding Mix layer (MIX/Guitar player 1/Guitar player 2) to then perform your own and independent balance even with processing (EQ / Comp) on the AES67 stream.