Service Host Administrator Guide

Version 2.1 | Published September 27, 2022 ©

Operation and Troubleshooting

You can use the application Viz Send, which is included in the Viz Engine installation, to communicate with Channel Recorder. Connect the tool to the port specified in the Channel Recorder configuration file.

Channel Recorder Initialization

You can start Channel Recorder with the Service Host web interface.

When Channel Recorder is started, the following happens:

  1. User specified configuration runs in a specific order:

    1. If no serial number is specified, Channel Recorder selects the first board detected by the system.

    2. If no connector is selected, Channel Recorder fails to execute.

  2. Depending on the selected clock type, one of the following can happen:

    1. If GENLOCK is selected, Channel Recorder queries for the genlock signal. Channel Recorder compares the genlock frequency to the signal frequency. The signal frequencies need to be from the same frequency family, for example, 25i and 50p frequencies match, but 29.97i and 50p do not.

    2. If INPUT is selected, Channel Recorder does not query for the genlock signal.

Note: INPUT clock type is only available for Matrox X.mio3 IP, Matrox X.mio3 and Matrox DSX LE4.

If everything works as expected, the input channel is set up and Channel Recorder starts capturing from it. As long as no clip is recorded, the captured frames are thrown away. When a recording starts, these frames are written to the file. This is necessary to be able to provide:

  1. Instant recording

  2. Scheduling of recordings

Workflow Example

  1. Start the service from the Service Host web interface. For more information, refer to the Service Host documentation.

  2. Check the log in the Service Host web interface to make sure that everything has started correctly. You can also check the log file located at %programdata%vizrt/ServiceHost/[service name].

  3. You should not see any errors or warning messages. If there is any error or warning messages, please try to amend it and restart the service using the web interface provided by Service Host. For more information, refer to the Service Host documentation. The following is an example of a successful initial run by Channel Recorder:

    [2018-06-29 08:23:35.031 +02:00][24300][info]: Startup 'ChannelRecorder::ChannelRecorder::Initialize' as 'VizrtCRTest'
    [2018-06-29 08:23:35.031 +02:00][24300][info]: Startup 'ChannelRecorder::ChannelRecorder::Initialize' version of ServiceHost is ''
    [2018-06-29 08:23:35.031 +02:00][24300][info]: Startup 'ChannelRecorder::ChannelRecorder::Initialize' version of ChannelRecorder is ''
    [2018-06-29 08:23:35.046 +02:00][24300][info]: [VizrtCRTest] starting up. thread-id: 24300
    [2018-06-29 08:23:35.046 +02:00][24300][info]: [VizrtCRTest] Applying settings from configuration file!
    [2018-06-29 08:23:35.046 +02:00][24300][info]: [VizrtCRTest] Received: -1 COMMAND_HANDLER PORT SET 6810
    [2018-06-29 08:23:35.046 +02:00][24300][info]: [VizrtCRTest] setting COMMAND_HANDLER PORT=6810
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] OK
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] Received: -1 MVCP PORT SET 10000
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] setting MVCP PORT=10000
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] OK
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] Received: -1 CONFIG SET CLIP_ROOT D:/cr_clips
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] setting CLIP_ROOT=D:/cr_clips
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] OK
    [2018-06-29 08:23:35.047 +02:00][24300][info]: [VizrtCRTest] Received: -1 MAIN CONNECTOR SELECT A
    [2018-06-29 08:23:39.303 +02:00][24300][info]: [VizrtCRTest::CaptureChannelSystemInA] SetInputResolution: Detected input resolution is 1080i25
    [2018-06-29 08:23:39.303 +02:00][24300][info]: [VizrtCRTest::CaptureChannelSystemInA] DetectInputResolutionSdi: Selected resolution is 1080i25
    [2018-06-29 08:23:40.908 +02:00][24300][info]: [VizrtCRTest] Capture from channel InA on board XMIO3/8/550 (serial: A523502)
    [2018-06-29 08:23:40.909 +02:00][24300][info]: [VizrtCRTest] OK
    [2018-06-29 08:23:40.909 +02:00][2916][info]: [VizrtCRTest::CaptureChannelSystemInA] starting up
    [2018-06-29 08:23:40.912 +02:00][5000][info]: [VizrtCRTest::CaptureChannelSystemInA::ClipOutChannel0] starting up
    [2018-06-29 08:23:40.912 +02:00][29676][info]: [VizrtCRTest::CaptureChannelSystemInA::ClipOutChannel1] starting up
  4. The most common errors are not specifying a connector, or specifying a connector that is already in use or non-existing.

When Channel Recorder is successfully running, you can control it using Viz Send, or by using Viz Dart through the MVCP protocol. Refer to Channel Recorder Control Commands for available commands.

Note: Telnet can also be used as a way to control Channel Recorder through the MVCP protocol.

Change of Input Resolution

Starting with version 1.1, the Channel Recorder handles input resolution changes during run-time. When Channel Recorder detects a change in the input resolution, it resets the channel to use the new resolution, without the need to restart the service.

Recording with No Input Signal

Starting with version 1.1, the Channel Recorder can record without an input signal attached. When a signal is attached during recording, Channel Recorder seamlessly uses the signal. This means that the recorder file has a black signal, plus the new connected signal. This requires that the configured resolution matches the connected signal resolution, and that you select the INPUT Clock Type during initial configuration.

Drop Frame Timecode

The user should be mindful when using commands to operate Channel Recorder than involves inputting timecode in drop frame resolutions. Such commands require the input of a valid timecode. However, when a timecode is not recognized as valid, Channel Recorder attempts to fix it by rounding down the timecode to a a valid one. For example:

RECORD SET schedule.mxf IN=15:00:00:00 OUT=16:00:00:00

Both timecodes are not valid when operating in drop frame resolution. The command and timecode automatically change to:

RECORD SET schedule.mxf IN=15:00:00:04 OUT=16:00:00:04

for progressive resolution. For interlace resolution, the timecode automatically changes to:

RECORD SET schedule.mxf IN=15:00:00:02 OUT=16:00:00:02

See Also