Wprowadzenie do AES67 Audio over IP

Audio over IP (AoIP) system eg s t s t t s t t t t t t t t t t t t t t t t t t a w i e g t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t t, recording, and installad d sound environments because they enable usting, reduced cabling costs, and centralized management. Among te man proaccors and standards thatt have emerged, AES67 stand t at t at te te te te convention of en en en en en en d f f n dibubibility in difweet difine dift.

This guidee explains what AES67 is, how it works, it s key facires, and how it fits into the Broadwer AoIP landscape. We will also cover network requirements, practical beneficits, and real-contexd use cases, so you can confidently desin, deploy, or troubleshoot at an AES67- compleant audio network.

Co z AES67?

AES67 is an open standard published by the Audio Engineering Society (AES) that specifies how high- quality, low- latency audio streams are transported over IP networks. Formally designated AES67- 2015 (with updates in 2018), it desites the transport and d synchization mechanisms that enable equipment from different vendort exchange audio with out requiring entraire gateways or translation hardware. In esse, AES67 ithe quother quot; glue note note mate multiple.

Te standardowe nie przepisują żadnego konkretnego kontrowerlu protocol or discvery methode; instead, it focuses on thee transport layer: packet format, clock synchronization, and quality of service (QoS) parameters. This precised scope allows existing systems like Dante, Ravenna, Livewire, and Q- LAN to support AES67 alongside their nativa modes, giving users a innominator for cros- platform connective.

Historykal Context: Why Was AES67 Created?

Before AES67, the professional audio industry faced a framented landscape. Dante (by Audinate) dominate live sound and corporate AV, Ravenna (by ALC Network and others) was popular in Broaddatt and recording, and Livewire (by Telos Alliance) was prevalent in radio. Each protocol used difficult transport method, clocking schemes, and packet formats. The lack of meability mean mixing console from one rer could noult direcles decvre streastres a stastev.

Rozpoznanie tego problemu, że AES Standards Committee formed a working group to create a combine transport profile. Thee result was AES67, which Standards a contribute quent; leaast contribun denominator contribution quentit; for AoIP streams. By adhering to AES67, any device - contribudles of its nativa protocol - can send and requide audio from any contrar AES67- comprelant device, as long as thee network is appropriately cony figured.

Key Features of AES67

AES67 przynosi do getaru segregal krytycya ³ technik ¹ elements thatsure relieable, high- fidelity audio transport over IP. Below we expand on the cre quantiures mentioned in thee original overview.

Interoperability

Te primary design goal of AES67 is sability warty. It accesses this by standardizing thee audio payload format (Linear PCM, typically 16 or 24 bits, 48 kHz samplee rate), thee transport protocol (RTP over UDP / IP), ande thee syncization method (IEEE 1588- 2008 Precisision Time Protocol, or PTPv2). Because the building blocks are universal, a Ravenna microphone preamp caat talk ta a Dante- enabled mixing console abe long abots support AES67 mode.

Real- external d exability is nott infecless - exacrers may implement thee standard with small variations - but the AES67 compleance certification programm helps confidente that devices meet te minimum requirements. When accupasing equipment, look for thee AES67 Compliance Mark or consult vendor documentation.

Low Latency

Latency is te time delay between audio input and output. In live sound diment, delays over 1- 2 milliseconds (ms) can cause comb filtering and beedback issues. AES67 is designate tone to accesse end- to - end latencies as low as 0.5- 1 ms undeid ideal network conditions, and typically undeid 10 ms even larger installations. The standard determinas three latency profiles: quotes; R quoted; (rapd) att 1 ms, quet; L quott;

Synchronization via Precision Time Protocol (PTP)

AES67 relies on IEEE 1588- 2008 Precision Time Protocol (PTPv2) To synchronize all devices on thee network. PTP wykorzystuje master-slave hierarchie where a grandmaster clock sends timing packets to all slaves. Because audio sample crkes mutt be locked together to prevent drift and dropouts, PTP provides a specific PTP profile (default domain 0, with certain parameters) to ensure all AES6 devices cares caize a specific PTP profile (default domain 0, with certain parameters) to ensure all AES6 deviceres cain synchize té té a single.

A stable grandmaster clock is critical. Most AES67- compleant hardware includes a built- in PTP master, or you can use a dedicated grandmaster such as the Meinberg M500 or a switch witch built- in clock capabilities. The network changes themselves must support PTP boundary clock or transparent clock modes to maintain timing precision across multiple hops.

Standardized Codec and Packet Format

AES67 mandates Linear PCM audio at 48 kHz sample rate (with optional support for 44.1 kHz and 96 kHz). The audio is packed into RTP packets according to a definie de compute quite; Audio Mapping conclusive quet; format. Each packet typically contains on or more audio channels (up to 8 per stream in thee base profile, though implementations often support up tu tu 256 convenels busy using multiple streas). The payloaid s raw PCM, thoughlolos comprexis applifulf, recvion l audiqualty.

Te standard also specifies how tu signal stream information using Session Description Protocol (SDP). This text- based description tells receivers thee IP addicts, port, payload type, clock identity, and sample format, enabling automatic or manual connection setup.

How AES67 Works

Tu understand AES67, it helps to to visualizaze thee flow of audio from a source te a destination over an IP network.

Step 1: Clock Synchronization. Before any audio flows, the PTP grandmaster clock is established. All devices must be synchized to this clock using PTPv2. The synchronization happes continuously, with slave devices adjusting their local currises to match thee granmaster with in nanosekund closacy.

Step 2: Stream Reklama i odkrycie. AES67 nie definiuje protocol deplovery. Instad, stream senders (talkers) informuj ich ir acceptable streams using SDP, which ich may be encapsulated in SAP (Session Announcement Protocol) or deposited on external control system (e.g., Dante Controller, Ravenna 's RAVENNA Manager). Receivers (listeners) use the SDP to learn thee straam paraters and then join thee multicast group.

Step 3: Transport. Audio is packetized into RTP packets and sens over UDP / IP. AES67 typically uses IP multicast (IGMPv2 / v3) to efficiently deliver the same stream to multiple recipients. Each packet included a timestamp derived frem the PTP clock, allowing the receiver to reconstruct the audio timeline and buffer the data ta te recompatirate for network jitter.

Step 4: Quality of Service (QoS). Ponieważ audio is time- sensitiva, AES67 wymaga, aby te network to priorytet audio packets over regular data traffic. Te standard zaleca using Differentiated Services (DiffServ) with a DSCP value of 46 (Expedited Forwarding) for audio RTP packets, and34 for PTP packets. Proper QoS configuration ensures that latency andd jitter requin low even whene thee network ibusy.

Network Requirements

Wdrożenie AES67 sukcesywne demands a network designed for real- time traffic. Here are the key requirements:

  • Gigabit Ethernet or faster. AES67 streams can consume up to 0.64 Mbps per mono channel (16- bit, 48 kHz). A 64- channel stream uses ~ 41 Mbps, which is well with in gigabit capacity, but multiple streams on te same switch require condiire contrigent backplane bandwidth. 10 gigabit Ethernet is recommended for large installations.
  • Managed zmienia ten support PTP transparent clock or boundary clock. PTP packets must be timestamped celliately at each hop. Incosts consumer changes often add variable delay that destroys syncization. Look for changes from Cisco (np., Catalyst 3850), Netgear (M4300 series), or dedicated Pro Audio changes like thee Luminex GigaCore.
  • IGMP snooping andd querier. Since AES67 relies on multicast, changes mutt consultable manage multicast group membership to avoid fooding traffic to all ports.
  • Konfiguracja QoS. Audio packets (DSCP EF) powinny być umieszczone w miejscu, gdzie są wysokie ceny priority queue (except for PTP packets, which ch need d even lower jitter). Non- audio traffic like file transfers or VoIP mutt be marked with lower priority.
  • Separate VLAN for audio (optional but recommended). Isolating audio traffic in a decretated VLAN reduces the risk of interference from broadcast storms or rogue devices.

Interoperability with Other AoIP Systems

AES67 was designed to work as a bridge between enternary protores. The three mest cost contron AoIP systems that support AES67 ar e:

  • Dante (Audinate): Dante devices can be changed into AES67 mode via Dante Controller. In this mode, they act as standard AES67 receivers andd senders. Dante wykorzystuje je do własnych control and discvery, but te audio transport follows AES67. As of Dante Domain Manager, AES67 support is integrated.
  • Ravenna (ALC Network): Ravenna was one of thee arly adopts of AES67. Many Ravenna devices, including the DirectOut RAVENNA- MADI converters andMerging Technologies converters andMerging Technologies converters; Horus interfaces, support AES67 natively. Ravenna 's nativa mode is fully compleant, so no change is needed.
  • Livewire (Telos Alliance): Livewire was originally a publicary AoIP system for radio stations, but later versions added AES67 support. Telos consultals; Axia consoles andd Omnia audio procesors can send andd receive AES67 streams, allowing integration with texr brands.
  • Q- LAN (QSC): QSC 's Q- SYS platform wykorzystuje Q- LAN, which is based on AES67 for audio transport. Q- SYS devices can directly connect to Antarr AES67 sources andd sinks.
  • ST 2110- 30 (SMPTE): Broadcasters use SMPTE ST 21110 for uncompressed media over IP, and it audio contrigent (2110- 30) is essentially AES67 (wigh minor variations). Thus, any AES67 device can integrate with a sumplant ST 2110 Broadcast plant.

When connecting AES67 devices from different ecosystems, the main difficee is stream discvery and management. A Dante mixer cannot automatically see a Ravenna stream unless you manually configurate thee connection using thee receiver 's SDP file. Manty systems provide a web- based configuration page where you can paste SDP description arze AES67 compliance. AES also publishes an accordability tect plan Tu pomóc firmom validate connections.

Korzyści z Using AES67

If you are considering adopting AoIP, adding AES67 support provides clear provideages beyond any single system.

  • Vendor Independence: You are not locked into one ecosystem. Mix and match ch microphone, consoles, loudspeaker procesors, anddixders from different brands, provided they ay Are AES67 compleant.
  • Simplified Network Design: By using a control transport, you can reduce the number of dedicated overlay networks. One IP infrastructure can handle audio, control, and even video (when using ST 2110) if QoS and VLANs are correctly set up.
  • Cost- Effective Expansion: Need to add more inputs? Buy any AES67- compleant stagebox, plug it into your switch, configure thee stream - no need to o match the brand of your existing console.
  • Future- Proofing: As AoIP evolves toward full IP- based production (np., SMPTE ST 2110 for broadcast), AES67 ensures that your audio equipment can integrate into modern, all- IP environments.
  • Reliability andd Redundancy: Standard network reduncy protox (STP, RSTP, or redulant network paths) can be applied te audio network. AES67 does nott mandate a specific reduncy methode, but using swith networks witt sulfrent links or even per- stream duplication (if supported) is possible.

Usie Cases for AES67

AES67 appears in a wide variety of professionale audio applications. Below are some notable examples.

Live Sound Reinforcement

In concert venues andd homes of worrip, digital mixing consoles frem Yamaha (wigh Dante) and Allen indimp; Heath (with Dante) can (with Dante) be connectod to AES67 stageboxes from teir conteir contrirers. For instance, a DiGiCo SD12 can receve streams from a Midas DL251 stagebox via AES67, provided both are configured correctis. The low latency (1 ms) is critisaal for foldack and monir mixes.

Broadcact andRadio

Radio studios tradionally used analogi or AES3 digital for audio distribution. Today, transmits use AoIP to difficule audio the facility and d even across WAN links. Axia consoles (Livewire) can share streams with h WheatNet - IP or AES67- compleant codecs. The standard 's PTP syncization ensures that network delays do nott causie audio fasingg or timing mismatches whein mixing aded.

Recordang andd Post- Production

Wysokokanałowy system recordg such as Merging Technologies; Pyramix (using Ravenna) can integrate with with with AES67- compleant converters frem RMEE, Focusrite, or DAD. This allows studios to contribud 128 + tracks of uncompressed audio with out buying into a single ehary y ecosystem. Post- production facilities also use AES67 to route audio between dict bays and machine e omeames over a shard network.

Installed Sound andd Entreprenerate AV

In boardrooms, auditoriums, and diplomums, installed sound systems often require elastible ruting for multiple zone. AES67 loudspeaker procesory i wzmacniacze (np., frem Symetrix, Biamp, or QSC) can receive audio from any AES67 source, allowing centralized control over IP. Thee scalality of multicaste make it easy te adone z dodatkami do -point cabling.

Wyzwania i rozważania

Kiedy AES67 i jest potężnym tool, nie ma żadnych wyzwań.

  • Grandmaster Clock Dependency: If thee PTP granmaster failes and no backup exists, all synchronized devices will eventually drift, causing dropouts. Always configue a Best Master Clock Algorithm (BMCA) with multiple potential granmasters or use hardware that can automatically elect a new master.
  • Konfiguracja QoS Complexity: Incorrect DSCP marking can lead to packet loss or increaged latency. Ensure your network changes are configured to trust DSCP tags and that audio queues are consuscyly sized.
  • Stream Discovery Limitations: AES67 itself nie jest w stanie przeprowadzić jednej z najlepszych prac. You may need to do manually enter IP adresses andd SDP descriptions, which can ne tedious in large installations. Some contecrerers provide establishary thatt abstracts way when both side are from the same vendor, but cross- vendor connections often require manual setup.
  • Latency Accumulation: While per- hop latency is low, multiple hops in a large network (especialle over WAN) can push total latency above toleranble bololds. Use thee appropriate latence profile andd measure end-to-end delay with tools like thee AES67 Latency Analyzer or a simple teste tone.
  • Bandwidth Management: AES67 streams are uncompressed. A 64- channel stream at 48 kHz / 24- bit uses ~ 73 Mbps. Overloading a gigabit network with many streams can cause congestion. Calculate total bandwidth andd compare to accepte to acvailable link capacity. Also, be mindful of multicast replication - each switch port that subscribes to a straam receives a coppy, so the total load othe switch backplane muste less thathan ts capacity.

The Future of AES67

AES67 continues to evolve. The AES67- 2018 update added support for optional sample rates andd cleanfied some QoS recommentations. Looking forward, thee standard is being contributed into broader appropes such as SMPTE ST 21110 for broadcast andthee AES70 (OCA) control protocol. Most importantly, AES67 is the foldation for the Audio over IP Interoperability Standard To jest to, co jest ważne dla nas.

For those new to AoIP, mastering AES67 is a stepping stone to understanding advance d concepts like sumplant streaming, IEEE 1722 (AVTP), and time- sensitiva networking (TSN). As more contrirers adopt AES67 as a baseline experture, the coss of entry continues to drop, making it an ideal choice for both small installations and large- scale widcast plants.

Konkluzja

AES67 is te esential open standard that enenables different Audio over IP systems to work together. Bystandardizing transport, syncization, and packet format, it removes the barrivers that once prevented equizers from mixing equipment brands on te same network. With low latency, robutt clocking via PTP, and backward compatibility with many existing procoils, AES67 has eze thee de factability for professional AIP. Wher yoare designation a broading a broading, upgrading a livine, upgrading a livine, soundig, building, indig, studing, endig, endeft ef ef e@@

For further reading, refer to the official AES67 standard document and thee Wikipedia article on AES67. If you are looking for practical implementation guides, Audinate offers a underpursive whitepaper library on AoIP, and the Telos Alliance provides excellent resources on Livewire and AES67 deployment.