Ventuz 4.1 - Control a Cluster from within the Director
Posted: 16 Oct 2013, 16:50
Ventuz Director is now able to control remote machines
Director has now a configuration file that contains the Topology describing the Ventuz network. If this file doesn't exist, the default topology is created and saved. If one wants to control a non-default Ventuz network, this configuration has to be edited manually.
This will be accessable from a Topology Editor in the future and will provide more flexibilty.
So stay tuned!
A sample file for 3 machines would look like that.
This is maybe a subject to change
Director has now a configuration file that contains the Topology describing the Ventuz network. If this file doesn't exist, the default topology is created and saved. If one wants to control a non-default Ventuz network, this configuration has to be edited manually.
This will be accessable from a Topology Editor in the future and will provide more flexibilty.
So stay tuned!
- The driven project must exist only once on each system within the network.
- A local machine must be involved in the network
- Director uses VMS service to launch Ventuz on remote and local machines.
- Exactly one single Channel (timeline) must be defined. More or less than one result in an error.
- You should declare two PreviewWindows that connect to the local Cluster
Code: Select all
C:\Users\Public\Documents\Ventuz4\Configuration\Director\Auto.xmlCode: Select all
<Director>
<Topology>
<Cluster Name="Wall">
<Machine IP="192.168.3.60"/>
<Machine IP="192.168.3.61"/>
<Machine IP="192.168.3.62"/>
</Cluster>
<Cluster Name="Local">
<Machine IP="127.0.0.1"/>
</Cluster>
<MultiPort Name="PGM">
<Connection Cluster="Wall" Pipe="0" Port="0"/>
<Connection Cluster="Local" Pipe="0" Port="0"/>
</MultiPort>
<MultiPort Name="PRV">
<Connection Cluster="Local" Pipe="1" Port="0"/>
</MultiPort>
<Channel Name="Main" Program="PGM" Preview="PRV"/>
<PreviewWindow Name="P1" Cluster="Local" Pipe="0"/>
<PreviewWindow Name="P2" Cluster="Local" Pipe="1"/>
</Topology>
</Director>