PlatformsTechnical DevelopmentOctober 30, 2026

Cloudbass remote production workflow cuts bandwidth to 50 Mbps at Thruxton

Cloudbass remote production workflow cuts bandwidth to 50 Mbps at Thruxton

Cloudbass successfully tested a software-defined remote production workflow at the British Touring Car Championship using Grass Valley AMPP and SSL virtualized audio processing. By keeping processing onsite and remoting only control data, the company reduced onsite infrastructure requirements and bandwidth needs compared to traditional remote production models.

Key Takeaways

  • Bandwidth requirements dropped to approximately 50 Mbps by remoting only control data and monitoring feeds rather than uncompressed sources.
  • Core services were consolidated onto commercial off-the-shelf (COTS) servers, replacing traditional power-intensive hardware.
  • Remote operations were managed from a Ripley gallery using an SSL System T S400 control surface over a public internet connection.
  • The workflow utilized Grass Valley AMPP for video and SSL’s Virtual Tempest Engine for audio processing onsite at Thruxton Circuit.

Why It Matters

This trial demonstrates a shift toward decentralized outside broadcasts where processing stays local to the event while control moves to the cloud or a remote hub. By retaining high-quality signals onsite and only transporting 50 Mbps of control data, Cloudbass addresses the primary bottleneck of traditional remote production: the lack of high-bandwidth infrastructure at many sporting venues. This software-defined approach allows broadcasters to scale resources dynamically without the thermal and spatial constraints of physical trucks. As the industry faces increasing pressure to improve sustainability and operational efficiency, watch for whether this hybrid local-processing/remote-control model becomes the standard for mid-tier live sports rights.

Companies in this story

In short

Cloudbass successfully tested a software-defined remote production workflow at the British Touring Car Championship. By utilizing virtualized processing and remoting only control data, the team reduced bandwidth requirements to 50 Mbps. This innovation allows broadcasters to scale resources dynamically while overcoming the lack of high-bandwidth infrastructure at sporting venues.

FAQ

What bandwidth did the Cloudbass remote production workflow require?

The workflow required approximately 50 Mbps of bandwidth by remoting only control data and monitoring feeds instead of uncompressed sources.

What technologies were used in the Cloudbass test at Thruxton?

The test combined Grass Valley AMPP for video processing and the SSL Virtual Tempest Engine for audio processing.

Why is this remote production workflow significant?

It addresses the bottleneck of limited high-bandwidth infrastructure at sporting venues by keeping processing local while moving control to a remote hub.

Where were the remote operations managed from?

Remote operations were managed from a Ripley gallery using an SSL System T S400 control surface connected via the public internet.


Read full article at tvbeurope.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

Related Articles

Get this in your inbox → Subscribe