Master/slave redundancy, Introduction, Requirements for master/slave redundancy – EVS IPDirector Version 6.0 - November 2012 Part 9 User's Manual User Manual
Page 12: Redundancy status in ipedit, Purpose, Terminology

1.2.
Master/Slave Redundancy
1.2.1.
Introduction
Purpose
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.
Terminology
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.
Requirements for Master/Slave Redundancy
If you want to use the Edit While Playout mode with the Master/Slave configuration, you
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, or 3 PGMs
with one of them supporting the ‘Mix on one channel’. See section "Channel
Assignment" on page 2.
•
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.
1.2.3.
Redundancy Status in IPEdit
You can check that both Master and Slave EVS servers are correctly connected in the
Status bar of IPEdit.
The following connection status information related to the Master/Slave redundancy can
be displayed:
4
1. Edit While Playout
EVS Broadcast Equipment S.A. - November 2012
Issue 6.00.A