Dante and AES67 Audio Networking: Routing, Sync, and Redundancy

Short answer

Dante is the industry-standard Audio-over-IP (AoIP) protocol for transporting uncompressed multichannel audio across standard gigabit IT networks. AES67 is an open interoperability standard enabling Dante to share audio with other AoIP protocols like Ravenna and Q-LAN. Network stability relies on Precision Time Protocol (PTP) for clock synchronization and IGMP Snooping to manage multicast traffic.

Overview

This technical guide details digital audio network architecture. We examine clocking mechanisms, network traffic management, latency configuration, and building redundant infrastructures for live event applications.

Target audience

•System engineers and network architects
•Broadcast and touring sound engineers
•Corporate AV integrators
•Technical directors of performance venues

Key takeaways

•PTP clocking operation and Leader Clock election
•Unicast vs Multicast audio flows in Dante networks
•Configuring IGMP Snooping on network switches
•Designing redundant networks (Primary / Secondary)
•Interoperability between Dante and AES67 devices

Introduction

Heavy copper multicore snakes that picked up radio interference and caused ground loops are a thing of the past. Today, a 128-channel 96 kHz live concert stream runs down a single CAT5e/CAT6 copper cable or fiber line. Behind this convenience lies network management. A misconfigured switch, clock conflict, or multicast packet storm can cause instant audio dropouts across the entire system. Audio engineers now need solid IT networking skills.

Synchronization: PTP (Precision Time Protocol)

In AoIP networks, audio packets break apart, pass through switches, and reassemble at receivers. For all network devices to play sample points simultaneously without phase shift or clicks, they must sync to a single shared master clock.

Dante uses PTP (IEEE 1588). One device on the network is elected automatically or assigned manually as the Leader Clock (Master Clock). All other devices function as Followers (Slaves).

•When syncing a device to external Word Clock (such as a console tied to a house sync generator), check Sync To External and Preferred Leader in Dante Controller.
•If multiple devices are set as Preferred Leader, Dante selects the master by lowest MAC address, establishing a clear fallback rule.

Routing: Unicast vs Multicast

Flow routing occurs inside Dante Controller using its patch matrix.

Unicast

Dante creates Unicast flows by default. This is a point-to-point connection between transmitter and receiver. Sending a single channel from a stagebox to two consoles (FOH and Monitors) forces the stagebox to send two separate identical streams, doubling bandwidth consumption.

Multicast

When broadcasting audio to multiple receivers (such as routing a master mix to 10 power amplifiers), use Multicast. The transmitter generates one flow, while the network switch replicates packets to requesting ports.

*Warning:* Unmanaged multicast traffic can flood your network, causing underpowered devices to drop off line.

Traffic management: IGMP Snooping

To deliver multicast streams only to switch ports where devices explicitly request them, your switch must support and enable IGMP Snooping. Without IGMP Snooping, switches act like hubs, flooding multicast to every port (Broadcast style), which causes packet collisions on large Dante networks.

Redundancy

Professional Dante devices (consoles, system DSPs) feature dual network ports: Primary and Secondary.

•These form two completely isolated physical networks (separate cables, separate switches).
•Devices transmit audio packets simultaneously to both networks.
•If the Primary cable breaks or a switch fails, receivers switch to the Secondary port instantly with zero audio dropouts (glitch-free redundancy).

*Critical rule:* Never connect Primary and Secondary switches together with a cable. Doing so creates a network loop that brings down the entire network.

Network Latency in Dante

Dante lets you set fixed buffer latency for each receiving device, compensating for network jitter.

•0.25 – 0.5 ms: Single gigabit switch connections.
•1.0 ms: Standard setting across 3 to 5 hop switch topologies, remaining safe and imperceptible to musicians.
•5.0 ms: Large venue networks (such as stadium fiber backbones).

Receiver latency must exceed the total travel time of packets across all network switches.

Common mistakes

1.Leaving Energy Efficient Ethernet (EEE / Green Ethernet) active. EEE powers down switch ports during low activity, causing PTP synchronization drops. Disable EEE on all audio switches.
2.Disabling IGMP Snooping on multicast networks. Disabling snooping overloads device network interfaces, particularly 100-Mbps legacy Dante modules.
3.Improper clocking settings. Allowing two devices to act as master clocks for different clock sources (like one taking Word Clock from a desk and another from a video router) causes audible clicks and pops.
4.Mixing control traffic with Dante without VLANs. Running heavy network traffic (video transfers, general internet, unthrottled Art-Net) over the audio network risks packet loss. Separate traffic physically or create VLANs with QoS prioritizing PTP (DSCP 56) and Audio (DSCP 46).

Best practices

1.Use enterprise switches. Select switches designed for audio (Cisco CBS350, Luminex, Netgear AV Line) featuring pre-built Dante profiles that configure QoS and IGMP Snooping automatically.
2.Isolate Secondary network paths. Route Secondary network cables along separate physical pathways to protect against accidental cable cuts.
3.Deploy Dante Domain Manager (DDM). In large installations (broadcast centers, campuses), DDM routes audio across Layer 3 subnets and enforces user permissions.
4.Assign static IP addresses to key nodes. While Dante works on Link-Local (169.254.x.x) or DHCP, assigning static IPs to core consoles and processors speeds up reboot recovery after power loss.

Protocol comparison matrix

Feature	Dante	AES67
Compatibility (Plug & Play)	High (Dante Controller)	Requires manual SAP/SDP configuration
Standard type	Proprietary (Audinate)	Open standard
Discovery protocol	mDNS (Bonjour)	Varies by implementation
Recommendation	Live sound industry standard	Inter-ecosystem bridging

ART-R recommendations

We integrate digital ecosystems built on stable network protocols. AVID VENUE S6L consoles integrate with Dante networks through DNT-192 expansion cards, providing 128 bi-directional channels at 96 kHz with full redundancy support.

For sound reinforcement, CODA Audio LINUS14D amplifiers feature onboard Dante inputs, receiving clean digital audio directly from the console with low latency.

FAQ

Does Dante work over Wi-Fi?

No. Wireless networks cannot guarantee precise timing delivery for PTP sync packets, so Dante audio transmission over Wi-Fi is unsupported. You can, however, run Dante Controller management software over Wi-Fi.

How many audio channels fit on a single Gigabit Ethernet cable?

Up to 512 channels uncompressed at 48 kHz / 24-bit (256 channels each direction), or 256 channels at 96 kHz.

How do you connect Dante and AES67 devices?

Dante hardware modules (like Brooklyn II or Broadway) include an AES67 mode. Enabling AES67 Mode in Dante Controller allows the device to send and receive AES67 multicast flows, bridging Dante with Q-SYS or Ravenna devices.

•How do you configure QoS settings on Cisco switches for Dante?
•What does the Elevate to Clock Master warning mean?
•What is the difference between Dante Virtual Soundcard and Dante Via?
•How do you check for multicast flooding on a network switch?

•Loudspeakers & Sound
•Cable Products

Downloads

•Cisco CBS350 setup guide for Dante (PDF)
•AES67 integration manual for AVID systems (PDF)
•Network bandwidth calculation sheet (Excel)

Glossary

Term	Definition
Dante	Audio-over-IP protocol developed by Audinate.
AES67	Open Audio-over-IP interoperability standard developed by the AES.
IGMP Snooping	Switch feature for managing multicast group subscriptions and filtering traffic.
VLAN	Virtual Local Area Network, isolating network traffic logically on a switch.
Latency	Fixed transit buffer time for audio packets passing from transmitter to receiver.

Conclusion

Dante audio networking provides reliable digital routing for modern venues. System stability relies on proper IT configuration. Enabling IGMP Snooping, keeping Secondary networks isolated, and managing PTP clocking ensures your audio network runs without dropouts.

Schema recommendation

•Article for technical manual indexing
•FAQPage for Q&A rich snippets
•HowTo for PTP and IGMP setup instructions

Image recommendations

1.Hero image: Laptop running Dante Controller software displaying green patch matrix checkmarks.
2.Technical diagram: Redundant Dante network diagram (Primary / Secondary) connecting FOH console, monitor console, stageboxes, and isolated switches.
3.Technical diagram: Unicast vs Multicast flow comparison showing packet distribution differences.
4.Setup photo: Rack-mount network switches with Neutrik opticalCON fiber connections.
5.Software screenshot: Dante Controller Clock Status tab showing Leader Clock assignment and follower device sync metrics.