User guide

Viz Engine Administrator’s Guide

9.2 Internal Data (Interactive Scene)

When data is modified on one Viz Engine through a script or through a plugin, the data

change will get reflected on the other Viz Engines automatically.

A use case could be a touch screen scene which modifies data, which is also used for

HD-SDI Viz Engines or Viz Engines driving a Video Wall.

This synchronization uses the Viz Graphic Hub as a relay. Therefore it is important that

all Viz Engines, which are to receive the data, are connected to the same Viz Graphic

Hub, which use the same user or at least the same group.

9.3 Synchronization

If a Viz Engine is restarted or added to the cluster of Viz Engines for playout, the

VizCommunication.Map data will not available on this Viz Engine. The local map on a

new or restarted Viz Engine can be synchronized with the local map on another running

Viz Engine in the same cluster.

Example: If Viz Engine 1 restarts it will look to, for example, Viz Engine 3 to

update it’s local VizCommunication.Map.

A start-up Viz Engine can be synchronized through:

• TCP, or

• UDP, or

• An External Control Application, or

• Commands

This section contains information on the following topics:

• TCP and UDP Synchronization

• External Control Synchronization

• Command Synchronization

9.3.1 TCP and UDP Synchronization

Use the procedure detailed below to synchronize a restarted or added Viz Engines, in a

cluster, with the TCP or UDP protocol: