In the legacy world of broadcast engineering, the control room was a cathedral of dedicated hardware. Dozens of SDI cables snaked from routers to rows of expensive, single-purpose CRT monitors. To see all your sources—cameras, graphics, feeds from satellites—you needed a multiviewer: a specialized, often proprietary, and notoriously expensive piece of gear. If you wanted to monitor 16 sources on a single 4K screen, you bought a $20,000+ hardware multiviewer or a proprietary software license that cost as much as a car.
The first building blocks appeared as libraries. Projects like and FFmpeg added robust support for decoding RTP streams, handling JPEG-XS compression, and synchronizing PTP clocks. These weren’t multiviewers themselves, but they were the engine and the transmission. ip multiviewer software open source
The first true open-source IP multiviewer to gain traction was a scrappy web-based tool. A developer frustrated with the cost of monitoring a small ST2110 network built a Node.js application that used and WebRTC. It could ingest up to four UDP streams, scale them, and display them in a browser window. It was ugly, had no audio metering, and dropped frames when the CPU got busy. But it worked. For a high school TV studio or a church broadcast team, it was a miracle. In the legacy world of broadcast engineering, the