Dante Network Design Guide: Routing, Clocking, Latency & Multicast Explained
Masters Voice Insights
Technology

Dante Network Design: Routing, Clocking & Latency

Learn how Dante networks handle audio routing, clock synchronisation, latency, unicast, multicast, switching and the infrastructure behind reliable networked audio.

{{wf:Author/Name|Dynamo}}
Written by Dane Lewis Technical Director | Communications & Audio Visual
New to Dante Audio Networking?

If you are starting with the fundamentals, first read our Dante Audio Networking guide to understand how Dante transports professional audio over IP. This technical guide goes further into routing, switching, multicast, clock synchronisation, latency and network design.

Networked Audio · Technical Guide

Dante Network Design Guide: Routing, Clocking, Latency & Multicast

A practical guide to designing dependable Dante audio networks for commercial AV systems — from signal routing and clock synchronisation to multicast, bandwidth, switching and long-term support.

Dante Controller Networked Audio Unicast Multicast Clocking AV Networks
Explore Dante Integration → Jump to Network Requirements
Dante Audio Network
Microphones
DSP
Amplifiers
Recording
Mixing
Computers
01 · Network Architecture

Dante Network Architecture: Routing, Clocking, Latency & Multicast

Dante separates the physical network from the audio route.

Traditional analogue audio systems often create signal paths physically. A microphone connects to an input, another cable connects processing equipment, and dedicated cable paths continue toward amplifiers or other destinations.

Dante changes that architecture. Dante-enabled equipment connects to an IP network and compatible audio channels are subscribed to destinations through software.

This allows many audio routes to share Ethernet infrastructure, but it also means the network becomes part of the AV system. Switches, uplinks, timing, multicast behaviour and network management therefore need to be considered during design.

Networked audio is part of a wider AV-over-IP strategy.

For the video and wider media-distribution layer, read AV over IP: Why the Industry Is Moving Away from Point-to-Point.

02 · Dante Controller

Dante Controller turns the network into a manageable audio system.

Dante Controller provides visibility into devices, channels, subscriptions, clock status, network information and performance data across compatible Dante endpoints.

Device discovery

View Dante-enabled devices and their available transmit and receive channels across the network.

Channel routing

Create subscriptions between source and destination channels and review existing route status.

Clock monitoring

Review clock configuration, synchronisation and clock-related status information.

Latency visibility

Inspect latency configuration and supported performance statistics across receiving devices.

Bandwidth

Review transmit, receive and multicast bandwidth information when diagnosing the network.

Naming & presets

Consistent device names, channel names and saved routing presets improve long-term supportability.

Official Dante Controller Documentation ↗
03 · Traffic Design

Unicast and multicast solve different distribution problems.

Dante normally creates unicast flows for ordinary subscriptions. Multicast becomes useful when one source must efficiently distribute media to multiple destinations.

1:1

Unicast

Media is supplied toward specific receiving devices. It is straightforward for ordinary point-to-point subscriptions and is Dante's normal routing behaviour.

1:N

Multicast

A multicast flow can serve several receivers from one transmitted media flow, making it useful for planned one-to-many distribution.

Multicast should solve a real design requirement.

It should not simply be enabled everywhere. Multicast traffic can propagate more widely across a network than required, so switch configuration and IGMP behaviour should be planned for larger installations.

Audinate Unicast & Multicast Guide ↗
04 · Clocking & Latency

Audio packets must arrive — and they must arrive at the right time.

Networked digital audio depends on accurate timing. Dante devices maintain a shared timing reference and receiving devices use configured latency to allow packets enough time to cross the network before playback.

Clock leadership

Eligible devices participate in establishing a common timing reference used across the Dante network.

Receiver latency

The receiving device allows sufficient time for packets to travel through the expected network path.

Packet performance

Late packets, congestion or unsuitable topology can create glitches and indicate that latency or network architecture needs investigation.

Lowest latency is not automatically best.

Select latency for the real topology and endpoint capability. A stable configuration is more valuable than an unnecessarily aggressive setting that leaves insufficient margin for packet delivery.

Audinate Latency Documentation ↗
05 · Network Requirements

What should be considered when designing a Dante network?

Ethernet capacity

Size ports and uplinks for channel count, multicast, other AV traffic and future expansion.

Suitable switching

Use network equipment appropriate for continuous real-time media rather than treating AV as ordinary intermittent office traffic.

Multicast management

Where multicast is required, review IGMP behaviour and prevent media reaching ports that do not require it.

QoS

Shared and more complex networks may use QoS to protect time-sensitive media and timing traffic.

Network ownership

Establish whether the AV integrator, IT team or managed service provider controls network configuration and changes.

Documentation

Record device names, switches, port assignments, addressing, VLANs where used, routes and configuration backups.

Dante does not automatically require a dedicated network.

The appropriate architecture depends on network ownership, traffic, security, scale and organisational ICT standards. The audio workflow and network architecture should be designed together.

06 · Architecture Comparison

Dante does not eliminate cabling. It changes what the cabling has to do.

Design Area Traditional Analogue Dante Networked Audio
Signal routing Primarily determined by physical connections. Channels are subscribed logically over the network.
Cable density Individual signals often require dedicated cable paths. Multiple channels can share Ethernet or fibre infrastructure.
Expansion New routes may require extra cabling and I/O. New endpoints can be added where network and device capacity permit.
Reconfiguration Often requires physical repatching. Many route changes can be performed through software.
Fault finding Follow the physical signal chain. Requires both AV and network diagnostics.
Support Primarily audio and cabling skills. Audio, networking, software configuration and documentation all matter.
07 · Networked AV

Dante and AV over IP are related, but they are not interchangeable terms.

AV over IP is the broader concept of transporting professional audio, video and related media through IP networks rather than conventional point-to-point AV signal paths.

Dante is an Audinate platform with a particularly established role in professional networked audio.

A commercial AV project can therefore use Dante for audio transport while another AV-over-IP platform distributes video. Those systems still need to be coordinated across networking, control, security and support.

Read the AV over IP Guide → Explore AV over IP Integration →
08 · Applications

Dante becomes especially useful when audio must move between many locations.

Schools & campuses

Paging, bells, halls, administration, distributed amplifiers and multi-building audio systems. Explore our School PA & Bell System Guide .

Performance venues

Mixing consoles, stage I/O, DSP, amplification, recording and distributed audience areas.

Corporate facilities

Training rooms, divisible spaces, networked DSP, ceiling microphones and centralised audio services.

Worship spaces

Front-of-house audio, stage inputs, streaming, overflow rooms and distributed amplification.

Multi-zone venues

Flexible source distribution across bars, restaurants, functions, outdoor spaces and back-of-house zones.

09 · Common Problems

Most Dante problems are easier to prevent during design than diagnose later.

01

Designing audio before the network

Channel counts are defined without confirming switch ports, uplinks or network ownership.

02

Unnecessary multicast

Multicast is introduced without first establishing whether the workflow actually requires one-to-many flows.

03

Ignoring switch behaviour

Network policies, multicast, QoS and uplink behaviour are not reviewed before endpoints are commissioned.

04

Poor naming

Generic device and channel names make support unnecessarily difficult after handover.

05

Latency set too aggressively

Latency is reduced for theoretical performance instead of being selected for the actual network path.

06

No handover records

Routes, presets, switch details and configuration backups are not documented.

Network documentation is part of AV maintenance.

Device names, routes, firmware information, switch configuration and network drawings should remain available throughout the technology lifecycle. See our Commercial AV Preventative Maintenance Checklist .

10 · Integrated Systems

Dante and Q-SYS can solve different layers of the same AV system.

Dante can provide the networked-audio transport layer, while Q-SYS integration can provide DSP, control, automation, user interfaces and wider AV-system management.

The important part is not simply connecting compatible products. Signal flow, naming, network architecture, user workflows and support documentation should be designed as one system.

EDUCATION PROJECT

Leichhardt Public School

Masters Voice Technology used Dante networked audio as part of a Q-SYS school PA and bell system supporting paging, scheduled bells, priority communication and distributed campus audio.

View School PA Project →
PERFORMANCE PROJECT

Campbelltown Performing Arts High School

The hall audio redevelopment combines Q-SYS processing, Dante network audio, professional amplification and performance loudspeakers for assemblies and productions.

View Hall Audio Project →
11 · Project Checklist

Define the network before commissioning begins.

A useful Dante design brief should answer these questions before the system reaches site.

✓ What are every source and destination in the audio workflow?
✓ How many transmit and receive channels are required?
✓ Is the AV network dedicated or shared?
✓ Who owns and manages the network switches?
✓ Which channels require one-to-many distribution?
✓ Is multicast genuinely required?
✓ Are switch uplinks sized for the expected traffic?
✓ What receiver latency is appropriate?
✓ How will devices and channels be named?
✓ What routing and configuration records will be handed over?
✓ Who is responsible for future firmware and network changes?
✓ How will the system be supported after handover?
Continue Exploring

Dante is one part of the wider networked AV architecture.

AV over IP

Understand how video and media distribution are moving from fixed point-to-point architecture onto managed networks.

Read AV over IP Guide →

School PA & Bell Systems

See how networked audio can support paging, scheduling, zoning and campus communications.

Read School PA Guide →

Commercial AV Maintenance

Learn what should be tested and documented as connected AV systems move through their lifecycle.

Read Maintenance Guide →
Frequently Asked Questions

Dante network design questions.

Does Dante require a dedicated network?
Not necessarily. Dante can be deployed on dedicated or shared network infrastructure. The appropriate design depends on system scale, network ownership, traffic, security and organisational ICT requirements.
What is Dante Controller used for?
Dante Controller is used to discover compatible Dante devices, route channels, configure supported device parameters and review clock, network, bandwidth, latency and performance information.
What is the difference between Dante unicast and multicast?
Unicast media flows serve specific receivers. Multicast allows the same transmitted media flow to serve multiple receivers and can be useful for planned one-to-many distribution.
Does Dante require QoS?
Requirements vary with the network. More complex or converged environments may use QoS to prioritise time-sensitive media and clock traffic. The network policy should be designed for the actual topology rather than applied generically.
What does IGMP snooping do?
IGMP snooping allows compatible switches to better control where multicast traffic is forwarded instead of unnecessarily sending it throughout the switched network.
Can Dante work with Q-SYS?
Yes, where compatible Dante-capable Q-SYS hardware, software or interfaces are used. Dante may provide the audio-transport layer while Q-SYS handles DSP, automation, control and other system functions.
What should Dante handover documentation contain?
Useful records include device names, channel names, network diagrams, switch and port information, addressing and VLAN details where relevant, routing information, saved presets, firmware records and configuration backups.
Is Dante the same as AV over IP?
Dante is a specific Audinate networking platform with a strong professional-audio ecosystem. AV over IP is the broader category of transporting professional audio, video and related media using IP networks.
Design · Install · Support

Planning a Dante or networked-audio system?

Masters Voice Technology designs and integrates Dante-based audio systems across commercial AV, education, government, workplace and venue environments. Start with the required audio workflow, network architecture and long-term support requirements.

Dante Audio Networking → Discuss a Project →