Projects and Scenes

One of the most important things to understand when starting to work with Ventuz is how the generated content will be organized and why. This page gives you an overview of the general structure of a Ventuz Project and how to handle Scenes inside Ventuz.

Upon starting Ventuz, the Project Browser will appear as the very first thing:

Project

A Project is a collection of assets such as images, audio files, geometries, scenes, and a single project file with the extension .vzp. The assets are grouped into different folders based on the type of asset and are all located in the main project folder. If an asset outside of the project is used in a scene, it will be imported, or automatically copied into the project unless it is specifically marked as an external reference.

As an example, in a conference with multiple speakers or topics, each scene will be used for a single presentation but all of the presentations will use the same font, background, videos, etc. Hosting the assets inside the project instead of the scene allows for reuse and thus saves both disk space and memory.

Another way to think of a project is as a working folder. Instead of searching for specific images from various folders on the computer's hard disk, they are imported into the project and thus everything relevant is in one place. A project folder can be compressed and moved to another computer without compromising integrity as scenes only reference assets within the project folder (unless specifically told not to).

Creating a New Project

Select New Project from the Project Browser to open the Create Project Wizard. Choose a name and icon for your project, the aspect ratio of your target display, the location of the project folder on your hard disk and additional information like a description. Click Finish and Ventuz will create, initialize and open the project as well as a new empty scene.

Once a Project is opened, Ventuz switches from the Project Browser to the standard user interface. For more information on the specific windows, see User Interface.

The Scene

A Ventuz Scene is a collection of Layers, Nodes and Bindings. There are various nodes to generate geometry, assign materials, receive input from external sources and much more. Each node has various input and output properties that either influence a node (for example the size of a Rectangle) or are generated by the node (see for example the Mover node). Properties can be connected by so called Bindings to create complex logic without having to write a single line of code.

Within these concepts of parametrized nodes and binding of properties lies the power of Ventuz. Everything is calculated and rendered in real-time, and nearly everything can be changed in real-time as well. A presentation is no longer a linear succession of predefined content but rather a collection of possibilities. The operator or speaker can decide on the fly in which order things should happen and when to reveal certain information. Although the graphic design and logic of a scene is prepared in advance, the information that populates it can be replaced later on or even come from real-time sources such as RSS feeds or databases.

There a two ways to create a Scene.

• The first one is to create a new blank scene by selecting New from the Scene Menu. In an empty scene everything must be built from scratch.
• The second way is to use the Create Scene Dialog by selecting New... from the Scene Menu or by clicking Create Scene in one of the Editors when no scene is open. The dialog will ask for the type of scene to be created. Scene types displayed in the dialog are either internal scenes (Standard) or scene-templates located in open Repositories.

Project Structure

The graphic below illustrates the typical structure of a Ventuz project. Generally the Project consists of several Scenes that again consist of several Layers, be it 3D Layers or 2D Layers. Layers are a collection of Content Nodes and Bindings and - in the case of 3D Layers - Hierarchy Nodes. The Nodes are referencing any Assets needed by the logic of the scene.

Scene Backup and Versioning

Ventuz provides a system to minimize the damage of unexpected application crashes and to keep track of scene file changes. To enable this system, open the Scene Menu and select the Load & Save category. There you find the AutoSave and the Create backup files option. The AutoSave mechanism will periodically save the current state of the open scene to the Scenes.revisions folder. The scene is saved under its current name with additional .auto extension.

The backup mechanism works as follows: every time a scene is saved (under the old name) by the user, a copy of the old scene version on disk is saved to the Scenes.revisions folder with an additional extension ####.bak. #### represents a number between 0000 and 9999. This number is incremented with every new save operation. If the maximum number of backup files is reached (as configured in the Load & Save Options) the oldest backup file (with the lowest index number) is deleted before a new backup file is created.

To open one of the Backup files or the AutoSave file open the Open Scene dialog and choose the desired scene version in the Revision drop-down box at the bottom of the dialog. Note that if such a backup scene is saved in the Designer, it is saved under its original name in the Scene folder - this does not overwrite the backup file!

Scene Transfer and Archiving

To transfer a Ventuz scene from one Project to another, a Ventuz Scene Archive (VZA) must be exported (Export in the File menu). This export creates an archive file which contains the scene and all associated resources that are used in the scene and part of the current Project structure. All resources which are referenced by the scene and are outside the Project folder are not included in the archive. This archive can be imported in any other Ventuz Project (Import in the File menu) and the contained files are copied to the according Project sub-folder.