The Case for AES67: Why Independent Audio Manufacturers Must Embrace Open Standards

The professional audio industry is in the midst of a historic transition. Analog signal chains are giving way to digital networked systems, and the way audio equipment is designed, deployed, and integrated has shifted fundamentally. For independent equipment manufacturers, this change brings both serious challenges and rare opportunities. The central question is no longer whether to adopt networked audio, but how to do so in a way that maximizes compatibility, minimizes cost, and preserves long-term flexibility.

Open standards have become the bedrock of this new environment. Among them, AES67 stands out as the essential standard for audio-over-IP interoperability. For independent manufacturers, understanding and adopting AES67 is not just a technical decision. It is a strategic business move that directly influences market relevance, product development speed, and competitive positioning. This article examines what AES67 offers, how it works, and why independent manufacturers should prioritize it in their product roadmaps.

Understanding AES67: The Interoperability Backbone

AES67 is an open, international standard for transporting high-quality audio over IP networks. Developed by the Audio Engineering Society and formally published as AES67-2015, the standard specifies the protocols, sampling rates, and timing mechanisms required to ensure interoperability between different audio-over-IP systems. It operates over standard Ethernet networks, including both managed and unmanaged switches, making it accessible for a wide range of applications.

The standard defines a common set of parameters that any compliant device must support. These include sampling rates of 44.1 kHz and 48 kHz, bit depths of 16, 20, and 24 bits, and packet transmission intervals of 1 ms and 125 microseconds. AES67 also specifies the use of RTP (Real-Time Transport Protocol) for audio data transport, RTCP (RTP Control Protocol) for timing and synchronization, and IEEE 1588-2008 (Precision Time Protocol) for clock synchronization across the network.

Notably, AES67 does not prescribe a specific control protocol or discovery mechanism. Instead, it focuses on the transport layer, allowing higher-level protocols such as RAVENNA, Dante, and SMPTE ST 2110-30 to build upon it. This layered approach is what makes AES67 a true interoperability standard: it provides the common ground that different ecosystems can share.

The standard has seen broad adoption across the pro audio, broadcast, and installed sound markets. The Audio Engineering Society continues to maintain and update the standard, ensuring it remains relevant as technology evolves.

How AES67 Solves the Interoperability Problem

The fundamental challenge in networked audio is that different manufacturers have historically developed proprietary solutions to manage timing, synchronization, and data transport. While these proprietary systems often perform well within their own ecosystems, they create barriers when equipment from different vendors needs to work together. AES67 solves this problem by establishing a common language for audio transport.

When a device is AES67-compliant, it can send and receive audio streams to and from any other AES67-compliant device on the network, regardless of the manufacturer. This is achieved through several key technical mechanisms:

  • Common clock synchronization using IEEE 1588 PTP ensures that all devices on the network share the same time base, eliminating clock drift and ensuring sample-accurate alignment.
  • Standardized packet formats using RTP mean that audio data is structured identically across different devices, so no protocol translation is required.
  • Defined session description via SDP (Session Description Protocol) allows devices to advertise their capabilities and discover compatible streams.
  • Fixed latency profiles ensure that timing behavior is predictable and consistent across different implementations.

This interoperability is not theoretical. It has been demonstrated repeatedly in plugfest events organized by the AES and the Media Networking Alliance, where dozens of devices from different manufacturers successfully exchange audio streams in real time.

Strategic Advantages for Independent Manufacturers

Reduced Development Costs and Faster Time to Market

Developing a proprietary networked audio protocol from scratch requires substantial investment in engineering, testing, and certification. For independent manufacturers with limited R&D budgets, this can be prohibitively expensive. AES67 eliminates the need for this investment by providing a ready-made, tested, and widely accepted transport layer.

Instead of spending months or years developing low-level networking code, engineers can focus on implementing the AES67 standard using existing SDKs, reference implementations, and hardware modules from multiple suppliers. Many silicon vendors now offer AES67-compatible networking chips and modules, further reducing development effort. The result is faster time to market with lower upfront costs, allowing independent manufacturers to compete more effectively against larger players.

Expanded Market Reach Through Interoperability

When a manufacturer adopts AES67, their products become compatible with a vast ecosystem of existing AES67-compatible equipment. This instantly expands the potential customer base. A sound reinforcement system from one vendor can integrate with a mixing console from another. A broadcast codec can work with a studio monitor system from a third manufacturer. This kind of flexibility is highly valued by system integrators, consultants, and end users who prefer best-of-breed solutions over single-vendor lock-in.

For independent manufacturers, this means their products can be specified in projects where interoperability requirements are mandatory, such as government contracts, large-scale installations, and broadcast facilities. Being AES67-compliant can be the difference between being considered for a project and being excluded from the bid list entirely.

Future-Proofing Product Investments

Open standards evolve through public, collaborative processes that involve input from a broad range of stakeholders. This ensures that the standard adapts to new technologies and market requirements over time. When a manufacturer builds their product around AES67, they are not tied to the roadmap of a single vendor or the fate of a proprietary protocol. Instead, they benefit from ongoing improvements, bug fixes, and feature enhancements contributed by the entire industry.

This is especially important for independent manufacturers who may not have the resources to continuously update their proprietary protocols. With AES67, the standard updates are managed by the AES and the broader community, reducing the maintenance burden on individual companies.

Enhanced Innovation Focus

When development resources are not consumed by building and maintaining a proprietary networking stack, engineers can focus on what truly differentiates their products: audio quality, user interface, feature set, reliability, and price-performance ratio. This shift in focus allows independent manufacturers to innovate in areas that directly benefit their customers rather than reinventing networking infrastructure that already exists.

For example, a manufacturer specializing in microphone preamplifiers can concentrate on reducing noise, increasing gain range, and adding digital processing features, knowing that the networking layer is handled by a proven, interoperable standard. This specialization leads to better products and stronger competitive positions.

Access to Larger Projects and Enterprise Customers

Many large-scale audio projects, particularly in broadcast, live sound, and corporate AV, require interoperability between equipment from multiple vendors. Project specifications often mandate compliance with open standards like AES67 to ensure flexibility and avoid vendor lock-in. Independent manufacturers who support AES67 can participate in these larger projects, gaining access to revenue opportunities that would otherwise be out of reach.

AES67 Compared to Other Audio Networking Standards

AES67 vs. Dante

Dante, developed by Audinate, is one of the most widely adopted audio-over-IP protocols in the pro audio industry. It is a complete ecosystem that includes transport, control, and discovery. While Dante is proprietary, Audinate offers a licensing program for manufacturers. However, Dante devices can also support AES67, and many modern Dante-enabled products include AES67 compatibility. This allows manufacturers who adopt AES67 to interoperate with the large installed base of Dante equipment.

For independent manufacturers, the key difference is cost and control. Dante requires licensing fees and approval from Audinate, while AES67 is royalty-free and does not require permission from any single entity. Manufacturers who want maximum flexibility and minimal ongoing costs often prefer AES67 as their primary transport standard.

AES67 vs. RAVENNA

RAVENNA is another open standard for audio-over-IP, developed by ALC NetworX. It shares many technical foundations with AES67 and is actually a superset of the AES67 standard. RAVENNA includes additional features for redundant networks, higher channel counts, and advanced timing. RAVENNA devices are typically AES67-compatible, and the two standards are closely aligned. For manufacturers, choosing RAVENNA can provide additional capabilities while maintaining AES67 interoperability.

AES67 vs. AVB/TSN

Audio Video Bridging (AVB) and Time-Sensitive Networking (TSN) are IEEE standards for low-latency, time-synchronized networking. While AVB/TSN offers guaranteed bandwidth and precise timing, it requires specialized network switches and endpoint hardware. AES67, by contrast, works on standard Ethernet networks, making it more accessible and less expensive to implement. For independent manufacturers, AES67 typically represents a lower barrier to entry.

Implementation Considerations for Independent Manufacturers

Adopting AES67 is not without its challenges. Independent manufacturers should consider several factors before integrating the standard into their products.

Hardware Requirements

AES67 requires network interfaces that support PTP timestamping and can handle the real-time demands of audio streaming. While many modern Ethernet controllers include these capabilities, older or low-cost hardware may not be suitable. Manufacturers may need to select specific silicon or use dedicated networking modules to achieve reliable AES67 performance.

Latency and Performance Tuning

While AES67 defines standard latency profiles, achieving consistent low-latency performance requires careful implementation. Buffer sizes, interrupt handling, and driver optimization all affect latency and jitter. Independent manufacturers should budget sufficient engineering time for performance tuning and testing.

Testing and Certification

To claim AES67 compliance, manufacturers should test their products for interoperability with other AES67 devices. The AES and the Media Networking Alliance offer plugfest events where manufacturers can test their implementations in a collaborative environment. While formal certification is not mandatory, it adds credibility and reduces the risk of compatibility issues in the field.

Consumer and Pro Audio Market Differences

AES67 is primarily designed for professional audio applications where low latency, high channel counts, and deterministic performance are critical. For consumer audio applications, the requirements are different, and AES67 may not be the optimal choice. Independent manufacturers should align their standard selection with their target market.

Real-World Applications and Use Cases

AES67 has been adopted across a wide range of audio applications. In broadcast facilities, it enables seamless integration between mixing consoles, codecs, intercom systems, and monitoring equipment from different vendors. In live sound, AES67 allows digital mixing consoles to share audio streams with stage boxes, amplifiers, and recording systems over a single network cable. In installed sound, corporate AV systems and houses of worship use AES67 to connect microphones, processors, amplifiers, and loudspeakers from multiple manufacturers in a unified, manageable system.

For independent manufacturers, these use cases demonstrate the practical value of AES67 compliance. A manufacturer of powered loudspeakers, for example, can integrate AES67 support to allow their products to be used in any of these environments without requiring a proprietary ecosystem. This flexibility makes their products more attractive to system designers and integrators.

The Future of Open Standards in Audio

The momentum behind open standards like AES67 continues to grow. The Audio Engineering Society's standards committee actively maintains and evolves the standard, and the Media Networking Alliance promotes broader adoption through education and interoperability testing. As the industry moves toward IP-based infrastructure across all segments, the importance of open standards will only increase.

For independent manufacturers, the choice is becoming clear. Building products on proprietary networking protocols limits market access, increases development costs, and creates long-term maintenance burdens. Adopting open standards like AES67 provides a path to broader compatibility, lower costs, and greater strategic flexibility.

Several trends are reinforcing this direction. The broadcast industry's transition to IP-based production, driven by standards like SMPTE ST 2110, relies on AES67 as the audio transport layer. The pro AV market is increasingly specifying open standards in project requirements. And end users, particularly in enterprise and education markets, are demanding solutions that avoid vendor lock-in.

Strategic Recommendations for Independent Manufacturers

For independent equipment manufacturers evaluating AES67 adoption, a practical approach includes several steps. First, assess your target market's requirements. If your products will be used in environments where interoperability with other brands is required, AES67 support should be a priority. Second, evaluate the engineering investment required. Reference implementations and hardware modules can significantly reduce development time. Third, participate in industry interoperability events to validate your implementation and build relationships with other manufacturers. Fourth, communicate your AES67 support clearly in your product documentation and marketing materials, as this feature is increasingly becoming a purchasing criterion.

The AES67 standard document provides the complete technical specification and is the definitive reference for implementers. Additionally, resources from the Media Networking Alliance offer practical guidance and implementation support.

Conclusion

Independent audio equipment manufacturers operate in a competitive landscape where differentiation matters, but so does compatibility. Open standards like AES67 offer a practical and strategic solution to the tension between innovation and interoperability. By adopting AES67, manufacturers can reduce development costs, expand market reach, future-proof their products, and focus engineering resources on features that truly distinguish their offerings.

The professional audio industry's transition to networked, IP-based infrastructure is irreversible. Manufacturers who embrace open standards position themselves for growth in this new environment. Those who rely solely on proprietary protocols risk being marginalized as interoperability becomes a baseline requirement rather than a competitive advantage. For independent manufacturers with limited resources and ambitious goals, AES67 is not just a technical standard—it is a strategic tool for competing effectively in a networked world.