Troubleshooting Anubis

Users tend to bypass the Anubis Monitoring Engine. It is important to review the “Sources vs. Monitors Fundamentals” chapter in the User Manual.
By design at first a source should be created or used in order that Outputs such as a DAW 1-2 Playout are coming into the Anubis Monitoring Engine and then going to a Monitor set.

This is expected as each of the Anubis 3 types of Monitor set have their own features. Refer to the Monitors Tables.
In order to use Dim, the Reference level and other features on a Heaphone set this one must be changed to a Cue.

ASIO / MAD or VAD sound Interruption or glitches.

Adjust the Audio Driver I/O Buffer.
The size of the buffers determines how much delay you hear when monitoring live inputs through your audio software:
larger buffers produce more delay; smaller buffers produce less.
Change the Buffer adjustment are made in the ASIO / MAD and VAD panels

Reduce the I/O count of your ASIO or VAD panels, and select only what is needed.

“ASIO Clock error : latency of the master Horus/Hapi/Anubis and ASIO driver must be set accordingly"

The latency between the ASIO driver and the Anubis device must be in the same set; AES67 (48 - 12 - 6) or 64 (64 - 32 -16).
See Anubis Settings > General > Frame Mode : Latency setting.
If you have multiple devices on your network, this setting can only be configured on the Master PTP device.

Auto Sampling Rate

If you have several devices on your network, set at different sampling rates, make sure the PTP Master is set to the same sampling rate as the ASIO driver.

You may alternatively set the device ASIO Clock (Setup > System) to Off on the Master PTP device and On on the device connected to ASIO.

Monitor your PC sounds (YouTube, Spotify,...) using Anubis with similar use as a built-in soundcard, with a WDM bridge.

Depending on channel’s number to be process some slope won’t be set. 28 band are available for Bass management, e.g. 24/dB/octave max is possible with a 5.1 setup.

Windows can automatically reduce the network bandwidth on some specific process, which is not supported for RAVENNA.
See this page to fix this issue.

Using Pyramix the Anubis Preamps remote control are not supported on all versions of Pyramix.

The Anubis remote preamps control support within the Pyramix Mixer is supported as of Pyramix MassCore v11.1.6 Hotfix and on all Pyramix Native version running ASIO v12 (64 bit).

Note some parameters such as Boost, Link and Cut are not supported.

Firmware takes a long time to update, and the update button is not always showing

It is not recommended to use Safari for the Firmware update as it is known to cause slowdown at update and potentially the Update button might not be seen.

Merging recommends that you perform your Firmware update using Google Chrome. If you still encounter issue try using a Chrome Incognito Tab for the update.

Cannot have different Source trims for each Monitor set

Anubis Monitoring Mission has global sources trims.

-Boost:  Remote MIDI Preamps control does not support the Anubis Boost Preamps option. It will be interpreted as a Pad. For the moment it is recommended to set this parameter locally on the Anubis Preamps.

-Link and Cut:  Remote MIDI-Preamps control do not support the Anubis Link nor Cut Preamps options.
Users can use Stereo Inputs to control 2 Anubis inputs simultaneously, or use the Link locally on the Anubis.
The Cut option will need to be used locally as this parameter is not supported by the Avid MIDI Preamps protocol.

Source Trims are global and not individual to each Monitor set.

Workaround: If you wish to have independent Source trims levels for different Monitors is it recommended to duplicate the Sources and use Cue monitors, so that each Cues have a different selection of Sources.

The upcoming Anubis Music Mission will not have this limitation.

Logic’s channel strip parameters (solo, mute, pan, volume, etc) respond to specific MIDI Control Change messages, some of which Anubis is sending. One of these messages (CC9) will mute the selected track/channel strip in Logic. This is easily avoided by going to Logic’s Project Settings > MIDI > General and unchecking the Control Change 7/10 controls Volume/Pan of channel strip objects box. Note that even though this setting only mentions volume and pan, disabling it will also prevent the rest of channel strip parameters (solo, mute and send level) from responding to incoming CC's.