Service Host Administrator Guide

Version 2.2 | Published May 02, 2024 ©

Hardware and Software Requirements

Hardware Requirements

Channel Recorder runs on the following hardware:

  • HP Z840, HP Z8

  • Dell R7910 (2U) Rack Server

The Viz Engine Administrator Guide provides a detailed description of these machines.

Note: To be able to achieve maximum performance using Channel Recorder, Hyperthreading should be enabled. This is located in the BIOS.

Channel Recorder requires one of the following video boards:

Video Boards

Recording Capability

Matrox X.mio3

SDI

Matrox DSX LE4

SDI

Matrox X.mio3 IP

SMPTE ST 2110

Matrox DSX LE4 IP

SMPTE ST 2110

Matrox X.mio5 IP

SMPTE ST 2110

Matrox X.mio5

SDI

Matrox M264

RTP/H.264

DSX.Core (1)

RTP/H.264

(1) From Service Host version 2.1.0 and later, DSX.core has a new license mechanism. The CodeMeter server search list must be updated so that the old server license that contained DSX.core licenses is removed from the list. If CodeMeter server search list still has the old server license listed, then Channel Recorder still attempts to use the old license implementation.

Note: All the above boards should be upgraded to enable recording with different codecs. To check which upgrades the board has available, use the Matrox Utils in the task bar and check if the board has 500 or 550 upgrade applied (for ProRes). If the board does not have this upgrade, this must be ordered. Additionally, to receive RTP/H.264 the Matrox M.264 must have the RTP upgrade. Refer to Recording RTP/H.264 Stream for more information.


images/download/attachments/149916526/tempsnip.png


Note: The DSX.core is not technically a physical board and is used to receive and record RTP/H.264 streams. Refer to Recording RTP/H.264 Stream for more information.

Important: This procedure needs to be followed after installing DSX.core:

  1. Unregister mvfDsxCore.dll.

    1. Click Start > Run (or use the Windows command line: Search > CMD > (Right click) Run as Administrator).

    2. Type REGSVR32 /U "C:\Program Files\Matrox DSX-TopologyUtils\System64\mvfDsxCore.dll" and press ENTER.

  2. Shut down X.info in the task manager.

  3. Delete mvfDsxCore.dll from the folder C:\Program Files\Matrox DSX-TopologyUtils\System64\.

  4. Start X.info .

Note: The M.264 encoder/decoder board is required for CPU intense codecs like XAVC and ProRes. It is mandatory for UHD recording and strongly recommended for ProRes and AVC codecs.

To Upgrade Class and Firmware

To upgrade your Matrox board, for example to enable more IO-ports or a codec upgrade for HD recording, you must use the mvDongleUpdater.exe update utility with your Vizrt supplied license upgrade file <filename>.OPT . This utility is installed with the Matrox driver package and will normally be installed to:

C:\Program Files\Matrox DSK.utils\drivers\mvDongleUpdater.exe

To upgrade the card use this syntax:

C:\Program Files\Matrox DSX.utils\drivers\mvDongleUpdater.exe upgrade -sn="BoardSerialNumber" -f="Path to the upgrade file"

The command above must be run from a Windows command line window.

Software Requirements

Channel Recorder with Service Host requires Matrox DSXTopology Utils version 10.4.101.1285 .

In most cases, a system with a configured and reliable NTP server is necessary. This is particularly important when working with other components such as Viz Dart or Viz One, in which case they should all use the same NTP server. The NTP should be configured so that the polling interval is low enough to not cause noticeable drifting. A value of one minute polling time should be used as a maximum. In Windows, this can be changed using regedit. The important values are located in:

  • HKEY_LOCAL_MACHINE > SYSTEM > ControlSet001 > services > W32Time > TimeProviders > NtpClient

    • SpecialPollInterval should be 60.

  • HKEY_LOCAL_MACHINE > SYSTEM > ControlSet001 > services > W32Time > Config

    • MaxNegPhaseCorrection should be 0xFFFFFFFF (default value for domain members).

    • MaxPosPhaseCorrection should be 0xFFFFFFFF (default value for domain members).

    • UpdateInterval should be 100.

More info is available at https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/windows-time-service-tools-and-settings#Configuration.

See Also