Remote Production: Lessons Learned

Remote production, or REMI, has become a standard workflow. By 2025, broadcasters use it not only for sports but also concerts, conferences, and corporate events. The lessons learned over the past few years highlight what works and what doesn’t.

Why Remote Production Grew

Rising costs of travel and equipment, combined with better connectivity, made REMI attractive. Instead of sending full crews on-site, only cameras and minimal gear are deployed locally, with production handled centrally or in the cloud.

Technical Enablers

• Reliable transport: Protocols like RIST, SRT, and Zixi made long-distance contribution feasible.
• Low-latency compression: JPEG XS allows near‑real‑time UHD contribution.
• Cloud tools: Virtualized switchers and graphics expanded flexibility.

Operational Lessons

• Bandwidth planning: Always over‑provision; underestimating leads to failures.
• Redundancy: Dual paths and diverse ISPs are essential.
• Crew training: Remote workflows demand different skills than on-site production.
• Communication: Clear lines between remote and central teams prevent mistakes.

Challenges

• Latency: Even milliseconds matter for intercom and switching.
• Resource scheduling: Centralized facilities must manage multiple events simultaneously.
• Equipment mix: Interoperability between on-site and central systems remains tricky.

Remote production is no longer experimental. It saves costs and increases flexibility, but success depends on disciplined engineering and planning.