The Rise of Audio Over IP: Why Protocol Choice Matters

Modern audio infrastructure is migrating from dedicated analog and digital point-to-point connections to IP-based networks. This shift delivers flexibility, scalability, and reduced cabling costs, but it also introduces a critical decision: which audio networking protocol to adopt. Two protocols dominate the conversation: AES67, the open interoperability standard, and Dante, the popular proprietary solution from Audinate. Both enable high-quality, low-latency audio transport over Ethernet, but they differ significantly in philosophy, ease of use, ecosystem, and cost. Understanding these differences is essential for anyone designing a professional audio system—whether for live sound reinforcement, broadcast production, installed corporate AV, or recording studios.

Understanding AES67: The Open Standard

AES67 is a standard developed by the Audio Engineering Society (AES) and published in 2013. It specifies the transport and synchronization of high-quality, uncompressed audio over IP networks. As an open standard, AES67 allows devices from different manufacturers to communicate without requiring proprietary licensing. This interoperability is its primary value proposition.

How AES67 Works

AES67 is not a standalone system like Dante; rather, it defines a specific set of technical parameters that any manufacturer can implement. It uses Real-time Transport Protocol (RTP) to carry audio data, typically in uncompressed PCM format. Audio is streamed in multicast groups, and synchronization is achieved via the Precision Time Protocol (PTP) according to IEEE 1588-2008, often referred to as PTPv2. The standard prescribes sample rates of 48 kHz or 96 kHz, bit depths up to 24 bits, and channel counts up to 8 channels per stream (with higher counts possible through multiple streams). Latency is configurable, typically ranging from 1 ms to 10 ms depending on network quality and buffering.

Key Strengths of AES67

  • Interoperability: Devices from brands like RAVENNA, Livewire, Q-LAN, and others can coexist on the same network if they support AES67.
  • Vendor Neutrality: No single company controls the standard; it is managed by the AES and open for all.
  • Cost Effectiveness: Because no licensing fees are required, AES67-enabled devices can be more affordable, especially in large-scale multi-vendor installations.
  • Future Proofing: Open standards are less prone to vendor lock-in and may have longer longevity.

Common Use Cases for AES67

AES67 is prevalent in broadcast environments where compatibility across multiple equipment families is mandatory. It also appears in larger installed sound systems where a mix of manufacturers’ products must work together. Additionally, AES67 is the backbone for interoperability profiles such as ST 2110-30 (AES67 audio in SMPTE ST 2110 for professional media over managed IP networks).

Understanding Dante: The Ecosystem Leader

Dante, developed by Audinate, is a proprietary audio-over-IP protocol that has become the de facto standard in many professional audio sectors since its introduction in 2006. Unlike AES67, Dante is a complete system solution that includes hardware chips, software drivers, and management tools. Audinate licenses the technology to manufacturers, who pay royalties per device.

How Dante Works

Dante also uses standard IP networks, but it implements its own transport layer and clocking mechanisms. Audio is transmitted using UDP packets in multicast or unicast modes. Dante supports very low latency—as low as 0.25 ms in some configurations—and can deliver up to 1024 channels per stream (with practical limits determined by network bandwidth). Synchronization uses Audinate’s proprietary clocking, though later versions also support PTPv2 for interoperability.

Key Strengths of Dante

  • Ease of Use: Dante Controller software automatically discovers devices, manages subscriptions, and configures latency. Plug‑and‑play setup reduces deployment time.
  • Mature Ecosystem: Thousands of products from hundreds of manufacturers include Dante natively. Service and support are well established.
  • Built‑in Redundancy: Dante supports primary/secondary network redundancy via separate switches, providing failover in milliseconds.
  • Advanced Features: Dante Domain Manager enables user authentication, AES67 mode, and network segmentation for large-scale secure systems.
  • Software Integration: Dante Virtual Soundcard allows any computer to connect to a Dante network without additional hardware. Dante Via extends this to other applications.

Common Use Cases for Dante

Dante is overwhelmingly the choice for live sound reinforcement, concert touring, and performing arts venues. It is also heavily used in corporate AV, recording studios, and house of worship installations. Its reliability, low latency, and management tools make it ideal for systems where non-technical staff need to operate the network.

Head‑to‑Head Comparison: AES67 vs. Dante

While both protocols transport audio over IP, the differences influence system design, budget, and operational workflows. Below is a detailed comparison of the critical factors.

Standardization and Control

AES67 is an open standard defined by the AES. No single entity controls its development, although updates require consensus. Dante is fully controlled by Audinate. Audinate can introduce new features quickly, but users are dependent on the company’s roadmap.

Latency

Both offer low latency, but Dante can achieve lower minimums. Typical Dante latency settings are 0.25 ms, 0.5 ms, 1 ms, 2 ms, or 5 ms. AES67 latency is typically 1 ms or higher, but many implementations reach 1 ms reliably. In practice, most applications do not require sub‑millisecond latency, but for IEM (in-ear monitor) feeds or large live events, Dante’s edge can matter.

Channel Count

Dante supports up to 1024 channels per stream at 48 kHz (with 64‑channel streams being common). AES67 streams are limited to 8 channels per stream, but multiple streams can be aggregated. The practical total channel count on a network depends on bandwidth, switches, and use of multicast. Dante’s higher per‑stream density simplifies management for large systems.

Network Requirements

Both require a managed Ethernet network that supports IGMP snooping for multicast and QoS (Quality of Service) tagging. However, Dante is less tolerant of non‑managed switches because it relies on precise clocking and prioritization. AES67 also requires QoS, but its PTP clocking works well with standard network infrastructure as long as proper IGMP and DiffServ are configured. In practice, many integrators recommend the same switches for both.

Setup and Management

Dante’s proprietary tools—Dante Controller, Dante Domain Manager, and Dante Virtual Soundcard—provide a seamless user experience. AES67 devices often ship with their own manufacturer‑specific discovery and routing interfaces, which can be less consistent. Some brands (e.g., RAVENNA, QSC) offer unified management, but there is no single “AES67 Controller.” This fragmentation can make multi‑vendor AES67 networks more complex to configure.

Cost and Licensing

AES67 has no per‑device licensing fees, potentially lowering hardware costs. Dante devices include a royalty fee paid by the manufacturer, which may be passed to the end user—typically a few dollars per channel or per device. However, the cost difference is often negligible compared to the total system investment. Dante’s ecosystem may reduce engineering and troubleshooting labor, offsetting higher hardware costs.

Interoperability

AES67 is designed for interoperability across brands. Many Dante devices also support AES67 (via an optional mode), enabling them to communicate with AES67‑only devices. However, configuration of AES67 on Dante devices can be less straightforward, and not all Dante devices support it. Pure AES67 networks guarantee broad compatibility, but the user interface is less polished.

How AES67 and Dante Can Work Together

In practice, many systems contain a mix. For example, a broadcast facility might use AES67 on its routing infrastructure but integrate Dante for a live room or microphones. Thanks to the AES67 mode in many Dante devices, a common bridge exists. On the Dante side, enabling AES67 mode makes the device appear as an AES67 stream source or sink. The network must then be configured to support both protocols’ multicast and clocking schemes. This scenario often requires careful network planning, but it can be successful.

Additionally, protocols like RAVENNA (used in broadcast and ST 2110) and Livewire (Wheatstone) are AES67‑compatible. Dante Domain Manager also facilitates AES67 connectivity across different network domains. The AES67 standard remains the glue for these inter‑protocol links.

Which Protocol Should You Choose?

There is no universal right answer; the choice depends on your specific environment, expertise, and priorities.

Choose AES67 if:

  • You need to integrate equipment from multiple manufacturers that do not all support Dante.
  • Your project involves broadcast or media production in a SMPTE ST 2110 environment (where AES67 is mandated for audio).
  • You want to avoid any form of vendor lock‑in and prefer open standards for long‑term flexibility.
  • Budget constraints are tight and you are building a large‑scale system where per‑device licensing savings add up.

Choose Dante if:

  • You prioritize ease of installation and management, especially if your technical staff is not deeply experienced with IP networking.
  • You need the lowest possible latency for demanding applications like live in‑ear monitoring or large channel counts in a touring environment.
  • You value a huge ecosystem of compatible products with mature support and training resources.
  • Your system requires redundancy features like automatic switchover using Dante’s primary/secondary network.

Real‑World Scenarios

Live Event Production (Dante Preferred)

In a touring rig with digital mixing consoles, stage boxes, wireless microphone receivers, and personal monitors, Dante’s plug‑and‑play nature saves hours of setup time. Engineers can quickly patch channels and diagnose issues with Dante Controller. Low latency is critical for foldback. Most major console manufacturers (e.g., Yamaha, Allen & Heath, DiGiCo, Soundcraft) offer Dante cards or native Dante I/O.

Broadcast Facility (AES67 Common)

Broadcasters often use equipment from many vendors: intercoms, router frames, codecs, and playout servers. ST 2110 infrastructure requires AES67 for audio. While some facilities include Dante‑equipped consoles, the core routing is often AES67 via RAVENNA or similar. Equipment such as Audinate’s own documentation explains how Dante can integrate into ST 2110.

Corporate AV and Installed Systems (Both Possible)

For a meeting room with a DSP, ceiling microphones, and speakers, either protocol works. Dante’s simplicity makes it popular with integrators. However, a corporate campus that uses a mix of AV over IP systems (e.g., video with SDVoE or NDI) might prefer AES67 to maintain a single network policy. RAVENNA is a good example of AES67 in installed audio.

Final Thoughts

Neither AES67 nor Dante is inherently superior; they serve different purposes. AES67 is the interoperability bedrock that permits cross‑vendor communication, while Dante is an optimized, full‑featured ecosystem that simplifies deployment and management. The best approach is to assess your project’s scale, required latency, existing equipment, and staff expertise. In many cases, a hybrid solution leveraging AES67 for bridging and Dante for local high‑performance zones offers the best of both worlds.

For further reading, the AES Standards page provides the full AES67 document, and Audinate’s Dante overview covers the latest features. A whitepaper from Rane (now part of Synthax) offers an excellent technical comparison of audio‑over‑IP protocols.

By carefully weighing these factors, you can build an audio infrastructure that is reliable, scalable, and ready for the future—whether you choose AES67, Dante, or a combination of both.