Implementing AES67 and ST 2110-30 in Your Plant

Presenters : Dominic Giambo - Wheatstone

Year : 2019

dlp_document_download : Implementing AES67 and ST 2110 - 30 in Your Plant Dominic Giambo , Development Engineer, Wheatstone C U R A T E D B Y IP S H O W C A S E T H E AT E R AT N A B – A P R I L 8 -11 , 2 01 9 What is AES67? A Layer 3 protocol suite for transporting audio ratified by AES in 2013. AES67 makes interoperability between AoIP networks such as Dante, WheatNet -IP and Livewire possible. It has since become useful for more. Why AES67? • Audio transport standard for SMPTE 2110 -30 • Supported by most AoIP systems • Key to transitioning to IP workflows • AES67 will eventually find its way into every broadcast plant that includes audio. SMPTE 2110 -30 Requirements • 48kHz sampling is required for all devices • 1ms packet time is required for all devices • 1..8 channels per stream is required for all devices • Slave -Only Mode PTP must be supported • Media clock offset must be zero • ST -2059 -2: PTP Media Profile only (Message rates of 4/s) Setting the stage: Simulated AES67 Studio AES67 Uses IEEE -1588 PTPv2 PTPv2 timing and synchronization: • Precise timing accuracy better than 1 microsecond • Sub -microsecond timing accuracy not required • PTPv2 devices found in most AoIP devices are not reliable Key Finding The PTPv2 synchronization role is best filled by a specialized PTP master clock device. Packet Structure: Send device and receive device have to agree on header and payload information. Packet Structure: Packet Structure: Key Finding Unless you know the device sample rate, set the system sample rate to 48kHz as AES67 does not require devices to support 44.1kHz and many do not . Configuration Considerations: • AES67 specifies a range of multicast addresses • AES67 specifies a standard port (5004) Discovery and Control: Since AES67 only specifies stream content parameters and does nothing to manage stream discovery and control, these functions must be managed manually. This is the purpose of SDP specified in the AES67 standard. Mapping out an IP and multicast address plan: • Determine how multicast stream addresses are allocated throughout. Multicast addresses are in the form of 239.xxx.yyy.zzz. Mapping out an IP and multicast address plan: • Determine how multicast stream addresses are allocated throughout. • Isolate address ranges for each system. Start with less common devices. Change their addresses to an isolated address range. Key Finding Assure all devices are on the same IP subnet as multicasting does not normally cross subnet boundaries. WheatNet -IP Navigator system information tab screen Navigator screen showing all available streams Navigator screen showing AES67 1 msec support functionality enabled Navigator screen showing AES67 devices added to the system Four xNode channels configured to make AES67 compatible streams Defining the streams to match the xNode sources Navigator screen after all the AES67 streams have been defined Crosspoint grid of AES67 source -to -destination connections About SDP Files… Sample WheatNet -IP SDP file Sample Dante SDP file In Closing • Provide a PTPv2 master clock source. • Assure all devices are on the same IP subnet as multicasting does not normally cross subnet boundaries. • Configure the desired multicast addresses, port, packet timing, and payload type for Source streams. • Configure Destinations with the stream details for the desired stream to receive. C U R A T E D B Y IP S H O W C A S E T H E AT E R AT N A B – A P R I L 8 -11 , 2 01 9