Friday 9 Sept.
Andy Rayner, Nevion
A review of recent IP production deployment use cases using federation and distributed production.
Distributed IP production is the direction of travel of the industry – this realises the significant benefit of an all-IP production architecture by allowing all of resources – the people, the processing, and the real estate to be in the optimum and most efficient locations.
This presentation will look at recent and up and coming real-world deployed use cases that are using this distributed architecture and will explore the technology challenges and implementations of federation that enable the seamless connectivity and control of resources between locations.
It will also look at the recent completed standards work in this area.
Rob Porter, Sony
Rob Porter, Sony
At the recent JT-NM Tested event, automated testing of controllers for NMOS compliance took place for the first time. This talk will describe the need for controller testing and how this was added to the NMOS Testing Tool to allow it to be used at the JT-NM Tested event.
Controllers on professional media networks use the AMWA NMOS protocols to perform operations such as discovering media devices on the network (IS-04) and making connections between them (IS-05), allowing media flows to be set up between different devices.
The NMOS Testing Tool is a freely available open-source software development. It has been developed by AMWA members to ensure that equipment that supports NMOS conforms to the specifications correctly. It allows vendors, systems integrators, and end users to self-test their equipment and has been extremely valuable in the drive to better interoperability between different vendors’ equipment. This includes being used at JT-NM Tested events, which allow vendors to obtain a JT-NM Tested badge and an entry in a publicly available catalog describing which parts of the NMOS specifications their equipment supports.
However, until recently the Testing Tool was limited to testing only NMOS nodes and registries. At the previous JT-NM Tested event, controllers were tested but this was done manually, a very time-consuming and expensive process.
To address this, Sony proposed and led an AMWA activity to add controller testing to the NMOS Testing Tool. This required a different approach to node and registry testing, involving a semi-automated framework that guides the user to perform a set of steps using their controller interface and then verifies the results automatically. The new controller test suite was successfully trialled at an AMWA workshop earlier this year, allowing it to be officially introduced as part of the recent JT-NM Tested event.
The new controller test suites currently test only some key IS-04 and IS-05 functionality for controllers. To clearly define what else controllers should be able to do, another AMWA activity was launched to provide better guidance for implementers. This “NMOS Controller Specification” activity resulted in the addition of clearly worded controller sections to the IS-04, IS-05 and BCP-003-01 (transport layer security) specifications and the creation of a new implementation guide for controllers, INFO-005. These documents will be used as the basis to provide further additions to the controller test suites in future.
This talk describes how the new test framework was created and how to use it. It also introduces the new controller sections in the NMOS specifications and discusses how these can be used to provide further additions to the Testing Tool in future, leading to better interoperability for everyone.
John Mailhot, Imagine Communications
The integration of live signals into cloud-based production and playout applications across vendors brings unique challenges - hear about how the VSF is working to address these complex workflow requirements.
The integration of live signals into cloud-based production and playout applications across vendors brings unique challenges - the multitude of possible codecs, how to signal and find the endpoints, and making the transport robust against troubles. Within cloud-based workflows the fun really starts - how to send media signals between elements of a large-scale workflow such that the timing of the whole chain is managed - without replicating the traditional "frame-lock-step" approach we use on the ground. This session talks about the current work within the VSF to establish a flexible timing model and set of recommended practices for ground-to-cloud-to-cloud-to-ground workflows.
Andy Rayner, Nevion
This presentation will explain the principles involved in the way ST 2110 and other linear systems interact with non-linear compute and will look at the evolving standards work that is addressing these, including the VSF GCCG work and new SMPTE guidelines.
For the last 90 years, the handling of live broadcast production video and audio has been achieved by linear transport and processing of the media streams.
The industry evolution towards software-based live production workflows means that to effectively make optimal use of native compute processing, the handling of media flow needs to evolve to an inherently non-linear connectivity and processing architecture.
This presentation will explain the principles involved, the way ST 2110 and other linear systems interact with non-linear compute and will look at the evolving standards work that is addressing these, including the VSF GCCG work and new SMPTE guidelines.
Thomas Edwards, AWS
JPEG XS is a low-latency, high-quality codec that is being increasingly used in ST 2110 IP systems, both on-premises, on the cloud, and between ground and cloud. A combination of standards and specifications, including SMPTE ST 2110-22, ISO/IEC 21122-3, IETF RFC 9134, and VSF TR-08, define the transport of JPEG XS in RTP over IP. This presentation describes the essential details of that transport, and how Wireshark can help you to dissect JPEG XS RTP packets.
Gerard Phillps, Arista Networks
This presentation will describe the network design, provisioning of network services, and automation of network configuration that lead to the 2022 JT-NM Tested event in August being hosted on the most realistic ST 2110 live production network to date
In order to maximise the industry benefits of the JT-NM Tested event, it was decided to design the network and associated network services in a way that reflects the best practices that we see employed in today's live production networks. Hear how the media and management networks were architected with universal access to the basic network services that are needed for NMOS operation (DHCP, DNS), and how these design principles provide scalability and reduce failure domain size ("blast radius"). As the scope of the event has continued to grow, it was also obvious that taking an automated approach to the design and creation of switch configs would reduce human error, event setup time, and make design changes easier to implement. Hear how this was achieved with an open-source Ansible based approach.
Cristian Recoseanu, Pebble
An overview of the NMOS Device Capabilities Control Suite of specifications and how we remove barriers for simple and seamless integrations. We will explore the control framework and protocol and see them in action in an end-to-end demo.
It doesn’t come as a surprise that device capabilities control has always been a hot topic in the hope of enabling simpler and more seamless integrations inside media production facilities. As depicted in layer 3 (Operational Control) of the EBU technology pyramid, it has gained significance at a time when there is a greater desire to make the transition to IP technologies while keeping complexity and integration efforts under control.
The NMOS Device Capabilities Control Suite of specifications provides a platform for interoperability inside an open ecosystem powered by modern web technologies. The journey sets out clear convergence points in the modelling language, discoverability, transport, message encoding, and even prepares the ground for identifying common reusable components.
We explore the specifications with particular focus on the control framework and protocol and how the architecture enables vendors to implement the protocol once. This allows more focus on modelling the functionality of their device, making interoperability an easy task when adding new exposed features.
We touch on why having the platform as a part of the NMOS ecosystem comes with benefits in terms of governance, interoperability testing, security, and openness.
We explore some of the technologies involved and how they can enable quicker adoption with implementers having access to a wider pool of developer talent.
Finally, we go through an end-to-end demo showcasing a controller and mock node. This demonstrates how without any prior knowledge of the device, the controller can find its control endpoint, establish a session, explore its structure, discover its capabilities and constraints, make changes to its properties, and keep up to date with changes using notifications.
With a comprehensive set of public specifications available and a full open-source mock device repository, vendors can start their early implementations with confidence in preparation for future interoperability workshops.
It’s rare to be in the right place at the right time, but as shown by the needs of the industry that time is now, and the place is within the open NMOS ecosystem.
Chris Lennon, Ross Video
NMOS provides many well thought-out and useful capabilities that make the entire ST 2110 ecosystem more complete. Can we apply any of that good work to non-ST 2110 environments? We'll explore that very topic.
NMOS' Interface Specifications are the result of a great deal of input and effort from the best and brightest in our industry. They fill a critical gap in SMPTE's ST 2110 suite of standards, providing capabilities critical to operations. From IS-04, providing discovery and registration, IS-05 handling device connection management, and IS-10 providing authorization, just to name a few, these specifications contain excellent means of addressing challenges that aren't necessarily unique to ST 2110 environments.
We are increasingly seeing IS-10 cited in RFIs and RFPs as a wide-ranging answer to authorization of media devices in new and existing environments. Being able to discover, register, and manage devices across environments is becoming something media organizations demand.
We will look at what's possible, and what's being proposed to take this valuable work and make it applicable to other codecs, transports, and even other platforms entirely (think "the cloud"). Could this be a step in the direction of enabling simpler overall facility/platform management? We think it might.
Saturday 10 Sept.
Kieran Kunhya, Open Broadcast Systems
Timestamps in ST 2110 are exceptionally important but many ST 2110 tutorials lack the time to go into detail about how they work, how they relate to PTP, and, for example, the differences between RTP timestamps and packet arrival times. This presentation will aim to fill that gap and allow engineers to diagnose problems with timestamps based on examples from real world facilities.
Jed Deame, Nextera Video
This tutorial will describe NMOS, the control system for SMPTE ST 2110 video over IP, in a very pragmatic and not overly technical way. Rather than digging into the syntax, we will focus on the use cases and the primary goals of the AMWA NMOS specification set and how it is used in the real world to meet the users' needs in an IP studio.
We will also review the new activities such as building a universal control language that takes NMOS beyond signal routing into the realm of system control.
The purpose of this talk is to answer the following questions (in simple, relatable language):
• What is this NMOS thing I keep hearing about?
• Why does it exist?
• What does it do for me as a user?
• How can it be extended to both simplify and secure the studio control system?
Brad Gilmer, AMWA and Felix Poulin
In this presentation, we will see why we need a common, open and secure approach to device capability control. We will explore user requirements from both broadcasters and system integrators and what the AMWA has on its roadmap to satisfy those requirements.
A huge benefit of the migration to networked media is the convergence of all types of media and control signals into the same IP transport layer. The industry has agreed on many aspects of the transition to IP technology, from the transport of separate essences with SMPTE ST 2110, to time distribution with PTP, and discovery, registration and connection management using the AMWA’s NMOS.
Now with the first major projects delivered, we can identify the gaps that will make the difference in the wide adoption and evolution of networked media toward easier to use and more dynamic facilities.
In this presentation, we will see why we need a common, open and secured approach to device capability control from initial day one configuration, to live operation and status monitoring. We will explore user requirements from broadcasters and system integrators and what the AMWA has on its roadmap to satisfy those requirements.
Nemanja Kamenica, Cisco
This session will address how to design an IP network for 2110 transport, with emphasis on how to avoid congestion and hashing collisions, and on how these problems are solved with network protocols and enhancements, or SDN controller orchestrating the network.
The world of IP networks can be complicated, full of protocols and choices to make, but what are the right choices and how to be sure everything will work.
This session will explain the common issues and challenges for multicast transport in IP networks, and how to ensure that important media flows will reach the destination unaffected. Hashing of IP traffic over available links is another issue, that could affect media flows in the network.
This session will propose ideas on how to design multicast networks and what are options in actively managing flows in networks or doing it outside the network using an SDN controller, and how users can benefit from both approaches.
Come and see how your ST 2110 signals can be transported in a fast, reliable, and deterministic way.
ErinRose Widner, Verizon Business Group
As of 2022, video streaming has officially passed cable viewership. Due to this viewing trend, the end-to-end infrastructure to support video delivery (particularly for SVOD) has had to evolve to include a last-mile that is capable of delivering video that is the same quality (if not better) than traditional broadcast.
Subscriptions for video-on-demand services (SVOD) have now surpassed pay-TV subscriptions. Due to this new viewing trend, combined with the expectation of having a quality experience that is the same if not better than broadcast, the end-to-end infrastructure to support video delivery (particularly for SVOD) has needed to evolve.
To manage peak traffic and to maintain a steady state of content delivery, a content provider may use multiple CDNs and deploy techniques such as intelligent load balancers to switch traffic between CDNs. Additionally, commercial CDNs also offer services such as video optimization to help distribute content more efficiently. But in spite of these improvements there are still weak-links in the video delivery ecosystem. This can be the capacity limitation at the meet point (POP), or somewhere within the ISP’s core network where all Internet traffic is competing for the same network resources, or bandwidth limitations at the ISP’s edge network (the proverbial last mile at the ISP).
In order to address these weak-links, media technology providers can leverage each component in the content delivery path. The new Open Caching standard enables a move away from proprietary systems, while still supporting an environment that leverages content delivery networks, last mile providers and streaming technologies that bring content closer to the consumer. Content stored closer to customers in this manner travels a shorter distance over the network through fewer routers and switches before reaching the customer.
Open Caching is standards-based and encourages collaboration between all constituents in the content delivery pipeline including the content providers, the commercial content delivery networks and the last mile ISP.
Additionally, as the market becomes more saturated with video subscription services, content providers are seeking ways to grow and defend their market share in ways that go beyond the actual content they provide. To do this, content providers can use open caching to provide the best possible user experience by reducing network events that could cause freezing or buffering, which will overall improve a user’s quality of experience and enable customers to stream content sooner.
By leveraging Open Caching, content providers can bring content closer to the user, and create an overall better viewing experience and ultimately leverage a new way to retain subscribers.
Ciro Noronha, Cobalt Digital
This presentation will give an overview of the work being done in the VSF RIST Activity Group to address the problem of facilitating the secure communication between broadcast streaming devices behind firewalls, without the need for special configurations. The work is expected to be published as one of the TR-06-4 parts.
One challenge in using the RIST protocol to establish communication over the Internet is that the server endpoint must accept a connection from the client endpoint. No special configuration is needed to support a client behind a firewall – it simply accesses a resource out on the Internet. However, this is not the case for the server – it needs to have either a public IP address, or a firewall configured to forward the packets. In some cases, this is either difficult or impossible for administrative reasons.
The RIST Activity Group has completed the technical work on the upcoming TR-06-4 Part 3. The objective of this work is to create a common Specification for a relay device, responsible for facilitating the communication between two RIST endpoints behind firewalls that, for administrative reasons, cannot be configured to allow direct communication. This talk provides an overview of the RIST Relay functionality and protocols, including the support for symmetric and asymmetric firewalls, traffic replication, and protocol conversion, among other functions.
Sergio Ammirata, SipRadius/Ammux
Video Services Forum (VSF) is submitting an Internet RFC for a new authorization protocol, called EAP SHA256-SRP6a, based upon existing protocols. For lossy network environments where RIST normally finds use, it provides robustness even when packets are lost. Because RIST often transports high-value content streams, it provides a very high level of security.
This session will be quite detailed, actually describing some of the formulae behind the protocol. But for those who don't need to see the math, we'll discuss up front how a regular user or sysadmin can take advantage of command line utilities such as the FOSS librist to benefit from it without having to know too much about how it works. The authorization protocol has the ability to recover from packet loss during the authentication process, as for example, should the Internet application use the UDP transport protocol under lossy network conditions. RIST, for which we developed the protocol, normally functions in lossy networks. Because RIST often transports high-value content streams, the new protocol provides a very high level of security. The protocol follows the Extensible Authentication Protocol [EAP] framework, which allows for the use of multiple authentication mechanisms. It utilizes Secure Remote Password protocol [SRP], with strong, password-based cryptographic hashing. It utilizes the Secure Hashing Algorithm 256 [SHA-256] message digest algorithm as the hashing mechanism. The authentication protocol allows for one Server and one or more clients. The authentication algorithm is based on a username/password or passphrase pair. These are used to generate secure ephemeral keys. The server has a store of all valid usernames and password hashes. Each client stores its own username and password. The authentication algorithm provides for each side to prove to the other that it has a valid username/password or passphrase pair, in a way that a third-party monitoring the transactions could not use intercepted information to later successfully authenticate.
John Mailhot, Imagine Communications
In SMPTE ST 2110 workflows, details about the colorimetry and transfer characteristic of signals (HDR signaling) are not part of the video stream. This talk focuses on system workflows and presumptions within the ST 2110 standard and related NMOS specifications about HDR signaling.
In SMPTE ST 2110 workflows, details about the video format, colorimetry and transfer characteristic of signals (HDR signaling) is not part of the video stream. This data is advertised through NMOS (SDP) and it is the responsibility of the control system to track and propagate changes to subscribed receivers in an orderly manner, including managing any effects on network bandwidth. Dynamic HDR metadata from VANC compounds the problem if not tracked alongside the video stream. This talk focuses on system workflow practices within the 2110 and related NMOS specifications around HDR and video format signaling.
Bill Redmann, InterDigital
The Ultra HD Forum’s generic testbed was defined to evaluate state-of-the-art IP-based media systems relative to technologies beyond HD (e.g., UHD, HDR, HFR). A first experiment, directed to ST 2110, carried live, uncompressed video, in HDR. This experiment proved extant capabilities, but identified a need for more comprehensive signaling.
The Ultra HD Forum’s Interoperability Work Group launched the IP Production Users Group to evaluate the readiness of IP-based media systems to carry content that relies on technologies promoted by the Forum – those beyond HD, such as UHD resolution, HDR/WCG color volumes, and HFR timing.
Interested in not only productions having IP networks residing strictly on-prem, but also live, cloud-based workflows, the Forum defined a generic testbed for evaluating the state-of-the-art with respect to technologies beyond HD (UHD, HDR, HFR), in the context of current IP-based media environments.
For NAB this year, a first instance of the testbed was constructed, an SDI-ST 2110 hybrid, wherein the experiment conveyed live, uncompressed, HD video, in HDR, over ST 2110. Assembled from components contributed by members and interested industry partners, this instance proved the extant capabilities of present-day off-the-shelf components, but also identified needs for more comprehensive signaling.
David Mitchinson, Appear
This presentation will discuss the key interoperability and architectural considerations for VSF-TR07 and SMPTE ST 2110.
There are multiple layers to consider, making many practical end-to-end solutions complex. Although the standardisation layers work, synchronisation and management of ST 2110 essences can be difficult. While the codec used in JPEG XS is generic and inherently works with sub-frame delay, it is essential that the rest of the delivery chain is properly optimised to avoid adding extra frames of delay.
The next industry goal should be to offer NMOS control for the entire solution: Achieving this for the VSF TR07 domain requires some standardization focus. The high flexibility of the standard, coupled with some manufacturer’s desire to rigidly enforce their approach towards implementation, is creating a degree of unnecessary vendor lock-in in some cases.
Koji Oyama, Xcelux Design
This presentation provides a design flow and some common pitfalls when broadcast network engineers consider their Media-over-IP (MoIP) network architecture and configure network switches. In addition to the essential technology such as VLAN, VRF, IGMP, PIM, and OSPF I introduced at the NAB 2022 IPShowcase, you can also see how to verify the network design and some issues that have happened in the design so far, and some key points to consider in your logical design.
One of the current biggest issues in the design and development of the SMPTE ST-2110-based broadcasting facilities is the shortage of Media-over-IP (MoIP) network design engineers who understand both broadcasting and network communications. This is the topic that has been discussed for several years, and I have been working to train engineers over the past years through my experience of the MoIP network design, the situation is getting worse and more serious as the number of the facility developments increases. This presentation can help the target audience, broadcast engineers, who are studying or to study MoIP network technology. When trying to build an actual ST-2110-based network, the first question would be how we design a specific IP network. Unlike peer-to-peer SDI network where we can focus on the physical connection, the data on the MoIP network can be transmitted with inbounded multiple streams in an Ethernet optical cable, and multicast routing settings are required in its network switches. In other words, not only physical design but also logical design becomes more important. The more complicated the system becomes, the more complicated the logical configuration becomes. The network architecture design and its IP addressing could be a key to success of the reliable and scalable network. These technique and idea would be similar as the ones in software engineering, which kind of knowledge and skill set has never been needed by broadcast engineers before.
If the SDN controller manages the configuration of its network switches in the near future, it may be possible to build a system without knowing specifically how to implement the logic network design. However, once the network occurs in trouble, engineers who don’t have the network design skill would be at a loss, there should be a risk that we would not be able to analyze to take workarounds. For this reason, I believe it is necessary to study the fundamental skill of such appropriate MoIP network design.
At the previous NAB2022 IPShowcase, I introduced the essential terminologies for configuring network switches that network engineers should know (VLAN, VRF, Multicast routing, IGMP, PIM, OSPF, LAG/LACP Such). At this IBC2022 IPShowcase, in addition to that, I would like to explain how to verify the designed logical network.
In addition, I would like to share some information about the actual issues I have faced so far. One of the issues is that an unintended network path could be routed by OSPF in the event of a network switch failure. Some streams that should have been disconnected could be transmitted with other path and put pressure on the bandwidth of other streams. Another issue is that the short time of IGMP leave/join could be in trouble with bandwidth when a PIM join driven by an IGMP join is issued before a PIM prone driven by an IGMP leave is completed. It may cause more streams than expected to pass for a moment, affecting other streams.
Due to the increasing scale and complexity of MoIP network, the design workflow of logic design and verification has become similar as the workflow of the design, implementation, and verification of software, rather than the conventional simple setting and confirmation workflow. Efficient verification workflow has become particularly important in the MoIP network design, and the concept, preparation, and planning have become the key to success your MoIP network. Project managers of the MoIP facility development also should be understood such kind of changing workflow.
Gabriel Kerner, Alvalinks and Adi Rozenberg, Alvalinks
The broadcast industry is in the midst of this digital transformation - the migration of networks and applications to a centralized IP-based cloud, accelerated innovation, and business expansion for enterprises – however moving to all-IP network and cloud must rely on automated expertise for the industry to concentrate on content and distribution.
Enterprise digital transformation has boosted business agility and market adaptivity. The migration of all networks and applications to a centralized IP-based cloud, accelerated innovation and business expansion.
The cloud however, requires expert engineers to deploy, manage and operate. Further, as it becomes business-critical, it needs to be monitored constantly and continuously.
As IT becomes a main artery of organizations, multiple tools have emerged to automate, abstract, and processize their operations. This reduced TCO and risks, ensured business continuity, and effectively accelerated adoption of cloud.
The broadcast industry is in the midst of this transformation – the challenge to move to cloud based on all-IP network, must rely on automated expertise, for the industry to concentrate on content and distribution.
In this presentation we will look at the challenges and concepts to build sound foundations to an all-IP network and cloud, and compare the steps performed by IT and expected in broadcast.
Sunday 11 Sept.
Ievgen Kostiukevych, EBU
Pavlo Kondratenko, EBU
Willem Vermost, VRT
The presentation will provide detailed explanations of the August 2022 JT-NM Tested event network and testing architectures and methodologies, as well as give an introduction to the testing results.
Adi Rozenberg, Alvalinks
IP-based transport is becoming the new backbone of our industry, from acquisition, transport to the cloud, and cloud to cloud. Protocols like RIST, SRT, NDI are used for the compressed transport while JpegXs and ST 2110 are used for the higher bandwidth. Setup may seem easy, but what do I need to know before I start?
How do I troubleshoot a problem when it arises? What do I need to monitor? Keep track of? And what are the option in my bag of tricks to identify a problem, isolate and avert it?
IP based transport is becoming the new backbone of our industry with RIST, SRT, NDI, JpegXs and ST2110 protocols fueling new applications, cloud workflows and a true enablers of the next technology leap to the cloud.
However networks are complex "living organisms" that are dynamic and have unpredictable behavior and performance.
The cloud is yet another challenge that we need to overcome; it is increasing dramatically with scale, sites, interconnection between networks, and the integration of cloud operations – those are not under our control or visibility.
The presentation will address the following questions:
When we come to setup a new service, we need to understand the basic concepts of network behavior and artifacts.
How to we test the network?
What do I need to monitor?
What should I Keep track off?
What are the option in my bag of tricks to identify a problem?
How do we isolate and avert it a problem?
We will show concepts and methodologies to resolve these questions effectively.
Monday 12 Sept.
Andy Rayner, Nevion
This presentation will use recent real-world deployments to explore the different ways the toolkit provided by ST 2110-30/31/AES67 and other audio interface technologies provides the required capabilities.
Audio is almost always the most complicated part of a live IP production. This presentation will use recent real-world deployments to explore the different ways the toolkit provided by ST 2110-30/31/AES67 and other audio interface technologies provides the required capabilities. It will also explore optimum ways of achieving required workflows.
The presentation will relate these case studies to the relevant standards.
Nemanja Kamenica, Cisco
This session will delve into how to design an IP network that can connect multiple locations together so remote and local production can be done from the same control room. This session will show advanced features allowing you to have post production in the cloud.
The world of IP networks allow much more flexibility and opportunity than SDI. How can you leverage those so you can have live remote productions at different location with one control room.
Consider connecting multiple sites, geographically distant but flexible to be controlled from one control room or import media signals so they can be processed in single location.
For users that want to move post production to the public cloud, users can leverage IP network flexibility and features, by converting transport signal to unicast, and transport of public internet.
Ievgen Kostiukevych, EBU
Gerben Dierick, VRT
The presentation will provide detailed explanations of the August 2022 JT-NM Tested event cybersecurity testing methodologies, as well as give an introduction to the testing results.
Kevin Salvidge, LEADER
Wouldn’t hindsight be a wonderful thing with your IP deployment? So, who better than a test and measurement equipment manufacturer to share its insight into the challenges and potential pitfalls of IP deployments? In our presentation, we will share some of our IP experiences based on years of experience.
If you have made the transition from SDI to IP, you will already be enjoying the operational benefits and the flexibility that IP brings. You can now handle multiple video and audio services bi-directionally over a single fibre. You can also expand your system without the eye-watering capital costs inherent in SDI expansion.
However, like any technology migration, the transition to IP has highlighted several legacy operations that we have been taking for granted in SDI. It is only when you start to use your IP systems in anger that you realise some areas of IP operation behave differently from their SDI counterparts. Before we explore these areas, keep in mind that the objective of your new IP-based facility remains the same as the old SDI one: namely, to deliver high-quality content to your customers.
Over the past 30 years, SDI-based productions have developed some highly refined operating practices that IP implementations may not have fully appreciated. Hindsight would be a wonderful thing with your IP deployment.
At Leader, we are extremely fortunate to have been selected as the IP Test and Measurement solution for many IP projects/. As a test and measurement equipment manufacturer, we are in effect the referees in broadcast facilities, accurately reporting and recording the in-depth impact that broadcast products have on the IP and SDI streams.
In this presentation, we are pleased to be able to share knowledge based on years of experience. This includes:
· Managing and keeping synchronised IP and SDI facilities
· Analysing and monitoring both IP and SDI video sources
· Analysing SDI VPID in an IP world
· Vision engineering camera switching
· IP latency
Although you have started your IP migration; you will still have legacy SDI-based equipment to monitor in parallel with your new IP operations. Having ‘True Hybrid’ test and measurement tools that can display simultaneous SDI and IP measurements will ensure your facility seamlessly performs whilst you initiate your IP deployment.
Ievgen Kostiukevych, EBU
Pavlo Kondratenko, EBU
Willem Vermost, VRT
Leigh Whitcomb, Imagine
The presentation will give an overview into new test-and-measurement and compliance testing recommendations for ST 2110 and the implications on manufacturers and end users.
Nicolas Sturmel, Merging Technologies
This presentation shows how the MNMS open source framework can be used to map the network and how real-time weather maps views from data can be mined in the network using MDNS, SNMP, NMOS and other protocols.
User trust in the network is challenged by the complexity of the system. Instead of baseband, physical, peer-to-peer connections (SDI, AES/EBU), the technician has to deal with multiple layers of abstractions such as ethernet connections, VLANS, IP subnets, and multicast flows. Although there are many proprietary UIs giving a simplified view of the network, most of them are statically configured and rely on specific protocols.
MNMS (Media Network Monitoring Services) is an open source framework that shows how using easy-to-get information on the network (via SNMP, NMOS, LLDP, and other means and standard IT protocols), a real-time, dynamic view, and protocol agnostic view of the system can be constructed for the user to easily pinpoint problems on the system.
We will show real-world applications of MNMS and detail its components as well as a tutorial to get the system up and running from the GitHub repository.