Introduction

The shift from traditional analog audio systems to digital audio-over-IP (AoIP) networks has become one of the most significant technological advancements in professional audio. Among the key standards driving this transition is AES67, which provides a robust framework for interconnecting digital audio devices over standard IP networks. While the benefits of AES67—such as superior audio quality, flexible routing, and scalability—are clear, moving from a trusted analog setup to a digital network can seem daunting. However, with a structured, step-by-step approach, organizations can execute a smooth migration that minimizes downtime, ensures compatibility, and unlocks the full potential of modern audio networking.

Understanding AES67 and Its Benefits

AES67 is a standard developed by the Audio Engineering Society (AES) for high-performance audio-over-IP streaming. It defines how to transport uncompressed, high-resolution audio over a local area network (LAN) using the Internet Protocol (IP) suite. At its core, AES67 uses Real-time Transport Protocol (RTP) for streaming and Precision Time Protocol (PTPv2, IEEE 1588-2008) for synchronization, enabling sub-millisecond latency and sample-accurate alignment across multiple devices. Importantly, AES67 is an interoperability standard—it does not replace proprietary discovery or control protocols but ensures that devices from different manufacturers (e.g., Dante, Ravenna, AVB, Q-LAN) can exchange audio streams seamlessly when properly configured.

Key benefits include:

  • High audio quality with low latency: AES67 supports up to 64 channels per stream at 48 kHz, 24-bit resolution with latency as low as 0.125 ms (1 frame). This rivals or exceeds typical analog performance while adding digital clarity and noise immunity.
  • Flexible routing and system expansion: Analog patch bays are replaced with software-based routing. Adding a new input or output often requires only a network cable and a configuration change, not a complete rewire.
  • Reduced cabling and physical space: A single Cat6 cable can carry hundreds of audio channels, eliminating bulky multi-pair snakes and reducing rack space for interface boxes.
  • Future-proof technology compatibility: AES67 is vendor-neutral and widely adopted. Systems built around it can integrate with newer devices for years to come.
  • Centralized monitoring and control: Digital networks allow real-time status checking, remote troubleshooting, and automated signal routing—capabilities impossible in analog domain.

Preparing for the Transition

Thorough preparation is the cornerstone of a successful migration. Rushing into a conversion without understanding your current infrastructure, network capabilities, and team readiness leads to costly mistakes and operational disruptions.

Assess Your Current Analog Infrastructure

Begin by inventorying every piece of analog equipment: mixing consoles, microphone preamps, speaker processors, distribution amplifiers, snake systems, and patch bays. Document signal flow, cable types (XLR, TRS, DB25), and physical locations. Identify which devices are candidates for replacement (e.g., aging consoles with no digital output) versus those that can be digitized with adapters (e.g., an analog interface with AES3 output that can be converted to AES67). Pay special attention to critical paths—main front-of-house, studio monitors, intercoms—that cannot tolerate downtime.

Evaluate Network Readiness

Analog audio does not care about switches, jitter, or packet loss. AES67 does. Your existing IT network must support three critical features:

  • IGMP snooping: Required for multicast traffic management. Without it, AES67 streams flood all ports, overwhelming switches.
  • Quality of Service (QoS): Audio traffic must be prioritized over best-effort data. Configure DSCP (Differentiated Services Code Point) values—typically EF (46) for audio and CS7 (56) for PTP traffic.
  • PTP-aware switching: Switches must support IEEE 1588 boundary or transparent clock functions, or at minimum have low latency and jitter.
  • Sufficient bandwidth: A single AES67 stereo stream at 48 kHz/24-bit consumes about 6 Mbps. Plan for peak simultaneous stream counts, plus overhead for control protocols.

If your existing network infrastructure lacks these capabilities, you may need to purchase new managed switches or segment audio onto a dedicated VLAN. Many organizations choose to build a separate audio network to avoid contention with IT traffic. Audinate’s network design guide provides detailed recommendations applicable to AES67 systems as well.

Check Device Compatibility

Not all “AES67-compatible” devices are plug-and-play out of the box. Verify that existing and new equipment supports the required sampling rates (48 kHz is most common), PTP profile, and RTP payload types (L24). Legacy gear may need firmware updates or external interface cards. For example, many current Dante-enabled devices can receive or send AES67 streams by enabling the AES67 mode in their configuration. Similarly, Ravenna and AVB devices often have AES67 interoperability modes. Check manufacturers’ documentation and compatibility matrices. The official AES67 standard (AES67-2018) details all requirements and profiles.

Develop a Transition Timeline

Do not attempt a “big bang” cutover. Instead, adopt a phased approach:

  • Phase 1 – Lab testing: Set up a small test network with two or three AES67 devices to validate device configuration, latency, and stability.
  • Phase 2 – Pilot in non-critical areas: Migrate a less essential zone (e.g., a recording room, overflow conference area) to AES67. Run it parallel to analog for a week.
  • Phase 3 – Gradual production migration: Move core systems one by one, scheduling changes during low-activity periods. Maintain analog fallback possibilities where practical.
  • Phase 4 – Full transition and decommissioning: Once all AES67 paths are stable, remove analog patch bays, snakes, and retired gear.

Throughout each phase, document every configuration change and performance metric (latency, jitter, packet loss). This data will inform later stages.

Budget Considerations

Beyond new audio equipment, budget for:

  • Managed network switches with QoS and PTP capabilities
  • Category-6a or fiber cabling
  • PTP grandmaster clocks (if not integrated into a device)
  • Analog-to-AES67 interface boxes (e.g., units from Klark Teknik, Ferrofish, or Digigram)
  • Training sessions for engineering and operations staff
  • Network analysis tools (e.g., dedicated AoIP analyzers or software like Wireshark with AES67 dissector)

Implementing the Transition

With a solid plan in place, execution must be methodical. The goal is to have a working digital network that matches or exceeds the reliability of your analog setup.

Network Configuration and QoS

Configure switches for audio isolation and performance. Start by creating a dedicated VLAN for AES67 traffic. This separates control and audio from office data, reducing the likelihood of collisions. On each switch port, enable IGMP snooping and querying. Set the QoS policy to map audio traffic to the highest priority queue. The recommended DSCP value for AES67 audio is 46 (EF). PTP event messages should be marked CS7 (56). On many switches, you can also set per-port rate limiting to protect against broadcast storms. Cisco’s switched audio network design guide offers excellent examples of QoS configuration applicable to AES67.

Synchronization and Clocking

AES67 relies on PTPv2 for sample-accurate synchronization. You must have one device acting as the PTP grandmaster. It can be a dedicated clock (like a GPS-disciplined oscillator) or a network switch configured as a boundary clock. All other devices become PTP slaves. Set a consistent domain number (default 0 for AES67) and ensure all devices use the same profile. Jitter buffers—typically 1 to 5 ms—should be set on each receiver to tolerate network jitter without introducing excessive latency. Test with the smallest buffer that yields zero packet loss under worst-case conditions.

Configuring AES67 Streams

Each AES67 stream is described by a Session Description Protocol (SDP) file that specifies IP addresses, port numbers, payload format, and clock parameters. Many devices allow you to import or paste SDP files to receive streams. For sending, configure multicast IP addresses in the range 239.192.x.x (default for AES67). Ensure the time-to-live (TTL) is at least 2 if traversing a router between VLANs. Some devices support unicast as well, but multicast is more efficient for one-to-many distribution. Document each stream’s SDP parameters in a central spreadsheet for troubleshooting.

Redundancy and Reliability

Analog systems have inherent resilience—a broken cable affects only one channel. Digital networks can fail catastrophically if a switch goes down. Plan for redundancy:

  • Redundant PTP grandmasters: Use the “best master clock algorithm” and have a backup clock on the network.
  • Link aggregation or dual-homing: Connect critical devices to two switches using separate physical interfaces. AES67 does not natively support stream redundancy (though some proprietary extensions do), so duplicate the stream across two multicast groups and have the receiver switch on failure.
  • Rapid Spanning Tree Protocol (RSTP): Implement on switches to recover from link failures quickly (sub-second).
  • UPS for network gear: Switches and clocks must be on battery backup to survive power flickers.

Testing and Troubleshooting

Before going live, conduct thorough tests. Measure end-to-end latency using a loop-back test (send a signal, record the return, calculate delay). Verify that the latency matches your configured buffer size. Monitor packet loss using system logs and tools like iperf or dedicated AoIP analyzers. Check that all streams remain synchronized by listening for phasing issues on correlated signals. Test failover scenarios: pull a network cable, disable a stream source, and verify that the system recovers within the expected time. The Ravenna documentation site includes detailed troubleshooting guides that apply broadly to AES67.

Training Staff and Creating Documentation

A digital audio network is more abstract than analog patch bays. Operators must understand IP concepts to diagnose problems like “no audio” when the device is actually online but not receiving the correct multicast group. Invest in hands-on training sessions where staff configure a test stream from scratch. Cover how to read SDP files, how to set PTP priority, and how to verify switch status. Create written documentation that includes network topology diagrams, IP address tables, RTP port assignments, and step-by-step SOPs for starting/stopping streams and switching to backups. Keep this documentation in a shared digital repository that is updated with every change.

Monitoring and Maintenance

After deployment, continuous monitoring ensures long-term stability. Use Simple Network Management Protocol (SNMP) to collect switch statistics—CPU load, port errors, packet discards. Enable Syslog on devices to capture PTP synchronization status changes. Implement a packet loss monitor that alerts you if loss exceeds 0.1%. Regularly check for firmware updates from manufacturers, as many patching cycles address PTP improvements or security vulnerabilities. Schedule a quarterly review of latency and jitter measurements; if drift appears, investigate cabling or switch clocking issues. The IEEE 1588 (PTP) standard provides details on clock hierarchy that can help diagnose sync problems.

Conclusion

Transitioning from analog to AES67 digital audio systems is not a trivial upgrade, but it is a rewarding one. By understanding the standard’s requirements, preparing your infrastructure, and executing a phased rollout with rigorous testing, you can achieve a smooth migration that delivers high-quality, flexible, and scalable audio networking. The key is to treat the transition as a system engineering project rather than a simple equipment swap. With proper planning, training, and ongoing maintenance, your organization will benefit from reduced cabling, simplified routing, and a future-proof foundation for professional audio.