Why Standardization Is the Foundation of Modern Network Audio

Network audio has transformed professional sound systems. A single Cat6 cable now carries hundreds of channels of high‑resolution audio, control data, and metadata across concert venues, broadcast studios, and corporate installations. But this capability depends entirely on devices from different manufacturers speaking a common language. Without agreed‑upon standards, a mixing console, stagebox, and DSP from three different brands cannot reliably exchange audio—they become isolated components rather than a unified system.

This article explains why standardization is not merely a technical convenience but a strategic imperative. We examine the core benefits, the leading standards, the obstacles that remain, and the direction the industry is heading. Understanding these forces helps integrators, engineers, and facility owners make informed purchasing and design decisions that protect their investments for years to come.

What Standardization Means in Network Audio

Standardization refers to the widespread adoption of technical specifications that define how audio devices discover each other, synchronise clocks, transport packets, and handle error conditions. These specifications cover physical cabling (Cat5e, Cat6, fiber), network protocols (TCP/IP, UDP, PTP), audio formats (PCM, compressed codecs), and control interfaces. A standard can be an open document (like AES67) or a broadly licensed proprietary protocol (like Dante). In either case, multiple vendors implement the same specification, enabling interoperability without custom gateways or vendor lock‑in.

The scope of standardization extends beyond audio transport. It includes zero‑configuration networking for automatic discovery, IEEE 1588 Precision Time Protocol for sample‑accurate synchronisation, and common control protocols such as AES70 (OCA) for remote management. When all devices adhere to these standards, a technician can connect equipment from any compliant manufacturer and expect it to work, reducing commissioning time and operational complexity.

Key Benefits of Standardized Network Audio

True Interoperability Across Brands

Interoperability is the most immediate gain. With standard‑compliant gear, a RAVENNA‑enabled microphone preamp can stream directly to an AES67‑compatible console without format converters or sample‑rate mismatches. This flexibility allows integrators to select best‑in‑class components from different manufacturers, fostering competition and driving down costs. In broadcast facilities where studios must integrate equipment from multiple regions and vendors, interoperability is a non‑negotiable requirement.

Lower Total Cost of Ownership

Standards reduce costs throughout the ecosystem. Manufacturers reuse common chipsets and software stacks, lowering R&D expenses; these savings often pass to customers. Integrators avoid expensive media converters and custom programming. End‑users benefit from simplified maintenance and the ability to upgrade individual components without replacing entire systems. A facility built on open standards typically has a lower lifetime cost than one locked into a single proprietary ecosystem.

Simplified Installation and Configuration

Setting up a network audio system involves managing clock domains, PTP profiles, jitter buffers, and multicast addresses. Standards provide clear guidelines that simplify these tasks. For example, most standard‑based devices support zero‑configuration networking (ZeroConf) for automatic discovery and IP address assignment. Common control protocols like AES70 allow a single software application to manage gain, routing, and filtering across devices from different brands. This reduces the likelihood of misconfiguration and shortens commissioning time.

Future‑Proofing and Scalability

Standards evolve through the work of organizations such as the Audio Engineering Society (AES), the IEEE, and the Avnu Alliance. They continuously update specifications to support higher sample rates, lower latency, larger channel counts, and emerging use cases like immersive audio and remote production. By choosing standard‑compliant equipment, operators can incrementally scale their systems—adding endpoints, increasing bandwidth, or integrating with cloud workflows—without a complete overhaul. This longevity protects capital investment and allows facilities to grow with changing demands.

Major Standards and Protocols in Detail

Several standards dominate professional audio networking. While each has a distinct history and technical approach, they share the goal of enabling high‑performance audio over IP. Understanding their differences is essential for system design.

AES67 – The Interoperability Bridge

AES67 is an open standard from the Audio Engineering Society that defines a common mode for audio‑over‑IP. It is not a full protocol stack but a set of requirements—RTP transport, PTP timing (IEEE 1588‑2008 profile), media clock, and a minimum support of 48 kHz / 16‑bit stereo—that any AoIP system must meet to interwork with others. Because vendors like Audinate (Dante), ALC NetworX (RAVENNA), and Wheatstone (LiveWire) include AES67 interoperability modes, this standard has become the cornerstone of multi‑vendor networking. For example, a Dante‑to‑AES67 gateway allows a Dante‑based console to receive streams from a RAVENNA‑based microphone array, enabling hybrid systems without dedicated converters.

Dante – The De‑Facto Industry Standard

Developed by Audinate, Dante is a proprietary technology that has achieved near‑universal adoption in pro AV. Its plug‑and‑play simplicity, automatic discovery, and intuitive software controller made it a favorite among systems integrators. Dante supports up to 512×512 channels at 48 kHz over Gigabit Ethernet, with latencies as low as 150 microseconds. Thousands of products from hundreds of manufacturers carry the Dante logo. While proprietary, Audinate publicly specifies the AES67 interoperability profile, ensuring Dante devices can participate in open‑standard networks. For many users, Dante offers the best balance of ease‑of‑use, mature ecosystem, and performance.

AVB / TSN – Deterministic Performance

IEEE 802.1 Audio Video Bridging (AVB) is a set of standards for stream synchronisation, bandwidth reservation, and traffic shaping over Ethernet. It is now part of the broader Time‑Sensitive Networking (TSN) family. AVB/TSN guarantees low and bounded latency by reserving bandwidth and using precise clock synchronisation (IEEE 802.1AS). The Avnu Alliance promotes interoperability between certified devices. AVB is popular in automotive, professional audio (Biamp, Q‑SC), and industrial applications. Its deterministic performance is an advantage, but it requires network switches that support AVB—an added cost not always necessary for Dante or AES67 setups.

RAVENNA – Open and Broadcast‑Ready

RAVENNA is an open, royalty‑free standard for real‑time professional audio over IP, developed by ALC NetworX. It runs on standard IP and Ethernet, requiring no special network infrastructure. RAVENNA is fully AES67‑compliant and adds optional features for redundancy, higher channel counts, and advanced media clock recovery. It is widely used in broadcast and classical music venues where deterministic performance and multi‑channel reliability are critical. Manufacturers such as Neumann, Lake, and Merging Technologies rely on RAVENNA.

Other Important Standards

  • SMPTE ST 2110 – The broadcast industry’s standard for professional media over IP, covering video, audio, and ancillary data. It uses AES67 for audio and is now the default for new IP‑based broadcast plants.
  • AES70 (OCA) – A standard for control and monitoring of professional audio devices over IP. Often used alongside AES67 to manage gain, routing, and filtering.
  • Milan – A user‑experience profile built on AVB/TSN that promises plug‑and‑play interoperability across all Milan‑certified devices. Designed by the Avnu Alliance for the pro‑AV market.
  • LiveWire – Wheatstone’s proprietary protocol, which now includes AES67 interoperability for integration with other standard systems.

Challenges to Widespread Standardization

Despite the advantages, full standardization faces several hurdles that can fragment the market and create compatibility islands.

Proprietary Protocols and Vendor Lock‑in

Some manufacturers develop closed protocols to differentiate their products and build customer loyalty. While these systems often perform well within a single brand, they make it expensive or impossible to integrate third‑party devices. Users become locked into a particular ecosystem over time. The industry response has been interoperability modes (e.g., Dante’s AES67 support), but these may offer reduced functionality—higher latency or lower channel counts—compared to native operation. This creates a tiered compatibility landscape.

Rapid Technological Evolution

New audio formats (immersive 3D, spatial audio, high‑resolution multichannel), higher sample rates (96 kHz, 192 kHz, DSD), and new networking paradigms (cloud, edge computing, IPMX) demand constant standard revision. Developing, testing, and certifying new versions takes time and resources. Manufacturers may hesitate to invest in new standards until market demand is clear, leading to a lag where proprietary extensions appear before the standard catches up.

Latency and Timing Requirements

Different applications have wildly different latency tolerances. A live concert monitor engineer needs round‑trip latency under 1 ms to avoid distracting echoes; a broadcast news studio can tolerate 5–10 ms; a recording studio may prioritise sample‑accurate phase coherence over absolute latency. Satisfying all within a single standard is challenging. AES67 allows devices to negotiate latency settings (e.g., 1 ms, 2 ms, 5 ms), but not all devices implement every option, leading to incompatibility even among AES67‑compliant products if their supported latencies do not overlap.

Network Infrastructure Complexity

Audio over IP works best on a well‑managed network. Small deployments may run on standard switches, but larger systems require managed switches with IGMP snooping, QoS, VLANs, and PTP‑aware hardware. If the network does not support the required profiles, even standard‑compliant devices may fail to synchronise or may drop packets. Standards help by publishing clear network requirements—for example, AES67‑2021 Annex A provides recommended switch configurations—but the installer must still implement them correctly. Inexperienced integrators sometimes overlook the network prerequisites, leading to performance issues.

Real‑World Impact: Case Studies

Broadcast Facility Modernization

A major European broadcaster upgraded from SDI‑based routing to an all‑IP infrastructure using SMPTE ST 2110 with AES67 audio. By choosing equipment from multiple vendors—Dante‑based microphones, RAVENNA‑compatible mixing desks, and an ST 2110 core from a third manufacturer—they avoided any single‑vendor lock‑in. The standard allowed them to expand the facility over several years, adding new studios and remote contribution links without breaking the existing network. The broadcaster reported a 40% reduction in cabling costs and improved flexibility for live event coverage.

Large‑Scale Touring Production

A touring sound company deployed a combined Dante and AES67 system for a world tour. The front‑of‑house console used Dante, while the monitor desk and wireless intercom system used RAVENNA. By enabling AES67 interoperability mode on both networks, they could share a single stagebox feeding both consoles. The standard ensured sample‑locking, so the monitor engineer could mix the same inputs as the FOH desk without additional hardware. This configuration saved the company over $15,000 in dedicated format converters and reduced setup time by two hours per show.

Choosing Standard‑Compliant Equipment: Practical Guidance

When specifying network audio gear, look for products that clearly list their compliance with industry standards. Check for AES67 certification, Dante certification, or Avnu Alliance certification (for AVB/TSN). Verify that the product supports the required PTP profile (IEEE 1588‑2008 for AES67) and the desired latency setting. If integrating devices from different ecosystems, confirm that AES67 interoperability mode is available and that the supported sample rates and channel counts overlap. Many manufacturers provide interoperability matrices on their websites.

Infrastructure is equally important. Use managed switches that support IGMP snooping, QoS (DSCP mapping), and PTP transparency. If using AVB, ensure the switch is AVB‑capable (IEEE 802.1Qat/802.1Qav). For cloud‑based workflows, require standards that support secure streaming over the public internet (e.g., SRT, RTMP, or future IPMX extensions).

The Future of Network Audio Standardization

Several trends are pushing standardization further. The adoption of IPMX (IP Media Experience), an open standard from the Alliance for IP Media Solutions (AIMS), promises to unify pro‑AV workflows with broadcast‑grade performance, bridging the gap between the two industries. The growing integration of audio, video, and control in a single network will require tighter alignment between AES67, ST 2110, and AES70. Cloud‑based audio processing—where local microphones feed a remote mixing engine—demands standards for secure, low‑latency streaming over the public internet, something current local‑network standards do not fully address.

Another significant development is the increasing use of virtualised and software‑defined audio routing. Open standards allow different software applications to create virtual patchbays, and they pave the way for “agnostic” network management tools that can discover and control any standard‑compliant device. The industry is moving toward a model where network audio is as easy as patching a cable—with greater flexibility, scalability, and reliability. Standardization is the engine driving that future, and every stakeholder benefits from its continued evolution.

Conclusion

Standardization in network audio is not a luxury—it is a necessity. It enables interoperability, reduces costs, simplifies integration, and protects investments over time. From AES67 and Dante to AVB/TSN and RAVENNA, each standard plays a role in building cohesive, scalable audio systems. While challenges like proprietary lock‑in and network complexity remain, the trajectory is clear: open, widely adopted standards will continue to expand, making network audio more accessible and powerful. For anyone designing or operating professional sound systems, committing to standards is the surest path to long‑term success.