Documentation Center

Viz Multichannel

Version 4.1 | Published May 27, 2019 ©

Running Viz Multichannel

This section contains information on the following topics:

Media Sequencer

There should always be a connection to the Media Sequencer(s) when running Viz Multichannel. By default, the Media Sequencer runs as a Windows service, and is automatically launched on machine startup. You can check Media Sequencer by starting the Media Sequencer Launcher application. From the Launcher you can start, stop and set run-mode. Alternatively, start Windows Services component and make sure Sequencer is running and set to autostart. You can browse the complete Media Sequencer Documentation (assuming it’s running on standard port) by browsing to:

http://YourMediaSequencerhost:8580/doc

Note: When running Viz Multichannel in Master Control Room (MCR) mode you will need to configure your channels.ini file or else Viz Multichannel will not start in MCR mode.

Also, note that the Playlist Importer by default runs on the Media Sequencer. Hence, in order for any schedule to be imported correctly your Viz Multichannel client must set the correct Startup Parameters for your Media Sequencer.

Startup Parameters

Parameter

Description

Example

-channelini

A path of channel.ini file that we want to use for MCR mode. If no -channelini is specified, MCP will read channel.ini file from the default path, [ProgramData]\Vizrt\Multichannel\channels.ini

-channelini "C:\channel_1.ini"

-msehost

Hostname or IP address for Media Sequencer. If none is used MCP will work in MCR mode, reading each channel’s Media Sequencer from channels.ini. See Playout and Configuration of Channels with channels.ini.If no parameter is provided, MCP will attempt to connect to localhost.

-msehost none-msehost 10.210.0.10-msehost hostname

-vizdb

host:db:user:pw Configure the Viz Engine 3.x database login for the local preview Engine.

-vizdb localhost:VizDb:Guest

Time Format and Timezones

All “internal” time handling calculations and operations, i.e. the time reference in the Media Sequencer, is UTC- Universal Time Code. This is always true, no matter what timezone and locale settings are set on your Windows servers and PCs. This is a reference time only - your actual Window PC clients running the User Interface can and often will have different time-settings. This can easily get confusing, so please keep in mind the following rules:

  • The Media Sequencer reference time is UTC.

  • The Multichannel UI will show the client machine time. If you click on the time-display in the Multichannel UI it will show the Media Sequencer’s time and local offset, if any.
    When importing and handling time-dependent items in Multichannel please make sure that:

  • Logic in rules should use the channel’s timezone setting, see Timezone Settings.

  • Logic for Page Content Filling (PCF) should use the playout channels timezone settings.
    A time-code in the Rules section always have to follow full time-code format, i.e. the value you write by hand has to be HH:mm:ss:00. The value that begin_time contains and what it will push to on-air when using it as an attribute to grab data from, is HH:mm:ss.

See Also