Issue
10.01.D
XT Series DISK RECORDER
Version 10.01 - Software Technical Reference
EVS Broadcast Equipment SA
October 2009
64
Technical Reference manual.
Note
From Multicam 9, the VarID has been introduced to allow a redundant
architecture where the VarID can be identical on two different servers. All
servers can stay on the same SDTI network. Consequently, this does not
require a full replication of the XNet network. With the Um ID, the full
replication was necessary as this clip ID has to be unique on the XNet
network.
4.2.2 CLIP IDENTIFIERS USED BY THE PROTOCOLS
VDCP Protocol
The VDCP can use two identifier types, the ‘fixed 8-byte length’ identifier and the
‘variable length’ identifier. The XT[2] server imposes the maximum length for the
variable ID, i.e. 32 characters in this instance. The VDCP protocol will use
completely different commands depending on the ID that will be used. The VDCP
protocol provides only this variable ID management.
The uniqueness and visibility functions are provided by the XT[2] servers to allow
the network architecture and redundancy management.
The protocol configuration for the ID management is performed via two interfaces:
• Multicam Application
In the ‘RS422 Protocols’ Section, on page 1 of the Setup menu (SHIFT-F2), the
ID type field allows the users to select the ID type to be used for all relevant
protocols, i.e. Xten DD35, Odetics and VDCP. The other protocols (Sony BVW,
AVSP et IPDP) do not manage the ID type, except for OSD display.
• VARID.ini File
The configuration of the VarID settings is performed via the VARID.ini file. The
content of this file is displayed in page 5 of the Setup menu. For more
information, refer to Section 1.3.5 ‘Dolby Audio Management’, on page 15.
De
pending on how the VDCP protocol will be used, various configurations
detailed in the table below can be performed in the Setup menu and the
VARID.ini file. When the parameter is not specified in the table (“-“ symbol), its
value does not influence the configuration.