Implementation of the Dante protocol in commercial audio systems: advantages of routing audio over existing corporate LAN infrastructure

In a large AV project in a hotel, conference center, or university, there comes a moment when the AV integrator says: “The system will run over your network, we will use Dante.” And the IT manager goes quiet for a second. Because no one has previously explained what that actually means for an infrastructure that normally handles computers and printers, not audio.

This article explains what Dante is, why it has become widely used in commercial sound systems, what it requires from a corporate network, and when it makes sense to use it. This is not a technical manual, just a framework for making informed decisions.

Audio cabling vs audio over network

Traditional sound systems use dedicated cabling. From each microphone, speaker, and processor, a physical audio cable must be run, sometimes stretching tens or even hundreds of meters. In small installations this is manageable, but in a building with multiple floors, zones, and dozens of speakers, it quickly becomes a separate infrastructure created solely for audio. This results in kilometers of cabling routed through ceilings, shafts, and corridors, serving no other purpose.

Networked audio solves this problem. Instead of its own dedicated cabling, audio is transmitted over the existing Ethernet network already used throughout the building for IT systems. A microphone sends audio as data packets over a standard network cable, the network delivers them to an amplifier or processor, and they are played back as sound. For operations, this means one unified network instead of two parallel infrastructures. For IT departments, audio is no longer a separate, unfamiliar domain but part of the same infrastructure they already manage.

Dante is a network audio protocol that enables high quality audio transmission over standard Ethernet networks. It was developed by the Australian company Audinate and has become the dominant standard in commercial AV. It is supported by nearly all major professional audio manufacturers. In practice, this means audio infrastructure becomes part of the IT network and scales like any other digital system in the building.

The term “Dante” is often used in the AV industry almost as a synonym for networked audio in general, even though alternatives such as AVB or AES67 also exist. The reason is practical: when most devices support the same protocol, equipment from different manufacturers can communicate seamlessly, and integrators are not locked into a single ecosystem.

What Dante is and how it works

Think of Dante as a set of rules that define how audio devices communicate over a network.

A microphone “says” within these rules: “I am microphone X, I am sending my audio to channel 1.”
A power amplifier says: “I am listening to channel 1 because I am driving speakers in the restaurant.”
The network simply delivers the right audio to the right destination.

For the user, this translates into two practical benefits.

Devices from different manufacturers can communicate with each other. A Shure microphone, a Biamp processor, a Yamaha amplifier, and Bose speakers can all operate within the same Dante system without converters or special interfaces. Dante is widely supported, and compatible devices can automatically “see” each other on the network. Ecosystem compatibility includes brands such as Yamaha, Shure, Bose, Biamp, Q-SYS, Crestron, Symetrix, and many other professional AV manufacturers.

Configuration happens in software, not in physical cabling. In a traditional audio system, adding a zone or moving a microphone typically means rewiring. In a Dante system, it is a software change: “send microphone 3 also to zone 5.”

The physical infrastructure remains the same; only the routing changes. This is especially important in environments where AV systems evolve over time.

Latency — the time it takes for audio to travel through the network — is negligible in Dante systems, typically under one millisecond. For comparison, sound traveling through air over three meters already has about 9 milliseconds of latency. The network adds less delay than the air itself.

Three practical advantages of Dante

From a building operations perspective, Dante translates into three concrete benefits:

1. Flexible zoning without new cabling

A hotel decides to add a separate audio zone for a terrace restaurant. A university needs to temporarily link two adjacent lecture halls for a larger event. A conference center wants to merge three smaller rooms into one large space.

In a traditional system, this requires installers, new cabling, and often construction work. In a Dante system, it is simply a configuration change. The cabling is already there because it is the same network infrastructure that connects the entire building.

2. Remote management and monitoring

The IT department of a hotel or university can monitor the entire audio system from a single location, in the same way they monitor servers or network infrastructure. They can see which processor is online, which speaker is unresponsive, or where a device is overheating.

In traditional audio systems, this visibility does not exist. Failures are typically discovered only when someone reports that something is not working.

3. Incremental upgrades instead of full system replacement

After five to seven years, a processor becomes outdated. It can be replaced with a newer Dante compatible unit while the rest of the system remains unchanged. New microphones from different manufacturers can be added to the same network and integrated seamlessly.

This is one of the main reasons Dante has a strong advantage in total cost of ownership (TCO). It does not lock the system into a single generation of hardware but allows gradual upgrades over time. In closed, non networked systems, aging components often force a full system replacement because new devices cannot communicate with legacy infrastructure.

These advantages matter mainly in larger, multi zone, long term installations. In small setups with one or two zones, they are often not noticeable. We address that in section 5.

What Dante requires from the network

The most common concern from IT managers is: “You want to run audio over the same network where I have accounting systems and CRM?” This is a valid question with two layers.

The first is technical capability of the network.
The second is organizational cooperation, without which Dante cannot be properly deployed, no matter how well the infrastructure is prepared.

Before looking at the technical requirements, it is important to address the concern that naturally arises: what if something else on the network takes priority and audio is interrupted? The short answer is no—and the reason is fundamental to how the system is designed.

The network operates with defined priority rules that are configured once and remain in place.

Audio packets are always given priority over other types of traffic. This is not a real time competition where the network decides what is more important at any given moment. It is a fixed hierarchy: audio first, data second. When IT runs a large backup transfer, it uses whatever bandwidth remains after audio traffic. When employees download large files, those transfers also use only the remaining capacity. Audio is never in a position where it must compete for bandwidth.

In practice, audio uses only a fraction of a typical enterprise network’s capacity. Even large Dante systems with dozens of zones require significantly less bandwidth than standard office applications today. A network that can handle video conferencing and cloud services will not be noticeably affected by audio traffic.

However, all of this assumes proper network design. “Proper design” means three concrete conditions:

Separate network or VLAN segmentation

Dante transmits a continuous data stream with strict timing requirements. If it shares bandwidth with general office traffic without any control, issues may occur. The solution is not complex but must be planned: either a dedicated physical network for audio or VLAN segmentation within the existing network to isolate audio into its own logical domain. In most modern enterprise networks, VLANs are already standard practice.

Gigabit infrastructure with QoS support

Dante requires Gigabit Ethernet and switches that support Quality of Service (QoS), a mechanism that assigns priority to specific types of network traffic. This is the hierarchy described above. Most modern enterprise switches support this, but older infrastructure may require upgrades. This is something IT needs to know before the AV project begins.

Cooperation between AV integrator and IT department

This is often the most important requirement, even though it is the least technical on paper. A Dante system is not a “turnkey and forget” installation. It requires AV integrators and IT teams to jointly define network design, agree on VLAN configuration, IP ranges, and access permissions.

Without this cooperation, one of two things usually happens: either IT refuses to allow AV traffic on the network, or it is allowed without proper structure, leading to disputes after the first incident about responsibility.

An experienced AV integrator anticipates this discussion early and involves IT at the beginning of the project. This is also one of the most reliable indicators of whether a supplier truly understands Dante or merely lists it in their portfolio.

The first type asks about network topology and requests switch configurations. The second says: “we will sort it out on site.”

When Dante makes sense and when it does not

Dante is not a universally better solution. It is better only for specific types of projects. In other cases, it can actually introduce unnecessary complexity. Being honest about this is important, because deploying Dante in a space that does not need it leads to higher costs, more configuration work, and greater maintenance requirements without any real benefit.

Dante makes sense in four main types of projects:

Multi zone buildings

Hotels, conference centers, universities with multiple buildings, or multi floor office spaces where audio is distributed across dozens of zones. In these environments, traditional cabling would require excessive infrastructure and constant physical expansion.

Projects with future growth potential

Spaces that are likely to expand over time by adding zones, connecting rooms, or reconfiguring layouts. Dante allows this type of growth without construction work or rewiring, since changes are made in configuration rather than infrastructure.

AV integration with other systems

Environments where AV must integrate with video conferencing, digital signage, building management systems, or IPTV. In such cases, audio is just one layer among many, and a network based architecture is the only practical way to align them.

Centralized or remote managed operations

Projects where the operator needs remote monitoring and control, typically across multiple locations. Examples include hotel chains or universities with campuses in different cities.

On the other hand, Dante does not make sense in small scale environments with one or two zones, where traditional audio cabling is simpler, cheaper, and essentially maintenance free. A restaurant with two zones does not need Dante, just as a small corporate meeting room does not. In these cases, networked audio adds complexity without solving a real operational problem.

Frequently asked questions

Is Dante secure on a corporate network?
Yes, when properly implemented. Dante is typically deployed using VLAN segmentation, which isolates audio traffic from other network operations. This makes it as isolated as any other critical system on an enterprise network. Security depends on following basic implementation rules such as changing default credentials on devices, keeping firmware updated, and managing access permissions. These are the same principles IT applies to any infrastructure.

What happens if the network goes down?
If the network fails, the audio system stops transmitting between devices, just like a traditional system would stop working if a physical cable is cut. In critical applications (such as emergency evacuation systems), Dante is combined with local redundancy or a backup system that operates independently of the network. For standard commercial audio, enterprise level network reliability is fully sufficient. If the network is reliable enough for office operations, it is also reliable enough for audio.

Can Dante be added to an existing audio system?
Partially yes. If the existing system includes Dante enabled devices, additional Dante components and network infrastructure can be integrated. If the system is entirely based on traditional cabling and legacy equipment, integration usually requires replacing key components such as the processor and sometimes amplifiers. In many cases, this is done gradually as part of a planned upgrade cycle.

Is a Dante system more expensive than a traditional one?
It depends on project size. For small installations, traditional cabling is usually cheaper. For larger multi zone systems, the balance shifts, as traditional audio requires extensive cabling and installation work, while Dante uses existing network infrastructure. Over a five to seven year total cost of ownership (TCO) period, Dante is typically more cost efficient even in projects with similar upfront costs, due to incremental upgrades instead of full system replacements.

Why Dante and not AVB or another protocol?
Technically, alternatives exist. AES67 is an open standard that Dante and other systems can use for interoperability. AVB (Audio Video Bridging) is another parallel technology. In practice, however, Dante has become the market standard. It is supported by the largest number of manufacturers and understood by the majority of AV integrators. This is not a matter of technical superiority, but ecosystem maturity, which makes it the most predictable choice for most projects.

Networked audio via Dante is not a technology trend, but a standard for scalable AV systems. The real question is not “should we use Dante or not”, but “is this a type of project where its advantages actually matter?”

In multi zone hotels, university buildings, or conference centers, the answer is almost always yes. In small installations with two zones, it is almost always no.

If you are planning an AV project where it is not clear whether to use networked audio or traditional cabling, an AAVS audit can evaluate project scale, growth potential, and network readiness, and recommend an architecture that matches the actual requirements.

MediaTech Central Europe, a.s. +421 220 999 700 | mediatech@mediatech.sk