Xtvia TechRef 21.0
Xtvia TechRef 21.0
XT-VIA Server
Version 21.0 | January 2025
TECHNICAL REFERENCE MANUAL
Disclaimer
This manual and the information contained herein are the sole property of EVS Broadcast Equipment SA
and/or its affiliates (EVS) and are provided “as is” without any expressed or implied warranties, including,
but not limited to, the implied warranties of merchantability and fitness for a particular purpose. In
particular, EVS makes no warranty regarding the use or the consequences of use of this manual and the
information contained herein. Furthermore, EVS may not be held liable for any direct or indirect,
incidental, punitive or consequential loss, damage, cost or expense of any kind whatsoever and
howsoever resulting from the normal or abnormal use of this manual and the information contained
herein, even if advised of the possibility of such loss, damage, cost or expense.
While every effort has been made to ensure that the information contained in this manual is accurate,
up-to-date and reliable, EVS cannot be held liable for inaccuracies or errors that may appear in this
publication. The information in this manual is furnished for informational purpose and use only and
subject to change without notice.
Copyright
Copyright © 2018-2025 EVS Broadcast Equipment SA. All rights reserved.
This manual may not be reproduced, transcribed, stored (in a database or a retrieval system), translated
into any language, computer language, transmitted in any form or by any means – electronically,
mechanically, printed, photocopied, optically, manually or otherwise – in whole or in part without the
prior written consent of EVS.
Trademarks
All product and brand names are registered trademarks and trademarks of EVS or of their respective
owners.
Improvement Requests
Your comments will help us improve the quality of the user documentation. Please send improvement
requests, or report any error or inaccuracy on this user manual by e-mail to [email protected].
Regional Contacts
You will find the full list of addresses and phone numbers on the following webpage:
https://evs.com/contact/offices.
Contents
Disclaimer I
Contents III
1. Overview 1
1.1. Presentation 1
2.4. CE Marking 4
3. Hardware Specifications 5
4. Software Specifications 11
5.6.1. IP Aggregator 56
5.6.2. XNet-VIA 59
5.7.1. Introduction 60
5.9.1. GP In Connections 75
6. Boards Description 79
6.3.1. Description 81
ICONOGRAPHY
What's New?
In the Technical Reference Manual the icon has been added on the left margin to highlight
information on updated features.
The changes linked to new features in version 21.0 are listed below.
New license packages Multicam, Spotbox and Sportlight, and easy upgrade from Spotbox/Sportlight to
Multicam.
• See section "Required Conditions to Set up and Run XNet-GO" on page 68.
1. Overview
1.1. Presentation
Welcome to the EVS range of products and thank you for using an EVS XT-VIA Server server. We will do
our best to satisfy your video production needs and we look forward to continuing working with you.
The XT-VIA server is the Live Production server that meets the needs of broadcasters, content creators
and OB truck facility companies who focus mainly on UHD-4K productions and look for a future proof
HD/1080p server with versatile SDI and IP connectivity.
In addition to the EVS Loop Recording technology, the XNet-VIA IP network offers a 10G interface for
your transfers as well as the legacy XNet SDTI with a 3G interface. XT-VIA provides support of Super
Motion cameras, slow motion replays and multi-channel playback with server-to-server transfer options.
With support of multiple options, the XT-VIA meets your business needs whether you are starting at 3G-
SDI, evolving to 12G-SDI, or building a next generation facility using IP protocols using ST 2110 and
NMOS.
XT-VIA comes with interfaces that allow to integrate it in a production network made of previous
generation XT3 or XT4K and at the same time sets the foundations for the new interactivity that will be
enabled by the VIA technology platform.
This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications. However,
there is no guarantee that interference will not occur in a particular installation.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
2.4. CE Marking
The CE marking is affixed to indicate compliance with the following directives:
• 2014/30/EU of 26 February 2014 on the harmonization of the laws of the Members States relating to
electromagnetic compatibility.
• 2014/35/EU of 26 February 2014 on the harmonization of the laws of the Members States relating to
the making available on the market of electrical equipment designed for use within certain voltage
limits.
• 1999/5/EC of 9 March 1999 on radio equipment and telecommunications terminal equipment and the
mutual recognition of their conformity.
3. Hardware Specifications
This section describes the following hardware specifications of the server: mechanical dimensions,
weight, power supply, environmental conditions and sound power level.
Dimensions
The following drawings provide the various dimensions, in mm, of the XT-VIA server with a 6U chassis.
Front view
Right view
Top view
Keyboard
Weight: 0.4 kg / 0.9 lb
The secondary hot-swappable power supply should be connected to the mains to allow automatic
power switching to this second power supply should the first one fail.
Grounding
The protective earth must be connected to the ground before powering up the unit.
Ensure the disk recorder unit is properly grounded at all times to avoid electrical shock hazard.
Electrical Specifications
Rated voltage: 100V-240VAC (single phase)
Connection to supply: Pluggable equipment Type A (EN 60950 §1.2.5): Equipment which is intended for
connection to the building power supply wiring via a non-industrial plug and socket-outlet or a non-
industrial appliance coupler or both. Correct mains polarity must always be observed. Do not use
reversible power plugs with this equipment.
Class of equipment: Class 1 equipment (EN 60950 § 1.2.5): electric shock protection by basic insulation
and protective earth.
Electrical Consumption
The following electrical specifications are valid for the XT-VIA server:
Frequency 47 Hz 50 / 60 Hz 63 Hz
AC inrush current: 20/40 amps@115/230 VAC (25°C ambient cold start for each power unit).
• Cooling requirements: Forced cooling air flow from right to left when looking at the EVS server from
the back panel.
4. Software Specifications
Digital Interface 10-bit 4:2:2 Serial (ST 292-1:2011) 10-bit 4:2:2 Serial (ST 292-1:2011)
Full frame synchronizer at input. Full frame synchronizer at input.
Monitoring & Down- 1 SDI output per channel, with OSD 1-built in down-converter per
converters channel.
1 3G-SDI or IP output per channel
with OSD.
Reference Analog Black Burst and HD Tri- Analog Black Burst and HD Tri-
Level Sync Level Sync
PTP PTP
D-VITC ST 266:2012
Ancillary TC in HD RP 188
VC-3 ST 2019-1:2008
3G SDI ST 424:2006
Image Format and Ancillary Data Mapping for the Quad ST 425-5:2014
Link 3 Gb/s Serial Interface
Professional Media Over Managed IP Networks: Traffic ST 2110-21 (senders: narrow; receivers: wide
Shaping Uncompressed Video and/or narrow(*))
• In 4K configurations, the embedded audio will be processed from the first channel (Top Left).
Audio Processing
• Uncompressed audio
• Audio scrub
• Audio mix
AVC-Intra code 13
XAVC-Intra HD code 15
DNxHR 4K code 16
ProRes-4K code 17
XAVC-Intra code 19
4K
The following table summarizes the proposed configurations, valid for encoding and file header:
ProRes LT 10-bit
ProRes SQ 10-bit
ProRes HQ 10-bit
AVC-Intra 10-bit
XAVC-Intra HD 10-bit
ProRes-4K 10 bit
XAVC-Intra 4K 10-bit
With a (10+1) or (10+2) RAID, the following maximum bitrates (hence codec flavors) are supported:
Codec Format up to 6 ch
59.94Hz 960
Codec Format 3 ch 4 ch 5 ch 6 ch
• Blocks of 16MB are recommended, but 8MB is still possible. You can decide the size to use.
50Hz
AVC-I 8 8 8 8/16 16 16 16 16
XAVC-I 8 8 8 8/16 16 16 16 16
59.94Hz
AVC-I 8 8 8 8 8/16 16 16 16
XAVC-I 8 8 8 8 8/16 16 16 16
1080p
50Hz
Codec 1x 2x 3x 4x 6x 8x
AVC-I 8 8/16 16 16 16 16
XAVC-I 8 8/16 16 16 16 16
59.94Hz
Codec 1x 2x 3x 4x 6x 8x
AVC-I 8 8 8/16 16 16 16
XAVC-I 8 8 8/16 16 16 16
50Hz
Codec 1x 2x 3x
XAVC 480 16 32 32
Avid DNxHR SQ 16 32 32
Avid DNxHR HQ 32 32 32
59.94Hz
Codec 1x 2x 3x
XAVC 480 16 32 32
Avid DNxHR SQ 16 32 32
Avid DNxHR HQ 32 32 32
UHD-8K
50Hz
Codec 1x
XAVC 300 32
XAVC 480 32
59.94Hz
Codec 1x
XAVC 300 32
XAVC 480 32
1. Block Size: Size of the disk block in MB. It can vary from one codec to the other. For a given codec,
the most appropriate size will automatically be used.
2. Video Bitrate: codec bitrate set by the user in the Codec section of the Server tab in the Multicam
Configuration window.
3. Fields/Block: numbers of video fields that can be stored in one disk block (disk block size specified in
the table) taking into account 8 audio tracks, in 1080i and UHD-4K.
4. Actual Bandwidth: actual disk/network bandwidth required for the real-time record or real-time
playback of one video stream and its associated audio tracks.
5. Max. RT Channels: maximum number of video channels (real-time record or real-time playback) that
one EVS server can support for a given frame rate and bitrate.
For a server running in a configuration with a given number of video channels, any additional real-
time access can be used for transfers over the XNet (SDTI) network.
The RT Channels calculation is based on the use of Seagate disks of 1800GB (10K9) configured in
10+1 raids. Such disks are able to write 1000 MB/s.
The reference writing speed in case of another RAID configuration is the following:
XAVC-Intra 4K 16 600 11 87 11
class 300
For a mixed configuration with standard and super motion channels on the same EVS server, the
following calculation must be used to ensure that the settings do not exceed the maximum bandwidth of
the server, that is to say 1000 MB/s:
(nbr of standard channels x their block-based bandwidth)
• external storage only: 1 array with 24 x 1.8 TB SAS disks, with or without spare disks
Recording capacities of an XT-VIA server with internal and external disk storage cannot
exceed 54 TB.
This limit will be reached with 30 disks of 1.8 TB.
RAID Level: 3
The video RAID uses striping process across 5, 6, 11 or 12 disk drives. The video and audio data is striped
over the first 4, 5 or 10 drives while the parity information is saved on the remaining drive(s).
If one drive is damaged, the video RAID can use the parity information to recover the missing
information, so that operation can continue seamlessly without bandwidth loss.
• In HD and UHD-4K, one record channel corresponds to 1 video + 8 stereo audio tracks.
1 157 138 94 34
1 157 120 78 28
• In XNet-GO and (SDTI), the bandwidth allocated to a transfer is impacted by the total number of
transfers on the whole XNet-GO and (SDTI) network.
1. Codec: codec set by the user in the Codec section of the Server tab in the Multicam Configuration
window.
2. Video Bitrate: codec bitrate set by the user in the Codec section of the Server tab in the Multicam
Configuration window.
3. RT Transfers:
- This corresponds to the number of record channels that can be played out simultaneously
over the network at a nominal speed of 100%.
- For example, a value 6 means that the recorder(s) of a given server can be played "live"
(considering a network delay of 500ms) on up to 6 players of one or more servers in the
network.
- This corresponds to the number of media assets (clips stored on a remote server, or remote
record channels played out with delay) that can be played out simultaneously over the
network at a variable speed. We consider a playout speed of 200% representing roughly the
double nominal video codec bandwidth.
- Note that when browsing remote content at variable speed (higher than 100%), the network
and storage bandwidth might increase and therefore the number of remote network transfers
decreases accordingly.
- For instance, a value 4 means that up to 4 clips stored on a given machine can be played out
simultaneously over the network from one or multiple other machines.
- This corresponds to the factor by which the transfer of a clip is faster compared to the clip
duration, taking into account the nominal speed of the clip.
- For example, a factor 6 means that: a regular clip with a duration of 60 seconds is copied in 10
seconds, or a 60-second clip recorded from an SLSM3x camera is copied in 30 seconds, or 6
clips with a duration of 20 seconds each are copied in a total time of 20 seconds.
When A/V data is transferred through the XNet-VIA network, you should take into account the following
maximum bandwidths:
• 950 MB/s for transfers between EVS servers on an XNet-VIA IP 10 Gbps network. For comparison,
240 MB/s for transfers between EVS servers on and SDTI network.
This ideal bandwidth can only be obtained in case of a low number of transfers with a high bitrate per
transfer.
In XNet-VIA, the bandwidth allocated to a transfer only depends on the outgoing transfer from
A and ingoing traffic to B. This is not impacted by the number of transfers on the whole XNet-
VIA network.
1080p
We consider a local channel configuration of 12 channels for all codecs on source and target servers.
50Hz
59.94Hz
UHD-4K
We consider a local channel configuration depending on the codec as illustrated in the tables below.
50Hz
59.54Hz
The observations and data focus on steady rates: the transfer performances with small clips
will be lower as they generate a lot of starts and ends of sessions.
1. Block Size: Size of the disk block in MB. It can vary from one codec to the other. For a given codec,
the most appropriate size will automatically be used.
2. Field Rate: field frequency used, or number of video fields transferred per second.
3. Video Bitrate: codec bitrate set by the user in the Codec section of the Server tab in the Multicam
Configuration window.
4. RT Transfers: maximum number of simultaneous transfers of A/V data that can be processed for the
given frame rate and video bitrate through the GbE network.
5. Transfer Speed: transfer speed for a single transfer expressed in faster than-real time speed. The
calculation formula is the same with a reference GbE bandwidth that is slightly smaller.
Reference Bandwidth
The table below specifies the reference GbE bandwidth used for calculations in this section. However,
the effective bandwidth depends on network behavior, which only partly relies on the EVS server.
10GbE (GbE board) 220 MB/s 140 MB/s 150 MB/s 80 MB/s
Restore Transfers
The maximum transfer speed through one port the GbE board on an XT-VIA server in 1080i and UHD-4K,
without SLSM REC, are summarized in the following tables.
◦ OEOEOEOEOEOEOEOE
◦ OOEEOOEEOOEEOOEE
◦ OOOEEEOOOEEEOOOE
◦ OOOOEEEEOOOOEEEE
Fields with parity violation are shown in bold, underlined letters. As it appears from the above table,
whatever the playback speed (with the exception of the normal 100% playback speed), a number of
fields violate the normal parity of the output signal. This parity violation induces a 1-line shift of the field,
resulting in a vertical jitter of the picture. The jitter frequency depends upon the chosen playback speed.
To avoid this phenomenon and provide a stable output picture, EVS developed 2 types of line
interpolator: 2-line and 4-line interpolators. The interpolation process can be enabled or disabled by the
operator on all EVS slow motion systems.
2-Line Interpolator
The 2-line interpolator actually generates a new field, when the original field is in parity violation. Each
line of this new field is calculated by a weighted average of the 2 neighboring lines. This process solves
the problem of parity violation and vertical jitter, but the drawback is a reduction of the vertical
resolution on the interpolated fields, that appear unfocused. Another side effect is the alternation of
original fields (perfectly focused) and interpolated fields (unfocused), resulting in a "pumping" video
signal.
4-Line Interpolator
The 4-line interpolator uses a more sophisticated calculation based on the 4 neighboring lines. By using
suitable coefficients for the weight of each line in the resulting calculation, we apply this interpolation to
all fields. The final result is a permanently, slightly unfocused picture. The advantage is a stable output
signal with no jitter and no "pumping", but the vertical bandwidth is even more reduced.
The interpolator is of course always disabled at 100% playback speed, because there is no parity
violation.
EVS uses the same techniques with the Super Slow Motion disk recorder, working with all models of
Super Motion cameras (150/180 Hz). The only difference between the processing of Super Motion and
normal scan (50/60 Hz) signals is that the interpolator is always disabled at 33% playback speed,
because the Super Motion signal does not cause parity violation at this particular speed.
Whatever the choice, the resulting picture is thus always a compromise between stability and resolution.
With EVS systems, the operator always has the choice between any of the 3 above described
techniques: no interpolation, 2-line interpolation or 4-line interpolation. Even if the operator chooses to
use the interpolation, this process will be automatically disabled when not necessary (100% playback for
50/60 Hz signal, 33% and 100% playback for 150/180 Hz signal).
All professional VTRs use line interpolation in PlayVar mode to avoid vertical jitters.
Default value is interpolator off for all configurations except SLSM configurations in which 4-
line interpolator mode is enabled.
• Remember that fans are used to air cool the equipment and protect it from overheating.
• Do not block fans intakes during operations.
Having regard to the weight of the server chassis, support guides are required for this unit into the rack
mount. The front ears of the unit are not designed to support its full weight. Applying full weight on these
might result in bending the metal plate.
Boards Checking
The main power switch is located at the front side (lower right corner) of the unit.
Before turning on the power, open the front door of Video disk recorder unit to check if all boards fit into
their guides. If a board is out of its guides, remove carefully the board and replace it in the same slot.
• 6U rack with mixed SDI and XIP connectors (called XIP rear panel).
The various parts of the rear panel are described in the following topics.
The various areas of the rear panel are highlighted in the drawing and their respective variants are listed
in the sections below along with a short description of the related connectors.
See section "Video and Reference Boards" on page 81 for more details on each connector specific usage
according to the different configurations.
The video and codec connector layout available with the XT-VIA server includes 6 codec modules
(codec module 1 to codec module 6) with one of the following layout on each codec module:
AND
When the SFP+ is used, the BNC connectors are no longer operational, and vice versa. See the
XT-VIA configuration manual for more information.
When using a 12G-SDI interface on a codec module, cable only the IN A or OUT A connector of
the codec module.
The video and codec connector layout available with the 8K version of the XT-VIA Server includes 8
codec modules (codec module 1 to codec module 8) with following layout on each codec module:
Multiviewer
The codec module 8 is used for the internal Multiviewer (MV4X).
to connect monitors directly to the server, and display PGM and REC channels on the monitors
• 2 IN connectors (A and B)
to connect monitors directly to the server, and display PGM and REC channels on the monitors
• 2 IN connectors (A and B)
On the 8K version of the XT-VIA Server separate MV4 connectors are available providing:
• 2 IN connectors
• 4 OUT connectors
The Multiviewer monitor display is configured in the Multicam Configuration window, Monitoring tab,
Multiviewer page. See the Multicam Configuration manual for a description of the configuration
parameters.
Monitoring
These BNC connectors provide 1080p monitoring of the UHD input or output channels.
Audio
See section "Audio Specifications" on page 13 for more details on the available audio configurations.
See section "Audio Connections" on page 53 for more details on the DA-15 connectors pinout
depending on the configuration.
The Ref Video connectors allow the server to receive or send back the analog genlock reference signal.
If the PTP is used to generate the Timecode and Genlock signals, these connectors do not
have to be cabled. In this case, the Timecode and Genlock signals are generated from the PTP
information received on the codec module 1 connector C.
This rear panel part, located below the audio connectors, presents connectors that allow the EVS server
to communicate with other devices.
The RS422 ports allow the server to be remotely controlled through remote panels or third-party control
devices. When a remote panel is used, it should be connected on the first RS422 port.
The GPI connector allows GPI (General Purpose Interface) devices to send or receive electric pulses that
will trigger commands on the server or to be connected with third-party devices.
The XNet connectors allow the interconnection of EVS servers in an XNet network. The IN connector of
a server is connected to the OUT connector of another server, and so on to form a closed loop network.
Two PC LAN connectors allow connection of the PC LAN interface of the EVS server to an Ethernet
network. Refer to the XT-VIA Configuration manual for more information on PC LAN redundancy.
The EVS Link connector is used to set up a management connection between the server and the XHub-
VIA IP Aggregator.
The Console connectors allow a monitor and a keyboard to be connected to the server.
If your XT-VIA server is fitted with MV4 multiviewer connectors, they will be ignored from
Multicam version 16.1 onwards. Instead, you need to cable the MV4X multiviewer which
corresponds to the codec module 8. See section "Multiviewer " on page 45.
Located on the right above the codec modules, 4 SFP+ connectors allow connection to the XNet-VIA
network.
Connector B1 is used for proxy streaming. See the Proxy Streaming Configuration settings in the
Configuration Manual.
The Gigabit Ethernet connector module allows the interconnection of servers, other EVS, and/or
third-party systems into a Gigabit Ethernet network via:
◦ SD card slot
The 10 GbE and 1GbE connectors cannot be used at the same time.
The Audio Monitoring Outputs connectors are analog XLR connectors that allow audio output
connections for monitoring purposes.
The External Disk Array connector allows the connection to the external disk array SAS-HDX2 if it is
installed. By default, it is covered with a cap.
Power Supplies
The server power supply is made of two hot-swappable units. Both of these units are connected to allow
automatic power switching to the second power supply should the first one fail.
Intel ESSFP-I-10G-SR
See the XHub-VIA Technical Reference manual for the accepted connectors in case the
XHub-VIA is used for LiveIP operations.
To ensure the mechanical reliability of a plugged adapter, it will be fixed with a screw to the rear panel.
To plug or unplug an adapter, the server should always be powered off first. Hot-plug or -
unplug is not supported.
Do not remove and insert an adapter more often than is necessary. Repeated removals and insertions of
an adapter can shorten its useful life and that of the rear panel.
Supported Configurations
HD
• PGM: 2 SFP+ to SDI adapters will be required to provide the 2 discrete monitoring outputs.
• REC: no SFP+ to SDI adapters will be required to provide the 2 discrete monitoring outputs.
• SLSM: With the appropriate number of SFP+ to SDI adapters, the SLSM3x and higher are supported.
UHD-8K
4 SFP+ to SDI adapters will be required.
The embedded audio modules and codecs can be used as input or output channels for embedded,
digital (AES/EBU)signals.
Depending on the server chassis or configuration, you can find the following audio connectors on the
rear panel:
• Digital audio:
◦ DA-15 connectors: 16 inputs (8 pairs) and 16 outputs (8 pairs) (110 Ohm balanced).
See also section "Audio Specifications" on page 13 for full information on the available audio hardware
configurations.
2 AES input 1/2 + AES input 9/10 + AES output 1/2 + AES output 9/10 +
4 AES input 3/4 + AES input 11/12 + AES output 3/4 + AES output 11/12 +
6 AES input 5/6 + AES input 13/14 + AES output 5/6 + AES output 13/14 +
8 AES input 7/8 + AES input 15/16 + AES output 7/8 + AES output 15/16 +
9 AES input 1/2 - AES input 9/10 - AES output 1/2 - AES output 9/10 -
11 AES input 3/4 - AES input 11/12 - AES output 3/4 - AES output 11/12 -
13 AES input 5/6 - AES input 13/14 - AES output 5/6 - AES output 13/14 -
15 AES input 7/8 - AES input 15/16 - AES output 7/8 - AES output 15/16 -
The cable wiring is a straightforward pin-to-pin connection as illustrated in the following diagram. You
should use a shielded cable to avoid electromagnetic interference on long distances.
The RESET command line from the remote control is sent through the pin 5 of the RS422
connector. This function should be disabled when the controller on connector #1 is not an EVS
controller.
◦ 19200 bauds
◦ No parity
◦ 8 data bits
◦ 1 stop bit
5.6.1. IP Aggregator
Limitation
You can connect only 1 server to the XHub-VIA 100G Enabler.
Management Connection
To establish a management connection between XHub-VIA and the server, the XHUB-VIA management
port has to be connected to the server's EVS LNK connector.
Without ST 2022-7
In a setup without redundancy (ST 2022-7), the server's SFP+ ports should be connected with the
XHub-VIA SFP28 ports as follows:
XHub-VIA XT-VIA
Port Port
1 1-C
2 2-C
3 3-C
4 4-C
5 5-C
6 6-C
8 8-C
1 1-C 9 1-D
2 2-C 10 2-D
3 3-C 11 3-D
4 4-C 12 4-D
5 5-C 13 5-D
6 6-C 14 6-D
8 8-C 16 8-D
5.6.2. XNet-VIA
Accepted Connectors
To create the connections between the XT servers and the XHub-VIA switch, and to create the uplinks
between the XHub-VIA switches, the following connectors can be used:
5.7.1. Introduction
The XNet network consists of several EVS video servers or other EVS hardware all connected with each
other.
The XNet network has three operation modes that are mutually exclusive:
• 3G-SDTI: The EVS video servers or other EVS hardware are connected with a 75-Ohm coaxial cable
(BNC). The data exchange between systems is operated through the SDTI interface at 2970 Mbps
(3Gbps), with non-relay connectors.
• XNet-VIA: The EVS video servers or other EVS hardware are connected via a dedicated IP hub
(XHub-VIA) with a DAC or SFP+ fiber optics cable. The data exchange between systems is operated
through the XNet-VIA interface (SFP+ connector) at 10Gbps.
• XNet-GO: The EVS video servers are connected with a 75-Ohm coaxial cable (BNC).
The XNet requires a network server dedicated to the management of the database shared among all
EVS video servers. This is automatically assigned to one of the EVS servers on the network. See section
"XNet Server Selection" on page 63. The EVS server acting as the network server can of course be used
for standard server operations.
The servers connected on the XNet network (XNet-VIA) are automatically discovered and their
IP adresses are automatically assigned by the acting XNet server.
To set up an XNet-VIA network, EVS servers can be connected using one or more dedicated IP hubs
(XHub-VIA). To support up to 42 servers, or to segregate the network (for example 2 OB vans), two
XHub-VIAs can be uplinked using 1 or 2x100GB links depending on the number of servers in the network.
From Multicam 16.1 onwards, XHub v4.01 only is supported if the XNet network include
XT-VIA or XS-VIA servers. Otherwise, XHub v4.00 is still supported.
The selection of this server is done automatically. The server net number and node ID play an important
role.
• Net number: The number you can assign to the server allowing you to identify it on the XNet network.
• Node ID: The number that unequivocally identifies the server. This number cannot be configured.
• have a lot of PGMs; Select the servers with the least PGMs.
• have a lot of record channels that are heavily used over the network.
Based on the above criteria, compose a list of servers that may potentially act as XNet server. Set the
XNet server (Preferred, Allowed, Forbidden) and Net Number accordingly. One should also take into
account to have at least one Allowed/Preferred server in each cluster in case the XNet is composed of
multiple XHub-VIA.
• If no XNet network has been established yet, and you add a new XT server (S5) that is configured as
Allowed or Forbidden, no XNet network is established.
• If two existing XNet networks (A and B) are merged, and both XNet servers (S1 and S7) are
configured as Preferred or Allowed, the server with the lower network number (S1) becomes the new
XNet server of the merged network (AB).
If the net number of the two servers is identical (S1), then the server with the highest Node ID or
serial number (304820) becomes the new XNet server of the merged network.
• If you remove the XNet server (S5) from the XNet network (A), and among the other servers at least
one server is configured as Preferred or Allowed, a new XNet server is selected. In case there are
two servers that are configured as Preferred or Allowed, the server with the lowest net number (S1)
is selected. In case the net number is identical, the server with the highest Node ID is selected.
• If a server gets introduced in the XNet network (3G-SDTI) and it becomes the new XNet
server, all ongoing clip transfers and remote train playouts are interrupted for all servers in
the network.
• If a server gets introduced in the XNet network (XNet-VIA) and it becomes the new XNet
server, all ongoing clip transfers continue for all servers in the network. However, all
remote train playouts are interrupted.
2. The SDTI advanced option code (117) shall be validated in the options list.
3. They shall all be running compatible software versions. Otherwise, a warning message is displayed.
Only Multicam 21.0 is supported. Versions 20.7 or lower are not supported.
4. The XNet Operation Mode parameter shall have the same value on all EVS servers (Network tab,
XNet section).
5. The EVS video servers shall operate the same multi-essence configuration.
6. The EVS video servers shall operate the same codec for video material to be fully interoperable
between EVS video servers.
7. At least one server should be set as "Preferred" XNet server. Only true for an initial setup of a
network.
8. A different network number must be specified for each EVS video server that you want to connect to
the network. If the same network number is assigned to 2 different systems, the second one will not
be able to connect and a warning message will be displayed.
9. All EVS video servers must be connected with a good quality BNC 75 Ohm cable to form a closed
loop.
Connect the 3G-SDTI OUT connector of the first EVS video server to the 3G-SDTI IN connector of
the second one, etc until the loop is closed by connecting the 3G-SDTI OUT connector of the last
EVS video server to the 3G-SDTI IN connector of the first one.
The 3G-SDTI loop must be closed at all times during network operation. If for any reason the loop is
open, all network communication will be interrupted and all systems will automatically switch to
stand alone mode. When the loop is closed again, network operation will resume automatically. This
problem can be avoided or limited using an XHub.
10. The distance shown in the table below is the maximum cable length between two active EVS
servers, or 2 SDTI reclockers, on an XNet 3G-SDTI network, using a single piece of cable between 2
servers or 2 reclockers.
Intermediate connectors, patch panels, etc., might degrade these figures. Depending on the number
of servers connected on the network, the location of the master server, the presence or not of an
XHub SDTI hub, the actual maximum values may be higher than indicated. If longer distances
between servers are required, SDTI to Fiber converters can be used, allowing distances over
thousands of meters if necessary.
(www.bluebell.tv)
(www.barnfind.no)
(www.yellobrik.com)
(www.extron.com)
◦ Multidyne HD‐3000‐TRX
(www.multidyne.com)
RG59 30 m / 98 ft
RG6 70 m / 230 ft
RG11 85 m / 279 ft
Fiber 55 km (*)
(*) 55 km is the total length of the return path, i.e. the actual distances between the 2 servers connected
via the fiber link is half of this value, i.e. 22.5 km @ 2970 Mbps.
When reclockers are used, the total delay induced by these reclockers between 2 active
servers on the network may not exceed 15 μs.
2. The XNet-GO option code (66) shall be validated in the options list.
3. They shall all be running compatible software versions. Otherwise, a warning message is displayed.
Only Multicam 21.0 is supported. Versions 20.7 or lower are not supported.
4. The XNet Operation Mode parameter shall have the same value on all EVS servers (Network tab,
XNet section).
5. The EVS video servers shall operate the same multi-essence configuration.
6. The EVS video servers shall operate the same codec for video material to be fully interoperable
between EVS video servers.
7. At least one server should be set as "Preferred" XNet server. Only true for an initial setup of a
network.
8. A different network number must be specified for each EVS video server that you want to connect to
the network. If the same network number is assigned to 2 different systems, the second one will not
be able to connect and a warning message will be displayed.
9. The EVS video servers must be connected with a good quality BNC 75 Ohm cable to form a closed
loop.
Connect the XNET-GO OUT connector of the first EVS video server to the XNET-GO IN connector of
the second one, etc until the loop is closed by connecting the XNET-GO OUT connector of the last
EVS video server to the XNET-GO IN connector of the first one.
The loop must be closed at all times during network operation. If for any reason the loop is open, all
network communication will be interrupted and all systems will automatically switch to stand alone
mode. When the loop is closed again, network operation will resume automatically. This problem can
be avoided or limited using an XHub.
10. The distance shown in the table below is the maximum cable length between two active EVS
servers, or 2 SDTI reclockers, on an XNet-GO network, using a single piece of cable between 2
servers or 2 reclockers.
Intermediate connectors, patch panels, etc., might degrade these figures. Depending on the number
of servers connected on the network, the location of the master server, the presence or not of an
XHub SDTI hub, the actual maximum values may be higher than indicated. If longer distances
between servers are required, SDTI to Fiber converters can be used, allowing distances over
thousands of meters if necessary.
(www.bluebell.tv)
(www.barnfind.no)
(www.yellobrik.com)
(www.extron.com)
◦ Multidyne HD‐3000‐TRX
(www.multidyne.com)
RG59 30 m / 98 ft
RG6 70 m / 230 ft
RG11 85 m / 279 ft
Fiber 55 km (*)
(*) 55 km is the total length of the return path, i.e. the actual distances between the 2 servers connected
via the fiber link is half of this value, i.e. 22.5 km @ 2970 Mbps.
When reclockers are used, the total delay induced by these reclockers between 2 active
servers on the network may not exceed 15 μs.
2. The XNet-VIA option code (65) shall be validated in the options list.
3. They shall all be running compatible software versions. Otherwise, warning message is displayed.
4. The XNet Operation Mode parameter shall have the same value on all EVS servers (Network page,
XNet section).
5. The EVS video servers shall operate the same multi-essence configuration.
6. The EVS video servers shall operate the same codec for video material to be fully interoperable
between EVS video servers.
7. At least one server should be set as "Preferred" XNet server. Only true for an initial setup of a
network.
8. A different network number must be specified for each EVS video server that you want to connect to
the network. If the same network number is assigned to 2 different systems, the second one will not
be able to connect and a warning message will be displayed.
9. All EVS video servers must be connected via the XNet-VIA A1 connector with one of the XHub-VIA
SFP+ ports.
◦ 2x 10G SPF+ Single Rate transceiver (1 for video server and 1 for XHub-VIA) + a LC-LC fiber cable
10. To avoid having potential bandwidth limitations, take into account the limitations/recommendations
in case the XNet-VIA network is composed of multiple XHub-VIA . See the XHub-VIA technical
reference manual for more information.
2. Make sure to set the value to Preferred in the XNet Server field in the XNet section on the Network
page. Then start Multicam.
They should see the "Preferred" XNet server on the network and they will connect automatically.
Connection takes a few seconds (usually between 2 and 5 sec) for each EVS video server.
However, the external systems cannot read the raw files coming from an XT-VIA server. For this reason,
VIA Xsquare/XTAccess are used as a "gateway" between your server and the IT world. In this
architecture, the VIA Xsquare application plays the role of XTAccess orchestrator on the Gigabit
network, communicating via the PC LAN connection.
VIA Xsquare is directly connected to the XT-VIA server through the Gigabit network via an FTP client. It
runs on a Windows workstation and is mainly controlled by the external systems (no user interface) via
soap requests or other processes.
Workflow
1. An external system, for example IP Director, sends a soap request to VIA Xsquare to request the
backup of a given clip created on XT-VIA server .
◦ It gets the clip content that has to be backed up from the server.
◦ It generates a backup file of the clip in the format specified by the external system (no
transcoding feature, only native codec).
◦ It stores the backup file in the target folder specified by the external system.
The following schema shows how the restore of clips is performed with the Gigabit connection and VIA
Xsquare:
◦ It restores, i.e. copies, the clip on the server specified in the soap request.
2. When a clip file has been written to the scanned folder, VIA Xsquare creates a copy of the clip on the
server specified in the VIA Xsquare parameters.
◦ A start LSM ID is specified in VIA Xsquare and incremented as defined for each new clip that is
restored in order to find an empty location on the server.
3. The restored clip is moved from the scanned folder to one of the following subfolders on the external
archiving or backup system:
◦ \Restore.done\: folder where the files are moved to when they are successfully restored.
◦ \Restore.error\: folder where files are moved to when they failed to restore.
• The hardware used on GbE networks with EVS servers need to support jumbo frames.
• The two GbE ports available on the internal switch (PC LAN) are 1000 Base-T ports.
The GbE ports are used for monitoring purposes (XNet Monitor) or for the communication with other
applications (LinX).
Contact the Support or Pre-Sales team to select the appropriate switches for your setup.
5.9.1. GP In Connections
GPI Triggers
The allocation of the XT-VIA Server server GPI triggers is performed in the Multicam Configuration
window, in the GPI tab. See the Configuration manual for detailed information on allocating GPI triggers.
Pin-Out
Specifications
• The input consists in an opto diode (VF @ 1.1 Volt) in series with a 470 ohm resistor.
◦ imax= 30 mA
• Direct connection to a TTL/CMOS signal possible (Pin opto - to GND and pin opto + to the
TTL/CMOS signal).
The relay must be connected between the ground and the corresponding TTL input on the DB-25.
Specifications
• each pin can be individually configured as an output or an input
Pin-Out
The user can define the functions, types and settings associated to the GPI outs in the following
applications:
Specifications
• normally open contact (power off -> open)
• maximum 1 A
• maximum 50 Volts
Pin-Out
6. Boards Description
7 R4X
6 H4X
4 —
3 V4X #2
2 V4X #1 Genlock
1 M4X
The table lists the hardware editions regardless of the date when a given EVS server was first commercialized. Consequently, any hardware revision earlier than
the hardware revision of the first commercialization should be disregarded.
Hardware MTPC Multiviewer Controller Audio Video Base Video Module TGE (10G) Rear Panel Internal LAN Multicam Version
Edition Board
6.00 HS-873 MV4 & MV4X H4X A3X V4X A4 6 x V4X TGE1 XT-VIA Yes 16.0
6.05 HS-873 MV4 H4X A3X V4X A4 8 x V4X TGE1 XT-VIA UHD-8K Yes 16.2
6.10 HS-873 MV4 & MV4X H4X A3X V4X A4 6 x V4X TGE2 XT-VIA Yes 20.5
6.15 HS-873 MV4 H4X A3X V4X A4 8 x V4X TGE2 XT-VIA Yes 20.5
UHD-8K
6.20 HS-873 MV4X H4X A3X V4X A4 6 x V4X TGE1 XT-VIA Yes 16.1
6.25 HS-873 MV4X H4X A3X V4X A4 6x V4X TGE2 XT-VIA Yes 20.5
6.30 M4X MV4X H4X A3X V4X A4 6 x V4X TGE1 XT-VIA Yes 16.4
6.40 M4X MV4X H4X A3X V4X A4 6x V4X TGE2 XT-VIA Yes 20.5
6.3.1. Description
Overview
The V4X board is divided in several parts:
It is highly advised not to remove a V4X board from your EVS server. Should you have to do so,
manipulate the board very carefully, making sure it is not exposed to mechanical or electric
shocks.
COD Modules
V4X modules are the actual codec modules, each of them being able to be configured by software either
as an encoder (for a record channel) or as a decoder (for a play channel).
Connectors
The following table lists the connectors and their respective function:
Connector Function
X RJ45 connected to a black connector on the switch module of the H4X board
LEDs
The table below lists the LEDs available with the genlock functionality. These are functional whatever
the genlock source.
It is crucial to have a continuous and stable genlock signal when the server is in operation. In
case of interferences on the genlock signal that would cause parity violations, the recorders
will automatically be restarted to maintain data integrity.
Green Blinking The genlock module is properly initialized, but no valid genlock signal
is detected.
On A resync is needed.
TF Green Blinking Data transfers occur between the module and the H4X board.
(transfer)
1 — — Not used.
IN Channels (3G-SDI)
IN Channels (12G-SDI)
XIP Panels
IN Channels (12G-SDI)
In a 2nd step, the IN channels are cabled starting from bottom to top, using the first two connectors of
each available codec module.
The remaining IN channels can only be cabled on the connectors C and D of the codec modules on
which HD IN channels are already cabled.
OUT Channels
IN 1A External video input for IPEdit Live-to-Tape feature. (Only active when the OUT1
and OUT2 channel are controlled by IPDirector.)
IN Channels
1080p
OUT 6A SDI monitoring output of the first SLSM phase of the IN1 channel.
OUT 6B SDI monitoring output of the first SLSM phase of the IN2 channel.
OUT 6C SDI monitoring output of the first SLSM phase of the IN2 channel.
OUT 6D SDI monitoring output of the second SLSM phase of the IN2 channel.
XIP Panels
On hybrid panels, you can either use the SDI connectors or the IP connectors for clean inputs and
outputs, but not both connector types concurrently.
In case you are using the IP connectors, the SDI connectors OUT A and OUT B can be used for discrete
SDI monitoring.
The cabling principles on hybrid panels are the same as on SDI panels.
The hybrid panels can accommodate configurations with maximum 8 channels using the 4 codec
modules on the SDI or IP interface.
IN 1A External video input for IPEdit Live-to-Tape feature. (Only active when the OUT1
and OUT2 channel are controlled by IPDirector.)
IN Channels - IP Mode
SFP 1D
CPU1 Green Blinking These LEDs blink to indicate that the processor is running.
EPLD
The available LEDs linked to the SDTI controller module are, from left to right:
FRAMER Green On The signal on the XNet IN connector is a valid EVS SDTI
signal.
NET Green On The XNet SDTI network is established (SDTI loop closed,
correct operation mode, etc).
Connectors
The following connectors are available on the XNet (SDTI) module:
Connector Connection
J15 OUT connector for XNet (SDTI network 2970 Mbps without relay).
J16 IN connector for XNet (SDTI network 2970 Mbps without relay).
T To TGE board.
R To R4X disks.
Switch Cabling
The internal switch module provides a more efficient communication between the H4X board on one
hand and the M4X board on the other hand.
The internal switch relies on the internal LAN, an IP-based network inside the EVS server.
The following connectors are available on the internal switch module and are cabled as described
below:
#4 White Connection to the EVS LNK connector on the rear panel (not
currently used)
TGE1 TGE2
Connectors
The SD card is connected to a slot on the 10GbE module of the EVS server backplane.
The two 1GbE connectors are connected to the two backplane 1GbE ports.
The two 10GbE connectors are connected to the two backplane 10GbE ports.
The Gigabit connectors must be on a network that supports Jumbo Frames of (at least) 9014 bytes
Ethernet frames.
You can set up the GbE IP addresses in the Multicam Configuration window, in the Network tab, Gigabit
Ethernet section. See the Configuration manual for more information.
SFP+ Modules
The following 10G SFP+ Single Rate modules are compatible with the 10GbE connectors of the GbE
board:
• X-SAS-HDX2
If you connect a wrong external array, the following warning message will be displayed:
A connected external array is not compatible with this server.
An array of six hot-swappable SAS disks consists of two stacked series of three disks, mounted from left
to right.
An array of 12 hot-swappable SAS disks consists of four stacked series of three disks, mounted from left
to right.
It is connected to the server via a dedicated SAS cable on the rear panel of the server, provided that the
X-ESAS connection module has been placed inside the server.
Status Function
On On, slowly Spare disk - the corresponding disk is started and used in the RAID
(steady) blinking array.
Blue and red blinking light makes the LED look purple.
It is connected to the server via a dedicated SAS cable on the rear panel of the server, provided that the
X-ESAS connection module has been placed inside the server.
Necessary equipment:
Status Function
Disk Insertion
To insert a disk into an external array, carefully follow these steps:
3. While holding the canister in place, press the 4. All canisters must be well-aligned.
lock lever. The canister is locked when you hear
a "click".
• A1
• 120 GB Flash Memory is used for storing the EVS software and the operating system. Neither audio
nor video data is saved on this disk.
Illustration
LED Information
Internal EVS information.
Board Configuration
REMOTE RESET jumpers are available to designate the remote(s) from which the RESET command can
be sent.
This jumper should be removed if the device connected to the RS422 port is NOT an EVS
controller. Maximum voltage on pin 5 of an RS422 port of the server should not exceed 5 Volt
when the corresponding jumper is engaged. Applying a higher voltage on pin 5 when the
corresponding jumper is engaged will result in permanent electronic damage to the board.
TCP CfgWeb 80 * *
TCP FTP 21 * *
TCP SSH 22 * *
TCP/UDP DNS 53 * *
UDP DHCP 67 * *
*From Multicam version 21.0 onwards, the read-only SNMP Community string has been modified. Please
contact EVS Support to request it.
The following ports are available both on PC LAN #2 and PC LAN #1.
UDP DHCP 67 *
TCP/UDP DNS 53 *
All other ports are closed on PC LAN #2 (and only available on PC LAN #1).
On PC LAN #1 all ports that are not listed in the table above are open.
UDP DHCP 67 *
TCP/UDP DNS 53 53
The following ports can be optionally activated on PC LAN #2 in addition to PC LAN #1.