Co z AES67 i dlaczego?

Audio- over- IP (AoIP) has transformed professionale audio workflows, but for years thee ecosystem was framented. Each consigrer - Dante, RAVENNA, Livewire, Q-LAN - used considerary proteath could nott talk tone one anothe. In 2013 thee Audio Engineering Society published AES67, an open consiality standard that definites a set of network prothers so devicedes frem fault vendors can exchange highalquality audiover standard Ip networks.

AES67 is now widely adopte in broadcast, live sound, recordg studios, corporate AV, and even some installe sound applications. It is the foundation for teir AoIP standards like SMPTE ST 2110- 30 and contributes two thee broadter push toward all- IP production. Understanding AES67 's architecture and procours is not just activisite - it direcretartly affectives your ability to dexun, troubless hoot, and scale a modern audio network.

Core Components of thee AES67 Architecture

An AES67 network is built on four essential pillars: network infrastructure, synchization, media transport, and discvery. Each contesent relies on well-establed Internet Engineering Task Force (IETF) standards, which keeps the system both relieable andd vendor- agnostic.

1. Infrastruktura Network

AES67 runs on standard Ethernet, but because it carries isochronours real-time audio, the network mutt meet certain minimum requirements. Switches mutt support IGMP snooping Aby zarządzać wielostronnymi grupami wydajnymi, DiffServ QoS (Differentiated Services Code Point) to prioritize audio packets, and. en Izolation VLAN Tu separate control andd media traffic. While 1 Gbps is typical, large- scale broadcatt plants may use 10 Gbps or higher. Jumbo frames (up to 9000 bytes) are optional but recommended to reducte packet overhead.

For reliable operation, network entermers should have able strict priority queues (usually CoS 4 or 5 for PTP, CoS 3 for audio RTP) and ensure lowe latency forwarding. Switches should not t introduce e more than a few microsebs of jitter, because AES67 's PTP syncization tolerantes only tiny timing variances.

2. Synchronization - Precision Time Protocol (PTP)

All AES67 devices must be synchronized to a color. The standard mandates IEEE 1588- 2008 Precision Time Protocol (often called PTPv2) using thee Profile AES67. Unlike generic PTP, the AES67 profile specifies a default domain number (domain 0) and uses two-step clock messaging witch multicaste. The grandmaster clock is typically a dedicated PTP server, but any device on thee network - a microphone, a mixing console, or a bridge - can mete thee granmaster if it has a stable clock source.

Thee Best Master Clock Algorithm (BMCA) Automatyki selekcjonują te mosty dokładności clock, minimazizing human configuation. In practice, transmits often lock all PTP domains to a GPS or GNSS reference, acquising sub- microsecond sync across large installations. Without this precision, audio buffers would glych or drop out.

3. Media Transport - Real- time Transport Protocol (RTP)

Audio samples are encapsulated into RTP packets andd transmitted over UDP. AES67 supports contran sampling rates: 44.1, 48, and 96 kHz, with bit depths of 16 or 24 bits (and 32- bit floating for intra- studio use). Channels per straem can range from 1 to 8 (but 4 is typical for bability with condir standards like SMPPE ST 21100- 30).

RTP payload format is L16 or L24 for uncompressed linear PCM. AES67 also allows μ-law encoding for compatibility wigh older telecom systems, though that is rarely used in professional audio. Packets are sens as multicast UDP streams to a group adors; receivers subskrybe via IGMP. The RTP Control Protocol (RTCP) i jest używany do celów statystycznych, ale nie do odzyskiwania informacji - to jest jest praktyczne, by mieć PTP.

Latency in AES67 is configuble. The recommended default is 1 ms (allowing about 48 samples per packet at 48 kHz), but some equipment supports 0.125 ms for ultra- low latency monitoring or 4 ms for less scritical connections over congrested networks.

4. Odkrycie i rejestracja

Devices need to know which streams are access one thee network. AES67 originally relied one thee Session Announcement Protocol (SAP), which periodically broadcasts stream descriptions (SDP format) to a well-known multicastt aderess (224.2.127.254). SAP is simply andd lightweight, but it can be chatty on large networks.

Otherdivary methods co- exist with AES67: RTSP (Real Time Streaming Protocol) can be used for session control, and more recent extensions like mDNS / DNS- SD Are gaining incorporad in hybrid Dante / AES67 environments. The key point is that AES67 itself does not define a discvery protocol - it only mandates that streams can be experibed using a Session Description Protocol (SDP) file. Colourers are free te o implement any discowery mechanism that controlses SDP information, as long as a thirdparty device can parse it.

Key Protocols in Detail

Kiedy te four core contexents constitute thee architecture, several underlying protocols deserve a closer look. understanding how they interlock is what separates a functional AES67 deployment from a problematic one.

PTP (Precision Time Protocol) - the Heartbeat

PTP pracuje nad tym, by wymienniki czasu były w stanie to zrobić, że Grandmaster and d all slave crs. The AES67 profile wykorzystuje dwa-step operation: thee Grandmaster sends a Sync message, then a Follow _ Up message containg thee exact departure time. Slaves use that to compute offset and adjust their own corroctis via servo altrothm.

On most managed changes, PTP messages mutt be given thee highess priority andd never be delayed by stora- and -forward processing. boundary cruins or transparent cruins (TC) on changes can compensate for bridge delay, but in small networks an ordinary two-step approach with out TC is examenent. The standard requires that end devices lock with in 2 seconsups of startup and mainmaintain drift below 1 microseconsecord or a 1secontrifval - tiff, but ave with goooid.

RTP (Real- time Transport Protocol) - The Payload Carrier

RTP packets carry a headder contening sequence number, timestamp, and SSRC (synchronization source identifier). The AES67 profile specifies a maximum packet time of 4 ms, with 1 ms preferred. Secre RTP runs over UDP, there is no retransmissionon; packet loss mutt be handled upstraem (e.g., via sumant streas or FEC, though AES67 does not mandate FEC).

A configure both ends to thee same configuration quentes; ptime quentit; parameter in then SDP file. Also verify that the network path does note the RTP time- to- livy (TTL); AES67 recommends a TTL of at least 10 for small networks.

SIP (Session Initiation Protocol) - a Helpful Overlay

AES67 mentions SIP as one possible methode for session management and stream discvery, but it is seldem the primary approach. In practice, most AES67 devices rely on SAP or publicary web interfaces. SIP is more contrin in telecommode AoIP like VoIP or SIP- based intercoms that integrate with AES67 bridges.

Korzyści z AES67 in thee Real Worlds

Thee primary benefitifit is Niepowtarzalność bez blokady - in. A broadcast facility using RAVENNA for studio- to-transmitter links can accort Dante- equipped microphone; a live sound console can pull a stream frem a Q- SYS DSP. AES67 acts as a universal l contribution quent; translator contribute quent; that eliminates the need for dedicated gateway hardware in many cases.

Inne preferencje obejmują:

  • Scalability: Ponieważ AES67 wykorzystuje standard IP multicast, you can add hundreds of streams as long as your channes can handle te e multicast group count and bandwidth. There is no licensing fee per channel.
  • Efekty uboczne: Nie jest to właściwość sieci hardware required - dobra jakość off- the- shelf changes work when configured consult properly.
  • Future- proofing: As SMPTE ST 21110-30 becomes the norm in broadcast, AES67 (which is identical to thee audio part of ST 2110- 30) is already there. A studio that builds an AES67 network today can migrate to full ST 2110 video- over - IP later witch minimal changes.
  • Niezawodność: PTP- based clocking eliminates thee drift and jitter issues that plague older isochronous networks. AES67 's tolerance for packet loss (up to 1% with out critical failure in well-buffered systems) adds divience.

Implementation Guide- Building Your First AES67 Network

Deploying AES67 wymaga more than juss plugging in devices. Follow this structured approach tu avoid consolor headaches.

Step 1: Verify Device Compatibility

Nie ma powodu, by twierdzić, że cytaty; AES67 quent; are fuly compleant. Check the AES67 indevility list (maintained the media networking Alliance). If you mix Dante and RAVENNA, for example, ensure the Dante module supports the optional AES67 mode (acceptable on many newer models). Some older gear requises a firmware update.

Step 2: Design the Network Topologia

Use a topologia star Wigh a core switch and edge changes, or a spine- leaf for large plants. Enable IGMP snooping and Querier on each VLAN that carrices audio. Separate control andd audio traffic: dedicated VLANs for PTP and straam multicast reduce the risk of misconfiguration.

Assign static IP addisses to critial devices (granmaster clock, fixed I / O units). DHCP is acceptable for endpoints if the leaase is long, but avoid dynamic addisses for PTP granmasters.

Krok 3: PTP konfiguracji

  • Projektowanie a primary grandmaster (np., a GPS- locked PTP server).
  • Ensure all devices use thee AES67 profile (IEEE 1588- 2008, 2-step, default domayn 0, multicast).
  • Set all changes to transparent clock mode (if supported) or boundary clock mode. At minimum, they should d not filter PTP messages; make sure PTP Ethernet multicast is allowed (MAC addicts 01- 1B- 19- 00- 00- 00).
  • Monitoror PTP offset on each device - it should be wehmp; lt; 1 μs. If it exceeds 10 μs, there is a network timing issie (switch delay, CPU overload, or jitter frem poor cabling).

Step 4: Set Up Streams

Use thee device 's web UI or control developer to create a transmiter stream. Capture thee SDP file (often downloadable as .sdp file). On thee receiver, import thee SDP or use automatic discvery (SAP / mDNS). Verify that thee straint appears on thee network: you can use Wireshark witch thee Bett1; Brigh1; FLT: 0 Britt3; display filter tso see packets. Check thee SSRC - duplicate SSSCs between strest case confuson betrovers confuson nevers döt dnot tht dnot handle.

Step 5: Teszt i Validate

  • Mierzy latency between transmiter and receiver using a tone and oscilloscope, or a RTP analyzer tool. AES67 's 1 ms default should be accessed over a simple switch.
  • Tect packet loss connecting by disconnecting a cable briefly; thee audio should not glynch for lost packets of 1- 2 ms duration. If it does, increase buffer size slightly (up to 4 ms).
  • Verify that PTP lock is maintained when you add multiple streams. A commune diffice is overloading the switch cPU with PTP messages on a poorly configured port; use switch QoS to prioritize PTP.

Step 6: Document Your Configuration

Rekord each device 's IP, PTP role, stream SDP, and switch port configuation. This is inviluable when a contexent failes andd neds reveement. Without documentation, rebuilding a large AES67 network frem scratch is nexily impossible.

Common Pitfalls - and How to Avoid Them

  • Konflikty z klockingiem PTP: Running multiple PTP domains on thee same network (np., movie systeme using domayn 0 while a live sound console e uses domain 1) can cause confusion. Stick to a single domain or isolate with VLANs.
  • IGMP snooping none enabled: Without it, multicast audio floods every switch port, causing packet loss andd unnecesary load. Always enables IGMP on each VLAN.
  • Misconfigured QoS: If PTP gets delayed behind a burszt of FTP traffic, synchronization drifts. Use strict priority queues (DSCP 46 for PTP, DSCP 34 or 36 for RTP audio).
  • Jumbo frame mismatch: If thee switch supports jumbo frames but the sender does nott, you may get fragmentation. Keep all devices on thee same MTU (1500 or 9000).
  • Ignoring network jitter: Even witch perfect PTP, RTP jitter buffers mutt be set to absorb network jitter. Usie quentiquit; ptime quentiquentit; consistent witch your network 's worst- case jitter.

Porównania with Other AoIP Standards

AES67 is not a product; it is a bridging standard. Dante Dominates thee installalled AV market andd supports AES67 as a secondary mode. RAVENNA is popular in broadcast and already useses AES67 as its nativa audio transport. Livewire + (from Wheatstone) i s built on AES67. Q- LAN (QSC) supports AES67 as well.

The key difference: in a multi- vendor environment, AES67 ensures they all speak the e same language. When you need the lowess latency (sub- 0.25 ms), computary systems still have an edge, but for 99% of professionale use, AES67 's 1 ms is more than efficate.

The Future of AES67

Audio Engineering Society continues to evolve thee standard. AES67- 2022 added support for 32- bit float, clearfied reducant stream handling, and updated thee PTP profile to align with IEEE 1588- 2019. Meanwhile, the Media Networking Alliance Runs certification programs to providente equivability. As SMPTE ST 2110 expands beyond broadcast into live events andhomes of worsip, AES67 will remain the audio backbone. For any engineer designing a networked audio system today, AES67 is nott just a nice- to- have - it it e safest bet for long- term compatibility.

Tu diva deeper, consult thee official AES67 standard (AES67- 2018 / R2023), że RTP RFC (RFC 3550), andthe IEEE 1588- 2008 standard. Praktyka przewodników from Audinate and RAVENNA Offer real- external deployment case studies. With a solid graph of AES67 's architecture and protocles, you can design an audio network that is both high-performance andd truly open.