Transport standards solved one question and opened another. SMPTE ST 2110 and AES67 can carry dozens of audio channels and video streams across an IT network, with a precise clock and perfect quality. But an ST 2110 stream does not introduce itself, and it is not routed with a click the way a cable was once patched. On a network carrying thousands of streams, you need a directory and a conductor. That role falls to NMOS.
The acronym covers a set of open specifications that sit on top of the transport. Where the foundation is laid by audio over IP and its standards, NMOS answers two practical needs: knowing which devices exist on the network, and commanding who sends what to whom.
The problem NMOS solves
In SDI, routing was physical. A signal left an output, arrived at an input, and a crosspoint matrix linked the two. Each link was a cable or a grid point. In IP, that obviousness disappears. A source becomes one stream among thousands, identified by an address and parameters, invisible until a system announces it. Without a discovery layer, an operator would have to know every stream’s address in advance and type it by hand. NMOS removes that chore and makes it reliable.
Who writes NMOS
NMOS is developed by the AMWA, the Advanced Media Workflow Association, a group of broadcasters and manufacturers. Its specifications carry numbers prefixed with IS, for Interface Specification. The appeal is their open nature: a Lawo device, a gateway from another maker and a third-party controller speak the same language, as long as they follow the same IS documents. You leave behind the proprietary logic where each brand imposed its own routing system.
IS-04, discovery and registration
The first brick answers the question of who is there. Each device is seen as a node. On start-up, it declares what it holds: its sources, its flows, its senders and its receivers. That declaration goes to a central registry, which keeps an up-to-date list of the whole network. A controller can then query the registry and get, in a single request, the full inventory of available streams. Without a registry, nodes can also announce themselves peer to peer, but the registry model dominates in serious installations because it scales better. The shared clock that aligns all these streams is a separate mechanism, detailed in the article on PTP and clocking.
IS-05, connection
Knowing who exists is not enough: you have to link a source to a destination. That is the job of IS-05, connection management. A controller asks a receiver to subscribe to a specific sender, passing it the stream parameters as an SDP descriptor. The receiver then locks onto the right stream. That operation reproduces, virtually, the crosspoint of an old switching matrix. An operator sees two lists, sources and destinations, and crosses them as on a classic router, never handling an address.
The other bricks, including one that speaks audio
The family does not stop there. IS-07 carries events, such as tallies. IS-09 distributes the system’s global configuration. Other documents handle security and fine control. One specification concerns sound directly: IS-08, which manages audio channel mapping. An ST 2110-30 stream can carry several channels, and IS-08 lets you route a given channel to a given input without rebuilding the whole stream. For a radio or TV control room juggling dozens of channels, that granularity matters as much as the connection itself.
Audio in a hybrid plant
NMOS applies to audio as it does to video, since ST 2110-30 carries exactly AES67-compatible audio. In a real installation, NMOS often coexists with Dante, which has its own discovery and routing mechanism through its in-house software. The article on Dante describes that integrated approach, both a strength and a limit: simple within a Dante world, less open between brands. NMOS plays the opposite card, that of multi-vendor interoperability, at the cost of a more demanding setup. Many plants mix the two, with gateways between the worlds. The redundancy of those streams rests on a separate mechanism described in the article on ST 2022-7.
In practice, one panel to route
In the field, NMOS takes the shape of a broadcast controller, a piece of software or a hardware panel that aggregates the whole network. The operator sees every declared stream and makes connections without worrying about addresses. Production consoles designed for IP expose their inputs and outputs natively to that controller. The Lawo diamond or the Calrec Argo, for instance, fit into an NMOS environment and can be patched from the same controller as the gateways and processors. A recent wireless device such as the one described in the Sennheiser Spectera article also joins this world of streams.
My take
NMOS is the quiet piece that makes IP usable day to day, far from trade-show demos. Without it, an ST 2110 network would stay an address puzzle; with it, routing is once again as simple as crossing two lists. The real value is its openness: being able to mix brands behind a single controller changes how you design a control room. The flip side is a more technical setup than a proprietary system. For a broadcaster investing over ten years, it is well worth it.
