For broadcasters, the move to IP-based infrastructure has long promised greater flexibility, scalability, and long-term viability. But those benefits can be offset by costly missteps, especially for teams accustomed to the straightforward interconnections of SDI. While the transition to IP is well underway, it’s rarely straightforward.
Drawing on lessons from real-world deployments, here are 10 of the most common pitfalls that broadcasters encounter when implementing IP-based workflows—along with steps broadcasters can take to avoid delay, complexity, or unexpected expense as they make the shift.
1. Treating the network as a commodity
With conventional SDI connections, routing and switching are handled by purpose-built, broadcast-grade hardware. The move to IP shifts that responsibility to the network itself. In this context, the switch fabric becomes the backbone of broadcast production. To ensure that network switches are up to the task of handling uncompressed video, precision timing, and multicast traffic, broadcasters benefit from validating their support for key broadcast protocols such as SMPTE ST 2110, NDI, and IPMX, as well as Dante, AES67, and others.
2. Overengineering the architecture
Designs that rely on excessive VLAN segmentation or overly complex Layer 3 routing can create as many problems as they solve. When based on a solid understanding of multicast traffic patterns, redundancy needs, and timing requirements, simple implementations tend to be more resilient and easier to support. Carefully engineered Layer 2 networks, especially those with robust multicast management, often meet the needs of small to mid-sized production facilities without unnecessary overhead.
3. Installing from the edge inward
In larger-scale IP-based media networks, it’s tempting to begin deployments at the endpoint level. This is especially true under deadline pressure. But building from the edge inward can lead to bandwidth mismatches, timing issues, and topology problems that are harder to fix later. Broadcasters can avoid this issue by starting at the core, ensuring that aggregation switches, inter-switch links, and timing infrastructure are designed and tested before they bring edge devices online.
4. Skipping interoperability testing
A successful IP-based workflow depends on interoperability between dozens of components: cameras, intercoms, routers, playout systems, timing sources, encoders, and more. Without prior testing —whether by the broadcaster, the vendor, or an integrator — teams can quickly run into performance issues or outright failure. Mutual certification, whether formal or informal, can significantly reduce time-to-air and ensure reliability when it matters most.
5. Undervaluing comms infrastructure
Show communications often take a backseat to video and audio infrastructure. But without reliable intercom, there is no show. For IP-based comms systems to work seamlessly, the network must support strict timing, redundancy, and prioritisation. This is especially critical for large-scale live productions, where latency or packet loss in comms can bring everything else to a halt.
6. Focusing on one technology to ‘future-proof’
Broadcasters are increasingly operating in hybrid environments. SMPTE ST 2110 may form the foundation of IP-based media operations, but NDI, SRT, Dante AV, and even emerging standards such as IPMX are all part of the conversation, particularly in remote production, contribution, and rapid-deployment scenarios. Rather than lock into any one standard, broadcasters can take advantage of broad standards support to build an infrastructure capable of supporting a mix of protocols and of evolving along with industry standards and protocols.
7. Assuming IP networking is just IT with video and audio
Broadcast networks have fundamentally different requirements than enterprise IT, which supports other vital operational and business areas. While IT often favours wireless access and shared bandwidth, broadcast demands deterministic performance, low latency, and precise synchronisation, especially in live workflows. Because features such as PTP timing and multicast routing aren’t typical IT concerns, standard switch configurations may fall short. Treating media transport like general IT traffic can lead to instability. Broadcast IP networks should be designed and managed with real-time media behaviour in mind.
8. Using unverified cabling or fibre links
High-bandwidth links between switches can be a critical failure point in IP-based networks. Using untested cables or trying to save money on optical modules can lead to compromise in the form of packet loss, synchronisation problems, or single points of failure. Redundant fibre links, proper link aggregation, and careful testing of all interconnects are non-negotiables for production-grade reliability.
9. Expecting one-off designs to be reusable
Every broadcast network has its quirks. Design templates can be useful starting points, but configurations often need to be customised for each use case, especially when dealing with varying stream counts, formats, and timing domains. Cloning an old design onto a new deployment without revalidation is risky.
10. Relying solely on in-house expertise
Having networking experts on staff is always a plus. In many cases, however, it’s not enough. Networking professionals are in high demand, and turnover can leave organisations vulnerable. Working with experienced integrators and technology partners with deep knowledge of both broadcast and networking ensures support is available before, during, and after deployment. More vendors are now offering professional services, from pre-sale validation and design reviews to on-site deployment support and live event standby assistance.
A final word
IP-based broadcast infrastructure does require a shift in mindset. Engineers must approach the network as part of the production toolset, not just an IT resource. With proper planning, simplified design, and trusted partnerships, broadcasters can avoid the most common pitfalls and build workflows that are flexible, reliable, and ready for the future.
