Did you know for example, that there is no requirement for every node in a system to run the same IS-04 version? This presentation will take a look at some of the lesser-known and more advanced features of IS-04 and IS-05, along with how they may assist you in deploying anything from a small ad-hoc setup through to a large-scale multi-format facility.

File Type: pdf
Presenters : Bill McLaughlin - EEG
Year : 2019
dlp_document_download : C U R A T E D B Y I P 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 TR - 1001 : Replacing Video By Spreadsheet Bill McLaughlin VP Product Development EEG Outline • Review : what is the TR -1001 document? • How does TR -1001 intersect with ST 2110? • What IP video problems exist without a well -defined "Full Stack" system? • Improving on SDI facility "video by spreadsheet" 2 What is the TR - 1001 document? • "Technical Recommendation " • " System Environment and Device Behaviors for SMPTE ST 2110 Media Nodes in Engineered Networks " • Colloquially: "Full Stack" 3 Why a TR - 1001 "Full Stack" Document? • SMPTE 2110 family defines essence format, not system context • How to manage new challenges in IP video production • Opportunity for IP facility to be more organized than traditional SDI 4 What does 2110 Constrain? • Essence packet payload (2110 -20,30,40, etc) • Well -defined RTP timestamps (PTP, SMPTE epoch) • Constraints on packet bursting (ST 2110 -21) • Description of the transmission in an SDP file 5 SENDER RECEIVER RTP / UDP / IP ST 2110 (20,30,40) EBU: "Minimum Stack to Build and Manage" 6 2110 2110 and TR -1001 TR -1001 TR -1001 (partial coverage) Elements in TR - 1001 7 2110 mostly describes Media Node What goes wrong when you set up 2110 • I can’t ping the new widget ‒ Worse: the new widget is now on the same IP as another widget • It won’t lock to PTP ‒ Worse: the new widget is stopping other widgets from locking • I can’t get a media output stream ‒ Worse: the stream is using the same multicast as an existing stream Plus: each of these problems on multiple interfaces per widget! 8 We wish the new 2110 widget could: • Automatically get an unused valid IP addresses • Auto -discover PTP domain and other settings • Never try to take over as a master clock • Transmit media on an appropriate multicast (or none at all) • Pop up quickly in a centralized monitoring system 9 TR - 1001 brings us closer to "plug and play" • DHCP for IP addressing • DNS -SD for finding NMOS IS -04 and System Resource JSON • System Resource provides PTP settings • System Resource provides a "system" UUID ‒ Power -cycling widget can resume operation with last settings ‒ Brand new widget should disable transmitter, await instructions • NMOS IS -04 registry of all Nodes (widgets) • NMOS IS -05 API to connect transmitters and receivers 10 Organizing Video: not just an IP problem! What does the SDI status quo usually look like? • Spreadsheets of management IP addresses • Spreadsheets of video router ports • Stickers on the cables • Stickers on the front panels • Spreadsheets of names on the stickers • A set of Visio and CAD drawings with the logical relationships 11 Spreadsheets and Stickers • Do not auto -update when something changes • Usually do not have direct linkage to control or monitoring systems • May contain manual errors even at the beginning • Tend to get less accurate over time • Are not done in a standardized way between companies and facilities 12 So maybe this "IP video" thing isn’t so much more difficult after all… When a TR - 1001 system is working: • All the current widgets/nodes are in your system registry ‒ With no dead entries ‒ The unicast IP for more detailed management is present and always accurate • Properties that every device has like PTP are auto -configured • Introducing a new compliant device can’t destabilize existing devices • A point and click connects one media device to another device • Every connection point can be monitored (multicast) 13 Known Limitations / Future Work • Security ‒ Humans should approve new widgets joining network ‒ Device credentials, stream permissions not in this scope • Labeling concerns ‒ The stickers on SDI equipment don’t have UUIDs ‒ Conventions on hierarchy and human labels vary among vendors • Vendor support of NMOS IS -04/IS -05 is a "work in progress" ‒ Competing control protocols exist in both open and proprietary domains 14 JT - NM Testing: Brief Case Study • 80 products from 50 vendors tested by a small group led by EBU and IRT engineers over 5 days in March 2019 • Centralized spreadsheet managing IP addressing – why not? ‒ Verbal communication and emails also exchanging settings as they change • Configuration problems the leading cause of delays and time extensions ‒ Made compliance with 2110 media standards seem simple… • Vendor experts had these issues with their own equipment! 15 For industry end users, less time configuring product -specific interfaces is more time enjoying the benefits of ST 2110 IP video! C U R A T E D B Y I P 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 Thank You Bill McLaughlin, EEG billm@eegent.com
Downloads: 3