How to work with our Ventuz products

Workflow with all 3 Ventuz Products

Ventuz offers 3 separate products to enhance your workflow; Ventuz Designer, Ventuz Director, and Ventuz Runtime.

In addition to these tools used for running and playback, there are other tools that are used to easily configure your hardware and software to work as one complete ecosystem.

Ventuz Designer is used to bring together external assets, to design and author new content, link external data and create the animations, logic and behaviors needed for your production. Use dozens of types of external assets such as Adobe Photoshop files with the ability to control individual layers, Substance Designer and many others.

Ventuz Runtime is used to take your Scenes and play them back. This can either be done as a standalone presentation, with no inputs such as data or audience interactivity devices; it can be used with external data, such as weather, stocks, election data, and countless other sources, and can also include interactivity devices such as touch screens, cameras, and buttons as a few examples.

Runtime can also be used in conjunction with Director:

Director is used to run or control the Projects and Scenes created in Ventuz Designer.

Using the template and data structures created in Designer, take control of launching and controlling any Runtime or collection of Runtimes. Create and select dynamic data such as news headlines, lower thirds, add image or video assets on the fly or use it to trigger a pre-set animation.

Ventuz Configuration Tool offers all of the screen setup, warping, shaping and clustering/synchronization tools of the various Runtime outputs. Ventuz Director’s Topology editor specifies how they all fit together in a single graphical interface.Create and design your Project and Scenes in Ventuz Designer, play them back in Ventuz Runtime, and control everything in Ventuz Director. The possibilities are endless.

For more information, please refer to our detailed documentation or reach out to our sales team.

Not sure which edition is for you? We help you select the right edition & additional enterprise options to suit your business. It’s simple, just click the button below to see a side-by-side edition comparison. If you’re still not sure, please reach out to our sales team.

Workflow for Ventuz Designer and Runtime

In this configuration, Ventuz Designer is used to bring together external assets (which include especially tight workflows with other packages such as Adobe Photoshop, Substance Designer), design and author new content, link data and create the animations, logic and behaviors. This results in a single file, called a Ventuz Presentation, which combines the Ventuz scene and any internal assets.

These presentations are simply loaded and then run by Runtime. The easiest way to launch is to double click a presentation on a machine with Runtime installed on it. Provided the external assets, data connections and requires hardware is present, it will run with no further intervention. Runtime, via the Ventuz configuration tool, also offers all the screen setup, warping, shaping and clustering/synchronization tools required for setting the machine up.

Because of Ventuz’ openness and APIs, it is also very easy to create external control applications, for example web-pages, .NET apps or use OSC to drive Runtime.

Runtime is not simply playing back the Ventuz though, it is actually generating and running it in Realtime, so any interactivity, connectivity or data feeds within the scene remains live. It can also, of course, be controlled live through APIs, external devices and/or scripting, as determined by how the content has been created in Designer.

Ventuz Designer and a cluster of Runtimes

In this configuration, Ventuz Designer is used to bring together external assets (which include especially tight workflows with other packages such as Adobe Photoshop, Substance Designer), design and author new content, link data and create the animations, logic and behaviors. This results in Ventuz scenes and templates.

Of course, because a Runtime cluster is not simply playing back a scene, but actually generating and running it in realtime, any interactivity, connectivity or data feeds within the scenes are live. It can also, of course, be controlled live through APIs, external devices and/or scripting, as determined by how the content has been created in Designer.

The only difference to the single Runtime version is that the content needs to be distributed and launched in a synchronized environment. For this, Ventuz has a configuration tool, which provides for content to be uploaded to the Runtime cluster and launched. This Ventuz configuration tool, which connects to the remote cluster machines via network, also contains all the screen configuration, warping and shaping and cluster setup tools.

The Runtimes then jointly ensure that they, and their content, remain synchronized to each other on the basis of a shared software cluster clock, which can be further enhanced by supported hardware features such as house sync, genlock or framelock/swapsync. If Director, or another external control application is present, it can take control of the Cluster in exactly the same way as if it were a single Runtime.