Page Comparison

Prerequisites

...

Prerequisites

• Pyramix 14.0 (or above) must be installed and authorized with Premium key for Dolby Atmos features.
• Merging Audio Device 2.1 (or above) must be installed and configured.
• Dolby Atmos Renderer version 3.7 (or above) must be installed and authorized on a separate MacOs or Windows computer.
• Dolby Atmos Renderer running on a Windows computer : Merging Audio Device 2.1 (or above) must be installed and configured.
• Dolby Atmos Renderer running on a MacOs computer : Virtual Audio Device 3.2 (or above) must be installed and configured.
  Depending on your configuration and requirements, VAD Premium might be required (Standard version being AES67 only and 64 IO Max
  
• Merging Hapi MKII 
  Highly recommended over Horus and Hapi 1^st generation due to the MkII ZMAN and AoIP stream flexibility.
• Merging Anubis running the Monitoring mission (optional)
• A properly configured managed network switch.   See this page for details and configuration guides.
  
  
  

...

• Timecode is required for real-time Loudness measurement in the Dolby Atmos Renderer, and will use 1 audio channel.
• The Dolby Atmos authoring process can be quite CPU intensive, depending on the size of your project.
  Therefore, Merging recommends running Pyramix Native on i7 CPU (or more) with 16 Gb of RAM (or more).

• Dolby Atmos Renderer on Windows: the Dolby Atmos Renderer requires MAD to be configured with a buffer size of 512 samples.  ThereforeTherefore, it cannot be used in AES67 mode (for connectivity with DANTE devices, i.e.) since AES67 requires MAD to be set with since AES67 requires MAD to be set with buffers sizes which are multiples of 48 (48, 96, 192 or 384 samples).
  If the Dolby Atmos Renderer is hosted on a Mac computer, there is no such limitation.

• Recording back Live Re-renders on the Pyramix computer is possible.  The number of channels may vary depending on your computer and project configuration.
  Exporting Re-renders offline from the Dolby Atmos Renderer application is possible when opening the Dolby Atmos ADM Master file (Export Audio > Re-Renders).
• MacMini 10Gb Ethernet port : currently not suitable for RAVENNA/AES67 network.   Please use a dedicated USB-C to Ethernet, USB3 to Ethernet, or Thunderbolt to Gigabit Ethernet (Sonnettech) adapter.
• Currently Pyramix can only export 48kHz Dolby Atmos ADM Master files.

...

Configure the AES67/RAVENNA Network

All the devices have to communicate in the same RAVENNA (64) or AES67 (48) mode.
If you use DANTE devices (MacOS only), you must set the network in AES67 mode (48).
If you use Merging devices, you can set the network in AES67 (48) or RAVENNA (64) mode.

...

• Pyramix - Merging Audio Device
  Please open the MAD Panel, and click on Advanced settings :
  Set MAD in RAV/AES67 mode
  Set Merging Audio Device as Master ASIO Host
  Set the sampling rate to 48000
  Set the Buffer size to 512
  Set the Sample type to 32bit integer
  Set the required Number of Inputs and outputs:
  Up to 128 Inputs and outputs, but unused channels will still use some power processing. 
  Therefore Merging recommends you rather set the number of channels you need ; e.g. if you don't plan to use Live Re-renders, 8 inputs are sufficient.
  Merging recommends you disable the MAD - WDM, or do not set the WDM outputs to any Bridge channels, to avoid having the WDM channels routed into the Dolby Atmos Renderer.
  Set the Latency to 6/12/48 AES67 (mandatory for DANTE devices) or 16/32/64 (RAVENNA).
  Click on Apply
  
  
• Hapi MKII
  Browse to Setup > System, and set the Latency to AES67 48smp (mandatory for DANTE devices) or Low 64 smp (RAVENNA).
• Anubis
  Browse to Home (Merging logo button) > Settings > General, and set the Latency to AES67Low-48 (mandatory for DANTE devices) or Low-64 (RAVENNA).
  
• DANTE devices
  Your DANTE devices must be set to AES67 mode.  Please consult your DANTE device documentation for details.
• 64 (RAVENNA).

Configure the Dolby Atmos Renderer audio driver

...

Important Note : The MacMini 10Gb Ethernet port (embedded) is not suitable for RAVENNA/AES67 network. 
Please use a dedicated USB-C to Ethernet, USB3 to Ethernet, or Thunderbolt to Gigabit Ethernet (Sonnettech) adapter.
The Dolby Atmos Renderer requires specific settings to communicate with Merging RAVENNA/AES67 devices.
Please go in the System Preferences - Merging RAVENNA / AES67 Settings :

...

More details on how to create sources and monitors can be found in the Anubis - Monitoring mission tutorials.
To be able to listen to the Multi-channel outputs (12 outputs -7.1.4 - in our example), you will need a Hapi MKII device connected on the network.

...

• In the World view (left pane), select both Anubis and your Hapi MKII.
• In the Matrix (right pane), connect the relevant Anubis Monitor to the Hapi MKII.
  Note: Make sure you first select the Monitor set on the Anubis itself in order to see it listed for connectivity in ANEMAN
  
• The Binaural Source can be listened to by selecting the Stereo Monitor (named "Phone" in our example), then the Stereo Source (named "Binaural" in our example), directly on the Anubis.
  

...

• Dolby® Dolby Atmos, and the double-D symbol are registered trademarks of Dolby Laboratories 
  Licensing Corporation. Confidential unpublished works. Copyright 2021 Dolby Laboratories. All 
  rights reserved.
• The computer running the Dolby Atmos Renderer application should also be properly configured for real-time audio applications.
  Please consult our configuration guides for Windows computers or Mac computers.
• Apple Mac M1 users : as of today (Dolby Atmos Renderer v3.7.3), the Dolby Atmos Renderer is compatible with, but not fully qualified on, M1 Macs, as the Renderer runs as an Intel process (see Activity Monitor under the “Kind” column) via the Rosetta 2 translation layer, which may cause performance issues.