The Ventuz Configuration Editor enables the configuration of a Ventuz system for production. The editor also allows for the administration of multiple configurations and easy switching between them. The Ventuz Configuration Editor can be found in the Windows Start menu, or in the Tools menu of Ventuz Designer.
The editor is capable of configuring and controlling remote systems utilizing the Ventuz Machine Service. In fact, the local system is actually also technically configured by remote access (via localhost)! An installed, started and accessible VMS is mandatory for all systems being configured.
The Ventuz Configuration is project independent and handles and configures all settings related to the Ventuz system. Most of the settings are hardware related but it also contains rendering, network and identification settings. This configuration affects settings of the Ventuz installation and likely needs to be changed whenever the system is used for another project.
Changing the Ventuz Configuration requires a restart of Ventuz is most cases! (except for changing Live Options. See below).
The Ventuz Configuration Editor consists of several sections which are described here:
All Ventuz configuration files are stored in the system's public documents folder in the Ventuz5\Configuration directory. On most systems this path is:
C:\Users\Public\Documents\Ventuz5\Configuration\
In the Ventuz config folder multiple files and folders are stored. All Ventuz configuration files use the XML format and therefore are human readable and easy to handle.
VentuzConfig.vcfg Ventuz Configuration MachineConfig\*.vmc Machine Configuration Files AVConfig\*.avc AV Configuration Files RendersSetup\*.vmc Render Setup Files Director\*.* Director Configuration Files (not part of the Ventuz Config Editor)
The Machine Selector shows all machines discovered within the network. The Ventuz Machine Service broadcasts its VMS signature periodically. The Machine Selector receives these messages and add the entries to the selector. Machines without VMS running can't be discovered and configured!
The entry with the green bar on the left marks the local machine. The local machine is the default selection when the Ventuz Configuration Editor is started.
The selector automatically groups all machines with the same GroupID. To select a group click on the group label (here Group 2). Only Render Setups and Project Management are available when a group is selected.
Each entry has a colored Ventuz icon. The color indicates the current state of the running Ventuz process on that particular machine:
OK | Ventuz is connected and running | |
INIT | Ventuz is connected and running, though no project is loaded yet | |
OFFLINE | Ventuz is not connected | |
TIMEOUT | No VMS discovery message received |
Some settings from all configuration areas as well as many settings for the renderer can be adjusted on-the-fly by entering the Live Options on a machine with a running and connected Ventuz Runtime process (green or yellow state). Currently there are three areas that have live options available:
Please note that Live Options can only be saved if the corresponding configuration is not set to (None). The actual values of the settings are injected into the currently loaded file and it will be saved to disk. If there is no configuration file Ventuz can't save it...
The ID and the currently used Render Setup can be changed live. Changing these values doesn't affect the saved Ventuz Configuration as long the Live Options have not been saved.
These options change some renderer-specific settings. The same options are also available in the Renderer Windows in Ventuz Designer.
Please note that the Rendering Options cannot be saved! After a restart of Ventuz all options fall back to their default values.
Some board and audio and video stream have settings that only can reasonably adjusted while Ventuz is running (Genlock delay, audio gains and delays, etc). The live AV options make all settings available that are changeable on-the-fly. Saving the AV part of the Live Options will overwrite the current AV Configuration File. If no configuration has been set (None) the live edited values cannot be saved!
The Ventuz Configuration contains general information about the Ventuz Machine. If defines the Name of the machine as well its numeric ID and GroupID. The ID is used to select the correct part to be rendered in the multi-machine Render Setup. The GroupID must be set to a value greater than zero if a machine is part of a Cluster (group). Only machines with a GroupID can interchange their timing (cluster clock) to synchronize Remoting, animation and movie playback. For proper synchronization a valid Cluster Option is required. The Name of a machine is technically not important. A proper name helps the user to identify a machine within a Ventuz network.
The Ventuz Configuration also defines which sub-configuration should be used for the three sub-sections: Machine Configuration, AV Configuration and Render Setup. The corresponding selection boxes (3a, 3b and 3c) allows the user to switch between the existing configurations. Changing a value here requires the Ventuz Configuration to be saved. This can be done by pressing the Save button.
Each of the three sub-configuration has an Administration Area. This is shown if the expander left of the selection box is clicked.
The Administration Area shows a list of all available configurations where the checked entry marks the currently active file.
Several action can be performed on the selected entries:
Edit selected entry | Create new entry | ||
Duplicates selected entry | Renames selected entry | ||
Deletes selected entry | |||
Imports a file | Exports selected entry |
The Edit and New buttons are also available in the compact view of each sub-configuration section though the shown entry is the check and selected one at the same time. (always the active configuration is edited)
Editing an entry switches to the corresponding sub-configuration editor. Each sub-editor has its own Save and Cancel buttons. These buttons affect only the current sub-configuration being edited. The Save button on the Ventuz Configuration page only affects the settings of the Ventuz Configuration which references the sub-configurations by name.
Importing and Exporting is just a simple way to copy the actual configuration files from/to the configuration folder. If a remote system or group of machines is configured this feature becomes very helpful!
The Live Project Management allows a project found on the target system to be selected and Ventuz Runtime to be started with the selection. The simple view can also be expanded to show more options:
The displayed list shows all projects found by VMS on the target system. If the user hovers the mouse over one entry a tooltip popup shows more details about the project. The project files must be stored in the project folder configured in VMS. The default folder is
C:\Users\Public\Documents\Ventuz5\Projects
Please note that only unique projects are displayed in that list. If a project with the same ID appears multiple times on a system or - in multi machine mode - a project ID doesn't exist on one or more system it won't be displayed!
In expanded mode the Live Project Management can perform several actions:
Start the selected project. Any previously running Ventuz Runtime will be closed before! | |
Stop (kill) any currently running Ventuz Runtime. | |
Upload a Ventuz Project (VPA or VPR) to all selected machines and initiate a re-scan on VMS. | |
Initiate a project scan on all selected target machines. |
Before starting or stopping and Ventuz Runtime processes make absolutely sure that you're connected to the correct machines! To disallow closing processes accidentally you can set security settings on the VMS.