| AES67 | |
|---|---|
| Manufacturer info | |
| Manufacturer | Audio Engineering Society |
| Development date | September 2013; 11 years ago (September 2013)[1] |
| Network compatibility | |
| Switchable | Yes |
| Routable | Yes |
| Ethernetdata rates | Agnostic |
| Audio specifications | |
| Minimumlatency | 125 μs to 4 ms |
| Maximum channels per link | 120 |
| Maximumsampling rate | 48, 44.1, or 96 kHz[1] |
| Maximumbit depth | 16 or 24 bits[1] |
AES67 is atechnical standard foraudio over IP andaudio over Ethernet (AoE) interoperability. The standard was developed by theAudio Engineering Society and first published in September 2013. It is alayer 3 protocol suite based on existingstandards and is designed to allow interoperability between various IP-based audio networking systems such asRAVENNA,Wheatnet,Livewire,Q-LAN andDante.
AES67 promises interoperability between previously competing networked audio systems[2] and long-term network interoperation between systems.[3] It also provides interoperability with layer 2 technologies, likeAudio Video Bridging (AVB).[4][5][6] Since its publication, AES67 has been implemented independently by several manufacturers and adopted by many others.
AES67 defines requirements for synchronizing clocks, setting QoS priorities for media traffic, and initiating media streams with standard protocols from theInternet protocol suite. AES67 also defines audio sample format and sample rate, supported number of channels, as well as IP data packet size and latency/buffering requirements.
The standard calls out several protocol options for device discovery but does not require any to be implemented.Session Initiation Protocol is used for unicast connection management. No connection management protocol is defined for multicast connections.
AES67 uses IEEE 1588-2008Precision Time Protocol (PTPv2) for clock synchronisation. For standard networking equipment, AES67 defines configuration parameters for a "PTP profile for media applications", based on IEEE 1588 delay request-response sync and (optionally) peer-to-peer sync (IEEE 1588 Annexes J.3 and J4); event messages are encapsulated in IPv4 packets over UDP transport (IEEE 1588 Annex D). Some of the default parameters are adjusted, specifically, logSyncInterval and logMinDelayReqInterval are reduced to improve accuracy and startup time.Clock Grade 2 as defined inAES11 Digital Audio Reference Signal (DARS) is signaled with clockClass.
Network equipment conforming to IEEE 1588-2008 uses default PTP profiles; for video streams,SMPTE 2059-2 PTP profile can be used.
In AVB/TSN networks, synchronization is achieved withIEEE 802.1AS profile for Time-Sensitive Applications.
The media clock is based on synchronized network time with an IEEE 1588 epoch (1 January 1970 00:00:00 TAI). Clock rates are fixed at audio sampling frequencies of 44.1 kHz, 48 kHz and 96 kHz (i.e. thousand samples per second). RTP transport works with a fixed time offset to network clock.
Media data is transported in IPv4 packets and attempts to avoidIP fragmentation.
Real-time Transport Protocol withRTP Profile for Audio and Video (L24 and L16 formats) is used over UDP transport. RTP payload is limited to 1460 bytes, to prevent fragmentation with default Ethernet MTU of 1500 bytes (after subtracting IP/UDP/RTP overhead of20+8+12=40 Bytes).[7]Contributing source (CSRC) identifiers and TLS encryption are not supported.
Time synchronization, media stream delivery, and discovery protocols may useIP multicasting withIGMPv2 (optionally IGMPv3) negotiation. Each media stream is assigned a unique multicast address (in the range from 239.0.0.0 to239.255.255.255); only one device can send to this address (many-to-many connections are not supported).
To monitorkeepalive status and allocate bandwidth, devices may use RTCP report interval, SIP session timers and OPTIONS ping, or ICMP Echo request (ping).
AES67 usesDiffServ to set QoS traffic priorities in the Differentiated Services Code Point (DSCP) field of the IP packet. Three classes should be supported at a minimum:
| Class name | Traffic type | Default DiffServ class (DSCP decimal value) |
|---|---|---|
| Clock | IEEE 1588-2008 time events * | EF (46) |
| Media | RTP / RTCP media streams | AF41 (34) |
| Best effort | IEEE 1588-2008 signaling, discovery and connection management | DF (0) |
250 μs maximum delay may be required for time-critical applications to prevent drops of audio. To prioritize critical media streams in a large network, applications may use additional values in the Assured Forwarding class 4 with low-drop probability (AF41), typically implemented as a weighted round-robin queue. Clock traffic is assigned to the Expedited Forwarding (EF) class, which typically implements strict priority per-hop behavior (PHB). All other traffic is handled on a best effort basis with Default Forwarding.
RTP Clock Source Signalling procedure is used to specify PTP domain and grandmaster ID for each media stream.
Sample formats include 16-bit and 24-bitLinear PCM with 48 kHz sampling frequency, and optional 24-bit 96 kHz and 16-bit 44.1 kHz. OtherRTP audio video formats may be supported. Multiple sample frequencies are optional. Devices may enforce a global sample frequency setting.
Media packets are scheduled according to 'packet time' - transmission duration of a standard Ethernet packet. Packet time is negotiated by the stream source for each streaming session. Short packet times provide low latency and high transmission rate, but introduce high overhead and require high-performance equipment and links. Long packet times increase latencies and require more buffering. A range from 125 μs to 4 ms is defined, though it is recommended that devices shall adapt to packet time changes and/or determine packet time by analyzing RTP timestamps.
Packet time determines RTP payload size according to a supported sample rate. 1 ms is required for all devices. Devices should support a minimum of 1 to 8 channels per stream.[7]
| Packet time | Samples per packet | Notes | |
|---|---|---|---|
| 44.1 / 48 kHz | 96 kHz | ||
| 125 μs | 6 | 12 | Compatible with AVB Class A |
| 250 μs | 12 | 24 | High-performance low-latency operation. Compatible with AVB Class B, interoperable with AVB Class A |
| 333+1⁄3 μs | 16 | 32 | Efficient low-latency operation |
| 1 ms | 48 | 96 | Required packet time for all devices |
| 4 ms | 192 | 384 | Wide area networks, networks with limited QoS capabilities, or interoperability withEBU 3326 |
| Audio format | Packet time | ||||
|---|---|---|---|---|---|
| 125 μs | 250 μs | 333+1⁄3 μs | 1 ms | 4 ms | |
| 48 kHz / 16 bit | 120 | 60 | 45 | 15 | 3 |
| 48 kHz / 24 bit | 80 | 40 | 30 | 10 | 2 |
| 96 kHz / 24 bit | 40 | 20 | 15 | 5 | 1 |
Network latency (link offset) is the time difference between the moment an audio stream enters the source (ingress time), marked by RTP timestamp in the media packet, and the moment it leaves the destination (egress time). Latency depends on packet time, propagation and queuing delays, packet processing overhead, and buffering in the destination device; thus minimum latency is the shortest packet time and network forwarding time, which can be less than 1 μs on a point-to-point Gigabit Ethernet link with minimum packet size, but in real-world networks could be twice the packet time.
Small buffers decrease latency but may result in drops of audio when media data does not arrive on time. Unexpected changes to network conditions and jitter from packet encoding and processing may require longer buffering and therefore higher latency. Destinations are required to use a buffer of 3 times the packet time, though at least 20 times the packet time (or 20 ms if smaller) is recommended. Sources are required to maintain transmission with jitter of less than 17 packet times (or 17 ms if shorter), though 1 packet time (or 1 ms if shorter) is recommended.
AES67 may transport media streams asIEEE 802.1BA AVB time-sensitive traffic Classes A and B on supported networks, with guaranteed latency of 2 ms and 50 ms respectively. Reservation of bandwidth with theStream Reservation Protocol (SRP) specifies the amount of traffic generated through a measurement interval of 125 μs and 250 μs respectively. Multicast IP addresses have to be used, though only with a single source, as AVB networks only support Ethernet multicast destination addressing in the range from 01:00:5e:00:00:00 to 01:00:5e:7f:ff:ff.
An SRP talker advertise message shall be mapped as follows:
| StreamID | A 64-bit globally-unique ID (48-bit EthernetMAC address of the source and 16-bit unique source stream ID). |
|---|---|
| Stream destination address | Ethernet multicast destination address. |
| VLAN ID | 12-bit IEEE 802.1Q VLAN tag. Default VLAN identifier for AVB streams is 2. |
| MaxFrameSize | The maximum size of the media stream packets, including the IP header but excluding Ethernet overhead. |
| MaxIntervalFrames | Maximum number of frames a source may transmit in one measurement interval. Since allowed packet times are greater than (or equal to) AVB measurement intervals, this is always 1. |
| Data Frame Priority | 3 for Class A, 2 for Class B. |
| Rank | 1 for normal traffic, 0 for emergency traffic. |
Under both IEEE 1588-2008 and IEEE 802.1AS, a PTP clock can be designated as an ordinary clock (OC), boundary clock (BC) or transparent clock (TC), though 802.1AS transparent clocks also have some boundary clock capabilities. A device may implement one or more of these capabilities. OC may have as few as one port (network connection), while TC and BC must have two or more ports. BC and OC ports can work as a master (grandmaster) or a slave. An IEEE 1588 profile is associated with each port. TC can belong to multiple clock domains and profiles.These provisions make it possible to synchronize IEEE 802.1AS clocks to IEEE 1588-2008 clocks used by AES67.
The standard was developed by theAudio Engineering Society beginning at the end of 2010.[8] The standard was initially published September 2013.[9][10][11][12] A second printing which added a patent statement fromAudinate was published in March 2014.
The Media Networking Alliance was formed in October 2014 to promote adoption of AES67.[13]
In October 2014 aplugfest was held to test interoperability achieved with AES67.[14][15] A second plugfest was conducted in November 2015[16] and third in February 2017.[17]
An update to the standard including clarifications and error corrections was issued in September 2015.[1]
In May 2016, the AES published a report describing synchronization interoperability between AES67 andSMPTE 2059-2.[18]
In June 2016, AES67 audio transport enhanced byAVB/TSN clock synchronisation and bandwidth reservation was demonstrated at InfoComm 2016.[19]
In September 2017,SMPTE published ST 2110, a standard forprofessional video over IP.[20]ST 2110-30 uses AES67 as the transport for audio accompanying the video.[21]
In December 2017 the Media Networking Alliance merged with the Alliance for IP Media Solutions (AIMS) combining efforts to promote standards-based network transport for audio and video.[22]
In April 2018 AES67-2018 was published. The principal change in this revision is addition of aprotocol implementation conformance statement (PICS).[23]
TheAES Standards Committee and AES67 editor, Kevin Gross, were recipients of aTechnology & Engineering Emmy Award in 2019 for thedevelopment of synchronized multi-channel uncompressed audio transport over IP networks.[24]
The standard has been implemented byLawo,[25] Digisynthetic,[26]Axia,[27] AMX (in SVSI devices), Wheatstone,[28][29]Extron Electronics,Riedel,[30]Ross Video,[31][32]ALC NetworX,[33]Audinate,[34] Archwave,[35] Digigram,[36] Sonifex,[37] Aqua Broadcast,[38]Yamaha,[39]QSC,[40] Neutrik, Attero Tech,[41]Merging Technologies,[42][43] Gallery SIENNA,[44]Behringer,[45] Tieline[46] and is supported by RAVENNA-enabled devices under its AES67 Operational Profile.[47]
Over time this table will grow to become a resource for integration and compatibility between devices. The discovery methods supported by each device are critical for integration since the AES67 specification does not stipulate how this should be done, but instead provides a variety of options or suggestions. Also, AES67 specifies multicast and unicast but many AES67 devices only support multicast.
| Vendor | Product | Description | OS | AES67 Model | Send | Receive | Multicast | Unicast | Notes | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Win | MacOS | Linux | SAP | mDNS /RTSP | NMOS | SAP | mDNS /RTSP | NMOS | |||||||
| Merging Technologies | Virtual Audio Device[48] | Ravenna/AES67 drivers |  Y | Y [49] | Y [50] | Ravenna AES67 | Y | Y | Y | Y | Y | Y | free | ||
| ALC Networks | Virtual Sound Card[51] | Ravenna/AES67 WDM driver | Y | Ravenna AES67 | Y | free | |||||||||
| RAV2SAP[52] | AES67 Discovery Tools | Y | Ravenna AES67 | Y | Y | Y | free | ||||||||
| Sienna | AES67 to NDI Gateway[44] | AES67 to NDI Gateway | Y | Y | Y | Native AES67 | Y | Y | Y | Y | |||||
| NDI to AES67[53] | NDI to AES67 Sender | Y | Y | Native AES67 | Y | Y | Y | Y | |||||||
| Lawo | VRX4[54] | Audio Mixer | Y | Ravenna AES67 | Y | ||||||||||
| Hasseb | AoE[55] | AES67 Interface: analog and optical | Native AES67 | Y | Y | Y | Y | ||||||||
| QSC | DSP, Amplifiers[56] | various | Q-SYS AES67 | Y | Y | Y | |||||||||
| Axia | Various[57] | various | Livewire+ AES67 | Y | Y | ||||||||||
| Yamaha | Mixers[58] | various | Dante AES67 | Y | Y | Y |  N | ||||||||
| Aqua Broadcast | Cobra FM Transmitters[38] | AES67 Dante input | Dante AES67 | Y | |||||||||||
| Attero Tech | Endpoints[59] | Endpoints | Attero AES67 | Y | Y | Y | N | ||||||||
| SoundTube Entertainment | Various[60] | Various | Dante AES67 | Y | Y | Y | N | ||||||||
| Behringer | Wing[45] | Digital mixer | Dante AES67 | Y | Y | Y | N | ||||||||
| Tieline | Gateway, Gateway 4[61] | Audio Codecs | Y | Ravenna AES67, Livewire+, WheatNet-IP [clarification needed] | Y | Y | Y | Y | Y | Y | |||||
| Cisco | Collaboration devices[62] | Interoperability with microphones and speakers | Native AES67 | Y | Y | Y | |||||||||
| Digisynthetic | DL08[63] | AES67+DSP Network Module | Y | Y | Digisyn Link AES67 | Y | Y | Y | |||||||
| 2-Channel Virtual Sound Card[64] | Digisyn Link/AES67 WDM driver | Y | Digisyn Link AES67 | Y | Y | Y | free | ||||||||
{{cite journal}}:Cite journal requires|journal= (help){{cite journal}}:Cite journal requires|journal= (help){{cite journal}}:Cite journal requires|journal= (help){{cite journal}}:Cite journal requires|journal= (help)