The Dolby Atmos Renderers comes in either fully qualified turnkey solutions including hardware and software (HE-RMU: Home Entertainment Rendering Mastering Unit), or software only solutions running on the user's machine (DAPS: Dolby Atmos Production Suite). |
When connecting to a MADI HE-RMU, one needs to use a MERGING+HAPI, HAPI MK2 HORUS. (equipped with MADI card(s)).
Please go on this page to connect either Pyramix MassCore or Native to a MADI HE-RMU
When connecting to a Dante HE-RMU, one can configure the HE-RMU Dante card in AES67 mode for interoperability with Masscore Ravenna, or Merging Audio Device / Virtual Audio Device drivers. (48kHz only!)
Configuration guide coming soon.
The most popular alternative used successfully by Pyramix customers around the world (pending Dolby's official qualification), is to use a standard network port of the HE-RMU (or DAPS/DAMS computer) to run our AES67/RAVENNA drivers in order to receive/send audio, whether it's a Mac based or PC based computer.
Please go on this page to connect Pyramix MassCore to Dolby Atmos Renderer with AES67/RAVENNA network.
Please go on this page to connect Pyramix Native - Merging Audio Device driver to Dolby Atmos Renderer with AES67/RAVENNA network.
Any Dolby Atmos capable DAW (ASIO or Core Audio) can also take benefit from our AES67/RAVENNA drivers in order to receive/send audio to the computer running the Dolby Atmos Renderer (pending Dolby's official qualification), whether it's a Mac based or PC based computer.
Please go on this page to connect a CoreAudio DAW to Dolby Atmos Renderer with AES67/RAVENNA network.
Please go on this page to connect an ASIO DAW to Dolby Atmos Renderer with AES67/RAVENNA network.
This solution is only possible with Pyramix Native running the Merging Audio Device driver, and is limited to 96 channels.
Please follow the instructions on this page.