Quick Answer
SMPTE ST 2110 is a standards suite for carrying separate professional media essences over managed IP networks. It is most useful in larger broadcast systems that need precise timing, flexible routing, and multi-vendor control. NDI solves a different problem: simpler compressed production IP on lighter infrastructure.
What It Is
ST 2110 breaks video, audio, and ancillary data into separate multicast streams instead of bundling them into one combined signal. That lets systems subscribe to only the essences they need and makes facility-level routing much more flexible than baseband SDI or compressed all-in-one transport schemes.
- ST 2110-20: Uncompressed active video
- ST 2110-30: PCM audio transport aligned with AES67 concepts
- ST 2110-40: Ancillary data transport
- ST 2059: PTP timing profile used to align the system clock
ST 2110 vs NDI
A practical question is not "which one is better?" but "which problem am I solving?" ST 2110 is designed for high-control broadcast environments. NDI is designed for more accessible, compressed media networking on standard Ethernet infrastructure.
How to Use It
ST 2110 becomes attractive when you need independent routing of video, audio, and ancillary data, predictable timing, and standardized control in a larger plant. Smaller systems may run on 10 GbE, while larger facilities often move to 25 GbE or higher depending on raster, redundancy, and stream count.
If you are only comparing one compressed production workflow to another, ST 2110 may be unnecessary overhead. If you are designing a facility fabric, that tradeoff changes quickly.
The Control Layer: AMWA NMOS
ST 2110 defines how the media travels, but not how every device discovers and connects to every other device. In many multi-vendor systems, that role is handled by AMWA NMOS.
- IS-04: Discovery and registration
- IS-05: Connection management
Smaller systems may rely on multicast and IGMP behavior without a larger orchestration layer. In bigger facilities, centralized control and bandwidth awareness usually become much more important.
PTP Matters
Once video, audio, and ancillary data are separate network flows, the system needs a shared timing reference. That is where PTP (IEEE 1588) and the ST 2059 profile matter. Good timing design is what allows receivers to align separate essences reliably.
If PTP design, QoS, or clock behavior is unstable, synchronization quality degrades quickly. In real plants, that is a timing and network-engineering problem, not just a media-format problem.
Common Mistakes
- Assuming every ST 2110 design starts at the same link speed.
- Treating NMOS as optional in a multi-vendor control workflow.
- Planning only media bandwidth and skipping the timing layer.
- Comparing ST 2110 to NDI on bitrate alone instead of use case and control needs.
Related Tools & Next Step
Use the IP Video Calculator for bandwidth math, and review PTP Clocking Basics before treating media and timing as separate design problems.