By default Ventuz executable files are installed in this folder.
C:\Program Files\Ventuz Technology Group\Ventuz 5
The installation may differ if the user has selected another installation path or the system drive letter is not C:\. If a Ventuz process is launched by the Windows Explorer, these options are used to define which project will be opened or presented. Creating Windows Shortcuts makes it easy to apply such options and launch desired standard projects or presentations.
The Ventuz Designer supports the following command line syntax:
Ventuz.exe [project] [options]
The optional project argument selects a Ventuz Project file (*.vzp) to be loaded. If a project is specified on the command line, the Project Browser will not be shown during start-up.
Dedicated Designer options
| Option | Description |
|---|---|
| -nosave | Disables the save entry in the scene menu |
Ventuz Presenter/Runtime can run in two diffent modes:
VentuzPresenter.exe presentation [options]
VentuzPresenter.exe project [options]
Additional options:
| Option | Description |
|---|---|
| -stats | Enables the Perfomance Statistics |
| -diag | Enables the Input Diagnostics |
| -kill | Any other running VentuzPresenter.exe process will be killed before launching the new instance. |
| -default:scene | Defines the scene identity (name) of the default scene to be initially loaded when launching in Director Mode. If this option is omitted, Ventuz tries to load a scene named "/default". |
| -override | Only valid if a Ventuz Presentation is specified: Edit the project configuration overrides. (see Deployment) |
| -win | Forces the Runtime to start in windowed mode. |
| -nosplash | Disables the splashscreen. |
Example: Start Ventuz Presenter/Runtime in Director Mode and disable log output. The scene named "/start" will be loaded as startup scene.
VentuzPresenter.exe "C:\MyProject\MyProject.vzp" -log:0 -default:/start
Ventuz Designer and Ventuz Runtime accept some general command line options.
All Ventuz applications write log messages to a log file on a local drive. These files are
| Designer | C:\Users\Public\Documents\Ventuz5\Log\designer.log |
| Director | C:\Users\Public\Documents\Ventuz5\Log\director.log |
| Presenter | C:\Users\Public\Documents\Ventuz5\Log\presenter.log |
| Configuration Editor | C:\Users\Public\Documents\Ventuz5\Log\VentuzConfig.log |
The Ventuz Presenter/Runtime has the ability to select the minimum log level that will be written to file with the -logwrite: option. This means that -logwrite:warning will only write warnings, errors and fatal errors to the presenter.log file. When starting Runtime a limited amount of Info logs about the configuration are written anyway even if the logging is restricted to higher level.
| Option | Log Level |
|---|---|
| -logwrite:0 -logwrite:none | None |
| -logwrite:1 -logwrite:fatal | Fatal |
| -logwrite:2 -logwrite:error | Error |
| -logwrite:3 -logwrite:warning | Warning |
| -logwrite:4 -logwrite:info | Info |
| -logwrite:5 -logwrite:debug | Debug |
| -logwrite:6 -logwrite:debugff | Debug FFmpeg |
There is also a -log option to restict the messages that are written to an optional Message Window in the Runtime. It uses the same parameters like the -logwrite option.
The special option -df enables logging of dropped frames. Every time Ventuz drops a frame, a log entry is written. Please note that writing a log message itself can cause another frame-drop. This option could turn into a vicious circle of dropped frames caused by dropped frames!
| Option | Description |
|---|---|
| -df | Enables logging of dropped frames for quality control. |
| -al | Append Log. Messages of a new Ventuz session are appended to an existing log file. By default a new file is created. |
| -kl:N | Keep Log. An existing log file is backed up before it is overwriten. The optional :N specifies the maximum number of backup files. If this number is exceeded the oldes files are removed. |