Introduction

In modern audio production and broadcasting, seamless integration of different audio networking protocols is essential for efficient workflows. AES67, Dante, and Ravenna are three prominent standards that facilitate high-quality, low-latency audio transmission over IP networks. Integrating AES67 with existing Dante and Ravenna systems allows for a unified, flexible, and scalable audio infrastructure. This approach enables audio engineers to combine the best features of each protocol, reduce equipment costs, and future-proof their installations. As the industry moves toward fully networked audio, understanding how to bridge these technologies becomes a critical skill for system designers and technical managers.

Understanding the Protocols

Before diving into integration tactics, it is important to understand the characteristics and origins of each protocol. Although all three transmit digital audio over IP, they differ in their core technologies, discovery mechanisms, timing models, and vendor ecosystems.

AES67

AES67 is an open, vendor-neutral standard developed by the Audio Engineering Society. It was designed specifically to enable interoperability between different audio-over-IP (AoIP) systems. AES67 defines a common set of parameters for audio transport, including media clock synchronization (IEEE 1588 Precision Time Protocol), stream discovery (using SAP), and data formats (16/24-bit PCM at common sample rates). Because it does not impose a single controller or management protocol, AES67 acts as a universal translation layer. Any device that supports AES67 can send or receive audio to or from any other AES67-compliant device, regardless of the underlying native protocol.

Dante

Dante, developed by Audinate, is a proprietary but widely adopted AoIP solution. It offers a complete ecosystem including automatic device discovery (via Dante Controller), redundant networking, and integrated clock synchronization. Dante uses its own timing scheme based on IEEE 1588-2008 (PTPv2) with a master-slave architecture. The protocol supports up to 512 channels per link at 48 kHz and is known for its low latency (down to 250 microseconds) and plug-and-play simplicity. Dante networks are common in live sound, corporate AV, and broadcast environments.

Ravenna

Ravenna, developed by ALC NetworX, is an open technology built on standard IP networking principles. It leverages standard protocols such as RTP, UDP, SAP/SDP for stream discovery, and IEEE 1588 (PTP) for precise synchronization. Ravenna is highly flexible and can be customized for specific applications, making it popular in installed sound, stadiums, and broadcast infrastructures that require large channel counts and long cable runs. Many manufacturers of mixing consoles and I/O hardware offer Ravenna support, and it is the foundation for the IP Showcase and other interoperability demonstrations.

The Need for Interoperability

In practice, few facilities operate on a single protocol. A broadcast studio may use Dante for its mixing consoles and intercom systems, while the distribution to transmitter sites relies on Ravenna. A concert venue might have a Dante-based digital snake but add AES67-compliant third-party effects processors. Without a bridging mechanism, these islands cannot share audio streams. The result is increased hardware cost, limited flexibility, and operational complexity as engineers must manually patch using analog or digital converters. AES67 solves this by providing a common language that Dante and Ravenna devices can speak, but implementation requires careful planning.

Key Compatibility Challenges

Each protocol has unique features and network configurations that can lead to compatibility issues. Dante, for example, uses its own discovery (Dante Controller) and clock synchronization methods (Dante clocking), while Ravenna relies on standard SAP and PTP. Dante also employs a simpler multicast addressing scheme compared to Ravenna’s flexible session management. When integrating, problems often arise from differences in:

  • Media clock synchronization: Dante’s clocking is proprietary, while Ravenna and AES67 follow IEEE 1588-2008 (PTP). Although many Dante devices now support PTP, precision must be maintained across the network.
  • Stream discovery and routing: Dante uses a centralized controller; Ravenna and AES67 use SAP/SDP announcements. This means a Dante device cannot automatically see Ravenna streams without a translation layer.
  • Packet timing and latency: Each protocol defines acceptable packet intervals (e.g., 1 ms vs. 125 µs). Mismatched timing can cause underruns or excessive jitter.
  • Multicast address management: Dante uses a proprietary IGMP approach, while Ravenna may require manual configuration of multicast groups.

Core Integration Strategies

To effectively integrate AES67 with Dante and Ravenna, audio professionals can employ several proven strategies. The choice depends on the existing equipment, required channel count, latency tolerance, and budget.

Use AES67-Compatible Devices

Select hardware that supports AES67 natively. Many modern Dante-enabled devices now include AES67 mode (through firmware upgrades or by enabling a setting). Similarly, Ravenna devices often support AES67 out of the box. By choosing these multiprotocol products, integration becomes a matter of configuration rather than adding extra hardware. When purchasing, look for the "AES67-compliant" logo or check the manufacturer’s datasheets.

Implement Bridging Solutions

For existing legacy devices that lack native AES67 support, use dedicated network bridges or gateways. These devices translate between protocols at the packet level. For example, a Dante-to-AES67 gateway receives Dante streams and retransmits them as AES67 streams (or vice versa). Some popular options include the Audinate Dante AVIO adapters and the ALC NetworX Ravenna gateways. Ensure the gateway supports the required sample rates, bit depths, and number of channels, and can maintain low latency (<1 ms typical).

Configure Network Settings Carefully

Proper network configuration is the foundation of a successful integration. Pay special attention to:

  • Clock synchronization: Use a single grandmaster clock (PTP) for the entire network. Assign one device as the PTP master (preferably a dedicated switch or a high-precision audio device). All Dante and Ravenna devices must be configured to follow the same PTP domain and profile.
  • Multicast management: Enable IGMP snooping on all switches and set appropriate query intervals. Ensure that multicast groups used by Dante (typically 239.192.x.x) and Ravenna/AES67 (often 239.38.x.x or custom) do not conflict. If necessary, use separate multicast addresses or VLANs.
  • Quality of Service (QoS): Prioritize audio packets using DSCP tags. Dante typically uses AF41 (100 010) for audio, while Ravenna and AES67 may use EF (101 110). Align these markings across the network to prevent packet loss.
  • Jitter buffers: Adjust jitter buffers on receiving devices to account for network jitter. Starting with a buffer of 1 ms to 2 ms is common, then reduce if the network is stable.

Maintain Network Segmentation

Isolate different protocol domains on separate VLANs to improve stability and security. For example, keep Dante traffic on VLAN 100 and Ravenna/AES67 on VLAN 200, then route audio only at bridging points (gateways). This prevents unintended discovery messages from interfering with each protocol’s control plane. Use firewalls or ACLs to restrict traffic between VLANs to only the necessary audio streams. In some cases, a dedicated audio network switch is recommended to separate audio from data traffic entirely.

Network Configuration Best Practices

Beyond the initial integration, ongoing management of a unified audio network requires adherence to standard best practices.

Switch Selection and Configuration

Use managed Gigabit Ethernet switches with low latency and support for IGMP snooping, PTP (Boundary Clock or Transparent Clock), and QoS. Avoid consumer-grade switches that drop multicast packets or introduce high jitter. Configure each switch to be PTP-aware; some switches can act as PTP boundary clocks to improve clock accuracy over long distances.

Redundancy

For mission-critical applications, implement network redundancy. Dante devices often support redundant ports (primary and secondary networks). Ravenna and AES67 can use multiple network paths if the infrastructure supports it. Consider using Spanning Tree Protocol (STP) or rapid STP to prevent loops, and always test failover behavior.

Monitoring and Diagnostics

Deploy network monitoring tools that can visualize PTP timing offsets, multicast stream integrity, and packet loss. Tools like Audinate’s Dante Controller (for Dante-specific monitoring) or Wireshark (for analyzing AES67/Ravenna streams) help identify configuration errors. Set up alerts for clock drift, excessive jitter, or dropped packets.

Real-World Use Cases

Integration of AES67 with Dante and Ravenna has been successfully implemented in many environments.

Broadcast Facilities

A radio station uses a Dante-based digital console for on-air talent and a Ravenna-based intercom system for studio-to-transmitter links. By adding an AES67 gateway, the console’s outputs can be sent as Ravenna streams to the transmitter, while the intercom’s return audio is bridged back to Dante. The result is a single audio network that covers the entire facility without analog patching.

Concert Venues

A large arena has a Dante network for the front-of-house console and stage boxes, but wants to integrate a Ravenna-based PA system (powered loudspeakers with onboard processing). Using a multiprotocol stage box that supports both Dante and AES67, the audio from the console is converted to AES67 and sent to the loudspeakers. The PA system sees the streams as native Ravenna, and the whole system runs on one switch stack.

Educational Institutions

A university campus with multiple performance spaces uses different protocols in each hall. A central control room bridges all spaces using AES67. This allows any performance to be recorded, streamed, or broadcast from a single location, regardless of the local protocol. Students learn to work with multiple AoIP systems, preparing them for real-world workflows.

Troubleshooting Common Issues

Despite careful planning, issues can arise. Here are common problems and solutions:

  • No audio or intermittent dropouts: Check PTP synchronization. All devices must be locked to the same master clock. Use a PTP analysis tool to verify offset and delay.
  • Streams not visible: Ensure SAP announcements are enabled on Ravenna/AES67 devices and that Dante devices are in AES67 mode. Verify that VLANs and IGMP snooping are correctly set.
  • High latency: Reduce jitter buffers incrementally. Ensure network switches are not adding store-and-forward delays. Use cut-through switches where possible.
  • Clock drift: Use a dedicated PTP grandmaster, especially in multi-switch networks. Avoid daisy-chaining switches without PTC/Boundary Clock support.
  • Audio artifacts (clicks/pops): Often caused by packet loss or timing errors. Check QoS DSCP markings; ensure audio packets are not competing with data traffic. Increase jitter buffer temporarily to identify if network jitter is the cause.

Future of Audio-Over-IP

The trend toward IP-based audio is accelerating. The AES67 standard continues to evolve, with profiles like SMPTE ST 2110-30 (for professional media) adopting AES67 as the audio transport layer. Dante has incorporated AES67 support in its Dante Domain Manager and firmware updates. Ravenna is increasingly used in large-scale broadcast installations, such as the IP Showcase demonstrations. Going forward, integration will become simpler as more devices support multiple protocols natively. The emergence of ST 2110, AES67-2018, and AoIP over 25GbE will further unify the landscape. Engineers who master integration today will be well-prepared for the all-IP future.

Conclusion

Integrating AES67 with existing Dante and Ravenna systems enhances the versatility and efficiency of audio networking setups. By understanding protocol differences and employing strategic solutions—such as using AES67-compliant devices, bridging gateways, careful network configuration, and segmentation—audio professionals can create unified networks that meet the demands of modern broadcast, live sound, and installed audio environments. The result is a flexible, scalable, and future-proofed audio infrastructure that maximizes equipment investment and simplifies workflow.