WIXLIB

AES67-101: The Basics of AES67Anthony P. KuzubIP Audio Product emsTorontoAES.orgVice-Chair

Ward-Beck.Systems - Audio LIFY.audioCONSOLES.audioGROUNDING.audio

The least you SHOULDknow about networking:The physical datalink networkstransported sessionspresented by the application

AES67.audio2110-30.AES67.audioTXDATA7 - Application6 - SING.audio5 - Session4 - TransportROUTING.audioIGMP.audio3 - NetworkSWITCHING.audioCLOCKING.audio2 - Data LinkMULTICASTING.audio1 - PhysicalRJ45.audio

The Road to Incompatibility DanteRAVENNAQLANLivewireControl & MonitoringProprietaryHTTP, Ember TCP, HTTPHTTP, roprietaryConnectionManagementProprietaryRTSP, SIP, IGMPProprietaryProprietary, HTTP, IGMPSession DescriptionProprietarySDPProprietaryChannel #TransportProprietary, IPv4RTP, IPv4RTP, IPv4RTP, IPv4Quality of oding & StreamingL16-32, 4 ch/flowL16-32, 64 cha/str32B-FP, 16 ch/strL24, st, -2008ProprietaryMedia Clock44.1kHz, 192kHz44.1kHz – 384kHz48kHz48kHz

AES67-2013 Standard for audio applications ofnetworks:High-performance streaming audio-over-IPinteroperability

ReferencesAudio Engineering Society, New York, NY., US.AES11 - AES recommended practice for digital audio engineeringSynchronization of digital audio equipment in studio operationsInstitute of Electrical and Electronics Engineers (IEEE)IEEE 1588-2008 - IEEE Standard for a Precision Clock Synchronization Protocolfor Networked Measurement and Control Systems, July 2008AES67-2018 Standard foraudio applications of networks:High-performance streaming audio-over-IP interoperabilityInternet Engineering Task ForceRFC 768 – User Datagram Protocol”RFC 791 – Internet ProtocolRFC 1112 – Host Extensions for IP MulticastingRFC 2236 - Internet Group Management Protocol, Version 2RFC 2474 – Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 HeadersRFC 2616 - Hypertext Transfer Protocol - HTTP/1.1RFC 2974 – Session Announcement ProtocolRFC 3190 – RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled AudioRFC 3261 - SIP: Session Initiation ProtocolRFC 3264 - An Offer/Answer Model with the Session Description Protocol (SDP)RFC 3376 - Internet Group Management Protocol, Version 3RFC 3550 – RTP: A Transport Protocol for Real-Time ApplicationsRFC 3551 - RTP Profile for Audio and Video Conferences with Minimal ControlRFC 4566 – Session Description ProtocolRFC 5939 – Session Description Protocol (SDP) Capability NegotiationRFC 7273 – RTP Clock Source Signalling

AES67.audioDevice ControlConnectionManagementDOMAINS:Control onDescriptionTransportTransportQuality ofServiceEncoding &StreamingSynchronizationTimingMedia KING.audio

AES StandardsAES 3 - Serial Digital AudioAES 10 - Serial Multichannel Audio Digital Interface (sMADI)AES 14 - XLR-type polarity and genderAES 59 - 25 pin D-Sub connectorAES67 - High-performance streaming audio-over-IPAES70 - Audio applications of networks - Open Control Architecture

AES3-1992

AES 10 - MADIAES Recommended Practice for Digital Audio Engineering — SerialMultichannel Audio Digital Interface (MADI)

Data RatesControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

RTP Packets - Required andrecommended packet timesControl &MonitoringPacket samples (48kHz)Packet samples (96kHz)Packet samples (44,1kHz)⅛ millisecond“125 microseconds”6126¼ millisecond“250 microseconds”122412“333 microseconds”163216“1 millisecond”489648“4 milliseconds”192n.a.192EXACT Packet nTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

Layered Packet EncapsulationRTP overhead12 BytesIP UDP RTP overhead20 8 12 40 Bytes1518 / 1522Bytes14/182081214604TrailerMTU (maximum transmission unit, largest size of a packet that can be transmittedwithout being split) 1500 Bytes in an IP/Ethernet LAN: in principle 0 to 1460 bytesavailable for RTP payload data per packet

RTP Packets - Required andrecommended packet timesControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

RTP Packets - Required andrecommended packet timesControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia ClockSMPTE Toronto Section – Toronto Technical Conference (TTC) 2018

RTP Packets - Required andrecommended packet timesControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

RTP Packets - Required andrecommended packet timesControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

2110- 30

AES67 - RX SHALL SUPPORT1ms - 1-8 Channels 48KHz - 24bitControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

SMPTE 2110-30RX CONFORMANCELEVEL A1ms1-8 CHLEVEL C0.125ms1-64 CHLEVEL B0.125ms1-8 CH

AES67Mandatory24bit / 48kHz1ms 1-8 CHNADIST2110-30LEVEL A24bit / 48kHz1ms 1-8 CH

AES67 Solution:AES67 provides the ability to interconnect entire systems and/or campuses basedon different network technologyStadiumRecording StudioStageOutside BroadcastFOH / MONBroadcaster

ANEMAN.AES67.audioControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia ClockConnectionChangeBrokenConnection

Mix and MatchControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

DEVICES INSUBNETSTREAM NAMEOF DEVICEAPI / MANUALSDPCH INSTREAMSTREAM SDPINFORMATIONRAVENNASOURCES

NAME IP ADDRESSPCM AUDIORATECONFIGPTPCONFIGSIPCONFIGSAPCONFIG

SYSTEM CONFIGAPI:STREAM NAME TALENT MIC LINE AES CITY:BUILDING:FLOOR:STUDIOTX AES67SDP:JSONAutomation ControllerPATCHINGaudioRavennaBonjourSAPSIPMANUAL dioROUTING REQUESTRX AES67API:CH NAME SDP:JSONCONSUMER NAME POOL TALENT ANALOG AES

Remote control of deviceapplication functionsControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock device and channel names network settings sample rate, bit rate Status and health monitoring Status reportingAES70Ember EmberMidiSNMPRS232RS485 busCopperlanVISAEuconMackie HUIJSONService DirectoryMade up - UDP / TCP

DISCOVERY.AES67.audioControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock SIP - Session Initiation ProtocolSAP - Session Announcement ProtocolBONJOUR - apple zeroconfAES70 - Connection Management MDNSNMOS SNMPKLV within streamFAST METADATA (SDP extension)

NMOSControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock Stream identificationTimingRelationshipsDiscovery and registrationConnection managementJSON data structures

Session Description Protocolv 0o - 2 0 IN IP4 192.168.110.178s WardBeck 32MEt 0 0a clock-domain:PTPv2 0m audio 50000 RTP/AVP 98c IN IP4 239.30.178.1/100a rtpmap:98 L24/48000/8a framecount:48a sync-time:0a ptime:1a ts-refclk:ptp IEEE1588-2008:EC-46-70-FF-FE-00-8F-C8:0a mediaclk:direct 0v (protocol version number, currently only 0)Control criptionTransportQuality ofServiceEncoding &StreamingSynchronization(originator and session identifier : username, id, version number, network address)s (session name : mandatory with at least one UTF-8-encoded character)t (time the session is active)a * (attribute Clock version and domain)m (media name and transport port and IP addressc * (connection information/TTL)a * (attribute RTP profile / Bit Rate / Sample Rate / Channels)a * (attribute )a * (attribute required by ST2110-30)a * (attribute: Packet Time)a * (attribute)Media Clock/ RTP profile 98)a * (attribute)

OCA Extended SDP TLV - KLVControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clocka OCA:1000:1.1.3:OcaBlock:0:1:BLK Library Librarya OCA:1001::OcaLibrary:0:1e6:Application 222a OCA:1002::OcaLibrary:0:1e6:Preset 57575a OCA:1003::OcaLibrary:0:1e6:Microphone 23452345a OCA:10000:1.1.3:OcaBlock:0:5:preAMP 1 Kick Druma OCA:10001:1.1.1.4:OcaSwitch:0:1:Phantom 1a OCA:10002:1.1.1.4:OcaSwitch:0:1:Phase Invert 0a OCA:10003:1.1.1.4:OcaSwitch:0:1:Input(MIC/LINE) 0a OCA:10005:1.1.1.5:OcaGain:0:63:Pre Amp Gain 45a OCA:10100:1.1.3:OcaBlock:0:3:DSP Input 1 2a OCA:10101:1.1.1.4:OcaSwitch:0:1:HPF Enable 1a OCA:1000 Librarya OCA:1001 222a OCA:1002 57575a OCA:1003 23452345a OCA:10000 Kick Druma OCA:10001 1a OCA:10002 0a OCA:10003 0a OCA:10005 45a OCA:10100 2a OCA:10101 1

http://MULTICASTING.audioNetwork Layer(3) : (one-to-many)Control &Monitoring Only one connection per stream on transmitter sideDiscovery Network traffic increases on last (closest to receiver) segment(s) ofnetwork path tQuality ofServiceEncoding &StreamingSynchronizationMedia Clock Switches copy packets as required IETF RFC 1112 “Host Extensions for IP Multicasting”

QoS – Differentiated Services(DiffServ)Control &MonitoringClass nameTraffic typeDefault DiffServ class (DSCPdecimal value)ClockIEEE 1588-2008 Announce, Sync, Follow Up, Delay Req,Delay Resp, Pdelay Req, Pdelay Resp andPdelay Resp Follow Up packetsEF (46)MediaRTP and RTCP media stream dataAF41 (34)BesteffortIEEE 1588-2008 signaling and managementmessages. Discovery and connectionmanagement messages.DF TransportQuality ofServiceEncoding &StreamingSynchronizationMedia Clock

IEEE1588 Precision Time Protocol (PTP)PTP DomainLogical grouping of clocks that are synchronised to each other using PTP, but may not be synchronised to other clocks inControl criptionanother domainGrandmaster clock (GM)A grandmaster clock is the highest-ranking clock within its PTP domain and is the primary reference source for all otherPTP elements.Master Clock (Mode)A clock that is the source of time to which all other clocks in thatTransportQuality ofServiceEncoding &StreamingSynchronizationynchronizationdomain are synchronisedSlave clockA slave clock receives the time information from a master clock bysynchronizing itself with the master clock. It does not redistribute thetime to another clock. In the data center, servers are typically PTPslave clocks.Media Clock

IEEE1588 Precision Time Protocol (PTP)Ordinary clockControl criptionTransportQuality ofServiceEncoding &StreamingSynchronizationynchronizationMedia ClockAn ordinary clock is a PTP clock with a single PTP port. It could be a master clock (grandmaster) or a slaveclock.Boundary clock (BC)A boundary clock is the intermediary device between a PTP grandmaster and its PTP slave clients. It hasmultiple PTP ports in a domain and maintains the time scale used in the domain. Different ports on theboundary clock can be master ports or slave ports. The boundary clock terminates the PTP flow, recovers theclock and time stamp, and regenerates the PTP flow. Effectively, there is a slave port to recover the clock andmaster ports to regenerate the PTP packets.Transparent clock (TC)A transparent clock measures the time needed for a PTP event message to transit the device and thencompensates for the packet delay.

AES67 PTP Media Profile:Control criptionTransportQuality ofServiceEncoding &StreamingSynchronizationMedia ClockDelay Mechanism: E2EAnnounce Interval: 2 secsAnnounce Timeout: 3 secsSync Interval: 1/8 secDelay Req Interval: 1 secPeer Delay Req Interval: 1 secPriority 1: 128Priority 2: 128Domain: 0Slave Only: DisabledAnnounce Timeout –time to wait for anannounce message and is a multiple of announceintervals. No announce messages are received withinthe timeout interval, the unit will assume the role ofgrandmaster.Sync Interval – Rate that one sync message issent. The sync and follow up messages are sent fromthe master to the slave to determine the difference inclock frequency. This information is used in conjunctionwith the network delay to synchronise the clocks.Delay Req Interval – rate at which a slave clocksends delay request messages to the master. The delayrequest message allows a slave device to calculate thenetwork delay from the slave to the master. This optionis only valid when using the E2E delay mechanism.