Cloudbass software-defined remote production trial cuts outside broadcast hardware footprint
Cloudbass has completed a proof of concept for software-defined remote production during live racing coverage, utilizing Grass Valley AMPP and SSL System T technology. The trial demonstrated that processing can be kept onsite while control is managed remotely over public internet, potentially reducing the physical infrastructure footprint for outside broadcast operations.
Key Takeaways
- Remote control of onsite processing required only 50 Mbps of upload bandwidth over public internet.
- Virtualised audio processing ran on commercial off-the-shelf (COTS) servers using SSL’s Virtual Tempest Engine.
- The setup allowed a 32-fader SSL System T S400 surface in Ripley to control hardware at Thruxton Circuit.
- Integration with ST 2110 infrastructure was achieved via an SSL Net I/O bridge for local signal distribution.
Why It Matters
This proof of concept demonstrates a shift toward decentralized live production where heavy processing remains at the source while operators work from centralized hubs. By utilizing COTS hardware and public internet for control, Cloudbass reduces the need for massive, purpose-built outside broadcast vehicles and expensive dedicated fiber links. This model addresses the industry's push for sustainability and cost-efficiency by allowing production teams to scale processing power based on specific event needs rather than fixed hardware limits. Watch for whether this hybrid approach—onsite processing with remote control—becomes the standard for mid-tier sports rights to avoid the latency and bandwidth costs of full cloud migration.
Companies in this story
In short
Cloudbass recently completed a proof of concept for software-defined remote production during live racing coverage. By keeping processing onsite while controlling operations remotely via public internet, the trial successfully reduced the need for large outside broadcast vehicles. This hybrid model offers a sustainable, cost-efficient alternative for scaling live production workflows.
FAQ
What technology did Cloudbass use for the remote production trial?
The trial utilized Grass Valley AMPP and SSL System T, with virtualized audio processing running on commercial off-the-shelf (COTS) servers using the SSL Virtual Tempest Engine.
How much bandwidth was required for the remote control setup?
The remote control of the onsite processing required only 50 Mbps of upload bandwidth over the public internet.
What was the benefit of this remote production setup?
This setup reduced the physical infrastructure footprint typically required for large-scale outside broadcast vehicles, allowing production teams to scale processing power based on specific event needs.
How was the SSL System T surface used in the trial?
A 32-fader SSL System T S400 surface located in Ripley was used to control hardware situated at the Thruxton Circuit.
Read full article at thebroadcastbridge.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source