Enabling Debug Logging

To enable debug logging, go to the Service Host web interface and to the configuration page of the instance of Channel Recorder that you wish to enable the debug logging. In the configuration page go to:

Add the following arguments: -v -l debug -n 10 -m 50

Where n specifies the maximum number of log files and m the maximum size of each log file in MB. By default, the number of log files is four and the maximum size of each log file is 10 MB.

Channel Recorder and Viz Engine

As both Channel Recorder and Viz Engine use Matrox topology, make sure Viz Engine starts before Channel Recorder if you need to use a shared input. If Viz Engine starts after Channel Recorder, the acquisition of the selected input connector fails.

The Service Reports Timeout Errors / Failed to Get Frame / Uninitialized Pointer

If Channel Recorder reports timeout errors, try increasing the timeout value by sending the command CONFIG SET TIMEOUT [timeout], or by configuring the timeout value using the web interface provided by Service Host.

Channel Recorder reports the following:

This is usually related to the performance of the HDD and/or RAID.

Recordings Stop Unexpectedly when Using Viz Dart

The issue is usually related to the signal being unstable and Channel Recorder restarting due to change in resolution. Check in the Channel Recorder logs for the Status of connector string. If there are more than two signals present in the logs, then the signal is unstable.

An example of a good output after searching the logs is the following:

The Service Reports Output Dropped a Buffer, Cancelled Late

If Channel Recorder reports output dropped a buffer errors, try increasing the timeout value by sending the command CONFIG SET TIMEOUT [timeout] or configuring the timeout value using the web interface provided by Service Host. Increasing the ringbuffer size by sending the command CONFIG SET RINGBUFFERSIZE [size] or configuring the ringbuffer size using the web interface provided by Service Host, might also help.

Channel Recorder reports the following:

This is usually related to the performance of the CPU. Please make sure that CPU usage while recording does not exceed 80%. Do not forget to enable Hyperthreading if this is disabled in the BIOS.

Service Stops without a Dump File

If there is a change in Windows time (changing the timezone) while Service Host is running, it stops functioning and must be restarted. This is a known issue and will be fixed in future release. To avoid this problem, make sure that Windows time is synchronized to an NTP server. Daylight Savings Time is not affected by this and does not stop Service Host.

Recording with Unsupported Codec / Container / Resolution

If a combination of Codec / Container / Resolution is not supported Channel Recorder will not start the recording.

Channel Recorder reports the following:

Configuring via Service Host Web Interface is slow

This is a known issue and happens due to having the license server located in a location that is far from where the Channel Recorder machine is located. This is not only affecting Service Host but also Viz Engine. This used to also affects a Channel Recorder instance start up however in Service Host 2.0.0 this was improved by not contacting the server during start up and using the configured value directly. The license configuration was usually in the form 130-4098016501-ENG_SVCHOST_CORE but in 2.0.0 this has been modified to 130-4098016501-ENG_SVCHOST_CORE-X, X is the location of the license and can be local (0) or network (1). This configuration should be filled automatically during Channel Recorder configuration in the Web Interface. Old license string will still be supported.