2 master/slave redundancy, 1 introduction, Purpose – EVS IPDirector Version 5.8 - July 2010 Part 8 User's Manual User Manual
Page 10: Terminology, 2 requirements for master/slave redundancy, Master/slave redundancy, Introduction, Requirements for master/slave redundancy, Ntroduction, Equirements for

IP Director – Version 5.8 – User’s Manual – Part 8
EVS Broadcast Equipment – July 2010
Issue 5.8.A
1.2 MASTER/SLAVE REDUNDANCY
1.2.1 I
NTRODUCTION
P
URPOSE
The Master/Slave redundancy feature is available with the Edit While Playout
mode. It makes it possible to synchronize the content of a timeline being edited on
the Master (main) EVS server running IPEdit to a Slave (backup) EVS server also
running IPEdit.
This redundancy allows providing a failover mechanism when using the Edit While
Playout mode in IPEdit.
T
ERMINOLOGY
To make it short, we will use the following terms:
•
‘Master IPEdit’ to refer to the IPEdit application working with the Master EVS
server
•
‘Slave IPEdit’ to refer to the IPEdit application working with the Slave EVS
server.
1.2.2 R
EQUIREMENTS FOR
M
ASTER
/S
LAVE
R
EDUNDANCY
If you want to use the Edit While Playout mode with the Master/Slave
configuration, your need to:
•
Have the same versions of IPDirector
•
Work with 6-channel EVS servers having the same Multicam version
•
Work with the Multicam application, having 4 PGMs on each EVS server,
typically the application ‘IPDP Spotbox 4 PGM/2 REC’.
•
Associate your EVS servers in Master/Slave relationship in the Redundancy
tab of the Remote Installer. Master/Slave servers need to have exactly the
same genlock, same LTC timecode signal, and same source signal on the
recorders selected for redundancy.
For more information on how to set up the redundancy between a Master and
Slave EVS server, please refer to the Technical Reference manual.
9