Audinate Dante Core Integration

Driver Maturity

Production

Recommended for normal production use.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Minimum hi Version: v2.3.0

Overview

The Audinate^® Dante^® Core Integration discovers Dante devices and exposes their audio transmit and receive channels for routing in hi. It supports unmanaged Dante networks and optional Dante Domain Manager connectivity.

Network Requirements

Connection Model: The integration uses the Dante API on the selected primary and optional secondary server interfaces.
Multicast / Unicast: Follow the Dante network design for discovery and media flows.
VLAN / IGMP: Configure the network according to Audinate guidance.
Bandwidth: hi carries control traffic. Dante media flows between the Dante endpoints.
IP Version: IPv4 interfaces are selected in the hi Node configuration.
Firewall: Permit the Dante traffic required by the devices and optional Dante Domain Manager. Dante uses mDNS discovery on UDP port 5353, Dante monitoring traffic on UDP ports 8700 to 8708, and Dante controller connections to Dante Domain Manager on TCP ports 8001 and 8443.

Standards Conformance

Standard	Conformance	Notes
Dante	Implemented through the Audinate Dante API	Audio discovery and channel routing AES67 interoperability depends on device configuration

Operator Workflow

UI Surface in hi: Routing Matrix, Topology, and Inventory
Layers Controlled: Audio
Routing Semantics: Dante transmit channels are Sources and receive channels are Destinations.
Device Administration: Use Dante Controller or Dante Domain Manager for firmware, device names, and network policy.

Connection Methods

Connection: Audinate Dante SDK

Property	Value
Protocol	Audinate Dante SDK
Transport	UDP and TCP
Default Port	Service-discovered no fixed port is configured in hi
Authentication	None configured for unmanaged Dante discovery
Encryption in Transit	No separate TLS setting is exposed by this hi surface
Connection Model	SDK-based discovery and audio subscription routing
Required License	hiDante
Traffic Flow	Bidirectional discovery and control media flows between Dante endpoints

Connection: Dante Domain Manager

Property	Value
Protocol	Dante Domain Manager control
Transport	TCP
Default Port	Configured during commissioning
Authentication	Dante Domain Manager username and password
Encryption in Transit	TLS.
Connection Model	Outbound domain-scoped control and update subscription
Required License	hiDante
Traffic Flow	Outbound requests with inbound responses and domain updates

Required Configuration

Parameter	Description	Default
Primary Interface	Server interface connected to the primary Dante network	-
Secondary interface	Optional server interface connected to the secondary Dante network	-
Host	Optional Dante Domain Manager hostname or IP address	-
Port	Optional Dante Domain Manager port	0
Domain	Dante Domain Manager domain controlled by hi	Unmanaged
Login Name	Dante Domain Manager username	admin
Password	Dante Domain Manager password	-

Device-Side Setup

Follow Audinate Dante Core Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Device Discovery	Read-only	Discover Dante devices on selected networks or through DDM.
Channel Inventory	Read-only	Represent Dante transmit and receive channels as hi Ports.
Audio Routing	Read/write	Create and remove supported Dante channel subscriptions.
Redundant Network Selection	hi-side configuration	Select the primary and optional secondary server interfaces.
DDM Integration	Read/write scoped to exposed DDM operations	Discover and control selected Dante domains through Dante Domain Manager.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies devices that use the same protocol or connection method but have not been tested with hi. Device-specific configuration, firmware, and feature support can affect results.

Tested With

AJA Video Systems:
- AJA OG-DANTE-12GAM
Amphenol:
- Amphenol Amphe-Dante RJD1212
- Amphenol Amphe-Dante RJD2203
Audinate:
- Audinate Dante AVIO, including the AVIO Analog Output 2-Channel, AVIO USB, and AVIO USB-C adapters
- Audinate Dante Virtual Soundcard
DirectOut:
- DirectOut PRODIGY
Elytone:
- Elytone RM3-DT
Extron:
- Extron DMP 128 Plus
Ferrofish:
- Ferrofish A32pro Dante
Focusrite:
- Focusrite RedNet A16R MkII
- Focusrite RedNet AM2
- Focusrite RedNet D16R MkII
- Focusrite RedNet D64R
- Focusrite RedNet MP8R
- Focusrite RedNet PCIeNX
Genelec:
- Genelec 4420A
Glensound:
- Glensound DARK88
NTP Technology:
- NTP Technology PENTA 720
Powersoft:
- Powersoft Mezzo
QSC:
- QSC Q-SYS Core 610
RME:
- RME Digiface Dante
Sennheiser:
- Sennheiser TeamConnect Ceiling 2
Shure:
- Shure AD4D
- Shure MXA920
- Shure ULXD4Q
Solid State Logic:
- Solid State Logic Live Dante Expansion
- Solid State Logic Network I/O A16.D16
- Solid State Logic Network I/O HC Bridge
- Solid State Logic Network I/O SB 16.12
- Solid State Logic Network I/O SB 32.24
Sonifex:
- Sonifex AVN-AI16
- Sonifex AVN-AO16
- Sonifex AVN-DIO10
TASCAM:
- TASCAM ML-4D/OUT
Yamaha:
- Yamaha DM7 Compact
- Yamaha DSP-RX-EX
- Yamaha QL Series
- Yamaha Rio Series, including Rio3224-D

Potentially Compatible (Not Yet Verified)

Other Dante-enabled devices that expose the discovery and routing functions used by this integration.

Known Limitations

Validate Dante API and DDM interoperability with the exact deployed products.

What's Not Supported

Dante Via is not supported.
AES67 mode and QoS configuration, and Dante firmware administration from hi. Perform these tasks on the Dante devices.
Audio processing or media encoding.
Renaming Dante transmit or receive channels from hi. Rename channels with Dante Controller.
Creating or changing Dante multicast transmit flows. Configure multicast flows with Dante Controller.
Receiver latency and packet-size settings. Configure them with Audinate tools.

Trademarks

Note

Dante is a registered trademark of Audinate Pty Ltd.

All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.

RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Audinate unless explicitly stated.