In this implementers guide video Cristian walks us through the Implementers guide for NMOS Control & Monitoring (INFO-006) and how some of its recommended checklists have been implemented in the open source NMOS control mock device example implementation. The video starts with a quick NMOS Specs overview of the NMOS categories or themes and then goes over the NMOS Control & Monitoring ecosystem including a diagram covering how interoperability and conformance was achieved and maintained whilst preserving vendor freedom. The next section introduces the NMOS control mock device open source project on GitHub and how to use it. This is a fully compliant and tested example implementation of IS-12 and BCP-008 written in TypeScript/NodeJS. Following on from this, the video dives more deeply into the INFO-006 guidance including its checklists for both device and controller implementations. Then the majority of the checklists are matched between the INFO-006 guidance and how they have been implemented in the mock device code base. Finally, the end of the video brings everything together by running the mock device application and utilizing a compatible IS-12 / BCP-008 controller showcases an operational demo of the device being monitored. ----------------- 4:07 AMWA NMOS specs overview and Control & Monitoring ecosystem diagram 6:15 NMOS device control mock introduction 11:25 INFO-006 introduction and device implementation tutorial 13:56 INFO-006 controller implementation tutorial 14:25 INFO-006 how to practical examples and how to get started 15:45 Device implementation checklist 21:40 Device implementation Blocks 28:42 Device implementation Managers 33:10 Device implementation IS-12 Protocol, IS-04 & IS-05 interactions, Commands, Subscriptions, Events & Notifications. 45:40 Status monitoring (BCP-008) 47:40 Other more advanced topics: NMOS control features sets, Nested blocks, Non-standard classes 58:20 Operational demo with compatible Controller ____ (auto-generated partial transcript) Hello everyone. This is Cristian here from Pebble. I'm here to talk to you about NMOS device control and monitoring. I'm one of the main contributors in the activity group and just wanted today to talk to you a bit about some of the resources available to implementers. This is a very important area for the NMOS community and it's progressed very quickly in the last few months. We want to let you know about the resources we have in place. Today, we're going to look at some actual code and the implementers guide. Before we go into that, I just wanted to give you a brief little overview of the ecosystem. Most of you will know about NMOS IS-04 Discovery & Registration and IS-05 Connection Management. Today, however, we're going to focus on Device Control and Monitoring. I'm going to briefly show you a diagram that I enjoy, which is this squid diagram depicting the ecosystem of control and monitoring. [00:01:21.02] It relies on different parts, different logical parts, playing really nicely together and splitting the problem space into different layers that we can then solve with the best tools available. We've got MS-O5-02 on the left-hand side, which is the modeling language. This is how we define what data types and what object entities, what classes you can create. There are core classes that are really needed for everything. But then vendors can also define their own classes. They can create their own vendor-specific objects with their own vendor-specific data types, and all need to be discoverable by the same means. Anyone can use those as well, but they are not part of the standard set. MS-O5-02 establishes these rules. Then you need a way to interact with those models in a device structure. You have IS-12, which is our communication protocol. That relies on the WebSocket transport, and we send JSON payloads over that. It's bi-directional. It allows for both control and notifications to flow backwards and forwards. That is how you interact with those models. It's really efficient, really compact, and also straightforward to debug and to view.   [00:02:42.24] Also, you can create a web app entirely in a browser that can control one of those endpoints. You can use a WebSocket extension for a browser to interact with devices. We thought about some of these nonfunctional requirements. The other element of this is BCP-008. That establishes monitoring behaviors of some of these media devices at a feature-specific level. For example, we have BCP-08-01 receiver monitoring which defines how to describe receiver statuses via this framework. Then we have BCP-08-02, which is the counterpart for senders. Those all establish requirements and behavior on top of having the transport conformance, the message payload conformance, and data types and classes. And all of these fit really nicely together in one big set allowing conforming devices which are still very distinctive. They have their own features they can do, but they are all advertised and interactable using the same protocol and offer the same discovery means to a controller. That's where we are. I'll show you briefly where everything is again. If you go to specs.amwa.tv, that forwards you to this nice portal.   [00:04:14.20] You can also go directly to specs.amwa.tv/nmos, or you can just click here on the NMOS tab, and that directs you to the NMOS portal. Here, you have a rendition of the diagram I just showed with the columns in a table format with all the links and the versions. You've got resource management, connection management, device control and monitoring. The one that we're going to focus today is actually here: device control and monitoring. Specifically, we're going to focus on the implementer's guide. So INFO-006 which you can view as the point of entry into this. So you've got references and guidance for all of the other subparts in there. We're going to look at that as one of the main resources for today's video. We're also going to use a controller to show you some of the operational feel of the ecosystem and we're going to use what we call the NMOS device control mock.   [00:05:29.10] This is another open-source application. It's a TypeScript NodeJs application that you can use. It's rendered here as documentation, but the codebase is available on GitHub. If you navigate to this link, there are links throughout the specs as well. Once you have NodeJs installed, you can install all its dependencies using "npm install", and then you can build it or you can build and start it. Or if you want to make changes to the code base, you run "npm run serve", which effectively recompiles the application if you make any changes. We're going to see that today. There's the specs.amwa.tv link. If you search for this, you will find the GitHub repo as well. All of that documentation is here as well. The way you grab this is by doing a clone of it. It's all in the public domain, or you can just grab a zip file if you want, or whichever way you want to do it. Once you pull that in, you're going to have something that looks a bit like this. I'm going to grab this across the screen so you can see. I'll go to the main folder.  [00:06:43.15] You get something like this. It's got some of the documentation, but what we're interested in is the code there. If you go to the code directory, and for this session, I'm just going to open it in Visual Studio Code. I've opened it here. Okay, so we've opened that in Visual Studio Code, and I'm in the code subfolder. I'm just going to wait for the Terminal to load here just to show you how you can run this in those two ways. So if I run through the first one "npm run build-and-start". This will compile the application and run it up. It'll take a couple of seconds, but it will show you what it's doing in there. We'll wait for that to finish and that should run up. I should have said for this, I've also got an NMOS registry running in the background. You can configure this. If you look at the documentation, you can run this without a registry. You just have to change one of the configuration items in there.   [00:08:15.13] For this demo, I've got the nmos-cpp-registry running here. Now, it's just going to copy those compiled files to the distribution folder and then hopefully run it. Then we can look at our controller just to establish the environment we're in and give you a brief look at what we have for the mock device. Then we're going to go back to the implementer's guide. That's all up and running. It's on port 49999, and it's registered in the registry, and it's already starting to communicate with the controller. Let's have a look at that. We got our controller up and running here, and that shows up as this NC-O1 node. This is our IS-04 node. It's got a device, and it's got a receiver and a sender. You'll see that device has a control endpoint. We're going to look at this through the lens of implementation guide checklist in a second. This is the IS-12 control endpoint in here. This is how the controller interacts with our device. If I briefly do a little exploration of that, you'll see this is our device model structure.   NMOS Control and Monitoring: Implementers Guide and Device Mock

AMWA has won a Technology & Engineering Emmy® Award! We are honored to announce that AMWA is the recipient of a Technology & Engineering Emmy® Award for SMPTE ST 2067 — Standardization of Interoperable Master Format (IMF) by The National Academy of Television Arts & Sciences.  AMWA is a co-honoree along with SMPTE, Digital Cinema Initiatives (DCI), and the University of Southern California’s Entertainment Technology Center. On December 4th, 2025 in New York, AMWA and our fellow honorees will be recognized at the 76th Annual Technology & Engineering Emmy® Awards ceremony.  IMF is a file-based media format that simplifies the delivery and storage of audio-visual masters intended for multiple territories and platforms. Using open-source, proven technology, IMF works with any finished audio-visual masters, including long-form movies, episodic content, advertisements, and short-form content.  “This is a great example of how trade associations, industry partnerships, and standards bodies can work together to achieve great things,” said Brad Gilmer, AMWA Executive Director. “On behalf of AMWA, we're thrilled to have been a part of it. You can find out more about SMPTE ST 2067 at SMPTE.org .  Keep up to date on all of the latest AMWA news at amwa.tv/blog .

Releases, Publications, Updates September 2025 NMOS Support for IPMX/USB, NMOS Support for IPMX/HKEP, and NMOS Support for IPMX/PEP are underway! Stay tuned for updates. ## New NMOS Publication: BCP-008 NMOS Minimum Status Reporting A persistent challenge in IP media systems is that monitoring and control tools often receive inconsistent or incomplete status information from devices. Vendors may expose data differently, rely on varying models, or require manual configuration before systems can interpret the information. This fragmentation makes it difficult for end-users to validate streams, confirm synchronization, and troubleshoot connectivity in multi-vendor environments. The BCP-008 initiative tackles this by defining a clear baseline for minimum status reporting across NMOS receivers and senders. The goal is to ensure that all NMOS-enabled devices provide a common set of status information covering three key areas identified in the white paper “Standardised Status Monitoring on NMOS Systems” (SRF): stream validation, synchronization, and connectivity. BCP-008 (NMOS Minimum Status Reporting) adds a simple, standardized way to check if NMOS devices are truly working after they’re connected. It uses a “traffic light” system—green for good, yellow for “check later,” and red for service impact now—so users can quickly see device health at a glance. Status is reported across four domains: connectivity, packets, synchronization, and stream level, with the overall state reflecting the most serious issue. This helps operators spot problems quickly, understand whether they need immediate action, and know who to call if something goes wrong. By completing consultation, aligning on scope, and selecting the technical framework, AMWA has laid the groundwork for consistent minimum status reporting. The activity is now entering the wider adoption and certification stage with further workshops and events planned. 🔗 https://specs.amwa.tv/bcp-008-01/ 🔗 https:// specs.amwa.tv/bcp-008-02/ ## New NMOS Publication: BCP-006-04 MPEG Transport Stream Although NMOS specifications are widely used for uncompressed IP-based workflows, many facilities and services rely on compressed MPEG Transport Streams (MPEG-TS) as part of their infrastructure. A persistent challenge has been ensuring that NMOS controllers can configure and manage connections between TS senders and receivers in a reliable, interoperable way. Without standardization, end-users face uncertainty around stream compatibility, while vendors must implement ad hoc methods to represent capabilities. The BCP-006-04 initiative addresses this by defining how NMOS can support configuration and interoperability for MPEG-TS devices, particularly for SMPTE ST 2022-2 streams including for VSF TR-01 (JPEG 2000) and TR-07 (JPEG XS). The first phase focuses on describing sender and receiver capabilities in a manner that controllers can use to automatically determine interoperability.  AMWA progress includes: - Release of BCP-006-04, which enables registration, discovery, and connection management of MPEG TS endpoints using the AMWA IS-04 and IS-05 NMOS specifications. - Refined the BCP-006-04 documentation to define the model for MPEG-TS support. - Designing and beginning implementation of a dedicated test plan within the NMOS testing framework. - Securing commitments from multiple implementers, including Pebble Control (controller), Appear (node), nmos-cpp, and additional vendors, to ensure a diverse test base. - Planning an interop remote workshop (via VPN) to validate implementations and confirm interoperability across real-world devices. Through this work, AMWA is enabling MPEG-TS devices to be managed consistently alongside other NMOS-enabled equipment. For users, this means simplified configuration and greater confidence in interoperability. For vendors, it reduces the need for custom integration while ensuring alignment with the broader NMOS ecosystem. 🔗 https:// specs.amwa.tv/bcp-006-04/ ## AMWA Publishes IS-14: NMOS Device Configuration Configuring IP-based media devices is often complex, with each vendor offering unique approaches to saving, restoring, or automating device settings. This fragmentation creates challenges for system integrators and engineers who need reliable ways to back up configurations, roll them back, or deploy them consistently at scale. Without a common method, operators face added effort in both day-to-day operations and long-term system maintenance. The IS-14 specification, recently published by AMWA, addresses this need by defining a standard mechanism for saving and restoring the configuration of NMOS Devices. The goal is to give system configurators and engineers a simple, consistent, and API-driven way to manage device states. User needs range from basic backup and versioning to advanced CI/CD integration, where configuration data can be delivered automatically to multiple systems in large-scale environments and Dynamic Media Facilities (DMF). IS-14 builds on MS-05-02 models, exposing them via an HTTP-based API with emphasis on efficient bulk Get and Set operations. It also considers context-dependent configurations, ensuring that fragments requiring specific device states can still be restored safely and intuitively. AMWA progress includes: Publishing the IS-14 specification with reviewed and confirmed conformance language. Adding nmos-testing coverage, so IS-14 can be validated as part of the broader NMOS Test Suite. With IS-14 now available, the industry gains a standardized, interoperable approach to device configuration—simplifying operations, enabling automation, and strengthening system resilience. 🔗 https:// specs.amwa.tv/is-14/ ## Open Source Sender Receiver Framework (OSSRF) Released One of the key challenges for vendors developing NMOS-enabled devices is bridging the gap between the control plane and the media/transport plane. Many vendors already have proprietary control protocols and data planes, but it is not obvious how integration with NMOS can be achieved, leading to increased development cost and slower time to market. The Open Source Sender Receiver Framework (OSSRF) addresses this challenge, providing an open-source reference sender/receiver with NMOS control (IS-04, IS-05) and media plane integration. Built on the widely adopted nmos-cpp project, OSSRF exposes both a bare media API and GStreamer plugins, enabling real-time streaming with low-resolution ST 2110-20 (video) and ST 2110-30 (audio) flows. The framework demonstrates seamless NMOS operation on both commodity and cloud-based hardware platforms. OSSRF serves multiple purposes: as a foundation for NMOS integration in commercial products, as a test target for interoperability, and as a development tool for control application testing. By reducing barriers to entry and promoting open development, OSSRF aims to accelerate adoption, foster innovation, and deliver a flexible, community-driven alternative to proprietary systems. ##

Partnership to address business and technical challenges of DMF adoption September 13, 2025  – The Advanced Media Workflow Association (AMWA) and the European Broadcasting Union (EBU) today announced the formation of the Joint Task Force on Dynamic Media Facilities (JT-DMF), a groundbreaking collaboration designed to facilitate an industry-wide transition to the Dynamic Media Facility (DMF) concept and software-based media production. The JT-DMF aims to establish an industry council bringing together vendors, end-users, and systems integrators to discuss critical business, technical, and strategic questions and challenges. Initial focus areas include developing timing models to support the Media Exchange Layer (MXL) Software Development Kit (SDK) open-source project, establishing a business-level advisory council, and addressing orchestration challenges through AMWA's expertise in media workflows and Networked Media Open Specifications (NMOS). The task force will operate as workgroups composed of members of EBU and AMWA, ensuring broad industry representation and expertise, with a governance committee composed of leadership from both organizations.  Félix Poulin, Director of Global Innovation Collaborations, CBC/Radio-Canada, emphasized the significance of the task force, stating, "This initiative will be at the forefront of this emerging technology and represents a pivotal next step in our industry's evolution toward more flexible, efficient media production environments." “This is a major milestone toward an open, efficient, software-defined future, as key players in the industry join together,” said Willem Vermost, Senior Media Technology Architect, EBU. "At EBU, we are proud to work with AMWA on this joint task force because our organizations share a common vision for a scalable, interoperable, agile media landscape." "This collaboration leverages the collective expertise of our member organizations to drive meaningful industry transformation," said Brad Gilmer, Executive Director, AMWA. "It represents the ideal place for these critical discussions to happen, bringing together business and technical perspectives to address the complex challenges of dynamic media facility implementation." Phil Tudor, Head of Applied Research, BBC R&D, emphasized the broad nature of the effort: "The Task Force will bring together a wealth of experience to ensure that the next wave of live production infrastructure can benefit users and vendors alike. We are looking forward to working with EBU and AMWA on what promises to be an exciting set of challenges for the industry." For more information on the JT-DMF, contact Cindy Zuelsdorf of AMWA  at cindy.zuelsdorf@amwa.tv  or Patrick Wautier of EBU  at wauthier@ebu.ch . See the EBU article here. About AMWA   The Advanced Media Workflow Association (AMWA) is a membership organization that brings together the media industry to collaborate on open standards and best practices for media workflows. AMWA develops the Networked Media Open Specifications (NMOS) and promotes vendor-neutral approaches to media technology implementation. Find out more at https://www.amwa.tv/ . About EBU   The European Broadcasting Union (EBU) is the world's foremost association of national public media organizations, representing 113 members from 56 countries. The EBU promotes the interests of public media and facilitates the exchange of program content, best practices, and technical standards among its members. Find out more at https://www.ebu.ch/home .  # # #

If you're involved in media production technology — whether you’re a broadcaster planning your next equipment purchase, a manufacturer developing new products, or a systems integrator architecting systems for the future — knowing the industry’s preferences for control plane standards will help you make decisions that align with where the market is clearly moving. The results from a comprehensive survey conducted by AMWA and EBU reveal critical insights that could shape your technology decisions and strategic planning for years to come. The survey explored how professionals across our industry view control, which is defined as the ways users interact with and manage media devices, including hardware equipment and software applications.  With 97 responses representing 75 different organizations — including everything from small media companies to the largest, most prominent manufacturers, systems integrators, and broadcasters — these findings offer a representative snapshot of where your peers and competitors see the industry heading. One methodology note before diving into the data is that when there were multiple responses from the same company, those responses were aggregated to count as a single response per organization. For the purposes of this survey, Control is defined by the ways users interact with and manage Media Devices - including hardware equipment as well as software applications. Those interactions include: Dynamic Operations: Adjusting live operational parameters through user interfaces like knobs, faders, buttons, and selectors. Device Observation: Monitoring Device status and alarms via monitoring systems. Initial Configuration: Configuring static parameters to establish a Device's initial or default state. An Open Control Specification is the Priority When asked to rank what’s most important to respondents, the top choice was an open control specification. The overall ranking was the same for all categories of respondents.  Respondents were less interested in conforming to the same spec, or a limited number of control specs. Because the least popular response was that only some devices should have a control specification, that could be interpreted as the industry wanting all devices to be controllable. NMOS-Control is the Top Choice for Interoperability When asked how we can best achieve control interoperability, the most popular answer is NMOS-Control APIs (IS-12, BCP-008, MS-05, and IS-14). This was the top choice among all categories of respondents. The second most popular response in all categories was any open specification or API. Combined, the vast majority of survey respondents (74%) are clear in wanting an open solution.  Catena was only selected by 7% of manufacturer respondents as their choice for interoperability, but it wasn't a preferred option for end users or systems integrators. Open specifications for the purposes of this survey means: Publicly Available: It is freely accessible to anyone, typically without a charge for the document itself. This means it can be read, downloaded, and distributed by all interested parties. Well-Documented: The specification is comprehensive, clear, and unambiguous, providing all necessary details for multiple independent implementations to achieve interoperability. It avoids intentional secrets or ambiguities that would hinder implementation. Royalty-Free/Compensation-Free: There are no royalties or fees required to implement or use the technology described by the specification. This means that anyone can develop products or services based on the specification without paying licensing fees for intellectual property (like patents or copyrights) essential to its implementation. While certification for compliance might incur a fee, the core use of the specification for development remains free. Vendor-Neutral & Non-Discriminatory: It is not controlled by a single company or individual. Its development and maintenance typically involves a collaborative, consensus-driven process overseen by an association, standardization body or open-source framework, ensuring fair competition and preventing vendor lock-in. When asked about using NMOS Minimum Status Monitoring (NMOS BCP-008),  which defines an easy-to-follow traffic light system to monitor the health of IP media facilities, 75% of all respondents were very or somewhat interested. As you might expect, twice the number of end users are very interested in NMOS Minimum Status Monitoring compared to manufacturers, clearly showing that it is the end users who feel the pain trying to monitor faults in real-world multi-vendor installations.  For more about Minimum Status Reporting and how it could simplify your workflow, check out this 2.5-minute video .  Three out of Four Are Moving Toward Software Finally, when asked how prepared respondents are for a transition to software-based (or cloud-based) production, 76% say they are fully or partially prepared. Manufacturers are the most likely to indicate that they’re ready, with nearly half saying they are fully prepared. Among end users and systems integrators, 25% say they are in the early stages of preparation.  These surprisingly strong data points may indicate a self-selection bias among respondents to a survey about a Media Control Plane. However, we can safely conclude that our industry is well aware of this next major transition.  Conclusions As the industry transitions to software-based production, it’s clear there is a real need and desire for control plane interoperability. And an open control plane is the most-wanted approach, with NMOS- Control as the top choice, followed by any open specification. There’s also a lot of interest in using NMOS Minimum Status Reporting.  Want to find out more about NMOS-Control? Read this blog post: NMOS: What’s In It For You? Device Monitoring, Minimum Status Reporting, and More.   The AMWA and EBU survey shows that the industry wants an open media control plane to achieve interoperability. Your Input! Take 30 seconds and let us know if you’d like to attend a workshop, participate in a tested event, or something more: https://forms.gle/wFXi11DWnrNN1PAK7

If you’d like to quickly pinpoint 80-90% of the problems that are encountered in IP systems, you will want to read this part 2 blog post to find out how NMOS device monitoring – just one of the useful benefits covered below – can save you time, costs, and errors. See how NMOS Control and BCP-008 give you the minimum status reporting you need. If you haven’t read the first blog post, which covered NMOS Connect – discovery, registration, device management, and signal management – you can read part 1 here.   Generic Control Protocol There’s a part in NMOS that allows you to read, write, or send any kind of settings of any device. It’s an open generic layer where you can send and read all kinds of settings and it could replace a lot of legacy control protocols.  Editor’s note: This is part 2 of a blog post based on the 2024 NAB presentation of Stefan Ledergerber at Simplexity  in Zurich, Switzerland. You can view the full presentation NMOS: What’s In It For Me? on YouTube . Connect with Stefan on LinkedIn . NMOS specifies a generic control protocol that defines a certain rule set of how to communicate with each other. It is open to define what are called device models. If you’re a manufacturer, you can model all of your products and parts inside that spec. Any device model distinguishes between:  Properties , which are device settings. Methods , which execute a functionality, so for example, hitting a play button on a machine would be a method.  Notifications , so you can subscribe to certain elements that you are interested in knowing about, and then if a value changes, you would be notified from the device.   The last one, notifications, is very important. As you know, right now, many systems require you to pole, reading out values repeatedly in order to find out whether it has changed. That's not very efficient and doesn't scale very well across big installations.  Device Monitoring On the device monitoring side, AMWA members  are about to finish standardizing IP-related status reporting mechanisms. It's not just a question of whether you get access to information. It goes beyond that and it's about minimizing the amount of information you're actually sending across the world. Less is more. Because nothing is more boring than looking at a screen with hundreds of messages. And in many practical cases, people operating MCR get stormed with messages, and assume they’re not relevant so they start ignoring them. NMOS allows you to reduce the storm of messages down to what’s most important.  By looking at 3 simple domain statuses that follow the analogy of traffic lights, you could probably find 80-90% of the problems you encounter in an audio/video-over-IP system. These traffic lights could at least allow an operator to call the right person quickly and address issues more efficiently.  The NMOS Reporting domains are: Connectivity , which includes 2 traffic lights: physical link and packet level. This could be a link down or some of the links down, or packets missing, being late, or lost (on receivers) or transmission errors of any kind (on senders). Synchronization , so is the expected synchronization present? This includes issues like PTP unlock or grandmaster change. Stream Validation , which include issues with decoding the stream (on receivers) or invalid baseband signal to transmit (on senders). If these 3 status reports are supported in every end device, you will be able to find most of your problems and target them quickly.  On top of these, every sender and receiver is indicating an “overall status,” as a summary of the 3 domain statuses. It takes the worst state of the 3 domains contained. By using a traffic light symbol again, this overall status could be indicated straight in your user interface. If every sender and receiver in use is indicating green, it will give you confidence that your IP system is working just fine. A yellow state would say that you should possibly check the system during the next break, but all audio/video signals are still perfectly fine. However, a red state on a sender or receiver should trigger immediate action, first by checking the 3 domain status lights, then by calling the expert on the respective domain. Minimum Status Reporting with NMOS BCP-008 Since this overall status is a summary, manufacturers are welcome to add more states to the 3 “minimum status” reports, as this AMWA initiative is called. The overall status would still take those extensions into account and indicate the worst of them. Initial Setup of Devices The third part of Device Settings and Monitoring is an initial setup of devices. These specs explain how you take the device out of the box and get it to a default setup. There's also a backup restore functionality that’s described. Network Security The fourth and final focus of NMOS is security. They describe the standard mechanisms IT uses:  Control encryption of commands using HTTPS Access authorization – how to use an authentication server How to handle certificates  None of this is news to IT folks, but there is a need for describing how to use it in the context of NMOS, and that’s what these specifications do.  So, as an overview, what’s in the web in the image above is what NMOS describes. It's basically everything. And most of it is ready and clearly defined. And yet, out of all of this, all that people are primarily familiar with IS-04 and IS-05. That’s what’s in the purple ovals.  Now in the next image, you can see the numbers that correspond to each function of NMOS. There's a whole channel of documents, best practices, and specifications on the NMOS website  that you can read. The documents are public, and even the meeting notes are public. Get started at https://specs.amwa.tv/nmos/ .  What’s In It For Me? So to sum up, if you’re an end user, NMOS can shorten your requirements engineering phase. You can leverage work done by others and actually use that work when you write your RFPs. You don't have to think it all through yourself.  With that being said, it is important to ask vendors for NMOS, but don't just write in your RFP, “It has to do NMOS.” That's just not enough. Now that you see everything that NMOS can do, you can appreciate why it’s important to get more specific with what you need.    Ultimately, it will help you build an open system with no vendor lock-in, and that will save you on costs. And if you’re a manufacturer, NMOS shortens your requirements engineering phase. You can also leverage work already by others – specifications, coding, and testing. You don't have to do that all yourself. You can become part of a complete solution rather than just offering products. And ultimately, all of these benefits add up to saving on costs, which means you can increase your profit.  If you’re surprised to find out that NMOS can save you time, costs, and many common problems and errors, you’re invited to find out even more by joining AMWA . As a member, you can take part in working groups and the NMOS community that provide a place for open technical discussions and consensus between a wide range of end users and suppliers. Join today and be a part of the future of NMOS.  Resources Download Download Download Info for Purchasers and decision-makers   Info for strategic technical people and details on business efficiencies   Info for those responsible for making everything work together, integrators, end users   Find out about IPMX and NMOS   Get started with NMOS here: Open source sender and receiver framework (GitHub) Want to start implementing NMOS Control in your products? See tutorials, info on IS-12, BCP-008, and more . Ready to join AMWA?

On the recent AMWA webinar: Getting Started with ST 2110? Here’s Why NMOS Should Be Part of Your Plan, the hosts, Willem Vermost of the EBU and Pedro Ferreira of Bisect answered common questions about NMOS like… Why NMOS is a suite, and not a single spec (much like ST 2110)  How (and why) to create your NMOS test bench Why NMOS uses existing internet technology How to choose between a proprietary control system and an open control system How RESTful interfaces and standard control mechanisms ensure that once you understand one NMOS API, all the rest feel familiar Check out the full recording of the webinar to get all the answers. When you watch, you'll find out about the tools, test-bench tips, and real-world reasons engineers rely on NMOS.  Using NMOS from the start in your ST 2110 set ups makes your day-to-day job so much easier.  Why? Because NMOS lets you automatically discover and connect devices, avoiding time-consuming manual setup. And going forward, it gives you vendor-neutral control of your system, so your workflows stay flexible and scalable. After you watch, if you’d like to find out more about how you can take advantage of all that NMOS has to offer to make it easier to run IP facilities, visit amwa.tv/nmos-getting-started Resources: Get started with NMOS here: Open source sender and receiver framework (GitHub) Want to start implementing NMOS Control in your products? See tutorials, info on IS-12, BCP-008, and more . Ready to join AMWA?

When people talk about NMOS, what they typically mean is IS-04, discovery, and IS-05, registration.  But the reality is, NMOS does so much more... ​ If you don’t know what NMOS is capable of, you’re not asking manufacturers for it. And if you’re a manufacturer, you’re not building it into your new products. And that’s a lost opportunity, as we’ll discuss in this blog post, as well as the next. NMOS goes far beyond its well-known IS-04 and IS-05 protocols, offering a comprehensive suite of tools for managing IP-based media networks – from dynamic signal routing and device configuration to security and monitoring. This complete toolset can make it easier for you to handle resource management, signal connections, and system maintenance across your entire media infrastructure. NMOS: What's in it for me? ​             Editor’s note: This blog post is based on the 2024 NAB IPSHOWCASE presentation of Stefan Ledergerber at Simplexity in Zurich, Switzerland. You can view the full presentation NMOS: What’s In It For Me? above, or on YouTube .  ​ ​Let’s start by looking at a typical IP installation. To understand NMOS's full capabilities, consider this scenario: You’re doing dynamic signal management and you want to start switching the signals between A and B. You have to configure correct stream formats again and again, unless you keep them static. But you’re using IP because you want flexibility, right? So it has to be set up correctly. And by the way, the conventional device settings are not going to go away. You still need to do multi-viewer setup, mic preamp control, and so on. ​ Then you need to monitor your installation. You need to know whether it's working fine. And you want to be able to find faults very quickly. And you also want to be able to move or replace products, moving  them around within pools.    You want to keep a number of devices in a pool and just take them out and connect them somewhere because that's where you need the device right now. And if you do that, then you need to discover where you just connected them because otherwise, they're invisible and not controllable. And what you also need to do is make sure that a new device gets the correct basic setup. Last but not least, you need to constantly ensure that the security standards in your network are met. ​ So if you look at those scenarios and challenges, the question is, what can NMOS do for you in terms of what's defined in NMOS in these very practical situations?  ​ Resource Management ​ What does NMOS specify in terms of managing your resources? NMOS describes a central inventory system, which can work across subnets and across the whole infrastructure.  The centralized inventory system allows you to: find devices and their IP senders and receivers read out by spec what a certain sender or receiver is able to do and which format it supports see what you can connect to a sender or receiver, or what kind of format it’s able to generate look at which streams belong to each other, which is called natural grouping give a device a label or tags put in any kind of device description ​ There is one more thing in resource management beyond these core features. It's possible to read out the system-wide parameters you have decided to use. For instance, PTP domains. You can read that out via a special mechanism. ​ Signal Management ​ This is the more dynamic part of day-by-day operation. Let’s walk through an example of 2 AV devices. They may contain all kinds of things you want to control like:  baseband inputs and outputs a matrix in there to switch between these inputs and outputs and maybe others or into a sender or receiver metering data GPIOs thumbnails on the video side ​ NMOS is able to control those elements inside AV devices and connect them to other devices. Breaking this down, of course you have senders to receivers, but also more than that. NMOS also specifies how you select baseband inputs and feed them into a sender. It also specifies in which baseband outputs a receiver should be fed on a monogranularity of an audio channel. It also allows you to transfer GPIO.  ​ So signal management means connecting all kinds of signals from a sender to a receiver or from one device to another. What everyone knows is that NMOS can connect pre-configured senders to receivers. That means you can assign multicast addresses, making it possible to reach the point where these multicast addresses are not statically typed into a device. NMOS describes clearly how to assign to a sender a certain multicast address.  ​ The same goes for enabling and disabling senders and receivers. Maybe you want to stop the packets coming out. You can do that with NMOS. Think of it as a copy-paste of a transport file, so an STP file from a sender to a receiver.  ​ More than that, you can use any generic data source. For example, button press or audio levels, which are generating constantly changing values, and you can look at such a data source as a sender and connect that sender to a receiver. And it will transmit the constantly changing values almost as if it would be audio or video, but in a much lower bandwidth consumption.  ​ So using this kind of functionality, you can implement, for instance, generic control panels where button pushes are transmitted from one source to a destination, and then they react to that button push. So that's also something you can do with NMOS.   Another thing not a lot of people are aware of is that you can control the baseband matrix. You can set a baseband matrix and say which channels you want in your senders and receivers.  ​ Then there is stream compatibility management, which allows you to ask a sender what can you do? What kind of stream formats do you support? And you can ask a receiver what kind of stream formats can you receive? And then as a control system, you can choose the perfect match. It allows you to choose a certain stream format on a sender freely via a specified control command.  ​ So you may be able to do what the ProAV guys want to do with HDMI, which is just plug in and then it adjusts and finds out what's the best resolution. Via this mechanism, a control system could switch the stream format accordingly, so the receiver can actually receive it in the best possible resolution or quality.  ​ So that’s signal management and resource management. In part 2, we’ll delve into device settings and monitoring, and finally, security.   ​ If you’ve already found out one or two things that NMOS can do for you that you didn’t know before, you’re invited to find out even more by joining AMWA . As a member, you can take part in online forums that provide a place for open technical discussions and consensus between a wide range of end users and suppliers. Join today and be a part of the future of NMOS.  This is part one. See part two about NMOS Control, BCP-008, and minimum status reporting here.

With NMOS, everything works together – ST 2110 equipment registration, discovery, and control. You know it’s all going to work well when you use the specifications. It gives you peace of mind. And if you’re using IPMX, NMOS is baked right in. Matt Robbins of Kitplus caught up with Cindy Zuelsdorf of AMWA to talk about why you're going to want NMOS to play a part in putting a 2110 system or facility together. Watch the 3-minute video. > > During the show, we spoke with someone who's built a lot of baseband stations over the years, and now he’s putting together a new facility that's all 2110. He shared how they're going to use NMOS in conjunction with 2110 to handle equipment registration, discovery, and control. He had confidence everything would work together, thanks to NMOS.   If you want to find out more about how you can use NMOS to make IP facilities easier to run, visit AMWA.tv/nmos-getting-started .  If you want to get involved in advancing NMOS, you can! NMOS is made by its users – customers, vendors, and manufacturers. It's all open, free, and made by the community. Visit AMWA.tv/join  to get involved in AMWA working groups or community forums.

One of the problems that operators often face in IP facilities is that when things go wrong, you’re suddenly awash with alarms. It takes a while to sort through and figure out what’s wrong. Meanwhile, if you lose a couple of ad breaks, you're talking about a major revenue loss. That’s why AMWA members and users have done a lot of work around simplifying minimum status reporting. Now you can use an NMOS traffic light graphic display that presents the most critical information, so you can quickly get back on the air. Watch the video to see a quick demo of how it works. >> Brad Gilmer of AMWA spoke with Matt Robbins from Kitplus at the AIMS IP Showcase booth at NAB 2025 about the simple graphic display of green, yellow, and red to represent device control on systems of up to thousands of senders and receivers. “If you have a whole segment of these devices that are showing yellow,” Brad explains, “Then very quickly somebody can look at it and say, ‘There must be something wrong in this area,’ and quickly can identify a failed piece of equipment.” If you want to find out how you can take advantage of all that NMOS has to offer to make it easier to run IP facilities, including this new control system, visit AMWA.tv/nmos-getting-started .

Come say hi and find out more about how NMOS enables connection, management, and control of your IP video and audio devices from different manufacturers – in a common eco-system and in an interoperable way. NMOS works whether you're using 2110 or IPMX, locally or in the cloud. Even if you use NMOS already, you’ll be able to check out what’s new… You’ll find NMOS at the IP Showcase / IPMX booth, W2843  in West Hall. Look for Stefan Ledergerber along with other AMWA community members at the NMOS demo station. Get a hands-on demo of: NMOS minimum status reporting NMOS open source sender receiver framework NMOS control Special thanks to these companies that are making the demo possible: Arista Bisect DirectOut Matrox Merging Technologies Pebble simplexity NMOS Talks and Training at NAB • Evolution of NMOS for ST 2110 and IPMX with Spencer Deame from Nextera Video, Sunday, April 6 at 3:00 PT, W2831 Theater 3 • What You Need to Know About NMOS in an IP World with Steve Holmes from Leader, Sunday, April 6 at 2:30 PT, W2831 Theater 3 •  AMWA: NMOS Discovery and Beyond with Felix Poulin from CBC and AMWA Board of Directors, and Cindy Zuelsdorf from AMWA, Presented with SBE Ennes Workshop (paid session) Media Over IP Essentials, Day 2, Saturday, April 5 at 1:45 PT, W224  • IPMX training sessions all day on Tuesday including a session on NMOS & IPMX with Stefan Ledergerber from simplexity, Tuesday, April 8 at 11:20 PT, W317  If you want to set up a time to meet at booth W2843 or you have any questions, set a time here or use the chat on the bottom right of this page. See you soon in Vegas! Brad, Cindy, and Tina P.S. Follow us on LinkedIn  for the latest in NMOS news and applications around enabling vendor-independent control of all your IP video and audio gear. ST 2110, IPMX, AES67...