Description of the mechanism of integration with Vizrt graphics systems via GsCtrl module. Function added in 2.8.0 version.

An additional license is required to use this component: Vizrt Software Option “Vizrt Software Option for Vizrt control (control from automation system, from secondary events). License for 1 software channel”

• Vizrt scene - a graphical scene with all animations, textures and scripts.
• Vizrt template - created on the basis of Vizrt scene, contains a reference to Vizrt scene, address in GH and a list of control objects of this scene.
• Page Vizrt - created based on a Vizrt template, contains a reference to the template.
• Graphic composition - basic element, has a name equal to the name of the Vizrt template. It contains elements corresponding to all fields of the Vizrt template. Elements can be of type either Text Object or PIP Frame.
• Text Parameterization Template - Refers to a graphic composition. In this template, you can select the fields to be filled in. Each field can have a fixed value, or be able to be changed by the operator. Each field can have a default value. The playlist loaded into the Program module is collected from these templates.

The image shows an example of possible interaction of software modules.

Before adding a new module, stop the server. To do this, right-click on the Neovid icon next to the clock, and then select Neovid→Stop Server in the opened window.

Open the Neovid→Configure Server Components module configurator window.

Move the External Graphics→Vizrt→MSE/IGH module to the right side of the window using the arrow button. If you want to manage multiple remote graphics systems, you will need to add the appropriate number of modules.

Click OK and start the server Neovid→Start Server.

Start SL NEO Media Platform, open the server control panel and go to the settings of the added module: Administrator Control Panel→Manage→External Graphics Controllers→External Graphics Controller N (Vizrt/MSE/IGH). Enable the module by checking the Service Enabled checkbox.

The customized GsCtrl module is controlled through actions.

In the Program module, you need to add calls to actions of the GsCtrl module: * in Playlist Events, we need to add the generation of a “Play” call on a secondary event for which “Vizrt” or other suitable meaning is specified in Player, * in General Events we need to add a “Stop” call on stopping the main playlist playback.

The “Play” (“Play with params”) command performs the following operations on Vizrt:

1. A template with the specified name is requested
2. A page is created from the template with filled in parameters by sequence number. The name for the page is obtained by adding date and time to the template name
3. A group is created in the Vizrt playlist, the name of the group is obtained by adding the date and time to the template name
4. A secondary event referring to the created page is added to the group
5. If the “Startup Delay (ms)” parameter is not set in the module configuration, the created secondary event is given the “take” command.
6. If the “Startup Delay (ms)” parameter is set in the module configuration, then Startup Delay is added to the time of secondary event generation and this time is entered into StartTime in the Vizrt playlist, at the same time, Vizrt must be configured to start events by time. Time-based triggering allows you to achieve higher accuracy in linking the output of Vizrt events and the main events of the automation playlist. When using the “Play with params” command, the exact time of secondary event generation can be passed from the automation using parameter 5 and passing the variable “$(event_anchor_gmt)” from the automation playlist

The “Stop” command performs the following operations on Vizrt:

1. VizRt playlist is queried
2. Found events are deleted
3. The pages referenced by the deleted events are deleted.

A Vizrt template with a set of control fields is created on the Vizrt side.

The main control field has a name: MediaName. This field describes the type of graphic being output:

• MediaName=Anons - triggers animation for graphics of the announcement type.
• MediaName=Logo_1 - launches graphics with logo #1.

This field can contain a set of different types of graphics at the same time, separated by “|”. For example: MediaName= Anons|Logo_1. In this case, 2 types of graphics will be aired at the same time.

The designer creates a set of graphic compositions, which will have the same parameterization fields as those needed to parameterize the corresponding part of the Vizrt scene. Additional data can be added to the templates, such as default parameter values and values for the marker field for the scene combination. Two types of objects are supported: “Text Object” and ‘PIP Frame’.

With the final parameterization of the “PIP Frame”, the operator will be able to select files from the file folder (via SMB/CIFS) and check dynamically for their presence to indicate “NoRef” status in the playlist. In addition, the operator will be able to see a preview of the song in File Monitor with appropriate text and parameterized graphics. The designer does not have to draw the graphic composition exactly as in the Vizrt editor, but can make it similar or not depending on what they want the operator to see.

This template references the created graphic composition. It also specifies values for the fields to be parameterized. The fields can have a default value. Each field can be made modifiable for the on-air operator, or you can mark that its value is not available to the operator by setting the Final option.

When attempting to edit such an object, the ether operator will not see the fields available for editing, as they are all marked Final.

Example of filling in the template:

• Graphic Composition Name=MasterScene_10_array
• Control objects: MediaName, text6, text7.
• There are default values: MediaName=LOGO_1.
• The “Final” option is enabled for MediaName, so the operator will have 2 fields available for editing:
  

Either graphic songs or text parameterizations of graphic songs are put into the secondary events list of the automation playlist.

Each element has parameters:

• Start Time - determines when this element should exit relative to the start of the primary event,
• Duration - not required to be filled in.

When adding a secondary event to the playlist, the Vizrt MSE/IGH component creates:

• a new group in the Vizrt playlist,
• a page with parameters from the template (page),
• a page in the playlist.

To use Vizrt's “Transition logic”, you just need to create one graphical composition with the same name as the main template in Vizrt. In this composition you need to create objects (“Text Object” and “PIP Frame”) with the same names as in the Vizrt template. This composition will be used for parameterization, but can also be used for a schematic preview of the content, as the resulting parameterization will be visible when working with the playlist in FileMonitor.

To control “Transition logic”, the graphics designer can create a set of text parameterization objects. Text parameterization allows you to use a graphic composition as a template, select fields in this composition and set their values. The field values can be marked as final or as open for changes (checkbox Final in the editor). The designer can create text parametrization objects for controlling various graphics elements - logos, tickers, etc., by setting values for control fields and marking them as final, and selecting actual fields that the operator can parametrize from the playlist. Also, he can set default values for some fields.

When setting graphics manually, the operator works with a set of text parameterization objects prepared by the designer. They can be set in the list of secondary events and parameterized in the usual way. Only fields marked as open for parameterization by the designer are available in the parameterization dialog (checkbox Final is not checked). The selection of video files to be placed in “PIP Frame” elements can be done in the usual way in the parameterization dialog via the browser. To do this, a file folder must be added to the storage list in AirMgr, to which the files available on the Vizrt server are published. These files can be selected from there. The playlist will also check if the corresponding files are available in this folder and show “NoRef” statuses if parameterized files are missing.

From the playlist, secondary events will be sent to the Vizrt control module using playlist events. For this purpose, you can select some value for the playlist field “Player” (e.g. “VZ”) and set up an event in “Playlist Events” that triggers this value and calls the “Play with params” action of the Vizrt control module. When calling this action, you need to pass the Media field from the secondary event (text parameterization name) and the list of parameters from the playlist item. The corresponding value for the Player field can be written in the Player field of the text object in the media database (this filling can be done automatically when using Active Folders or Folder Tags), then it will be transferred to the playlist automatically when dragging the secondary event there.

In Vizrt it is necessary to pass file names without paths and extensions, so if in the parameter value is added, for example, “.avi” then the status of such playlist lines will show “NoRef”. If both a file folder and a media database are added to configure GrStorages at the same time, then components are checked there and there. It is desirable to ensure that the files for Vizrt are only in the file folder, so that if there is no “NoRef” status, you can be sure that the file is in the Vizrt folder and not in some other database. If it is necessary to have files in both the folder and the media base, then this file folder can be added to the media base as Volume.

When Vizrt graphic events are released at the same time, the events are merged into a single page. TransitionLogic control field token values are combined via the “|” character. For example:

• MediaName=Logo_1, begin_time=00:00:00:00:00.
• MediaName=Anons_2, begin_time=00:00:00:00:00.

In Vizrt will be created:

• MediaName=Logo_1|Anons_2, begin_time=00:00:00:00:00.

To make this function work, you need to set the following parameters in the settings in WebConsole→Manage→ExternalGraphicsControllers:

• Transition Logic Template - name of the Vizrt template that is used for TransitionLogic,
• Transition Logic Field - name of the control field in the template,
• Transition Logic Out Suffix - suffix to be added to the value of the control field at the end of the duration.

Additionally, it is recommended to use Secondary check FS for params option (AirMgr→Configure→Actions→Broadcast list actions→Secondary check FS for params).

Another thing to note is that by default a module Program creates a playlist event “PlayGraphics”, which is triggered on a non-empty ‘Media’ value in the secondary event list. The second condition is that the value in the Player field is not “LOGO”. So, if a command with VZ player is sent to Vizrt and the Media field contains the ID of the template, such secondary events will generate “PlayGraphics” which will not go anywhere because a non-existent player is used there. But, they will also go to AsRun, because the command will be generated and the player will be VZ. Therefore, you need to change the second half of the condition in PlayGraphics from “NOT EQUAL” to “NOT CONTAINS” and add VZ|LOGO to the value.

In version 2.8.17, in the Program module settings in the Administrator Control Panel→Manage→Program Outputs→Program_N→Automation→AsRunLogs→Report Secondary Events Players field, you can specify a list of values for the Player column for secondary events. Secondary events with the specified player names will be logged in AsRun.

Since version 2.8.72 the Vizrt control module supports signaling of the current status of exchange with the Vizrt system. The exchange occurs when new secondary events are sent to the Vizrt playlist, when song completion timers are triggered according to their duration, as well as when old items and pages in Vizrt are periodically (every 5 seconds) cleared. If any error occurs during any of these operations, the communication state of the controller with Vizrt is signaled as an error state. The error state is cleared after successful commands resume and there are no error commands for some time.

The communication status can be seen in 2 places:

• on the Status tab in the web console (Status field. When an error occurs, Status=Error)\
• In AirMgr, you can create a Marker Display that will display the communication status of the controller with Vizrt
  

NTP time synchronization must be enabled on the Skylark and Vizrt servers for the systems to communicate properly.