CG Virtualisation

What if the entire insert graphics package could be delivered OTT natively?

Virtualisation

While virtualisation can run a CG engine, it would struggle to scale across multiple users and use cases. That's before you even look at handling the output from the virtual machine into your program.

Native is better.

To avoid the drawbacks of repacking existing systems into virtual machines, MST has taken a cloud-first approach to our software and service designs for both remote and traditional productions.

This means despite our integrations and work with traditional CG engines, our bespoke graphic operator interfaces and own graphics engine also work natively in the cloud.

Output & Operation

Our entire CG output can be built into a URL that renders graphics directly. No encoding/decoding at either end required! Once the URL is loaded at the production end, it's ready with minimal latency to receive commands, render and output.

Operationally, on the other end of the system, graphics operators need only connect to the web-based control user interface (customised per templates/sport/production) to service any number of connected systems.

This native cloud-first approach offers an agile way to insert broadcast-quality graphics without sacrificing traditional outputs if they are ever required. SDI, NDI and IP are all available with a small hardware add-on if a full software approach is not suitable.