EVS MulticamLSM Version 10.03 - July 2010 Configuration Manual - Manual (Page 18)

EVS Multicam – Version 10.03 – Configuration Manual
EVS Broadcast Equipment SA – July 2010
Issue 10.3.C
11
2.2.10 RS422 P
ROTOCOLS
ID T
YPE
This parameter specifies the clip ID used by the protocols to access and to
identify the clips.
Possible values: ID LSM (default) / UmID
At any time, the VDCP protocol can decide to use either the default value or the
VarID. This VarID has to be set up in the section 2.7 ‘RS422 Protocol Settings
(Page 5)’, on page 26.
2.2.11 G
ENERAL
T
IMECODE
S
ETTINGS
From Multicam version 9 onwards, the management of timecodes has been
improved. The users can now choose which type of timecode they want to use as
the reference to work on a given recorder of a server. This is made possible by
the management of two timecode jump tables.
T
IMECODE
J
UMP
T
ABLES
The timecode jump tables contain records with timecodes of video material
recorded on the server. A new record is created in the table each time a jump in
timecodes is detected on the recorded material.
The records of timecode jumps allow the identification of all the recorded material.
The timecode jump tables are used on all searches for and manipulations of video
material recorded on an XNet server.
The two timecode jump tables are filled with the following data:
• The first table is always filled in with the LTC timecode. This is the timecode
defined on or plugged into the server.
• The second table is filled in with the timecodes selected by the user. This can
be one of the following timecode type:
o
LTC and VITC (default) timecodes in SD
o
LTC, HANC LTC (default) or HANC VITC in HD
Note
The timecode jump tables are circular: when the table is full, the latest
entry will overwrite the oldest one.