Understanding Professional Audio Networking: Ravenna vs Livewire

Professional audio networking has transformed how broadcast facilities, live sound venues, and production studios handle audio distribution. Moving away from bulky analog snakes and dedicated digital point-to-point connections, audio-over-IP (AoIP) systems now deliver pristine audio with low latency over standard Ethernet infrastructure. Two protocols that frequently come up in these conversations are Ravenna and Livewire. While both serve the same fundamental purpose—transmitting high-quality audio over IP networks—they differ significantly in architecture, standardization approach, and ideal deployment scenarios. This article provides a thorough technical and practical comparison of these two protocols to help system designers, audio engineers, and technical managers make informed decisions.

What Is Ravenna?

Ravenna is an open, standards-based audio-over-IP technology developed by ALC Network, a German company specializing in real-time media networking. It was designed from the ground up to meet the stringent demands of broadcast, live performance, and installed sound environments where low latency, high channel counts, and precise synchronization are non-negotiable. Ravenna operates as a complete layer-3 solution, meaning it works over standard IP networks, including routed networks, without requiring dedicated switches or special configurations beyond standard Quality of Service (QoS) settings.

The protocol is built on the AES67 standard, which defines interoperability requirements for high-performance audio-over-IP streaming. Because Ravenna fully supports AES67, equipment from different manufacturers that also comply with AES67 can exchange audio streams with Ravenna devices. This openness has made Ravenna a popular choice in heterogeneous environments where gear from multiple vendors must coexist.

Ravenna supports sample rates up to 192 kHz, bit depths up to 32 bits, and channel counts that scale into the hundreds over a single network link. It uses standard transport protocols including RTP (Real-time Transport Protocol) for audio payload delivery and RTCP (RTP Control Protocol) for stream management. Synchronization relies on IEEE 1588 Precision Time Protocol (PTP), with profiles optimized for media applications to achieve sub-microsecond clock accuracy across the network.

What Is Livewire?

Livewire is a proprietary audio-over-IP protocol originally developed by Riedel Communications, a German company well-known for intercom systems, radio communications, and real-time networking solutions for broadcast and live event production. Livewire was created specifically to address the needs of Riedel's own intercom and audio distribution products, providing tight integration with Riedel's hardware ecosystem, including the Artist and Bolero intercom systems and the MediorNet real-time media transport platform.

Unlike Ravenna, Livewire uses its own protocol stack rather than adhering to a broad open standard like AES67. This means that Livewire devices communicate most efficiently within Riedel's product lineup, where the protocol's proprietary features—such as advanced redundancy mechanisms, deterministic latency behavior, and integrated signaling for intercom functions—are fully supported. While Riedel has introduced AES67 compatibility in some newer products, native Livewire mode remains the preferred configuration for performance-critical Riedel applications.

Livewire supports high-resolution audio up to 96 kHz sample rate and 24-bit depth, with channel densities that scale across multiple streams. The protocol operates at layer 2 and layer 3 depending on the specific implementation, with careful attention to network topology to guarantee the low and predictable latency required for live production use cases. Riedel provides detailed network design guides for Livewire deployments, and the protocol works optimally with managed switches configured according to Riedel's specifications.

Architecture and Technical Foundations

Ravenna: Standards-Based and Interoperable

Ravenna's architecture is fundamentally built around the concept of compatibility. By adopting AES67 as a baseline, Ravenna ensures that any compliant device can join the network and exchange audio with existing Ravenna streams. The protocol also extends beyond AES67 with additional capabilities such as redundant stream transmission, support for multiple audio formats in a single stream, and enhanced session management.

At the transport layer, Ravenna uses multicast RTP streams to distribute audio efficiently across the network. One source can feed multiple receivers without duplicating bandwidth consumption, making it highly efficient for broadcast distribution where one program feed must reach many destinations. The protocol also supports unicast for point-to-point connections when needed.

Synchronization in Ravenna networks relies on PTPv2 (IEEE 1588-2008) with the SMPTE ST 2059-2 profile, which defines how PTP is applied in professional broadcast environments. This provides timing accuracy on the order of nanoseconds, sufficient for sample-accurate alignment across dozens or hundreds of channels. Network switches must support PTP transparent clock or boundary clock functionality for optimal performance in larger deployments.

Livewire: Optimized for Riedel Ecosystems

Livewire's architecture prioritizes deterministic behavior and seamless integration with Riedel's intercom and signal distribution products. The protocol uses a combination of proprietary framing, stream management, and network resource reservation to ensure that audio packets arrive with minimal jitter and consistent latency. In Riedel's implementation, Livewire streams are typically configured as point-to-multipoint multicast flows, similar to Ravenna, but with additional metadata that carries intercom signaling, crosspoint routing information, and system status data.

Network timing in Livewire systems is achieved through a combination of hardware clocking in Riedel devices and network-based synchronization mechanisms. Livewire supports both proprietary clock distribution and PTP, depending on the product generation and configuration. In mixed-mode environments, Riedel devices can act as clock masters or slaves, allowing Livewire to coexist with AES67 streams when the appropriate bridging interfaces are used.

Latency in Livewire systems is typically configurable in steps ranging from sub-millisecond up to several milliseconds, giving engineers the ability to trade off latency against network buffering robustness. In practice, Livewire is often deployed with latency settings in the 1–3 millisecond range for live production, where every microsecond of delay affects foldback monitoring and artist performance.

Latency and Synchronization Comparison

Both Ravenna and Livewire offer excellent latency performance, but they achieve it through different design philosophies. Ravenna's latency is determined by the packet time—the duration of audio contained in each RTP packet—plus processing and network transit times. Typical packet times range from 0.125 milliseconds (1 sample at 48 kHz) to 4 milliseconds, with 1 millisecond being a common choice for broadcast applications. The use of PTP ensures that all devices on the network maintain sample-accurate alignment, which is critical for applications like surround sound or immersive audio where phase coherence across channels matters.

Livewire's latency performance is similarly impressive but is optimized for the specific hardware it runs on. Riedel devices use FPGA-based processing to keep latency as low as possible, with round-trip delays through a Livewire network often measured in the sub-millisecond range. The proprietary nature of the protocol allows Riedel to fine-tune buffering and clock recovery algorithms to match their hardware precisely, which can result in lower jitter and more consistent latency under heavy network load compared to a generic AES67 implementation.

In practice, the difference in absolute latency between Ravenna and Livewire is unlikely to be the deciding factor for most deployments. Both can achieve latencies well below the perceptible threshold for audio monitoring and live sound reinforcement. The more important distinction lies in synchronization accuracy and clock recovery stability, where Ravenna's strict adherence to PTP-based profiles offers an advantage in multi-vendor environments, while Livewire's hardware-tuned timing provides a more tightly integrated experience in Riedel-only systems.

Interoperability and Standards Compliance

Interoperability is the single most significant differentiator between Ravenna and Livewire. Ravenna was designed to be an open, multi-vendor solution. Because it fully implements AES67, and often goes beyond it with additional features like redundant streams and EMAC (Ethernet Media Access Control) based stream identification, Ravenna devices can communicate with AES67-compliant equipment from manufacturers such as Lawo, Neumann, Merging Technologies, and many others. Ravenna is also compatible with the SMPTE ST 2110 suite for broadcast production, which means it can integrate directly into modern IP-based broadcast infrastructures for video, audio, and ancillary data.

Livewire, by contrast, is primarily a single-vendor protocol. While Riedel has added AES67 bridging capabilities to some products, native Livewire devices speak a protocol that is not directly interoperable with non-Riedel equipment. This is not necessarily a drawback in environments that are already standardized on Riedel infrastructure, but it becomes a limitation when integrating with third-party consoles, processors, or distribution systems. In those cases, Riedel offers interface devices such as the Riedel Connect series, which translate between Livewire and AES67 or Dante, but these add cost and introduce an additional conversion step.

For organizations that value vendor independence and future flexibility, Ravenna's open standards approach is a clear advantage. Broadcasters and production companies that need to move audio between different facilities, connect with remote production trucks, or accommodate gear from multiple manufacturers will find Ravenna much easier to work with. Livewire, on the other hand, is the right choice when the entire audio chain is Riedel-based and the priority is maximum integration depth with Riedel's intercom and control features.

Use Cases and Applications

Broadcast and Production Facilities

Ravenna has found strong adoption in radio and television broadcast, particularly in Europe and increasingly in North America. Its compliance with AES67 and SMPTE ST 2110 makes it a natural fit for IP-based broadcast plants where audio must coexist with video, metadata, and control streams on the same network infrastructure. Ravenna is also used in OB (outside broadcast) vans, where its low latency and high channel density allow for complex multi-format production with equipment from multiple vendors.

Livewire is widely deployed in broadcast environments that use Riedel intercom systems as their communication backbone. In these facilities, Livewire carries not only program audio but also intercom audio, IFB (interruptible foldback) feeds, and talkback signals, all tightly integrated with the intercom control logic. The protocol's ability to carry signaling along with audio makes it more than just a transport mechanism—it becomes an integral part of the production communication system.

Live Sound and Event Production

Live sound reinforcement is an area where both protocols have strengths, but for different reasons. Ravenna's openness means it can connect FOH (front of house) consoles, monitor consoles, stage boxes, and processing gear from different manufacturers, giving system designers greater flexibility. Some digital mixing consoles, such as those from Lawo and Stagetec, natively support Ravenna, allowing direct digital connection to the network without additional interface hardware.

Livewire is particularly strong in large-scale live events where Riedel intercom systems are already deployed for crew communication. The ability to route audio and intercom on the same network reduces infrastructure complexity. Music festivals, sports events, and corporate productions that use Riedel's Artist or Bolero systems can benefit from Livewire's integrated approach, where audio distribution, intercom, and control all ride on a common platform with unified management software.

Installed Sound and Theatrical Systems

For permanent installations in theaters, houses of worship, and performance venues, Ravenna offers the advantage of using standard IT infrastructure and commodity networking hardware. The protocol's support for large channel counts and flexible routing makes it suitable for complex distributed audio systems with multiple zones and delays. Because Ravenna is OS-based and works with standard network adapters, it can also integrate directly with software-based audio processing and playback systems.

Livewire is less common in installed sound outside of venues that already use Riedel intercom or MediorNet signal distribution. In those cases, Livewire provides a convenient way to transport audio alongside video and intercom signals within the MediorNet framework. However, for a standalone installed sound system without Riedel infrastructure, Livewire's proprietary nature can limit options and increase long-term dependency on a single vendor.

Network Infrastructure Considerations

Building a reliable AoIP network requires careful attention to network design, regardless of which protocol is chosen. Both Ravenna and Livewire benefit from managed switches with IGMP snooping for efficient multicast handling, QoS prioritization for audio traffic, and PTP support for timing (in the case of Ravenna, or equivalent clock distribution for Livewire).

Ravenna networks typically require switches that support PTP boundary clock or transparent clock functionality to maintain timing accuracy across multiple switch hops. The protocol also benefits from jumbo frame support to reduce packet overhead at high channel counts. Ravenna's use of standard IP routing means that audio streams can traverse VLANs and subnets as long as multicast routing is properly configured, which is useful in large facilities with segmented networks.

Livewire networks are generally simpler to design within a single domain but require adherence to Riedel's specific network guidelines. Riedel provides detailed documentation on switch configuration, cable types, and topology recommendations. For best performance, Livewire should be deployed on a dedicated audio network or on a VLAN that is isolated from general IT traffic. Riedel also recommends specific managed switch models that have been tested and certified for Livewire operation.

In both cases, network redundancy is an important consideration. Ravenna supports redundant streams (stream A and stream B) that can be sent over separate network paths, allowing hitless failover if one path fails. Livewire systems can also be configured with redundant network interfaces and paths, typically using Riedel's own redundancy mechanisms that work in conjunction with the hardware.

Management and Configuration

Ravenna devices are typically configured and managed through web-based interfaces, SNMP, or manufacturer-specific control software. The open nature of the protocol means that third-party monitoring and management tools can also work with Ravenna streams, provided they support AES67 and RTP stream discovery. Features like SAP (Session Announcement Protocol) and RTSP (Real-Time Streaming Protocol) are used in some deployments for automatic stream discovery and session setup, simplifying configuration in dynamic environments.

Livewire management is handled through Riedel's proprietary software tools, primarily the Riedel Director configuration and monitoring platform. Director provides a centralized view of all Riedel devices on the network, including intercom panels, audio interfaces, and MediorNet nodes. Livewire stream routing and crosspoint configuration are integrated into this platform, allowing engineers to manage audio routing alongside intercom logic and user permissions. This tight integration is a significant advantage in environments where audio and intercom are part of the same operational workflow.

For organizations with IT-managed networks, Ravenna's use of standard protocols makes it easier to integrate with existing network monitoring and management systems. Livewire's proprietary tools, while powerful for Riedel-specific tasks, require dedicated training and are less likely to interface with general-purpose network management platforms.

Cost and Ecosystem Considerations

The total cost of ownership for a Ravenna-based system is often lower in multi-vendor environments because it avoids the need for proprietary hardware and interface converters. Standard network switches from major manufacturers (Cisco, Arista, Netgear, etc.) can be used as long as they meet the protocol's requirements, and a wide range of AES67-compatible devices are available at various price points. Ravenna's open nature also encourages competition among manufacturers, which helps keep prices competitive.

Livewire's ecosystem is centered around Riedel hardware, which is premium-priced but delivers a high degree of integration and reliability. For organizations that are already invested in Riedel intercom or MediorNet systems, adding Livewire audio transport is a logical and cost-effective extension. The cost of integrating non-Riedel equipment, however, can add up quickly, as interface boxes and protocol converters are often required.

Training and support are also factors. Ravenna's reliance on standard IT networking means that many system integrators and IT staff already have the foundational skills needed to deploy and maintain the network. Livewire benefits from Riedel's extensive training programs and application support, but expertise is more specialized and less widely available.

The broadcast and professional audio industries continue to move toward IP-based infrastructure, and both Ravenna and Livewire are evolving to meet these trends. Ravenna's alignment with AES67 and SMPTE ST 2110 positions it well for the future of all-IP broadcast production. As more manufacturers adopt AES67 as a baseline, the ecosystem of compatible devices will continue to grow, further increasing Ravenna's versatility.

Riedel, for its part, has recognized the importance of interoperability and has made AES67 support available in newer products such as the Riedel Connect series and certain MediorNet nodes. This allows Livewire systems to bridge into standards-based networks when needed, while still maintaining the proprietary advantages for core Riedel workflows. The trend is toward hybrid environments where proprietary protocols coexist with open standards, giving users the best of both worlds.

For system designers and technical managers, the choice between Ravenna and Livewire ultimately comes down to the specific needs of the installation. Ravenna offers maximum flexibility, vendor neutrality, and adherence to open standards, making it ideal for facilities that require interoperability across multiple manufacturers and long-term adaptability. Livewire delivers deep integration, deterministic performance, and a tightly managed user experience within Riedel-centric ecosystems, making it the preferred choice for operations where Riedel intercom and audio distribution are already the standard.

Practical Guidance for Decision-Making

When evaluating which protocol to adopt, consider the following practical steps:

  • Audit your existing infrastructure. If your facility already uses Riedel intercom or MediorNet extensively, Livewire is the natural extension. If your facility uses a mix of consoles, processors, and software from different vendors, Ravenna will likely be easier to integrate.
  • Assess interoperability requirements. Identify all the devices and systems that need to exchange audio. If any of them are from different manufacturers and require direct digital connection, Ravenna's AES67 compatibility is a major advantage.
  • Consider latency and synchronization needs. For most broadcast and live sound applications, both protocols deliver acceptable latency. However, if you need sample-accurate alignment across multiple zones or immersive audio formats, Ravenna's robust PTP implementation offers proven performance.
  • Evaluate network management capabilities. If your organization has a strong IT team with experience in managed networks, Ravenna will fit comfortably into existing workflows. If you prefer a turnkey solution with vendor-provided management tools, Livewire's Director platform simplifies the job.
  • Plan for future growth. Consider how your audio network may need to evolve over the next five to ten years. Ravenna's open standards path provides more flexibility for expansion and technology changes. Livewire's proprietary ecosystem offers stability and deep integration within its domain but may require additional interfaces for future integration with new equipment.

Both Ravenna and Livewire are mature, capable protocols that have been deployed successfully in demanding professional environments. Understanding their technical foundations, operational characteristics, and ecosystem implications allows audio professionals to choose the protocol that aligns best with their specific application, budget, and long-term strategy.

For additional technical details on AES67 and network design for AoIP systems, refer to the AES67 interoperability standard and the Riedel Livewire technical documentation. The SMPTE ST 2110 standard suite provides further information on IP-based broadcast production, and the ALC Network Ravenna page offers additional product and implementation resources.