Viz Opus Deployment Guide

Version 1.3 Copyright © 2019 Vizrt. All rights reserved. No part of this software, documentation or publication may be reproduced, transcribed, stored in a retrieval system, translated into any language, computer language, or transmitted in any form or by any means, electronically, mechanically, magnetically, optically, chemically, photocopied, manually, or otherwise, without prior written permission from Vizrt. Vizrt specifically retains title to all Vizrt software. This software is supplied under a license agreement and may only be installed, used or copied in accordance to that agreement.

Disclaimer Vizrt provides this publication “as is” without warranty of any kind, either expressed or implied. This publication may contain technical inaccuracies or typographical errors. While every precaution has been taken in the preparation of this document to ensure that it contains accurate and up-to-date information, the publisher and author assume no responsibility for errors or omissions. Nor is any liability assumed for damages resulting from the use of the information contained in this document. Vizrt’s policy is one of continual development, so the content of this document is periodically subject to be modified without notice. These changes will be incorporated in new editions of the publication. Vizrt may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. Vizrt may have patents or pending patent applications covering subject matters in this document. The furnishing of this document does not give you any license to these patents.

Technical Support For technical support and the latest news of upgrades, documentation, and related products, visit the Vizrt web site at www.vizrt.com.

Created on 2019/10/28 Viz Opus Deployment Guide - Version 1.3

Contents 1 Overview...... 5 2 Hardware specification...... 7 2.1 Hardware setup recommendation ...... 7 2.1.1 DELL R7910 Motherboard layout...... 8 3 Viz Opus Configuration...... 12 3.1 Prerequisites...... 12 3.2 NVIDIA graphics card configuration ...... 12 3.3 Viz Engine, version 3.9.1.73042 ...... 13 3.4 Multiview settings...... 14 3.5 Video settings (Live, Stream and Clip) ...... 14 3.6 Audio settings (live, stream and clip) ...... 15 3.7 Enable write lock for switcher scene...... 17 4 Viz Mosart server setup ...... 19 4.1 Media Administrator ...... 20 4.2 AVAutomation ...... 21 4.2.1 Audio settings ...... 21 4.2.2 Graphics settings...... 22 4.2.3 Integrated Engine ...... 23 4.2.4 VideoServer ...... 24 4.3 Overlay Graphics...... 24 4.4 MMTrioInterface ...... 25 4.5 Viz Opus Multiview ...... 26 5 Audio Mixer Configuration...... 28 5.1 Yamaha 01V961 Audio Mixer...... 28 5.2 Channel routing...... 30 6 Viz Opus Configuration Files...... 32 6.1 User.config settings changes ...... 32 6.1.1 MMAVAutomation user.config...... 32 6.1.2 MMConsoleAdmin_2007 user.config ...... 34 6.1.3 MMConsoleAdmin_MOS user.config ...... 34 6.1.4 MMMediaAdministrator user.config...... 34 6.1.5 MosartMultiGui user.config ...... 35 6.2 Configuration Files ...... 35

3 Viz Opus Deployment Guide - Version 1.3

6.2.1 %ProgramData%\Mosart Medialab\ConfigurationFiles\graphic_settings.xml ...... 35 6.2.2 %ProgramData%\Mosart Medialab\ConfigurationFiles\vsettings.xml...... 35 6.2.3 C:\channeltemplates\ClipServerVizEngine.xml...... 36 6.2.4 C:\channeltemplates\VizEngineSwitcherConfig.xml ...... 36 6.2.5 C:\channeltemplates\avconfig.xml ...... 36 6.2.6 C:\channeltemplates\channeltemplates.xml ...... 37 6.2.7 C:\channeltemplates\keyboard_shortcuts.xml ...... 37 6.2.8 C:\channeltemplates\VizrtUserMacros.xml ...... 38 6.2.9 C:\ProgramData\Vizrt\viz3\opus_config.cfg: ...... 38 6.2.10 C:\ProgramData\Vizrt\viz3\-1-0.cfg: ...... 42 6.2.11 C:\Manus\OpusDemoRundown.xml: ...... 46 6.2.12 %ProgramData%\vizrt\Media Service\config.json:...... 46 7 Viz Opus Clean Feed Setup ...... 48 7.1 Hardware Configuration...... 48 7.2 Software Configuration ...... 48 7.3 Clean Feed Configuration...... 48 7.4 Dirty Feed Configuration...... 49 7.5 Modifying the Dual Channel Shortcuts ...... 50 8 Viz Opus Graphics Scene - advanced ...... 51 8.1 Opus Viz Scenes Communication ...... 51 8.1.1 Transition Effects...... 51 8.1.2 DVE Effects (Butterfly, 3Box, media windows)...... 51 8.1.3 Diagram...... 51

4 Viz Opus Deployment Guide - 1.3

1 Overview This is the Viz Opus Deployment Guide. Its aim is to provide instructions on how to install, configure and service Viz Opus. Viz Opus is a single-box, relatively easy to set-up and configure studio automation software and hardware package. You can view Viz Opus as a packaged version of a subset of the full Viz Mosart studio automation package. As such, there will always be a corresponding Viz Mosart release to any given Viz Opus release. For instance, Opus 1.3 will be based on Mosart 3.8. And so on. Currently, Opus is packaged as a single server with two graphics cards and includes a hardware audio mixer. Full details are provided later in this guide and in the Viz Opus Administrator Guide.

If you are not familiar with Opus or Mosart, you should first take a look at our public product web pages to see how we present the solutions to our customers: • http://www.vizrt.com/products/viz_mosart/ • http://www.vizrt.com/products/viz_opus/ This manual ultimately requires an understanding of Mosart application(s) or rather the components of Mosart used in Opus. Find the relevant information on the Documentation Center. Other Resources: • Public Installers: • Opus ftp://ftp.vizrt.com/products/VizOpus/Latest%20Version/ • Mosart ftp://ftp.vizrt.com/products/VizMosart/Latest%20Version/

• Public forum: http://forum.vizrt.com/

2 Hardware Specification The Viz Opus package currently consists of the following pre-installed hardware components:

HP Z840 Viz Engine • 5U rack mountable server system • 1 NVIDIA Quadro P6000 graphics card • 1 NVIDIA Quadro P2000 graphics card • 1 Matrox X.mio3 +AES Audio break out • Viz License dongle • Yamaha 01V96i Audio Mixer • Breakout cable Or alternatively: Dell R7910 Viz Engine: • 2U rack mountable server system • 1 NVIDIA Quadro P6000 graphics card • 1 NVIDIA Quadro P2000 graphics card • 1 Matrox X.mio3 + AES Audio break out • Viz License dongle • Yamaha 01V96i Audio Mixer

 Note: With extra licensing, Viz Opus can control external equipment such as camera robotics, routers, NRCS integration in addition to providing a Timing Display, Audio File Display and Virtual Audio Fader Panel. However Viz Opus is designed to be a simple setup, so if you want to control a lot of existing equipment, Viz Mosart is usually the preferred solution.

2.1 Hardware Setup Recommendation HP Z840 Viz Engine: • 5U rack mountable server system • 1 NVIDIA Quadro P6000_ graphics card • 1 NVIDIA Quadro P2000_ graphics card • 1 Matrox PCI Card (Matrox X. Audio mio3 + AES) • Viz License dongle Dell R7910 Viz Engine: • 2U rack mountable server system, including: • 1 NVIDIA Quadro P6000_ graphics card

• 1 NVIDIA Quadro P2000_ graphics card • 1 Matrox PCI Card (Matrox X. Audio mio3 + AES) • Viz License dongle

HP Z840 Motherboard layout To achieve the maximum performance with an Opus system the Matrox and the GPU for rendering (K5200, P6000...) need to be on the same PCIe bus. This is independent of the usage of the live as DVE or texture. Below is the layout for the Z840. Slot 2 and 6 are connected to CPU 1 and have to be used for the render GPU and the Matrox. Slot 4 is connected to CPU 2 and has to be used for the GPU which drives the UI.

2.1.1 DELL R7910 Motherboard layout This is also a dual CPU setup and again the main GPU and the Matrox need to be on the same PCIe bus. The PCI slots are not directly on the motherboard but on riser cards. There are two full height riser cards. The middle one and the left one (when looking at the chassis from the front). The left one has an alternate layout where one PCie gen3 x 16 is available it is connected to CPU 1. The middle one has the lower slot connected to CPU 1 and the upper to CPU 2. This riser will hold the main GPU

This riser will hold the Matrox in slot 5 and the UI GPU in slot 4.

System with two GPUs Z840

The smaller GPU has the monitor/KVM attached. It also needs to be set as the primary GPU in the bios for the user to see the boot-up messages. To start an instance of Viz Engine on the render GPU, -u2 needs to be used for the first instance and -u4 for the second.If no configuration file name is specified as a command line argument the configs are named ....1-0.cfg and ....-3-0.cfg There will be no instance of viz running on GPU 1. It is only for the user interface and the media preview.

System with single GPU Z840

In the case of a single GPU setup, for example if there is no media preview needed, the monitor/ KVM gets connected to the render GPU. In this case, the first instance of viz needs to be started with -u1 or no command argument for GPU assignment and the second one with -u2.

3 Viz Opus Configuration This section describes The Viz Opus 1.3 setup for servers with Matrox XMio3, and a Yamaha audio mixer. We only describe settings that differ from default configuration of the components.

3.1 Prerequisites Viz Opus requires Graphic Hub and Media Sequencer. These can be installed locally on the Viz Opus or Viz Opus can be configured to use central servers running these applications. All necessary configuration and setup files are located on the FTP server: ftp.vizrt.com/products/ VizOpus/Latest Version/

3.2 NVIDIA Graphics Card Configuration On the Viz Opus server, make sure the GPU utilization in Nvidia Control Panel is set to use both graphics cards:

Viz Engine(s) should use the bigger graphics card - this is also the card the monitor must be connected to (as the Viz Engine will use the same card as the monitor).

3.3 Viz Engine, Version 3.9.1.73042 The Viz Engine works as a video server, and is the core of a Viz Opus package, with all the Viz Opus applications installed on it. The Viz Engine has 8 HD/SDI inputs, 4 HD/SDI outputs and one Media Preview output available from the Viz Opus GUI. Streaming is available with 2 in-streams and 1 out-stream. In a normal Viz Opus setup, the Viz Engine is physically connected to all the devices in a TV station's production control room. The system only needs a camera or other external inputs, graphics and video content to facilitate content production and distribution. Input is received from a Newsroom Control System, such as iNEWS or ENPS. One person can then control a full production for television, i.e. playout clips, run graphics, and cut between various camera sources. 1. Install the Viz Engine version 3.9.1.73042, in Dual Engine Mode for PGM and Clean Feed. 2. Start and stop the engine to create default configuration files. 3. Run the Opus Configuration Tool. The tool will normally be installed to C:\Program Files (x86)\vizrt\Viz Opus ConfigurationTool\VizOpus.ConfigurationTool.exe. a. This will automatically generate a config file for PGM setup. The filename of the PGM engine should be named (-1-0.cfg). For Clean Feed setup another configuration file must be added (-3-0.cfg) for the 2nd Viz Engine instance. Engine 1 will load the switcher scene and produces the clean feed while the second instance adds graphics elements on top of the clean feed output.

• Engine 1 - clean feed - -1-0.cfg • Engine 1 - dirty feed - -3-0.cfg

Replace the default configuration file (can be found in the ProgramData folder on the server (%programdata%\vizrt\viz3) with the one found on the FTP server. Note that it must be named the same as the default file: -1-0.cfg For setup instructions for the Clean Feed, see Viz Opus Clean Feed Setup. The following settings differ from the default configuration on the Viz Engine. While changes can be made in the configuration file, it is highly recommended that all available changes should be done in the GUI, as the text file is not meant to be edited.

3.4 Multiview Settings ## Enable multiview feature. Disabled by default. enable_media_preview = 1 ## Set the GPU on which Multiview should be executed. media_preview_gpu = 1 ## Set the update frequency for Multiview. media_preview_update_freq = 8

3.5 Video Settings (Live, Stream And Clip)

Under the Video Input section of the Viz Configuration, utilize the following settings to enable the media asset on the engine live_system1 = HD1080i live_system2 = HD1080i live_system3 = HD1080i live_system4 = HD1080i live_system5 = HD1080i live_system6 = HD1080i live_system7 = HD1080i live_system8 = HD1080i (set to INACTIVE when using Clean Feed setup) stream_system1 = HD1080i stream_system2 = HD1080i clip_system1 = HD1080i clip_system2 = HD1080i clip_system3 = HD1080i clip_system4 = HD1080i

3.6 Audio Settings (Live, Stream And Clip) The configuration for clip, live and stream audio is set up as described under (NB! Stream audio routing is available from VizEngine release 3.8): The channels in the configuration file is 0-based and on the format: ChannelRoute_ =

I.e: to route stereo audio from Live1 to AES/EBU output 1/2, the setting should look like this: ChannelRouteIn0_0 = 0 and ChannelRouteIn0_1 = 1.

CLIP (4 stereo channels):

Configuration setting Physical output

ChannelRouteClip0_0 = 0 Clip1 outputs to audio channels 1/2 ChannelRouteClip0_1 = 1

ChannelRouteClip1_0 = 2 Clip2 outputs to audio channels 3/4 ChannelRouteClip1_1 = 3

ChannelRouteClip2_0 = 4 Clip3 outputs to audio channels 5/6 ChannelRouteClip2_1 = 5

ChannelRouteClip3_0 = 6 Clip4 outputs to audio channels 7/8 ChannelRouteClip3_1 = 7

LIVE (4 stereo channels):

Configuration setting Physical output

ChannelRouteIn0_0 = 8 Live1 outputs to audio channels 9/10 ChannelRouteIn0_1 = 9

ChannelRouteIn1_0 = 10 Live2 outputs to audio channels 11/12 ChannelRouteIn1_1 = 11

ChannelRouteIn2_0 = 12 Live3 outputs to audio channels 13/14 ChannelRouteIn2_1 = 13

ChannelRouteIn3_0 = 14 Live4 outputs to audio channels 15/16 ChannelRouteIn3_1 = 15

 Note: Stream inputs are not supported for Viz Opus 1.3.

STREAM (2 stereo channels):

Configuration setting Physical output

ChannelRouteStream0_0 = 0 Not configured by default ChannelRouteStream0_1 = 1

ChannelRouteStream1_1 = 0 Not configured by default ChannelRouteStream1_0 = 1

This will output audio on Matrox AES break out (as we are limited to 8 stereo channels on the Yamaha, streams are not physically connected to the mixer in this setup). All information regarding Matrox mapping and engine setup is available in the Viz Engine Administrator's guide: https://docs.vizrt.com/viz-engine-3.9.1.html Matrox upgrade instructions can be found in the Viz Engine Administrator's guide: https:// docs.vizrt.com/viz-engine-guide/3.9.1/Matrox_Hardware.html For streaming capabilities, see: https://docs.vizrt.com/viz-engine-guide/3.9.1/ Configuring_Viz.html

Changing stream setup: 1. Stop Viz IP Stream In service if not stopped already 2. Configure input stream in config file C:\ProgramData\vizrt\IP Streaming Input Service\IPStreamIjn_startup.conf using the correct URL for the stream (udp) 3. Start stream service

 Note: When changing configurations on the Viz Engine, remember to restart the Viz Engine application for the changes to be applied.

3.7 Enable Write Lock For Switcher Scene The switcher scene for Opus 1.3 needs to be write locked so that customers cannot change or modify the scene by themselves. Therefore the scenes user-rights need to be changed after installation. • Install Graphic Hub Manager • Log in with the same user account used for importing the scene (usually Guest) • Right-click on the switcher scene and select attributes

• Change the Owner to Admin • Remove Group and World rights and Apply The scene can only be altered by users with Graphic Hub admin rights after that.

 Note: Switcher scene that was modified at a customer site, will not be covered under Support . Please use the common procedures for Feature Request for any needed changes.

4 Viz Mosart Server Setup

• Install Viz Mosart server and GUI on the Viz Opus server (Audio Panel and Timing Display is optional and not covered in this guide). • Change the Viz Mosart MultiGUI shortcut, adding the -opus parameter and change the icon to the Viz Opus icon.

1. Start and stop the following Viz Mosart applications to create default settings files: a. Media Administrator b. Manus Adminsitrator c. AVAutomation d. Overlay Graphics (optionally MMTrioI) e. Viz Opus GUI (Viz Mosart MultiGUI) 2. Copy the newly created files from Step 3 into C:\channeltemplates folder 3. Replace all user.config files in C: \Users\\AppData\Local\Mosart_Medialab each application folder and Viz Mosart version respectively.

4. Replace configuration files in C:\ProgramData\Mosart Medialab\ConfigurationFiles

4.1 Media Administrator user.config file in MMMediaAdministrator

4.2 AVAutomation

4.2.1 Audio settings user.config file in MMAVAutomation

4.2.2 Graphics settings user.config file in AVAutomation

4.2.3 Integrated Engine (VizEngine as VisionMixer) user.config file in AVAutomation

4.2.4 VideoServer

Settings.xml file in C:\ProgramData\Mosart Medialab\ConfigurationFiles

4.3 Overlay Graphics Choose to use either OverlayGraphics (preferred) or MMTrioInterface for overlay graphics handling. Overlay Graphics configuration file (if applicable) exists as graphic_settings.xml file in C: \ProgramData\Mosart Medialab\ConfigurationFiles

4.4 MMTrioInterface user.config file in MMTrioInterface

4.5 Viz Opus Multiview In the Viz Opus GUI, there is an option to open the Media Preview. This will output the enabled sources from the Viz Engine (directly). This window will auto-scale based on the available sources. It is possible to configure the visible sources by adding the following settings to the GUI's user.config file: PreviewUnusedVideoSources and PreviewUnusedClipSources Example (will remove the Video sources 4 and 5 and Clip source 6 from the Multiview window):

4,5 6

 Note: The above settings triggers hiding sources on the Viz Engine on opening the Multiview window. Resetting the Multiview visible sources requires a restart of the Viz Engine. It is also possible to hide or set sources visible by commands in the Viz Engine console (MEDIA_PREVIEW***VISIBLE SET 0/1 (false/true)) or by script. When adding multiple values, the following separators are allowed: space, comma and semicolon. In addition, the names of the source windows are changeable.

5 Audio Mixer Configuration

5.1 Yamaha 01V961 Audio Mixer The Viz Engine in a Viz Opus system comes bundled together with a Yamaha 01V96i digital audio mixing console. This mixing console has 32 mono and 4 stereo mixing channels. It comes with a MY8AEB interface card and a rack mount kit. This audio mixer can be controlled through the Viz Mosart Audio Panel and Viz Mosart Audio Player software, or the operator can make adjustments directly on the mixing console.

 Note: If not installed on shipping: install the Yamaha Steinberg USB driver: http:// www.yamahaproaudio.com/

A pre-configured setup is available to synchronize with the Audio Mixer console using Yamaha's Studio Manager. For enabling synchronization from the software, the port to be used must be specified on the panel itself. The same is true for allowing AVAutomation to control the panel:

In the DIO/SETUP console screen display, there are two relevant settings: 1. You enable synchronization by selecting USB in the port field under Special Functions - StudioManager. 2. Allowing AVAutomation to control the panel, select USB in both the port fields (Rx Port and Tx Port) under General.

 Note: Changing any one of these will clear the other host setup and must be re-inserted when the controller host changes.

5.2 Channel Routing Make sure all the cables are correct. Setup with streaming and live 1-4: Microphones are set up using fader 1-4 on the mixer, input patch AD1-4 Live channel 1 → routed to stereo channel 5 / 6 Live channel 1 → routed to stereo channel 7 / 8 Live channel 1 → routed to stereo channel 9 / 10 Live channel 1 → routed to stereo channel 11 / 12 Stream channel 1 → routed to stereo channel 13 / 14 Stream channel 2 → routed to stereo channel 15 / 16 Clip channel 1 → routed to stereo channel 17 / 18 Clip channel 1 → routed to stereo channel 19 / 20 Clip channel 1 → routed to stereo channel 21 / 22 Clip channel 1 → routed to stereo channel 23 / 24 Telephone → routed to channel 25

Mosart Audio Player → routed to channel 26 (see "Audio settings (live, stream and clip)" section for physical output on the Matrox break out box).

The channels must be routed correctly (input patch) on the Yamaha: Inputs on the interface card on the Yamaha mixer corresponds to SL-01, SL-02 etc.

(Note that this test setup is missing mics and has multiple routing of single inputs, thus it should not be copied directly). To control the faders from Opus, they must be set up in the Control Change Assign Table:

6 Viz Opus Configuration Files The Opus Configuration tool is adjusting several files while doing the auto-configure operation. This is an overview of the files and the changes it makes. This section contains information about the following files:

• User.config settings changes • MMAVAutomation user.config • MMConsoleAdmin_2007 user.config • MMConsoleAdmin_MOS user.config • MMMediaAdministrator user.config • MosartMultiGui user.config • Configuration Files • %ProgramData%\Mosart Medialab\ConfigurationFiles\graphic_settings.xml • %ProgramData%\Mosart Medialab\ConfigurationFiles\vsettings.xml • C:\channeltemplates\ClipServerVizEngine.xml • C:\channeltemplates\VizEngineSwitcherConfig.xml • C:\channeltemplates\avconfig.xml • C:\channeltemplates\channeltemplates.xml • C:\channeltemplates\keyboard_shortcuts.xml • C:\channeltemplates\VizrtUserMacros.xml • C:\ProgramData\Vizrt\viz3\opus_config.cfg: • C:\ProgramData\Vizrt\viz3\-1-0.cfg: • Viz Opus specific auto-configured fields defining the selected encoding • Common Viz Opus auto-configured fields • C:\Manus\OpusDemoRundown.xml: • %ProgramData%\vizrt\Media Service\config.json:

6.1 User.config Settings Changes The following files are customized and available with the installation of Viz Opus under the \AppData\Local\Mosart_Medialab folder:

6.1.1 MMAVAutomation user.config

Field Value If Field Description Exists

EnableVizEngine_1 True overrid Enables the engine e

VizEngineHost_1 localhost overrid The hostname for the engine e

Field Value If Field Description Exists

EnableVizEngine_2 True overrid (set to true as a workaround for a e known bug)

VizEngineHost_2 localhost overrid (set to same as 1 as a workaround e for a known bug) txt_MosPlayList Opus_Fullscreen overrid MOS playlist for fullscreens e graphics_system VIZRT overrid Enables use of Vizrt for graphics e gfxShows (XML for concepts) overrid Concepts to use for scenes e

TakeOutFullScreens True overrid Enables auto takeout for fullscreens e

Use_Consept_Override True overrid Enables concept override for e fullscreens

EnableAudioMixer True overrid Enables the audio mixer e cmbAudioMixerType MIDIMIXER overrid Sets the drive type for the audio e mixer (Yamaha)

MIDI_InputPort_Audio Yamaha 01V96i-1 overrid Sets the input port USB name for the e mixer

MIDI_Port_Audio Yamaha 01V96i-1 overrid Sets the output port USB name for e the mixer

EnableSoundFilePlaye True overrid Enables use of an audio player r e txtHostSoundPlayer localhost overrid Host name for audio player e

CurrentSoundFilePlay Mosart Audio Player overrid Enables use of the Mosart Audio er e Player as audio player txtDefaultSoundDirec D:\audio overrid The directory to store audio files tory e

Field Value If Field Description Exists

IntegratedEngineConn Type=VizEngine; overrid Defines the Viz Engine connection ectionString Server=localhost; e and points to its configuration. Config=VizEngineSwit cherConfig.xml

FrameRate 25 or 29.97 overrid The frame rate to use. NTSC: 29.97, e PAL: 25 (selected in the Opus Configuration)

6.1.2 MMConsoleAdmin_2007 user.config

Field Value If Field Exists Description

FrameRate 25 or 29.97 override The frame rate to use. NTSC: 29.97, PAL: 25 (selected in the Opus Configuration)

6.1.3 MMConsoleAdmin_MOS user.config

Field Value If Field Exists Description

FrameRate 25 or 29.97 override The frame rate to use. NTSC: 29.97, PAL: 25 (selected in the Opus Configuration)

6.1.4 MMMediaAdministrator user.config

Field Value If Field Exists Description

ClipServer1 Name=VizEngine; override Configures the local Type=VizOne; Media Service as video server. Server=localhost; Port=21099; UserName=admin; Password=admin; PublishingPoints=MediaS ervice; Folder=D:/Clips/; Config=ClipServerVizEng ine.xml

6.1.5 MosartMultiGui user.config

Field Value If Field Exists Description

DefaultPackageVar CLIP keep Default variant when drag and dropping iant a PACKAGE from search

DefaultFloatVaria FULL CLIP keep Default variant when drag and dropping nt an ADLIBPIX\FLOAT from search

DefaultVoiceOverV VO keep Default variant when drag and dropping ariant a VO from search

OutWordVisibleOnC True keep When playing cameras - show outwords ameras

OutWordVisibleOnF True keep When playing fullscreen graphics - show ullscreenGraphics outwords

ShowInewsUserRund True keep Only used if using iNews owns

Workspaces (workspace keep Default workspace setup named Opus XML)

6.2 Configuration Files

6.2.1 %ProgramData%\Mosart Medialab\ConfigurationFiles\graphic_settings.xml

A controller named VIZRT MSE to handle graphic content using the DSK handler is added. Existing controllers and handlers are not changed. Editing should only be done through the Graphics Interface UI.

6.2.2 %ProgramData%\Mosart Medialab\ConfigurationFiles\vsettings.xml

A video player named VizEngine using the ClipServerVizEngine.xml file as configuration (see below) is defined. Two virtual ports A/B are created and connected to the CLIP1/CLIP2 cross-points and video-port 1/2 on the VizEngine video playout. If the file exists from before it is not changed. Editing should only be done through the AV Automation UI.

6.2.3 C:\channeltemplates\ClipServerVizEngine.xml It gets configured how the Viz Engine is used as a video playout server. The table describes only the important fields.

Field Default value If Field Exists Description

ControlScenePa Vizrt/VizOpus/ keep Path to the switcher scene in Graphic th ControlScenes/ Hub switcher

ControlSceneLa Back keep The layer the switcher scene is located yer in on the Viz Engine renderer

ClipNamePrefix D:/Clips/ override The path prefix of the clips.

ClipNamePostfi (none) keep Clip extension (if not set, all types can x be played, but needs to be specified in the NCS)

AssetToMediaMa UseTitleAsSlug keep Chooses mapping of assets p

6.2.4 C:\channeltemplates\VizEngineSwitcherConfig.xml It configures the integrated engine used by AV Automation to use the Viz Engine as a switcher. The file is not changed if it exists from before.

Field Value If Field Exists Description

ControlSceneLayer Back keep The layer to set the switcher scene on the Viz Engine

NumberOfKeyBuses 8 keep Number of key buses in template editor

ControlScenePath Vizrt/VizOpus/ keep Path to the switcher ControlScenes/switcher control scene

6.2.5 C:\channeltemplates\avconfig.xml This file configures AV Automation. If the file exists from before it is not changed. The following sections are created otherwise.

• The video section defines the cross-points available in AV Automation that are open for automation using templates. It also links the cross-points to audio channels of the audio configuration. • The audio section defines the faders available in AV Automation that are open for automation using templates. • The effect section defines the effects available in AV Automation and GUI for automation purposes.

6.2.6 C:\channeltemplates\channeltemplates.xml It defines the template sets shown as Show in the Viz Opus UI and AV Automation. A template set called DEMO is added to operate the demo rundown.

6.2.7 C:\channeltemplates\keyboard_shortcuts.xml It defines the keyboard short-cuts to use for operation. If the file exists from before it is not changed. The table below lists the Viz Opus specific short-cuts that get created otherwise.

Text Usage

SET CAM 1 IN ME1 KEY 1 Used for setting cross-points within a DVE while it is on air. SET CAM 2 IN ME1 KEY 1 SET CAM 3 IN ME1 KEY 1 SET CAM 4 IN ME1 KEY 1 SET LIVE 1 IN ME1 KEY 2 SET LIVE 2 IN ME1 KEY 2 SET LIVE 3 IN ME1 KEY 2 SET LIVE 4 IN ME1 KEY 2

Text Usage

CAM 1 Used for setting labels on the preview panel. CAM 2 The preview panel will get the text associated as label. CAM 3 CAM 4 CLIP A CLIP B CLIP C CLIP D LIVE 1 LIVE 2 LIVE 3

LOWERTHIRD Used for letting manual lowerthirds drop to the keyboard.

6.2.8 C:\channeltemplates\VizrtUserMacros.xml It defines the macros used by Viz Opus. Macros to operate the demo rundown are added to the file. Existing macros are not deleted.

6.2.9 C:\ProgramData\Vizrt\viz3\opus_config.cfg: It configures the switcher scene running on the Viz Engine. Below are the available settings with the value set by the Opus Configuration displayed in the value column. If the file exists from before it is not changed.

Field Value If Description Field Exist s max_inputs 6 keep Amount of source inputs active at the same time. In order to save resources as much as possible, the switcher scene will automatically deactivate sources which haven't been used for a while. This avoids having all the inputs active all the time which does lead to decreasing the overall performance of the engine. The scripts define how many inputs can be active at the same time, will activate those which will be needed soon, and disables those who are not used. The maximum number of active inputs can be defined in the configuration file. To avoid performance issues the maximum number of active DVE inputs should never be higher than 6 while for texture-based sources it can be set to up to 8. audio_chann 1,2 keep Amount of active audio tracks within clips. The volume of any els other existing audio track within the clip will be set to 0. The engine typically reads all the available audio tracks within a single clip. If it is needed to mute certain audio tracks, this can be configured. The maximum number of trackings for one clip is defined with 16. video_mode TEXTUR keep TEXTURE or DVE sources. E Video sources can either be texture or DVE based. Depending if sources need to be used in other scenes in the layers above at the same time the correct setup needs to be defined. While DVE will provide the better rendering performance and therefore leaves more resources for other tasks, texture based sources will allow the usage of the same source on multiple scenes (layers) at the same time and provide more flexibility when it comes to scene design. internal_au 0 keep Requires SDI embedded audio signals. dio If audio needs to be handled internally due to the absence of an audio mixer, the switcher scene can handle audio cuts and cross fades between audio sources as well. Depending on the configuration the audio can follow the currently used video source or can be controlled via AV Automation manually. Internal audio handling is not the default behaviour and needs to be activated.

Field Value If Description Field Exist s audio_on_ma 0 keep Video sources in main layer scenes do also get controlled via in the switcher scene. It is important that sources also do have a corresponding director (e.g. LIVE1AUDIO) and the correct keyframe name (first and audioDuration). audio_follo 1 keep Audio follows video. If set to 1 the audio will behave in the w same way the video does. If the video source is not switched on program, the audio gets turned to 0%.If set to 0 all live sources are set to 100% (old behavior, for external mixing purposes only). audio_in 2 keep Audio fade in time (frames). Defines how long the fading animation will be. audio_out 6 keep Audio fade out time (frames). Defines how long the fading animation will be.

GPO_active 0 keep Activating GPO commands for tally lights (hardcuts within switcher scene only). The switcher scene does support sending a GPO during a fullscreen switch. Therefore a GPI/O board needs to be installed within the Viz Engine. The pin for the first source (Live 1) needs to be defined in the configuration file. GPO bits follow the order starting from Live 1 to 8, Clip 1 to 4 and Stream input. GPO triggering is only supported for switches within the switcher scene itself. Any use of video sources in another layer does not get recognized and a "high" will stay on the currently active video source within the back layer.

GPO 0 keep First GPO bit. Defines on what pin on the board LIVE1 is defined. All other sources follow. transition_ 35 keep Time (in frames) the crossfade between sources should take. time

Field Value If Description Field Exist s effects 12 keep Amount of effect scenes for preloading. Scenes called "effect_x" will be loaded into memory for immediate playout in the front layer. Custom made effect scenes can be used to cover a switch between two sources. Therefore the switcher scene will automatically load a chosen effect scene into the front layer which will then trigger the switch at a defined point in its scene animation. Preloading those scenes is essential which will be done by the switcher script automatically. The amount of effects scenes needed to be preloaded needs to be defined in the configuration file. The maximum amount is set to 99, having a high number of effects scenes will also result in having longer preloading times. transition_ 6100 keep Port number of local transition engine (for dual instance setup port with clean or dirty channel). program_on_ 0 keep Clip gets set to program as soon as it's loaded cue program_on_ 0 keep Clip gets set to program as soon as a play command is sent play opus_live 0 keep Live switching enabled (all textures sources are set to active). This will deactivate the automatic source deactivation in TEXTURE mode ext_prev_ac 0 keep Preview mirror: The switcher scene can forward any incoming tive preview commands directly to another engine for creating a separate preview channel. The second engine needs to have the switcher scene loaded which gets configured to set incoming preview commands to program. This feature needs to be activated via the configuration file. ext_prev_ho localh keep " st ost ext_prev_po 6100 keep " rt

Field Value If Description Field Exist s

ext_prev_ac 0 keep Program mirror: Similar to the external preview feature, the tive switcher scene can forward its program commands to another switcher scene on a separate instance in the network. The result will be having the same output on two different engines at the same time. Like the external preview, this feature needs to be activated specifically.

ext_prev_ho localh keep " st ost

ext_pro_por 6100 keep " t

dummy_sourc DUMMY keep Using this variable as crosspoint within AV Automation will e force the scene to make a switch. This can be used to switch between live sources or clips and fullscreen graphic elements.

show_comman 1 keep In case of experiencing issues with the switcher scene, it can be ds set to debugging mode which will print advanced information on every switch to the console. This information can be essential for finding the cause of the issue and a proper solution.

chroma_key (none) keep Turning on chroma key on inputs

6.2.10 C:\ProgramData\Vizrt\viz3\-1-0.cfg: This file contains the basic configuration of the Viz Engine for single instance setup.

Viz Opus specific auto-configured fields defining the selected encoding

Field Value (PAL) Value (NTSC) If Field Description Exists

output_syst 1080I_5000_SMPTE274 1080I_5994_SMPTE274 overwrite Output format em

cutout_widt 720 640 overwrite Resolution width h

cutout_heig 576 486 overwrite Resolution height ht

cutout_syst 576I_5000_SMPTE259_ 480I_5994_SMPTE259_N overwrite Output format em PAL TSC

Common Viz Opus auto-configured fields

Field Valu If Description e Field Exists

SECTION VIDEO

live_system1 HD108 overwr Enables video input 1 0i ite

live_system2 HD108 overwr Enables video input 2 0i ite

live_system3 HD108 overwr Enables video input 3 0i ite

live_system4 HD108 overwr Enables video input 4 0i ite

live_system5 INACT overwr Enables video input 5 IVE ite

live_system6 INACT overwr Enables video input 6 IVE ite

live_system7 INACT overwr Enables video input 7 IVE ite

live_system8 INACT overwr Enables video input 8 IVE ite

clip_system1 HD108 overwr Enables clip channels 1 0i ite

clip_system2 HD108 overwr Enables clip channels 2 0i ite

clip_data_directo D:/ overwr Where the clip files are stored ry Clips ite /

Ringbuffer-Size 3 overwr Number of ring buffer frames ite

enable_media_prev 1 overwr Enable Multiview/Media Preview feature. Disabled by iew ite default.

media_preview_aff 1 overwr Setting appropriate GPU to execute Multiview/Media inity_gpu ite Preview

Field Valu If Description e Field Exists media_preview_upd 8 overwr Set the update frequency for Multiview/Media Preview. ate_freq ite video_use_watchdo 1 overwr video_use_watchdog: Default=0. Allows live input 1 to be g ite passed to the Matrox output in case of engine crash. use_gpu_direct 0 overwr GPU Direct (for NVIDIA Quadro Cards DMA transfers). ite Increases performance if activated. Might interfere the engines behavior if media preview feature is in use.

SECTION COMMUNICATION service 6100 overwr TCP port to listen to. ite max_commands_pe 10 overwr Limits the commands processed in one field. Improves r_field ite behavior for TL scenes in Main Layer.

SECTION RENDER_OPTIONS create_default_re 1 overwr Create renderer even if there is no Viz Engine or Viz nderer ite Artist GUI rgb_2_yuv 0 overwr RGB to YUV conversion (0: Matrox, 1: Shader). Increases ite performance for frame accurate output. See Frame Accurate Output Configuration

SECTION MEMORY_MANAGE MENT

TextureAutoFree 0 overwr Turning off the automatic deletion of unused textures ite and fonts will avoid having to reload them again on air if needed

ImageAutoFree 0 overwr " ite

FontAutoFree 0 overwr " ite

GeomAutoFree 0 overwr Must be turned off. ite

PreloadTextures 1 overwr Preloading textures is needed when working with MSE ite playlists (initializing is mandatory)

Field Valu If Description e Field Exists

SECTION AUDIO_CONFIG

#AudioDevice1 Line - auto setup with Yamaha installed (disabled) (Yama ha 01V96 i)

#VIZChannelDevice Line - auto setup with Yamaha installed (disabled) 0 (Yama ha 01V96 i)

ChannelConfigurat 16 overwr ionChannels0 ite

ChannelRouteClip0 0 overwr _0 ite

ChannelRouteClip1 2 overwr _0 ite

ChannelRouteClip0 1 overwr _1 ite

ChannelRouteClip1 3 overwr _1 ite

MatroxAudioMode 1 overwr Audio output via video board. ite 1: MP3_MATROX_AES

SECTION CHANNELS_CONFIG

ClipIn1.AudioDela 2 overwr yDVE ite

ClipIn1.AudioDela 3 overwr yTexture ite

ClipIn2.AudioDela 2 overwr yDVE ite

ClipIn2.AudioDela 3 overwr yTexture ite

Field Valu If Description e Field Exists

ClipIn3.AudioDela 2 overwr yDVE ite

ClipIn3.AudioDela 3 overwr yTexture ite

ClipIn4.AudioDela 2 overwr yDVE ite

ClipIn4.AudioDela 3 overwr yTexture ite

SECTION DATABASE

AutoLogin 1 overwr Enable auto-login ite The audio delay settings for the live sources differ depending on the used output format. • Load the correct profile via the viz engines configuration UI fitting the used hardware, output format and frequency to set the right audio settings. • e.g.: video-resolution-1080i50-audio-xmio3.cfg All the profiles are located in C:\Program Files\vizrt\Viz3\Configuration Profiles

6.2.11 C:\Manus\OpusDemoRundown.xml: This provides the default Demo rundown file that is supplied with Viz Opus and works with the default template set and scenes. This file will be imported manually in Showmaker on the first load to import it into Media Sequencer as a proper Viz Mosart/Showmaker playlist. This file does not require any special handling and will be overwritten by the Opus Configuration without any special considerations. Using this file is optional for the user, but can be used as an aid for problem solving or bootstrapping.

6.2.12 %ProgramData%\vizrt\Media Service\config.json: This file contains the configuration for the Media Service.

Property Value If Field Description Exists

ClipFolderPath D:\Clips overwrite The default location for Opus video clips

Port 21099 keep

Property Value If Field Description Exists

SecurePort 21443 keep

TcpPort 21100 keep

VideoFileTypes .mxf keep .avi .mov .dv

ImageFileTypes .png keep .jpg .jpeg .tif .tiff .bmp .tga

UploadSubPath upload keep

RecordingSubPath recording keep

OutputPath D:\AuxMediaStore\ keep

CoderMasterServiceDocum http://localhost: keep entUrl 8081/

Encoder NVENC keep

ProxyAspectRatio Fixed keep

ExternalBaseUrl keep

LogLevel Debug keep

EnableTrace false keep

7 Viz Opus Clean Feed Setup Configuring clean feed for Opus systems is achieved by running two Viz Engine instances (similar to dual channel config), but where one of the instances are running an input channel in zero-frame delay mode using the video output of the second instances as video input. This means that one input gets lost, and seven SDI inputs will remain. For setting up the clean and dirty feed workflow the configuration files need to be adapted. Both engines will run on the same GPU which will be defined by the configuration files name.

• Engine 1 - clean feed - -1-0.cfg • Engine 2 - dirty feed - -3-0.cfg

7.1 Hardware Configuration Description of the video routing can be found in the Viz Opus Administrator Guide.

7.2 Software Configuration 1. Configure the engine in dual channel mode. It can still be installed as a single engine, but need to configure the shortcuts and adjust the Viz Config. 2. For default configuration of a dual channel, load the dual channel profiles for Channel 1 (Clean) and 2 (dirty). This will set the correct Ports. C:\Program Files\vizrt\Viz3\Configuration Profiles • dualchannel-0.cfg • dualchannel-1.cfg 3. Load the correct audio profile on both channels via the configuration tool C:\Program Files\vizrt\Viz3\Configuration Profiles • video-resolution-1080i50-audio-xmio3.cfg

7.3 Clean Feed Configuration Configure Program and Contains Alpha to Inactive. See Video out documentation to configure the program output of the engine to output program (fill) on VideoOutB and VideoOutD assigned by setting the Map to Viz channel t for reference. Configure the video inputs. Start by disabling video 1 by setting VideoInA to Unused. Set all other to the corresponding Video number, ie. VideoInB to Video2, VideoInC to Video3 etc.

Changes should be done via the configuration tool and will be stored in -1-0.cfg. The clean feed configuration should be based on the file provided by the bundle installer. Video (Matrox board configuration) Mapping Live Outputs • Set Out B and Out D to Program • Set Out A and Out C to Unused

• set In A to unused Mapping Live Inputs • In A to unused • In B set to Live 1 • In C set to Live 2 • ... • In H to Live 7 Activate Live 1 to Live 7 in Input config Audio • Audio Mode is set to AES • AES audio routing for clips needs to be done directly in the config file • Default settings for 2 separate audio channels ChannelRouteClip0_0 0

ChannelRouteClip1_0 2

ChannelRouteClip0_1 1

ChannelRouteClip1_1 3

More information can be found in the Viz Opus Configuration Files section.

7.4 Dirty Feed Configuration Configure the program output of the engine to output program (fill) on VideoOutA assigned by setting the Map to Viz channel to Program and Contains Alpha to active. See the Video out documentation for reference. Configure the video inputs by setting all of them to Unused. If not already set by the preloaded dual channel profiles, set communication General communication port on this engine to 6800.

Changes should be done via the configuration tool and will be stored in -3-0.cfg. Video (Matrox board configuration) Mapping Live Outputs • Set Out A to Program • Set Out B, Out C and Out D to Unused Mapping Live Inputs • Set all Inputs to Unused Audio • Audio on the dirty feed is not supported by default • routing of the AES channels needs to be done manually in the engines configuration file

Additional settings • turn on Zero Frame Delay option

7.5 Modifying The Dual Channel Shortcuts For Media Preview to work in Opus the clean feed instance needs to run in console mode (no VizArtist). Configure the desktop shortcuts properly by adding parameters: • -x (no UI, mandatory) • -u2 or u4 depending on the graphics board used, • -u2 points to the first engine on the second GPU (P6000) • -u4 points to the second engine on the second GPU • -n for engine mode • -c config mode • -u2 or -u4 for config shortcut of engine 1 or 2

8 Viz Opus Graphics Scene - Advanced This page will detail some advanced topics related to Viz scenes within Viz Opus workflows. It contains the following topics: • Opus Viz Scenes Communication

8.1 Opus Viz Scenes Communication Communication between the graphics scenes in an Opus production is done in a unique way. The Opus system will communicate with the different layers, at different occasions (depending on the tasks to be achieved) whether it is a media-related command, a graphics taken to air, or a transition effect. The communication is done via different modules of the Opus system (MMOverLayGraphicsInterface, MMAVAutomation, Media Admin, etc). When reaching the Viz Engine scenes, there is also internal communication between the scenes in the different viz layers.

8.1.1 Transition Effects Switcher Scene receives from Opus the command to load the Effect scene, and will send a command to load the relevant effect scene to the front layer and start its animation (function Load_transition_scene). A defined keyframe within the Effect scene will trigger the switching of Sources in the switcher scene at the correct timing (keyframe Auto_trans_back).

8.1.2 DVE Effects (Butterfly, 3Box, media windows) The "window" elements that should hold Media sources, have a script attached to them. The script "listens" to the shared memory, to an entry with the name of that element, in order to know when and to which Media source it should switch to. The switcher scene will update that shared-memory entry (shmem) according to commands received from Opus. The name of the entry will always be windowX ( window1, window2..) and should match the name of the container in the DVE scene.

8.1.3 Diagram The following diagram shows the communication lines described above

 Info: For more information, see the Opus scene design guidelines.