System T Virtual Tempest Engine (VTE) gives broadcasters the flexibility to deploy broadcast audio processing wherever it is needed: in the cloud, on-premises or as part of a hybrid production model. Designed for modern software-based productions, VTE enables audio production teams to scale processing resources for temporary, event-based, proof-of-concept or large-scale workflows while maintaining the familiar control, audio quality and operational consistency of the System T platform. Whether supporting remote production, temporary capacity, disaster recovery, multi-studio workflows or immersive audio production, VTE provides a flexible route to System T processing without being tied to a single deployment model.
Leveraging patented x86 CPU optimal core processing (OCP) technology, SSL’s Virtual Tempest Engine (VTE) provides the same advanced processing feature-set as the hardware-based Tempest Engine range. The software-based Virtual Tempest Engine (VTE) operates within a Linux-based environment optimised for low latency throughput, providing real-time, deterministic audio processing and mixing for the cloud, hybrid and on-premises environments.
System T VTE provides up to 256 processing paths, including support for stereo, 5.1 and immersive formats, all controlled via hardware or software interfaces from any location. These interfaces are specifically designed for broadcast production and provide the same familiar System T feature set across virtualised workflows.
VTE provides filters, EQ, dynamics processing, automixing and delays on all channels and buses, plus an inbuilt Effect Rack. Mix minus, monitoring and talkback features are included in addition to main program buses, stem groups, track buses and auxiliary outputs. Any channel or bus can be mono, stereo, 5.1, 5.1.4, 7.1.4 or 9.1.6, providing a full toolkit for immersive productions and Dolby Atmos workflows.
System T VTE supports a range of deployment models, giving broadcasters the freedom to choose the right infrastructure for each production.
This flexibility allows broadcasters to deploy, scale and repurpose System T processing resources according to operational needs, without compromising audio quality or the operator experience.
System T Cloud delivers flexible virtualised processing through a choice of DSP pack sizes.
Alongside the 256-path VTE1 option, the 140-path P1 DSP pack provides the same broadcast-grade processing feature set as the TE1 P1 engine, with software-based I/O via Dante and/or NDI.
For smaller production requirements, µVTE (“micro VTE”) offers a 96-path virtual engine designed to bring the System T feature set to workflows that require a reduced DSP footprint.
Together, these scalable options make it easier to adopt System T Cloud across temporary, event-based, proof-of-concept and full-scale cloud production environments.
System T Cloud is available with flexible licensing options designed to help broadcasters scale production resources precisely when they need them.
Alongside annual subscriptions, 4-week and 12-week licences provide a practical way to support temporary, variable or event-based productions without long-term commitments or significant upfront investment.
These short-term options are ideal for projects that require additional production capacity for a defined period, such as major event coverage, overflow production, temporary studios, disaster recovery, proof-of-concept deployments or seasonal programming. They also give teams the time needed to configure, test and deploy software-based production workflows with confidence.
By combining System T processing with flexible licensing, broadcasters can adapt quickly to changing production requirements while maintaining the quality, control and operational consistency expected from the System T platform.
System T VTE can be deployed on-premises on shared server hardware, reducing investment in dedicated hardware while enabling server resources to be repurposed for maximum operational efficiency. This is ideal for facilities with high utilisation requirements, hybrid production models or operational environments where local control, predictable infrastructure costs and direct integration with existing systems are essential.
On-premises VTE deployments can be combined with Tempest Control App, System T hardware tiles or existing System T control surfaces, providing the same familiar operator experience across software-based, hybrid and traditional production environments. Multiple software-based audio engines can also run on shared server hardware, helping broadcasters reduce dedicated hardware requirements while supporting scalable, multi-studio workflows.
This approach aligns with the move towards software-defined production, where processing resources can be deployed, scaled and repurposed across cloud, hybrid and on-premises environments according to the needs of each production.