Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Anubis not starting

DC Power Supply not connected or not plugged correctlyMake sure the DC power supply connector is correctly plugged.
If you are using the Merging power supply unit, align the two tabs on the power cable's connector to the notches on the Anubis input male connector, then rotate the barrel clockwise until latched.
DC Power Supply not sufficientAnubis requires a DC power input voltage from 9V to 15V
PoE power not sufficientAnubis requires PoE+ (802.3at).  Make sure your PoE source is configured to supply PoE+
No Monitoring Volume Control over the connected streamsMonitor not selectedMake sure you have selected the Monitor set you are listening to.
Source not connected to the Monitor engine

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.

Cannot Apply the Dim or Reference parameters to a Headphones Set.Wrong Monitor type

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 or VAD sound Interruption or glitches.

Wrong driver configuration

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 and VAD panels

Wrong driver configuration

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

Wrong Network configurationIf operating with multiple devices make sure that you are using a properly configured and recommended RAVENNA/AES67 Switch.
See this page for RAVENNA/AES67 validated switches.
Can't make connections on Anubis with Ravenna EasyConnectCompatibility - LegacyRavenna Easy Connect is not compatible with Anubis, you have to use Aneman.
When I create a new source/monitor, I can't enable it, it stays disabledLimitationThere is a maximum of 32 channel outputs-Monitors and 128 (44.1 to 96 kHz) / 64 (176.4-192 kHz) / 32 (352.8 to DSD) channel inputs-Sources.
Please disable some Monitors or Sources.
In Bass Management, I can't change to higher slopesLimitation

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.

"ASIO Clock Error : latency of the master Horus/Hapi and ASIO driver must be set accordingly" in Merging Ravenna ASIO PanelDriver compatibilityThe Merging RAVENNA ASIO driver version for Anubis must be V12 (or above)
Driver or Device Latency ConfigurationThe 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.
Using Reaper, the audio disconnectsReaper ConfigurationIn Reaper, the default behavior is to turn off the audio device when the application is inactive (when you are outside the application)
Go in Reaper Options > Preferences > Audio and untick the "Close audio device when stopped and application is inactive".
“no ASIO Host connected” in Merging Ravenna ASIO PanelDAW configurationMake sure your DAW is running and set to use the Merging Ravenna ASIO driver.
On some Media Players software, the playback must be started for the application to run its ASIO hosting.
Network Throttling error message in Merging Ravenna ASIO PanelWindows configuration

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

Anubis does not follow the sampling rate changes of the DAW or System, or
“ASIO clock sample rate (xxkHz) doesn't match driver's sample rate (xxkHz)” error message in Merging Ravenna ASIO Panel

Auto Sampling Rate

Under the Anubis>Settings>General enabled the Auto Sampling Rate option. The Auto sampling rate should follow provided at least one RAVENNA ASIO or Virtual Audio Device stream is connected to an Output of the Anubis. 
ANEMAN Sampling Rate ZoneLaunch ANEMAN and in the world view create a New Sampling rate Zone, select your RAVENNA ASIO or VAD driver and drag this one on the Crown within the Zone, then drag the Anubis in the Zone as well.

Several sampling rates in the same network.

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.

Requires third party applicationsRefer to the Merging’s Knowledge Database WDM -ASIO configuration proposal
Use Windows Audio with Anubis (WDM - ASIO Bridge).

Warning: Merging’s RAVENNA ASIO is not multi-clients and cannot be used simultaneously with a DAW if configured with a WDM bridge. Merging is investigating solutions.

Some of the Anubis Sources or Monitors cannot be activated under their respective Settings

Exceeding the maximum channels count available

The total channels used for Sources or Monitors available is most probably exceeded. Disable some of the other Sources or Monitors in use, or delete unused ones, then reactivate your Source or Monitor.
Refer to the table here for information on the maximum channel count that can be used for either the Sources or Monitors.

Cannot update Anubis firmware on mac Browser issueSafari is not supported with Anubis for the moment, the update firmware button will not be present and firmware could be slow to update if ever you click the update area. It is recommended that user on mac and PC use Chrome.
Remote Preamps: Some parameters such as Boost, Link and Cut cannot be controlled from ProToolsNot supported in Avid's remote Preamps protocol

-Boost:  Remote MIDI Preamps control does not support the Anubis Boost Preamps option. It will be interpreted as a Pad under ProTools. 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.

  • No labels