Dante — Full Architecture and Configuration Guide

For a concise overview of Dante, see glossary/dante. This article covers detailed architecture, network configuration, and troubleshooting.

Dante (Digital Audio Network Transport over Ethernet) is the most widely deployed professional audio networking protocol in the world, developed by Audinate. Dante replaces point-to-point analog and AES3 connections with a single Ethernet network capable of carrying hundreds of audio channels simultaneously. Its combination of automatic device discovery, sub-millisecond latency, IEEE 1588 PTP clock synchronization, and broad hardware support makes it the de facto standard for AV-over-IP audio in commercial installations.

Protocol Architecture

Unicast and Multicast Flows

Dante uses two transmission modes simultaneously:

Unicast audio flows — One transmitter sends to one receiver. Used for all point-to-point routing assignments. Unicast flows are the default for all audio routing in Dante Controller. A 64-channel transmitter routed to a single receiver generates 64 unicast flows, each consuming approximately 4-5 Mbps.

Multicast audio flows — One transmitter sends to multiple receivers using a single stream. In multicast mode, 10 receivers of the same transmitter channel consume no more bandwidth than 1 receiver. Multicast requires IGMP snooping on all switches in the path; without it, multicast floods all ports. Multicast is configured explicitly in Dante Controller per channel, not enabled by default.

Bandwidth per channel: Dante audio consumes approximately 4.5 Mbps per channel at 48 kHz/24-bit. A 32-channel transmitter sending to 5 receivers via unicast consumes 32 × 4.5 × 5 = 720 Mbps — significant on a 1 Gbps network. Plan multicast for high-receiver-count distributions to control bandwidth.

mDNS Device Discovery

Dante devices announce their presence and capabilities via mDNS (Multicast DNS, Bonjour). Discovery occurs automatically on the local subnet. All Dante devices on the same VLAN appear in Dante Controller without any manual configuration.

mDNS does not cross VLAN boundaries — Dante devices on VLAN 100 cannot discover devices on VLAN 200 without an mDNS proxy or Dante Domain Manager. This is the most common cause of "device appears on the network but not in Dante Controller."

IEEE 1588 Precision Time Protocol (PTP)

All Dante devices synchronize to a common clock using IEEE 1588v2 PTP. The network automatically elects one device as the PTP grandmaster clock based on the BMCA (Best Master Clock Algorithm), which evaluates clock accuracy, stratum, and priority settings. All other devices are PTP slaves synchronized to the grandmaster.

PTP accuracy achieved: sub-microsecond clock synchronization across all devices in the Dante domain. This precision ensures sample-accurate audio playback across all receivers simultaneously — a requirement for multi-speaker systems where timing offsets would cause comb filtering.

Grandmaster stability: Dante's automatic grandmaster election works well in pure-Dante systems. In mixed systems (Dante devices + non-Dante PTP devices), clock instability can occur. Best practice: designate a stable, always-on device (dedicated Dante processor, or the main DSP) as the clock master by setting its clock priority in Dante Device Manager. Avoid laptops running Dante Virtual Soundcard as grandmaster — laptop CPU load affects clock stability.

Network Infrastructure Requirements

Switch Requirements

Managed switches only — Dante requires:

• IGMP snooping — Controls multicast delivery. Without IGMP snooping, Dante multicast streams flood all switch ports, saturating links and causing dropouts.
• QoS (DSCP) — Dante marks audio packets with DSCP EF (46), which maps to the highest-priority queue. Switches must honor DSCP markings in their QoS configuration. Without QoS, bursty non-audio traffic can delay Dante packets, causing dropouts.
• Low latency — Dante requires consistent sub-millisecond forwarding times. Enterprise managed switches from Cisco, Aruba, Juniper, and most mainstream vendors meet this requirement. Avoid switches with software-based forwarding; all switching must be hardware-accelerated.

Recommended switches (widely deployed with Dante): Cisco Catalyst 9xxx series, Cisco SG350/SG550 (small rooms), Aruba 2530/2540 series, Netgear GS3xx series (smaller systems), Yamaha SWX series (Dante-optimized with preconfigured IGMP and QoS defaults).

Switch configuration checklist:

• IGMP snooping: enabled on all VLANs carrying Dante traffic
• IGMP querier: enabled on at least one switch per VLAN (or designated querier)
• QoS: DSCP EF → queue 1 (highest priority) on all ports carrying Dante
• Spanning tree: RSTP enabled; portfast on all endpoint ports
• MTU: 1500 bytes standard sufficient; jumbo frames not needed for Dante

VLAN Design for Dante

Dante traffic should be isolated on a dedicated VLAN, separate from general IT traffic, management traffic, and BYOD. Recommended VLAN architecture for AV installations:

All Dante endpoints on VLAN 100 discover each other automatically. The DSP and Dante Controller PC must also be on VLAN 100 (or a management VLAN with routed access to VLAN 100 for Dante Controller — though routing adds latency and is not recommended for latency-sensitive audio flows).

See vlan-configuration-for-av for detailed switch configuration examples.

Redundant Network (Secondary Port)

Dante devices with two Ethernet ports support a redundant network configuration. A second, physically separate switch carries duplicate Dante traffic. If the primary network fails (switch crash, cable cut), the secondary network takes over within approximately 1 second — brief audio muting at worst.

Redundant network configuration: primary and secondary Dante ports connect to two independent switches. Both switches carry the same VLAN. All Dante devices must be present on both switches for full redundancy. The redundant network carries live traffic continuously (not hot standby) — Dante Controller shows both network states in real time.

Dante Controller

Dante Controller is Audinate's free Windows/Mac software for managing Dante networks. It is the primary interface for all Dante configuration during commissioning and support.

Key views in Dante Controller:

Routing view — Matrix grid showing all transmitters (columns) and receivers (rows). Clicking a cell creates a unicast routing assignment. Green dots indicate active routes. The routing matrix is the primary commissioning tool.

Device info view — Shows all discovered Dante devices with their IP address, firmware version, sample rate, and clock status. The grandmaster clock is indicated by a clock icon. Devices with clock errors show warning indicators.

Clock status view — Displays the PTP clock hierarchy: grandmaster, preferred masters, and slaves. Shows clock offset (ideal: < 100 ns). Clock jitter and instability appear as elevated offset values — the first diagnostic to check when audio dropouts occur.

Network status view — Shows packet loss, latency, and bandwidth utilization per device. Elevated packet loss (even 0.1%) causes audio glitches. Latency above 10ms indicates network congestion.

Latency settings

Dante allows configuring audio latency at the device level: 0.25 ms, 0.5 ms, 1 ms (default), 2 ms, 5 ms, 10 ms. Lower latency settings are more susceptible to network jitter — a network hiccup that would cause no audible dropout at 1ms may cause a glitch at 0.25ms. Use:

• 1 ms — Standard for most professional installations on managed networks
• 0.5 ms — Live sound on dedicated AV networks with known-good switches
• 5-10 ms — Installations on shared IT networks or where network quality is uncertain

Dante Domain Manager (DDM)

See networking/dante-domain-manager for the full DDM reference: multi-VLAN architecture, server deployment, domain design, user roles, PTP across VLANs, and commissioning workflow.

Dante Domain Manager is an optional licensed server application for managing Dante networks that span multiple VLANs or require access control. DDM replaces mDNS-based discovery with a centralized registry, enabling devices on separate VLANs to discover each other and route audio across routed IP boundaries.

Key capabilities:

• Multi-VLAN Dante — Devices on different VLANs/subnets register with the DDM server and can route audio across Layer 3 boundaries. Audio flows directly between device IPs; DDM only handles the control plane.
• User authentication — Login required to make routing changes. Dante Controller connects through DDM and presents only the domains the user is authorized to access.
• Domain separation — Named logical partitions (e.g., "Ballroom-A", "Production-Hub") isolate unrelated systems and control which devices operators can access.
• Audit logging — Every routing change recorded with username and timestamp; exportable as CSV.

DDM is essential for enterprise deployments with multiple rooms on different VLANs. Single-room or single-VLAN installations with trusted operators do not require it.

AES67 Mode

Dante devices support AES67 interoperability mode, allowing them to exchange audio with non-Dante devices that support AES67 (Ravenna, Livewire, Q-SYS, SMPTE 2110-30 equipment).

In AES67 mode: the Dante device emits RTP multicast streams per the AES67 specification and can receive AES67 RTP streams from other vendors. Automatic Dante discovery and routing convenience is lost — AES67 routing requires manual SDP (Session Description Protocol) exchange.

AES67 mode is configured per-device in Dante Controller → Device Config → AES67 tab. The device must be restarted after switching modes. See aes67-network-audio and dante-vs-aes67 for full comparison.

Dante Virtual Soundcard (DVS) and AVIO Adapters

Dante Virtual Soundcard (DVS) — Software that makes a Windows/Mac computer a Dante endpoint, appearing in Dante Controller as a device with up to 64 channels in/out. Used for recording, playback, and monitoring on laptops and workstations. DVS is licensed per computer.

Important limitation: DVS uses the computer's general-purpose OS clock, which is less stable than dedicated hardware clock implementations. DVS should not be used as the PTP grandmaster clock in systems requiring high timing stability. Use DVS for recording and monitoring; use dedicated hardware DSPs as the clock master.

Dante AVIO adapters — Small hardware devices that bridge Dante to other analog/digital formats:

• AVIO Analog 2x2 — 2 analog inputs/outputs with XLR connectors
• AVIO AES3 2x2 — 2 AES3 (digital) inputs/outputs
• AVIO USB — USB audio bridge between a computer and Dante without DVS software

AVIO adapters are hardware-clocked, stable Dante endpoints. Preferred over DVS when physical I/O is needed at a workstation or patch point.

Common Pitfalls

• IGMP snooping disabled — Dante multicast floods all switch ports, saturating 1GbE links. Single most common cause of Dante dropouts in new installations. Verify IGMP snooping is enabled at the VLAN level, not just globally.
• No QoS configured — Audio packets delayed by burst IT traffic during video calls, file copies, or backup jobs. Configure DSCP EF → high priority queue on all switches. Verify with Dante Controller network status view.
• Clock instability from laptop grandmaster — DVS on a laptop becomes grandmaster; CPU load during a video call causes clock jitter; audio stutters. Set a dedicated hardware device as preferred clock master in Dante Device Manager.
• mDNS blocked by firewall or router — Dante devices on the same VLAN but behind a router or UTM firewall that drops mDNS traffic cannot discover each other. Dante must be on a flat Layer 2 VLAN, not routed between segments.
• Sample rate mismatch — One device at 44.1 kHz and all others at 48 kHz. Device appears in Dante Controller but all routing to/from it shows as inactive. Check sample rate in Device Config and align all devices to 48 kHz.
• DDM not licensed but required — Multi-VLAN campus deployment configured without DDM; devices on different VLANs cannot discover each other, so the system appears to work room-by-room but cross-room routing fails. Purchase DDM licenses before commissioning multi-VLAN deployments.