If you live in SDI, you already know the deal. One BNC, one signal, one cable from box to box. It just works, and it's been just working for thirty years. So when somebody starts talking about SMPTE ST 2110 and "video over IP," it sounds like a solution to a problem you don't have.
Here's why it matters anyway, in plain terms, from someone who grew up on coax.
SDI puts everything in one box. 2110 unpacks it.
An SDI stream is a bundle. Video, embedded audio, timecode, captions, all riding together down one wire. Convenient, until you want just the audio, or just one camera's worth of video, on the other side of a building. Then you're routing the whole bundle and stripping it back out.
ST 2110 splits that bundle into separate streams, called essences. Video rides on its own (that's 2110-20), audio rides on its own (2110-30), and the ancillary data like captions and timecode rides on its own (2110-40). Each one is its own flow on the network. You can grab the audio without touching the video. You can send one essence one place and another somewhere else. That separation is the whole point.
It runs on the network you already understand
2110 isn't some exotic broadcast fabric. It's video, audio, and data turned into IP packets and sent across standard Ethernet. The same kind of switches and fiber that move everything else in a modern building.
One catch worth saying out loud: this has to be a managed network. Real switches, configured on purpose, with bandwidth set aside for the streams. Office Wi-Fi will not carry uncompressed broadcast video. Anyone who tells you otherwise has never tried it on a show day.
The thing that holds it all together: PTP
When you split video and audio into separate streams on a network, you need a way to put them back in perfect sync at the other end. That job belongs to PTP, the Precision Time Protocol (IEEE 1588). It's the master clock the whole system locks to, down to the sub-microsecond.
If you remember genlock from the SDI world, PTP is the same idea built for IP. No clean timing, no clean show. It's the part people underestimate, and it's the part that bites first when something drifts.
How devices find each other: NMOS
In an SDI plant, your router and its crosspoints decide what goes where. In a 2110 system, that orchestration is handled by a controller, usually one speaking NMOS. It's how a camera, a multiviewer, or a gateway announces itself and how an operator says "send this source to that destination" without hand-editing IP addresses.
Think of NMOS as the router control panel for an IP plant. The streams do the moving. The controller decides the routing.
You don't have to rip out your SDI to start
This is the part that matters for working shops. You migrate at the edge, with gateways. An SDI-to-IP gateway takes your existing camera or router feed, wraps it into 2110, and puts it on the network. Coming back the other way, it unwraps IP into SDI for the gear that still speaks coax.
Most real facilities right now are hybrid. SDI islands where SDI makes sense, an IP core where scale and flexibility make sense, and gateways stitching the two together. Nobody serious is throwing out a working SDI router on a Friday.
So why bother?
Scale and flexibility. A big SDI router is a fixed box with a fixed number of ports. An IP fabric grows by adding switches. Remote production gets dramatically easier when your sources are streams on a network instead of cables in a rack. And separating essences means you route exactly what you need, not the whole bundle.
SDI isn't going away tomorrow, and you don't need to panic-learn 2110 this week. But the high-end is moving this direction, the cameras are starting to ship with it built in, and the people who understand it are the ones who get called for the big builds.
That's the short version. The long version, the one with the bandwidth math and the actual switch configs, is its own rabbit hole. We'll keep chipping at it here.
0 comments