Understanding AES67 and Its Role in Modern Audio Networking

AES67 is an interoperability standard developed by the Audio Engineering Society that enables high-performance audio-over-IP (AoIP) communication across devices from different manufacturers. Unlike proprietary protocols such as Dante, CobraNet, or AVB, AES67 defines a common set of transport, synchronization, and discovery mechanisms, ensuring that gear from various vendors can exchange live, low-latency audio streams over standard Ethernet networks. The standard is based on existing technologies: RTP (Real-time Transport Protocol) using uncompressed linear PCM audio, IEEE 1588-2008 Precision Time Protocol (PTPv2) for tight synchronization, and SIP/SDP or mDNS/SDP for session discovery and connection management.

AES67 supports audio sample rates of 44.1 kHz, 48 kHz, and 96 kHz, with bit depths of 16, 24, or 32 bits over IP multicast or unicast. It mandates maximum packetization intervals of 1 ms, 0.125 ms, or 0.25 ms, enabling end-to-end latencies as low as a few milliseconds — critical for live sound, broadcast, and intercom applications. Understanding these technical parameters is essential when planning an upgrade from an outdated analog or proprietary digital system.

Why Upgrade Legacy Audio Systems to AES67

Legacy audio systems often rely on analog snakes, proprietary digital busses (e.g., ADAT, MADI, or manufacturer-specific protocols), or early AoIP systems that are not interoperable with modern networked solutions. Upgrading to AES67 unlocks several benefits:

  • Interoperability: Mix and match AES67-compliant equipment from brands such as Audinate, Yamaha, Focusrite, RØDE, and Shure without compatibility headaches.
  • Scalability: Add or reconfigure channels over a single CAT6 cable instead of pulling multiple analog or coaxial lines.
  • Lower Total Cost of Ownership: Standardized networking gear (managed switches, fiber uplinks) replaces costly proprietary hardware.
  • Future-Proofing: AES67 is the foundation for newer interoperable layers like SMPTE ST 2110 for broadcast and the AES70 device control standard.

Assessing Your Legacy System Readiness

Before touching any equipment, conduct a thorough audit of your current audio infrastructure. Document everything: mixer models, installed DSPs, termination panels, existing network switches, and cable runs. Key questions to answer:

Can Your Existing Hardware Support AES67 via Firmware?

Some modern consoles and digital processors with AoIP ports already support AES67 or can be upgraded with a factory firmware update. For example, certain Yamaha CL/QL series consoles, Allen & Heath dLive systems, and Focusrite RedNet interfaces offer AES67 as a switchable mode. Check manufacturer release notes or ask their support team.

What is the State of Your Network Infrastructure?

AES67 runs on standard Gigabit Ethernet, but quality matters. You need managed switches with the ability to configure IGMP snooping for multicast filtering, and QoS/DSCP prioritization to keep audio packets ahead of data traffic. Unmanaged switches may cause packet drops, increased latency, or clock instability. The network should also support PTPv2 transparent clocks or boundary clocks for accurate synchronization — especially when mixing VLANs or crossing subnets.

Identify Conversion Needs

If your legacy gear lacks any AoIP port, you will need analog-to-AES67 converters or MADI-to-AES67 bridges. For instance, the Digigram ALP50 provides analog I/O with native AES67 support. Similarly, DirectOut devices can convert MADI streams to AES67. Budget for these adapters if your legacy interfaces are not replaceable.

Step-by-Step Upgrade Plan

A structured approach minimizes downtime and post-upgrade troubleshooting.

1. Update or Replace Control Firmware

Begin by loading the latest firmware on all devices that could potentially gain AES67 functionality. Many professional audio manufacturers have released free updates to enable AES67 on hardware that previously only supported Dante or Ravenna. Reboot and verify the new features in the device’s web interface or configuration tool.

2. Add or Upgrade Network Interface Modules (NIMs)

For mixing consoles and outboard gear with modular I/O slots (e.g., Yamaha NY64-D, Allen & Heath DX168), install a network interface card that explicitly supports AES67. Some cards are multi-protocol — such as the Audinate Dante AVIO AES67 adapter — which can switch between Dante and AES67 mode. Insert the card, connect to the network, and assign a static IP or use DHCP.

3. Overhaul Your Network Switches

If your current switches are consumer-grade or unmanaged, replace them with managed Gigabit switches that offer at least the following:

  • IGMP snooping (v2 and v3) to manage multicast traffic
  • PTPv2 hardware timestamping (transparent clock) for sub-μs synchronization
  • QoS with four priority queues and strict scheduling
  • VLAN support to separate audio control and streaming traffic
  • RSTP or faster redundancy protocols

This practical AES67 networking guide provides detailed switch configuration examples.

4. Configure Synchronization with PTPv2

Precision Time Protocol is the backbone of AES67’s low-latency operation. Designate one device as the grandmaster clock (usually a console or dedicated PTP clock like OreTech PTP Grandmaster). All other devices — converters, DSPs, recorders — lock to the grandmaster. On managed switches, enable PTP snooping or transparent clock mode if supported. Verify sync accuracy using a PTP monitor (e.g., ptpmonitor).

5. Set Up Discovery and Stream Connections

AES67 does not mandate a single discovery protocol; most implementations use either SAP (standard AES67) or mDNS with SDP. For practical connection, you may need manufacturer software such as Audinate Dante Controller (when in AES67 mode) or Ravenna’s Proprietary Control Panel. Ensure multicast groups are configured correctly and that IGMP snooping prevents traffic from flooding non-required ports.

6. Test Interoperability and Latency

Use free tools like AES67 Monitor to verify packet arrival times and jitter. Perform a “loopback” test: route an AES67 stream from the legacy converter back into itself through the network monitor output. Measure round-trip latency using an oscilloscope or software meter. Acceptable latency for live reinforcement is under 5 ms; for recording or post-production, up to 10 ms may be tolerable.

Overcoming Common Upgrade Challenges

Clock Domain Mismatch

If your legacy system uses word clock (BNC) and your new AES67 network uses PTP, you must inject a PTP-to-word clock converter (e.g., Ferrofish PTP Clock Converter) or use a hybrid device that samples both domains. Without proper bridging, analog outputs may drift relative to the AoIP streams.

Bandwidth Over-Runs

Uncompressed AES3 audio at 48 kHz / 24-bit uses roughly 3 Mbps per channel. A 64×64 system consumes approximately 200 Mbps. Ensure your network backbone is at least 1 Gbps and that multicast groups are not saturating any port. Use link aggregation (LACP) for trunked connections to switch stacks.

Firewall and VLAN Traversal

When audio must cross VLANs or subnets, configure multicast routing (PIM) or use RTP unicast instead of multicast. Many AES67 implementations support unicast fallback. If you restrict streaming traffic with firewalls, open UDP ports 5004 (RTP audio) and 5005 (RTCP), as well as the PTP port 319 (event) and 320 (general).

Best Practices for a Seamless Transition

  • Perform a dry run: Set up a small isolated test network with one legacy converter and one new AES67 node before going live.
  • Document everything: Map all IP addresses, multicast groups, PTP priorities, and QoS markings. Keep this as a living document.
  • Implement gradual migration: Phase out legacy analog snakes by replacing them floor by floor (or room by room) during off-hours.
  • Train operators: Ensure audio engineers understand how to set sample rates, latency, and PTP status using the device’s web GUI or controller app.
  • Set up redundancy: For critical broadcast or live events, use dual-network paths (primary/secondary) with redundancy protocols (e.g., PRP or HSR) if possible, or at least configure active/standby PTP grandmasters.

Looking Beyond AES67: The Road to ST 2110 and AES70

AES67 is not the final destination; it is the universal transport layer for professional AoIP. Much of the same hardware and network infrastructure you upgrade today can later support SMPTE ST 2110 (video, audio, and ancillary data over IP for broadcast) and AES70 (device monitoring and control over IP). When you choose converters and switches that comply with AES67 and ST 2110-30, you future-proof your facility for IP-based broadcast and production environments. Similarly, investing in Dante or Ravenna gear that includes a native AES67 mode gives you flexibility to integrate with future equipment that only speaks AES67.

Conclusion

Upgrading legacy audio systems to support AES67 protocols is a structured but rewarding process. By thoroughly assessing your current infrastructure, methodically updating firmware and hardware, configuring PTP and QoS, and testing systematically, you can achieve a network that is interoperable, scalable, and ready for tomorrow’s media workflows. Engage with manufacturer guides, AES standards documents, and community forums to stay informed as the standard evolves. With careful planning, your upgrade to AES67 will elevate your facility’s capabilities and reduce long-term operational costs.