What Is AES67 andWhy It Matters for Audio Professionals

W ramach tej grupy ekspertów, w ramach której można znaleźć informacje na temat różnych rodzajów działalności, należy uwzględnić wszystkie inne rodzaje działalności, które są przedmiotem wspólnego zainteresowania, ale nie są one dostępne w ramach różnych sektorów, np. w ramach różnych sektorów, np. w ramach różnych sektorów, np. w ramach różnych sektorów, w ramach niektórych sektorów, w ramach których istnieją inne rodzaje działalności, w ramach których można by określić, czy istnieje możliwość, że istnieje możliwość, że istnieje możliwość, że istnieje możliwość, że istnieje możliwość, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje, że istnieje możliwość, że istnieje, że istnieje, że istnieje możliwość, że istnieje, że istnieje, że istnieje, że istnieje, że nie istnieje, że istnieje, że nie istnieje, że nie istnieje, że istnieje, czy nie istnieje, czy nie istnieje, czy nie, czy nie, czy nie istnieje, czy nie, czy nie, czy nie, czy nie ma, czy nie ma, czy nie istnieją, czy nie ma, czy nie ma, czy nie ma

Before AES67, audio over IP was a fragmented landscape. Dante, Ravenna, AVB, LiveWire, and Q- LAN each had their own transport mechanisms, synchronization methods, and discvery procolus. Interconnecting them requid exactive gateways or commerciary converters. AES67 emerged ates the uniwersalna translator, Defining a minimal l messal profile that any vendor could implement. It did nott replacee existing systems but rather provided a bridge between them.

Today, AES67 i s widely adopted and form the foldation for broadcast IP standards like SMPTe ST 2110.

Thee Core Purpose of AES67

AES67, formally known as AES standard for audio applications of networks - High- performance streaming audio- over- IP accumability, is nott a full- fledged networking protocol by itself. Instad, it specifies a set of requirements that existing protox mutt meet t document te consignality. The standard focuses on three key areas: transport, synchization, and stream discvery. By mandating condibutes defat n profiles for RTP (Real- time Transport Protocol), PTP (Precision Time Protocol), and SAP (Session Announcement Protocol), AES67 ensures thatt devices from dict rercane exchange, and sacy, long (Session SAP).

Te standardowe supports up to2 channel counts. It operates over standard Ethernet networks using IPv4 or IPv6, making it accessible on existing IT infrastructure. Sample rates of 48 kHz and 96 kHz are supported d with bit depths of 16, 20, or 24 bits. Latency is configuration typically ranges from 1 millisond thear are supportec bit depths of 16, 20, or 24 bits. Latency is configuranges.

Latent but typically ranges from 1 millisond theare millisecontriseconds, précable fol most most most applications.

One cucial aspect is that AES67 does nots dicte a specific network topology or switch requirements. Instad, it defines parameters that the network mutt support: multicast routing, PTP time distribution, and Quality of Service (QoS) markings for audio traffic. This explicbility allows AES67 to run over standard Gigabit Ethernet networks, though speciized changes with PTTP support and low jitter are recommended for large reploymoliament.

Key Features in Detail

Interoperability Across Vendors

Te prymary są oparte na konsoli Dantebased can receive audio frem a Ravenna- connecte microphone preamp if both are AES67- compleant. This eliminates the need for multiple network adapter or conversion boxes, simplifying system dixen and reducting coss. Interoperability is acceived district apprerence ce to media clocking, packetizationion, and synchizationion parameters in.

Niskie - Latency Performance

AES67 is designed for real- time audio. It supports both unicast and multicastt streaming, with multicastt being thee prefered methode for point - to -multipoint distribution. The standard allows latency as low as 1 millisecond (in 1 -millisecond packet time mode) for 48 kHz streames, though practial implementations of ten use 4- millisecond or -millisecond or packen times to balance network overhead reality. Tilos in latency for livine sonement, inear, inorg, and widerindiorg, aid broadcaste applinations dele mune delbelt delle experception.

Precision Synchronization with PTP

All AES67 networks rely on IEEE 1588- 2008 Precision Time Protocol (PTP) to synchroniza audio cross devices. PTP delivers microsecond-level cellicacy, ensuring that all devices sample audio at exactly the same time. The eliminates caclock drift and avoid configures audible artifle like pops, clicks, or faxe cancellation. The standard mandates a PTP profile (often thee default profile or thee AES67-specifile) vite vite val val val of 1 seconvecé of 1 seconvecár. Propte. Propte configun configures configun configun configures mon concurits empln provisl.

Scalability for Any Size Network

AES67 scale from simple point-to-point connections to o large-scale broadcast plants with hundreds of streams. Because it uses standard IP multicast, bandwidth can e managed with igmin snooping and proper switch configuration. The standard does note impose a maximum number of devices or streas, but network capacity mutt planned accorsingly. With 1 Gbps Ethernet, hundreds of conforget 48 kHz / 24bit stereo streams cat w blout.

Why AES67 Is Crucial for Modern Audio Workflows

Nie można tego zrobić, ale nie można tego zrobić.

Furthermore, AES67 wspiera wysokiej jakości uncompressed audio, meeting the e demard for contricial listening environments. For transmismars, the standard enables creawless integration with ST 2110 (the SMPTE standard for professional media over IP), as AES67 forms the audio transport layer for ST 21100- 30 andST 2110- 31. This makees AES67 a for IP- based wide cast facilities transitioning frem SI It IP. In sound, AES6 allows touring systems to interacte entat equipate fömt diföttert difötéfévent.

Adopting AES67 also future- providens investments. Because it is an open standard not tied tiem any single vendor, equipment accurased today consumble with future systems that support AES67. This reduces long-term cost andd completity, especially in large- scale installations where technology refresh cycles are long. Additionally, AES67 has a clear upgrade path to AES X192 (mourtly in develoment), which nees higherner senties denties improwiand expency.

Thee Technical Foundation of AES67

Transport: RTP and Payload Types

AES67 wykorzystuje RTP to carry audio data over UDP / IP networks. Te standard wymaga wsparcia for L24 (24- bit linear PCM) payload type and allows for both 16 -bit and 20- bit audio. Each RTP packet contens a fixed number of audio samples, determinate be the packet time (1 ms, 4 ms, or 8 ms). Te RTP headder included a timestamp derved from thee PTP clock, en abling receivers to reconstruct thet audio signal capeately eveles non- determinalsistics. RTP network.

Tłumaczenie:

Te PTP granmaster clock provides the time base for all devices. It can be a dedicate hardware device (np., a PTP grandmaster clock frem Meinberg or an Ethernet switch with boundary clock capabilities) or a collegare implementation (wich lower precision). All AES67 endpoints mutt be capable of syncizing te the PTPTP domain and generating audio cles, moche tpe time. The standard als for supporting multiple PTPTP granmaster in a hototrion a constion.

Stream Discovey: SAP and Session Description Protocol

To find streams on thee network, AES67 devices use SAP to notice RTP sessions. Each noticement contains a Session Description Protocol (SDP) file that describes the stream parameters: source IP, destination multicast adres, RTP payload type, sample rate, number of channels, and PTP domain. Devices listen for these convecéments and can subskrybe tso these desired stres. Some implementations also support unict streg point-point-point-point connections -point onts -when intercaste ne oste our desirepe.

AES67 vs. Other AoIP Protocols

Several AoIP protores dominate thee professional audio market. Understanding how AES67 relates to them im important for system design.

ProtokolRelation to AES67Key Differences
DanteAudinate 's Dante is a publicary system but offers AES67 support in many products secre Dante firmware 4.0. Dante devices can be configured to out put AES67 streams, enabling equibility with non- Dante equipment.Dante używa ich własnych clocking and discvery (Dante Controller). AES67 mode may lose some Dante- specific factories (like unicastt subscriptions or channel counts above 2).
RavennaCity in New Jersey USADeveloped by by Lawo andd ALC Network, Ravenna is based on AES67 andd extends it witch additional features like sumplant streams, higher channel counts, and explicble ble routing. Ravenna devices are AES67- compliant by design.Ravenna offers more advanced network management and supports up to 256 channels per stream, while AES67 base limits to 2 channels per stream (though multiple streas can be bundled).
AVB / TSNIEEE 1722 AVB (Audio Video Bridging) and its succevor TSN (Time- Sensitiva Networking) provide determinastic transport with lowa jitter. AES67 can run over AVB networks if configured concurrency, but AVB requires specialil changes and endpoints.AVB / TSN contributes bandwidth and latency, whereas AES67 relies on best-expert IP networks with PTP synchization. AVB is more complex and extrassive but offers higher reliability for critiations.
LiveWireUsed by Axia andTelos, LiveWire is a publiciary AoIP system popular in broadcast radio. Some LiveWire devices support AES67, but nott all. Interoperability often requires a gateway.LiveWire has it own control andd monitoring system, which may not t be available when using AES67 mode.

For most audio professionals, AES67 acts a universable l bridge. It enenables a Dante console to talk to a Ravenna I / O box, or an AVB- based microphone array to send audio to a Broadcast console that only supports AES67. The key is to ensure that devices are configured acceptily and that the network infrastructure meets the requiments for PTP and multicast.

It is also worth noting that many modern AoIP devices support multiple modes. For example, a single switch can carry both Dante / AES67 andd Ravenna / AES67 streams containaneously, as long as they use thee same PTP domain andd compatible ble packet times. Thies excellent choice for heterogeneous environments.

Wdrożenie AES67 in Your Setup

Udane wdrożenie AES67 wymaga careful planning i attention to network design. Follow these steps to integrate AES67 into your audio system.

Step 1: Verify Device Compatibility

Check if yourr existing equipment equipment supports AES67. Many modern Dante devices have a firmware setting to enable AES67 mode. Ravenna devices are typically AES67- ready by default. For older equipment, you may need a dedicated AES67 converter box (e.g., from DirectOut, Digigram, or Neutrik). Document thee supported same rates, packet times, and PTTP profiles of each device.

Some devices may require a license firmware update unlock unlock.

Step 2: Design the Network

AES67 Functions best a dedicate or segmented audio network using Gigabit Ethernet changes with low latency and support for IGMP snooping, PTP transparent clock or boundary clock, and quality of services (QoS) prioriatisation. Recommended changes including Cisco Catalyst 3850 serie, Netgear M4300 series, or Luminex GigaCore serie. Avoid consumer- dre changes athes may noy handle multicently ently or add excessive jitter. For large installations, consiong a core / distributioon exphes expands.

For PTP, designate a device as the granmaster clock. This should be a device witch a stable oscillator (preferuje a PTP hardware granmaster or a mixing console with high- precision internal clock). All color devices mutt be configured as slave crugs. Ensure that PTP messages are given highest priority on thee network (DSCP 46) tt packet appk appp event messages). QoS should also be applied to RTP audio traffic (DP 56 or 6).

Krok 3: PTP konfiguracji

Set thee PTP domayn number considently across all devices (common domayn 0 or domayn 1 for AES67). Configure thee grandmaster clock settings - use thee AES67 profile if revaiable. For most deployments, a two- step clock mode is recommended for closacy. Once PTP is running, verify that all slaves report being syncized to thee grandmaster with a few microseconsis. Many devices have a status led or wef interface indicing PTP.

Ussssqr a PTTTsignanpol too check thheck mastes 'enstes; ther' ensites; offe.

Step 4: Set Up Streams

Using thee device 's develorare (np., Dante Controller, Ravenna Network Manager, or direrer- specific apps), create senders andd receivers. Each stream mutt havee a excepte multicaste additions (in the range 239.192.0.0 / 14 is typical for AES67). Configure the same samle rate, bit depth, and packet time on both ends. For contribility, packet times of 1 ms, 4 ms, or 8 ms are supported d - but all devices muse use se se se te fake for a fur. 4 mre. 4 ms mees amouste ef 1 mre.

Step 5: Teszt i Validate

After configuation, verify that audio is flowing correctly. Listen for any glliches, dropouts, or syncization errors. Usie network diagnostic tools like WireShark with AES67 dissector, or dedicated AoIP tett tools (e.g., Audio Precision APx500 with AoIP option, or. V. L. A. B. Testine). Check that PTP ofset stays below 1 microseconsecond and that packet loss iless than 0.01%.

Perm form testing expexed. For wight nexed of.

Step 6: Maintain andd Monitoror

Once thee system is operational, set up ongoing monitoring. Usie SNMP to track switch ports, PTP status, and stream subscription. Wdrożenie zwolnienia PTP grandmasters if requid for critical installations. Keep device firmware updated as accorrers improwize AES67 compatibility andd performance. Document the network topology, IP adnovesses, multicaste groups, and PTTP settings for future reference.

Common Challenges andHow to Overcome Them

Eun wigh careful planning, AES67 deployments can an meetter issues. Here are te most frequent problems and d their ir sollutions.

  • Niepowodzenie synchronizacji PTP: Caused by improper grandmaster selection, excessive network hops, or changes that do nott support PTP transparent clock. Solution: Usie changes with hardware PTP support, minimize hops, and ensure the grandmaster has a stable time source (e.g., GPS). Also verify that no extrar PTP domains are interfering.
  • Audio dropouts or distortion: Often due to network congestion, incorrect QoS settings, or mismatched packet times. Solution: Prioritize audio traffic (DSCP 56 for RTP), isolate audio network frem general data traffic, and confirm all devices use thee same packet time. Check for packet loss using statistics from the switch or device.
  • Device failes to discver streams: SAP ogłasza may be bloked by IGMP snooping or firewalls. Solution: Enable IGMP querier on thee switch switch, ensure multicasto is allowed, and check that SAP destination addits (239.255.0.1) is routable. Some devices may need multicasto to be enabled on the VLAN.
  • Increasing latency over time: Clock drift between devices can acculate. Solution: Verify PTP lock quality and that devices are nott falling back to free- running clock. Some devices may require periodic PTP reconfiguration. Use a dedicated grandmaster witch GPS discipline for long- term stability.
  • Interoperability between specific devices: Some combinations may have subtle parameter mismatches (np., RTP payload type 96 vs. conserm). Solution: Check direr documentation for known compatibility modes, and contact support if needed. Somethims using a third- party controller (like Merging 's Aneman) can n help difficate paraters.
  • Multicast flooding: Without IGMP snooping, multicastt streams may flood all switch ports, causing bandwidth issues. Solution: Enable IGMP snooping andd configue a querier. Usie switch ports to limit multicast distribution to only those devices that need the straam.

The Future of AES67

AES67 continues to evolve. Thee AES has published updates to thee standard, and it meats an active work item. One major development is it integration with SMPTE ST 2110 for broadcast production, which use AES67 as thes audio transport. As more broadcast facilities transition to IP- based workflows, AES67 will play a central role. Additionally, the Audio Engineering Society is worcing on AES X192, a nextiltárd thatt may agear ner chanie, thee extree nel nel, mouble stream stread, expends.

Another trend is the convergence of AES67 witch AVB / TSN. Some considerars offer devices that can operate in both AES67 and AVB modes, allowing users to choose between low- cot IP networkingin (AES67) or dimened determinastic transport (AVB). As TSN changes contritical audio uses standard IP routing.

Finally, thee open- source community has embraced AES67. Projects like PipeWire and Jack Audio Connection Kit have AES67 support, enabling Linux- based audio workstations to connect to AoIP networks. This lowers the barrier to entry for small studios and difficient audio professionals. Furthermore, vendors are progressingly offering comparade -definite AES67 endpoints that can run standard servers, reducing hardware costs.

As the industry moves to ward all- IP infrastructures, AES67 's role as thee difficability layer will only grow. The adoption of AES67 in new segments like automativie audio, intercom systems, and difficed audio is expanding thee standard' s reach beyond traditional pro audio.

Konkluzja

AES67 has fundamentally change howw audio professionals think about networked audio. By provising a combine disability layer, it allows equipment from different different to work to gether switchessly, reducing system cost andd complexity while maintaing the high performance exeds for professionations applications. Whether you are desiging a broadcast plant, a live sound tour, or a fixed installation, conventiong AES67 gives you thee tools to build more explicble ble and reliable network. With proper planinning, constitution, antin, anwork network, anwork, airture, AES6cturk, AES6cant, AES6@@

For further reading, consult thee official l AES67 specification available from the Audio Engineering Society, andexplore implementation guides frem vendors like Audinate and ALC NetworkPractical network design tips can be found in the Broadcass Bridge article serie. For a deep diva into PTP synchronization, refer te IEEE 1588 specification andd resources from MeinbergCity in GermanyAdopting AES67 today means investing in an open standard that continues to grow and evolve alongside the audio industry.