Multi System Configuration

<< Click to Display Table of Contents >>

Navigation:  Getting Started >

Multi System Configuration

Prerequisites for a VERTEX Session

1.VERTEX has to run on all Systems in the same Assembly Version such as "VERTEX 2023 R1 2023.01.14.0439"

2.All Systems must have a valid license.

3.Network Adapter Settings and Default Datasync Adapter must be set for all systems to the same network.

4.Vertex Background Services must run on every System.

VERTEX in Session Mode

A VERTEX Session always consist of

ONE Master System where the project file is created, loaded and saved.
and

ANY NUMBER OF Session Members.
Session Members are VERTEX systems that connect to the Master System's project.
The number of Session Members is designed to be unlimited, flexible and scalable:
it is possible to add new Session Members to a project or delete existing Session Members.

The 5 Cogs in Session Mode:

1.Data Sync

All project data and settings are shared between all systems in real-time, thus creating a true multi-user environment.

Every system will have the same data status, regardless on which system a change has been made to the project.

2.Playback Sync

Playbacks are always in sync on all systems in a VERTEX Session.

Any system (both Master or Session Member) can be defined as the clock master and will be synchronizing all playbacks of every Session Member.

3.Content Sync

VERTEX Content Sync is designed with a peer to peer technology that results in faster data transfer with increasing number of systems added.
Content can be imported on any system in the session and even so, all data is being shared in the background between all systems.

4.Data Routing

Incoming continuous data is shared between systems in a Session and can be routed: For instance,  Incoming DMX-Data on System1 could be routed

as  Art-Net™ output on System3. Incoming device data on one system is also shared between all other systems.

5.Backup Scenarios

This modular method of connecting Session Members is the foundation for VERTEX's flexible backup possibilities: create a redundant backup or only a partial one.

Session Members can switch render roles and render for another system that drops out. The Master role can also be taken over by another Session Member.

 

Information on Session Mode's advanced settings can be found here.