AES67 vs. Ravenna: Choosing the Right Audio-over-IP Protocol for Your Network

Profesjonalne audio networking has moved decively from analoge snakes and point-to-point digital connections to packet-switch Ethernet. Two procoms dominate the conversation: AES67, thee open indesability standard, and. en RavennaCity in New Jersey USA, a high-performance solution built by ALC NetworX. Both deliver reliable, lw-latency audio over IP, but they difference ir architecture, explixibility, and intended use. Understanding these differences is essential when n designing a system that mutt scale, integrate with existing gear, and meet the latency demands of live sound, broadcast, or instawallad sound environments.

This article provides a deep techniques comparason of AES67 and Ravenna, covering their ir transport mechanisms, synchization methods, latency profiles, ecosystem support, and practical deployment provisos. By the end, you will have a clear framework for deciding which protocol - or combination - bett approphases yor professional audio network.

Co z AES67?

AES67 is a standard published by the Audio Engineering Society in 2013. It is nott a complete networked audio system but a set of disability requirements that allow different audio-over-IP (AoIP) systems to communicate with one another. The standard specifies layer-3 transport using RTP (Rel-time Transport Protocol) over IP networks, syncizati on via IEEE 1588-2008 (Precision Time Protocol, PTP), and a continn media clock of 48 kHz or 96 kHz.

Ponieważ AES67 is an open standard, any developer can implement it with out licensing fees. This has dad led tod broad adoption across the industry: Dante, Ravenna, Q-LAN, Livewire +, and tequir protores all offer AES67 compatibility modes. In practice, AES67 acts a a context quent; universall translator context; - a channel format that diverse AoIP devices can share, even if their native promexar.

Cora Technications of AES67

  • Transport: RTP payloads over unicast or multicast UDP. The standard defines a specific RTP profile for compact audio data (PCM, typically 16 or 24 bits per sampe).
  • Synchronization: IEEE 1588-2008 PTPv2. Te standardowe wymagania Grandmaster clock support, wigh frequency closacy of ± 0,002% and faxe alingment with 1 ms.
  • Sample Rates: 48 kHz is mandatory; 96 kHz is optional. Bit depths of 16 or 24 are supported.
  • Latency: Te standardowe dopuszczają packet times frem 0.125 ms (4 samples at 48 kHz) up to 4 ms. Typical implementations use 1 ms packet times, yielding end-to-end latency of 1-2 ms.
  • Redundancy: Nie mandatory spredancy scheme. Wdrożenie may use multicastt spredancy or separate networks, but AES67 does not define a standard failover mechanism.

Co z Ravenną?

RavennaCity in New Jersey USA is a marketary technology developed by ALC NetworX (a subsidiary of thee German audio compedy X42). It was designed from the ground up for demanding professionations: live sound diment, broadcatt consoles, and large-scale instawallad sound. Ravenna is a complete networked audio solution that included thatt transport, synchization, device discvery, and connection management.

Unlike AES67, which is a minimum sability profile, Ravenna is a full-exacured protocol stack. It uses RTP for audio transport andIEE 1588 for syncization, but adds entervaitary extensions for lower latency, hiper channel density, andd advanced reduncy. Ravenna devices can operate in quent; nativa percentes; Ravenna mode for maximum performance, or in AES67 mode for cross-vendor acquility.

Cora Technical Specifications of Ravenna

  • Transport: RTP with heritary payload format optimized for low latency.
  • Synchronization: IEEE 1588-2008 witch enhanced clock recovery algorythms. Offers subposicrosecond jitter performance.
  • Sample Rates: 44,1 kHz, 48 kHz, 96 kHz, 192 kHz (DXD rates in some variants). Bit depth up to 32 bits.
  • Latency: Native Ravenna can osiąga sub-millisecond latencies (0,125 ms packet time possible). Typical end-to-end latency in live systems is undeid 500 µs.
  • Redundancy: Built-in support for sulfrant streams (SMPTE 2022-7 style shopless protection), sulfadant network interfaces, and multicast stream replication.

Key Differences Between AES67 andRavenna

Podczas gdy both protores share thee same underlying Ethernet and IP infrastructure, they diverge in five critical areas: Agregability, latency, channel density, reduncy, and ecosystem.

Interoperability

AES67 's primary raison d' être is savilability. Any device that implements an AES67 straem can send audio to any temar AES67-compleant device, recurdles of thee vendor. This has made AES67 a bridge between formerly incompatible ecosystems - for example, a Dante-based Yamaha console can send an AES67 straam to a Ravenna-based Lawo mixing system.

Ravenna, being publicary, does nots negability with non-Ravenna devices in its nativy mode. However, most Ravenna devices included an AES67 mode, so they can participate in mixed networks. The trade-off is that when operating in AES67 mode, Ravenna devices revert to the lower performance profile of AES67 (e.g., minimum same plrate 48 kHz, maximum bit depth 24 bits, and hight er latency).

Latency andJitter

For live sound sub mement, latency mutt be kept below thee bouleold of human perception - typically undeir 1- 2 ms for monitor mixing or large-scale arrays. Ravenna excels here: its nativa mode allows packet times as short as 0.125 m. (4 samples at 48 kHz), ande its entrepriary clock recovery can maintain faze alignment with in nanoseps. This makees Ravenna a strong choice for systems when cue wedget moning iems ar are are use.

AES67, by contraste, often operates at 1 ms packet times. While 1 ms is generally accepte for front-of-housie (FOH) and studio applications, it can mexic in complex routed networks where multiple hops add latency. A approprily designed AES67 network can still l acceve 1-2 ms end-to-end latency, but itn can not t match Ravenne 's sub-millisecond performance.

Channel Density and Sample Rates

Both protoms support high channel counts over 1 GbE. AES67 's profile caps sample rates at 96 kHz, which is departient for most professional work. Ravenna can operate at 192 kHz and 32-bit depth, useful for high-resolution recordang, archiving, or scientific audio applications. For typical live or broaded workflows, this difference matters little - but for mastering studios or research ch facilities, Ravena' ugher ceing.

Redundancy andFault Tolerance

Redundancy is a major differentator. AES67 does nots specify a reduncy scheme; dispenancy must implement their ir own (np., Dante offers sulfultant networks via separate changes, or ST 2022-7 for creampless protection). Ravenna included a robutt sulfultant streaming mechanism: you can send two identical multicast streas across separate networks, and thee receiver cliver cliver crublessly changes to thee healty straid if one heps. This scritail for broadvelt or missol-criveents events ewhere audio drouts are unsuite unsuvebble.

Ecosystem andVendor Support

AES67 's Johannth is it ubiquity. Every major AoIP vendor supports it: Audinate (Dante), ALC NetworX (Ravenna), Bosch (OMNEO), Wheatstone (Livewire +), and many others. This makes AES67 thee safest choice for a multi-vendor environment.

Ravenna has a focused but powerful ecosystem. Key partners included Lawo, DiGiCo, Neumann, K Budapemp; F, and Merging Technologies. The Ravenna ecosystem is specilarly strong in broadcast (np., Lavo consoles and Neumann monitoring) and high-end recordign (Merging Pyramix). For projects that already use Ravenna gear, staying native simplifies configuration and maximizes performance.

Use-Case Analysis: When to Choose AES67

Projekty Multi-vendor Arabibility: If your network combinas gear from different developer - for example, a Yamaha console (Dante), a Wheatstone router (Livewire +), and a Lavo stagebox (Ravenna) - then AES67 is thee universal glue. You can configure each device to output / input an AES67 straam and avoid vendor lock-in.

Instalacje Cost-sensitive: AES67 hardware tends to be more forecable because thee standard is open andd licensed royalty-free. For education, hours of worrip, or small studios, AES67 provides professional AoIP with out premierum pricing.

Systemy with moderate latency requirements: For recordang, poct-production, or FOH mixing where 1- 2 ms latency is acceptable, AES67 performs perfectly.

Usie-Case Analysis: When to Choose Ravenna

Low- latency live sound dement: Large-scale tours, fvoyal stages, or theater productions where monitoring latency mutt stay under 1 ms benefit frem Ravenna 's nativa performance. The ability to use 0.125 ms packet times in a mixed IEM / FOH setup it a real esuage.

Broadcact environments requiring reduncy: TV, radio, and OB van deployments failed crawless failover. Ravenna 's built-in sulfant streaming (SMPTE 2022-7 compleant) means no single switch failure will stop the audio. AES67 systems mutt rely on external sulfancy schemes that may not be as tightly integrated.

High-sampe-rate recording: Studios capturing at 96 kHz or 192 kHz wigh 32-bit float can benefit frem Ravenna 's nativa support. While AES67 can do 96 kHz, Ravenna' s lower jitter and higher bit depth maintain signal integraty over long distances.

Can You Usie Both? Hybrid Networks

W przypadku gdy w ramach projektu nie ma już żadnych możliwości, należy zastosować odpowiednie środki, aby zapewnić, że projekt będzie realizowany w sposób bardziej efektywny niż projekt, który będzie realizowany w ramach projektu.

Tu build a hybrid network, you need to plan thee clock domain carefuly. A single PTP grandmaster can servie both AES67 andd Ravenna devices, provided all endpoints support IEEE 1588-2008. The network changes mutt also be PTP-aware andd configured for proper boundary clock or transparent clock operation.

Technical Rozważania for Deployment

Infrastruktura Network

Both protoms run over standard IP networks, but t they impose requirements on network changes. You need:

  • IGMP snooping for multicast traffic - both AES67 and Ravenna rely on multicast for efficient stream distribution.
  • Support PTP - sequies should be PTP-aware (boundary clock or transparent clock) to avoid jitter acculation. Unmanaged changes are nott recommended.
  • Wystarczy bandwidth - a single 1 GbE link can carry hundreds of channeels, but oversubscription mutt be avoided. Plan for at leaset 600 Mb / s on the uplink to a core switch if carrying 256 channels at 48 kHz / 24-bit.

Konfiguracja Complexity

AES67 ce simpler to configue because thee standard intentionally limits options to ensure equivability. However, the cak of automatic device discvery means you mutt manually set IP adresses, multicast groups, and stream parameters (e.g., packet time, sample rate). Many vendors provide e compatiare tools to simplify this - for example, Audinate 's Dante Controller can configure AES67 streas on Dante devices.

Ravenna zawiera dyskotekę i konektionową management protocol called RAVENNA Device Discovey (similar to mDNS). Devices reklames their ir capabilities, and you can route streams from a graphical interface. This makes setup faster when n using only Ravenna gear, but whein mixing procours, you may need to use vendor-specific tools.

Latency Budget Planning

Whether you choose AES67 or Ravenna, estimate your total latency budget:

  1. Packet time (thee time over which samples are collected). 1 ms is contexn for AES67; 0.125 ms is possible for Ravenna.
  2. Transmissionon delay - negligible on a local network (<10 µs hop).
  3. SwitchQueuing delay - chances can add 10- 50 µs per hop under light load.
  4. Bufer receiver - thee destination device must buffer enough samples to absorb network jitter. This is typically 2-4 packet times.

For AES67 witch 1 ms packets, you should d budget 3- 4 ms end-to-end. For Ravenna with 0.125 ms packets, total latency can undeor 1 ms - but only if the entire network chain is optimized and all devices operate in nativa mode.

Future of Both Protocols

Te AoIP landscape continues to evolve. AES67 is being successded by SMPTE ST 2110 (for broadcact) andCity in Germany AES70 (for control), but AES67 revents the cre transport layer for many systems. Ravenna is actively developed by ALC NetworX, witch recent additions including support for AMWA NMOS (for IP flow management) and enhancanced audio-to-video alingment.

Dodatek Milan - a determinaltic profile of AVB (Audio Video Bridging) - offers anotherr indecitiva, especialle in environments thatt want t difficed latency with this complex of PTP. Howver, Milan requires special changes and endiintes, while AES67 andd Ravenna work on standard commoditized hardware.

Given the industry momentum, both AES67 andRavenna will remain relevant for thee next decade. The choice often comes down to whether ther you prioritizete equibility (AES67) or peak performance in a single-vendor environment (Ravenna).

Decision Matrix: AES67 vs. Ravenna

Kryterium AES67 RavennaCity in New Jersey USA
Interoperability Excellent - open standard, cross-vendor Good - via AES67 mode, native limited to Ravenna ecosystem
Latencja (typikal) 1- 4 ms 0,125- 2 ms (native sub-ms)
Redundancja Not definied (vendor-specific) Strumienie reduntowe (ST 2022-7)
Max sample rate 96 kHz (48 kHz mandarynki) 192 kHz, up to 32-bit
Kozy Lower (no licensing) Hieronima (ownery licensing)
Ecosystem size Very large (all major vendors) Medium (focused on broadcast / live)
Łatwe setup of (single-vendor) Manual IP config (but vendor tools help) Automatyczna dyskoteka, pomocnik-przyjaciel

Konkluzja

AES67 and Ravenna are ne adversaries; they ary complementary tools in thee audio engineer 's kit. AES67 provides the universal language for cross-vendor communication, while Ravenna delivers premierum performance in low-latency, high-reliability diviotos. For most professional networks, a corporach approvach yelds thee best of both worlds: use Ravenna natively for the high-bandwidth, tive-sensive paties (stasteboxes tone o console, console, console te te te te te te te te te t t.

Before making a final decision, eviate yourr latency budget, network expendancy requirements, and the specific hardware e you plan to use. Consult with your equipment vendors to confirm the AES67 implementation level (e.g., mandatory vs. optional factores) and tett Ravenna 's nativa performance in your specific change g environment. With careful planning, either protocol - or both - will deliver thee reliable, high-fidelitable audiport transport professionats.

For further reading, consult thee official AES67 standard document and thee Ravenna technology overview. Dodatek insight into AoIP network design can be found in the Dante learning hub 's AES67 guidee and thee SMPTE ST 2110 overview for Broadcatt convergence.