Avid® Maestro | News Installation and Configuration Guide V2019.2

Avid® Maestro | News Installation and Configuration Guide Version 2019.2 Legal Notices Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement.

This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.

This document is protected under copyright law. An authorized licensee of may reproduce this publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for . Reasonable care has been taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without notice.

The following disclaimer is required by Apple Computer, Inc.: APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THIS PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.

Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The following disclaimer is required by the Independent JPEG Group: This software is based in part on the work of the Independent JPEG Group.

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.

Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.

This product includes software developed by the University of California, Berkeley and its contributors.

The following disclaimer is required by Nexidia Inc.: © 2010 Nexidia Inc. All rights reserved, worldwide. Nexidia and the Nexidia logo are trademarks of Nexidia Inc. All other trademarks are the property of their respective owners. All Nexidia materials regardless of form, including without limitation, software applications, documentation and any other information relating to Nexidia Inc., and its products and services are the exclusive property of Nexidia Inc. or its licensors. The Nexidia products and services described in these materials may be covered by Nexidia's United States patents: 7,231,351; 7,263,484; 7,313,521; 7,324,939; 7,406,415, 7,475,065; 7,487,086 and/or other patents pending and may be manufactured under license from the Georgia Tech Research Corporation USA.

The following disclaimer is required by Paradigm Matrix: Portions of this software licensed from Paradigm Matrix.

The following disclaimer is required by Ray Sauers Associates, Inc.: “Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages.

The following disclaimer is required by Videomedia, Inc.: “Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with respect to its merchantability or its fitness for any particular purpose.”

“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by Videomedia, Inc. and V- LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players and the like.”

The following disclaimer is required by Ultimatte Corporation: Certain real-time compositing capabilities are provided under a license of such technology from Ultimatte Corporation and are subject to copyright protection.

The following disclaimer is required by 3Prong.com Inc.: Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.

The following disclaimer is required by Interplay Entertainment Corp.: The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.

This product includes portions of the Alloy Look & Feel software from Incors GmbH.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product may include the JCifs library, for which the following notice applies: JCifs © Copyright 2004, The JCIFS Project, is licensed under LGPL (http://jcifs.samba.org/). See the LGPL.txt file in the Third Party Software directory on the installation CD.

Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in connection with Avid Interplay.

This product includes the Warlib library, for which the following notice applies: Copyright Jarle (jgaa) Aase 2000 - 2009

warlib is copyright Jarle (jgaa) Aase 2000 - 2009

The warlib C++ Library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 3.0 of the License, or (at your option) any later version.

The warlib C++ Library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

3 Attn. Government User(s). Restricted Rights Legend U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.

Trademarks 003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II, Assistant Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, Avid DS Assist Station, Avid Ignite, Avid Liquid, Avid Media Engine, Avid Media Processor, Avid MEDIArray, Avid Mojo, Avid Remote Response, Avid Unity, Avid Unity ISIS, Avid VideoRAID, AvidRAID, AvidShare, AVIDstripe, AVX, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, D-Command, D-Control, Deko, DekoCast, D- Fi, D-fx, Digi 002, Digi 003, DigiBase, Digidesign, Digidesign Audio Engine, Digidesign Development Partners, Digidesign Intelligent Noise Reduction, Digidesign TDM Bus, DigiLink, DigiMeter, DigiPanner, DigiProNet, DigiRack, DigiSerial, DigiSnake, DigiSystem, Digital Choreography, Digital Nonlinear Accelerator, DigiTest, DigiTranslator, DigiWear, DINR, DNxchange, Do More, DPP-1, D-Show, DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, Euphonix, EUCON, EveryPhase, Expander, ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase, FXDeko, HD Core, HD Process, HDpack, Home-to-Hollywood, HYBRID, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, InGame, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, iS9, iS18, iS23, iS36, ISIS, IsoSync, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MIDI I/O, Mix Rack, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, NewsVision, Nitris, NL3D, NLP, NSDOS, NSWIN, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Painterly Effects, Palladium, Personal Q, PET, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, QuickPunch, QuietDrive, Realtime Motion Synthesis, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, Reprise, Res Rocket Surfer, Reso, RetroLoop, Reverb One, ReVibe, Revolution, rS9, rS18, RTAS, Salesview, Sci-Fi, Scorch, ScriptSync, SecureProductionEnvironment, Serv|GT, Serv|LT, Shape-to-Shape, ShuttleCase, Sibelius, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, SubCap, Sundance, Sundance Digital, SurroundScope, Symphony, SYNC HD, SYNC I/O, Synchronic, SynchroScope, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, TimeLiner, Titansync, Titan, TL Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, tools for storytellers, Transit, TransJammer, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Video the Web Way, VideoRAID, VideoSPACE, VTEM, Work-N-Play, Xdeck, X-Form, Xmon and XPAND! are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

Footage Arizona Images — KNTV Production — Courtesy of Granite Broadcasting, Inc.,  Editor/Producer Bryan Foote. Canyonlands — Courtesy of the National Park Service/Department of the Interior. Ice Island — Courtesy of Kurtis Productions, Ltd. Tornados + Belle Isle footage — Courtesy of KWTV News 9. WCAU Fire Story — Courtesy of NBC-10, Philadelphia, PA. Women in Sports – Paragliding — Courtesy of Legendary Entertainment, Inc.

News material provided by WFTV Television Inc.

Avid Maestro | News Installation Guide v2019.2 • Created 4/8/19 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

4 Contents

Symbols and Conventions ...... 10 Chapter 1 Introduction ...... 11 Installation Prerequisites ...... 11 Components ...... 11 Component Groups...... 12 Machine Roles ...... 13 Applications within Components ...... 13 Documentation of the Components ...... 14 Chapter 2 Requirements ...... 15 Notes about Dependencies ...... 15 Licensing Server...... 15 Database Server ...... 15 Shared Data...... 15 Rendering Software ...... 16 Scene Creation Software ...... 16 Network Requirements...... 16 Firewall ...... 16 Antivirus ...... 17 Machine Requirements...... 18 Component Dependencies ...... 19 Components Prerequisites ...... 20 Maestro | News Supported Products ...... 21 Avid Software Products ...... 21 Third Party Software ...... 22 Automation Protocols...... 23 NRCS Systems Supported by MOS Plugins ...... 23 Support for Video Assets ...... 23 Chapter 3 Installing Components ...... 25 Planning the Deployment...... 25 Example Deployment Scenarios at Machine Roles Level ...... 25 Simple Playout Controlling...... 25 Integration with Assets, Production and Newsroom Management Systems ...... 26 NLE Scenario ...... 26 Example Deployment Scenarios at Components Level ...... 27 Minimal Scenario for the Maestro | News Controller...... 27 Controlling Playout on DVG ...... 27

5 Integration with Avid MediaCentral | Cloud UX ...... 28 HTML5 MOS Plugin integration with NRCS ...... 29 ActiveX MOS Plugin Integration with Avid MediaCentral | Newsroom Management . . . . 30 Controller MOS-aware Integration with Avid MediaCentral | Newsroom Management . . . 30 Controller MOS-less Integration with Avid | Newsroom Management ...... 31 Direct integration with Avid MediaCentral | Asset Management...... 31 Integration with Avid MediaCentral | Asset Management using MediaCentral | Cloud UX (REST Connection)...... 32 Integration with Avid MediaCentral | Production Management and Avid NEXIS ...... 33 MOS-less integration with Avid MediaCentral | Command ...... 34 Integration with Avid Media Composer ...... 35 Example of a More Complex Integration ...... 36 Notes About Deploying in a Windows Domain Environment ...... 36 Verifying and Applying Requirements ...... 37 Installing VideoEngine for Windows for Preview ...... 37 Installing VideoEngine for Windows for Maestro | News Render Server ...... 38 Notes for Installing VideoEngine for Linux...... 39 Installing Other Avid Components or Components From Other Vendors...... 40 Obtaining and Verifying Components ...... 40 Verifying the Integrity of the Installation Files ...... 40 Installing Maestro | News Components ...... 41 Generic Installation Process ...... 42 Additional Steps Required for Specific Components...... 46 Maestro | News Bus Services ...... 46 Maestro | News Controller ...... 49 Maestro | News IPM ...... 51 Maestro | News ENPS Plugin (32 and 64 bit)...... 52 Maestro | News GAM Access...... 53 Maestro | News iNews Plugin...... 54 Maestro | News iNews Simple Plugin...... 56 Maestro | News NLE...... 58 Maestro | News MOS28 Plugin...... 59 Maestro | News Page Browser (32 bit and 64 bit) ...... 61 Maestro | News Render Server ...... 63 Installing HTML5 MOS Plugin ...... 66 Configure Maestro | News Bus Services...... 66 Install the Maestro | News Bus Services Certificate ...... 67 Install HTTP Web Server for Proxy Support ...... 72 Configure HTTP Proxy...... 73 Example Configuration for Apache HTTPD 2.2: ...... 73

6 Unzip HTML5 MOS Plugin ...... 74 Test Your Installation ...... 74 Installing MediaCentral | Cloud UX Plugin ...... 74 Configuring Maestro Bus Services for Cloud UX ...... 75 Configuring Render Server for Cloud UX ...... 75 Integration with MediaCentral | Cloud UX Rundown App ...... 77 Notes About Running Installers ...... 77 Applying Licenses ...... 78 License Types...... 78 Licenses List...... 79 Checking Available Licenses ...... 81 Testing Your Installation ...... 82 Initial Configuration...... 82 Configuring DVG to Play Maestro | News Assets ...... 82 Using MediaCentral | Asset Management Assets on Maestro | News Pages ...... 83 Configuring MediaCentral | Asset Management Share Access on Playout or Journalist Station . 84 Configuring MAM File Transit using Maestro GMAM / MediaCentral | Asset Management . . . 88 Troubleshooting ...... 93 Known Problems...... 94 Configuring MediaCentral | Production Management and NEXIS Connection ...... 97 Checking MediaCentral | Production Management Configuration with MediaCentral | UX. 97 Configuration of the NEXIS Client Manager ...... 97 Checking status of Interplay Production Web Services ...... 99 Configuration of Local VideoEngine ...... 101 Verifying the Configuration in the Maestro | News Controller ...... 102 Configuring MOS-less Communication with MediaCentral | Newsroom Management ...... 103 Verifying MediaCentral | Newsroom Management WS API configuration...... 103 Configuring MediaCentral | Newsroom Management Web Services...... 104 Verifying the Connection from the Maestro | News Controller ...... 107 Configuring Maestro | News Render Server...... 109 Configuring Maestro | News Bus Services...... 113 Enabling the Services ...... 113 Verifying the Installation ...... 113 Accessing the Avid ACS Monitor Tool ...... 114 Configuring Maestro | News ActiveX MOS Plugins to Work in Octopus...... 114 Checking Prerequisites ...... 114 Configuring the ActiveX MOS Plugins ...... 115 Verifying the Configuration ...... 118 Configuring Maestro | News HTML5 MOS to Work in Octopus ...... 119 Checking Prerequisites ...... 119

7 Configuring the Maestro | News HTML5 MOS Plugin ...... 119 Verifying the Configuration ...... 120 Configuring Maestro | News ActiveX MOS Plugin to Work in AP ENPS ...... 121 Checking Prerequisites ...... 121 Configuring the Maestro | News ActiveX Plugin for AP ENPS...... 121 Verifying the Configuration ...... 122 Configuring Maestro | News HTML5 MOS to Work in AP ENPS ...... 124 Checking Prerequisites ...... 124 Configuring the Maestro | News HTML5 MOS Plugin ...... 124 Verifying the Configuration ...... 125 Configuring MOS Server and MOS-aware Communication with MediaCentral | Newsroom Manage- ment ...... 126 Configuring the MOS Server ...... 126 Configuring MediaCentral | Newsroom Management to Work with MOS Server ...... 128 Configuring ASF Graphics Device Service for MediaCentral | Command Integration...... 130 Configuring OradControl ...... 132 Chapter 4 Upgrading Components...... 134 Version Compatibility Matrix ...... 134 Installing Several Versions of Specified Component ...... 135 Migrating Maestro | News Asset Database ...... 136 Chapter 5 Maintenance ...... 137 Modifying the Installation ...... 137 Modifying the Installation ...... 137 Repairing the Installation ...... 138 Removing Components ...... 139 Notes...... 139 Logs and Crash Dumps ...... 140 Browsing Logs ...... 140 Crash Dumps ...... 141 Browsing Logs and Checking Issues in HTML Components ...... 141 Test Tools...... 142 Basic Example of the DB API Test Application Tool ...... 142 Basic Example Instruction of the CII Test Tool...... 143 Basic Example Instruction of the VDCP Test Tool ...... 144 Importing Content ...... 145 Recurring activities ...... 145 Cleaning the Maestro | News Render Server Database and Files...... 146 Cleaning the Maestro | News Controller Rundowns ...... 147 Backup databases ...... 147 Backup Shared data files ...... 148

8 Cleaning logs ...... 148 Backup Stations ...... 148 Other activities you should consider ...... 148 Troubleshooting ...... 148 Checking existing database version ...... 148 Checking the RenderServer Database Version...... 150 Changing Components Settings Manually ...... 151

9 Using This Guide

Symbols and Conventions

Avid documentation uses the following symbols and conventions:

Symbol or Convention Meaning or Action

A note provides important related information, reminders, n recommendations, and strong suggestions.

A caution means that a specific action you take could cause harm to c your computer or cause you to lose data.

A warning describes an action that could cause you physical harm. w Follow the guidelines in this document or on the unit itself when handling electrical equipment.

> This symbol indicates menu commands (and subcommands) in the order you select them. For example, File > Import means to open the File menu and then select the Import command.

This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.

(Windows), (Windows This text indicates that the information applies only to the specified only), (Macintosh), or operating system, either Windows or Macintosh OS X. (Macintosh only)

Bold font Bold font is primarily used in task instructions to identify user interface items and keyboard sequences.

Italic font Italic font is used to emphasize certain words and to indicate variables.

Courier Bold font Courier Bold font identifies text that you type.

Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the mouse action. For example, Command+Option+C or Ctrl+drag.

| (pipe character) The pipe character is used in some Avid product names, such as Interplay | Production. In this document, the pipe is used in product names when they are in headings or at their first use in text. 1 Introduction

Maestro | News is a universal controller for video and graphics that enables you to create, manage, distribute, and play out stunning, high-resolution 3D graphics and videos easily.

Topics in this chapter include: • Installation Prerequisites • Components

Installation Prerequisites

The purpose of this chapter is to guide the preparation of all materials needed for the Maestro | News installation.

Target Audience

The installation should be performed by experienced personnel or by Avid support team members.

Version

This Installation Guide is intended for Maestro | News version 2019.2.0.

Components

Full List of Components

MediaCentral | Maestro News (formerly MaestroUX) plugin for MediaCentral | UX is not supported n since Maestro | News v2018.11.

The Maestro | News Controller can be run in one of four (4) modes: • Standard Mode (Controller + PageEditor), • PageEditor Only, • FastServe | Playout Mode, • Preview Mode.

The running mode depends on command line arguments and the available licensing options.

Component Naming and Branding

Certain Avid products have been re-branded and received new names. When installing a Maestro | News system you can encounter the previous names of some components. The list below illustrates the most common examples: • Some components and their installers may use the “Maestro” alias instead of “Maestro | News” and the “Orad” vendor name instead of “Avid”. • MOS Server was previously named “Orad MOS Gateway 2". • Maestro Monitor was formerly named Maestro Restarter. • MOS Plugins can be called “News Producer Plugins” and the NLE Server can be called "MOS Producer NLE Plugin” in other documents.

Component Groups

Some components may be grouped in the following way:

Component Group Name Components

Controllers and editors Maestro | News Controller, Maestro | News Journalist Station

GAM Accessor Maestro | News GAM Access Plugin 32 bit, Maestro | News GAM Access Plugin 64 bit

Others Maestro | News Bus Services, Maestro | News HTML5 MOS Plugin, Maestro | News HTML5 Cloud UX Plugin, Maestro | News NLE

12 Machine Roles

The table below illustrates the machine roles for all Maestro | News components:

Machine Role Main Components and other Software

Maestro | News Server Maestro | News database, Shared Data, and other optional shared components, e.g.: Maestro | News Bus Services, Floating license server, Java Application Container with iNews Web Services, MOS Server

Rendering Server Maestro | News Render Server, Maestro | RenderEngine for Windows

Playout Station Maestro | News Controller, VideoEngine for Windows and Maestro | RenderEngine for Windows

Editing Station NLE software (e.g. Media Composer), Maestro | News NLE and Maestro | RenderEngine for Windows

Authoring Station Maestro | Designer and Maestro | News Controller with the license only for PageEditor, Maestro | RenderEngine for Windows

Journalist Station Maestro | News Journalist Station - or - NRCS client and one of Maestro | News MOS Plugins; VideoEngine for Windows and Maestro | RenderEngine for Windows

DVG HDVG, Blend, Maestro Media Engine, FastServe | Playout or Maestro | Engine

Applications within Components

Each component can consist of multiple applications. Some of them are redundant between components. The list below is not comprehensive as it only shows the most important applications:

Component Applications

Maestro | News Bus Services Asset Service, DataLink Service, MediaBrowser Service, Render Service, Maestro Monitor Service, Maestro Monitor GUI, Log Viewer

Maestro | News Controller Controller and Page Editor, Maestro Admin, Maestro Sync, Log Viewer, Maestro Monitor Service, Maestro Monitor GUI

Maestro | News ENPS Plugin ENPS MOS ActiveX Plugin 32 bit 32 bit

Maestro | News ENPS Plugin ENPS MOS ActiveX Plugin 64 bit 64 bit

Maestro | News GAM Access GAM Access ActiveX Plugin 32 bit, GAM Accessor Test Tool Plugin 32 bit

Maestro | News GAM Access GAM Access ActiveX Plugin 64 bit, GAM Accessor Test Tool Plugin 64 bit

Maestro | News iNews Plugin iNews MOS ActiveX Plugin

Maestro | News iNews iNews Simple MOS ActiveX Plugin Simple Plugin

Maestro | News IPM Maestro IPM Server

13 Component Applications

Maestro | News Journalist Journalist Station, Log Viewer Station

Maestro | News MOS28 MOS 2.8 ActiveX Plugin Plugin

Maestro | News NLE NLE Server, NLE Plugin, Log Viewer

Maestro | News PageBrowser Page Browser ActiveX plugin 32 bit Plugin 32 bit

Maestro | News PageBrowser Page Browser ActiveX plugin 32 bit Plugin 64 bit

Maestro | News Render Render Server, Render Manager, DB API Test Application Tool Server

Maestro | News HTML5 HTML5 Cloud UX Plugin (as part of MediaCentral | Cloud UX™ 2019.2 Cloud UX Plugin feature pack)

MOS Server MOS Gateway Service, MOS Gateway GUI

OradControl OradControl Application

Maestro | News HTML5 HTML5 MOS Plugin MOS Plugin

Documentation of the Components

On the Avid Knowledge Base you can find the latest documentation for Maestro | News. The Maestro | News User Guide contains extensive information about the Maestro | News Controller and Maestro | News plugins, such as Journalist Station or NLE. You can find the latest Maestro | News documentation on the Avid Knowledge Base here:

http://avid.force.com/pkb/articles/user_guide/Maestro-Documentation

14 2 Requirements

Topics in this chapter include: • Notes about Dependencies • Network Requirements • Firewall • Machine Requirements • Component Dependencies • Components Prerequisites • Maestro | News Supported Products

Notes about Dependencies

Licensing Server

Most components require a licensing server (Avid Hasp Driver) to work. Also, be aware that other Avid components integrated with Maestro | News (especially VideoEngine and Maestro | RenderEngine) require their own licenses.

Database Server

Most components require a database (on the Microsoft SQL Server). Maestro | News works with the following databases: • Asset database (default name maestro_3) - contains Maestro | News assets (pages, items, rundowns etc.). • Render Server database (default name RenderServer) - contains Maestro | News Render Server data (rendering tasks etc.). •MOS Server database (default name CyberGraphics) - contains MOS Server data. • IBIS Database (only Maestro Bus Services component when Asset Service is running in REST mode).

Shared Data

Most components require Shared Data to work properly. Shared data is a folder (usually a Windows share on a remote machine) that contains scene files (from Maestro | Designer), clips, images and image sequences. This folder or share should be mapped as a G:\ drive on every Windows machine with Maestro | News components that requires access to the scenes, clips, etc. Although, you can use basic functionality of the components without this share, you should assume that the share is required by all components except for the MOS Server. For the MediaCentral | Mastro News component, the Shared Data should be a mapped as /Control_Data. Rendering Software

For the preview / playout purposes, video and graphics rendering software is required: VideoEngine, Maestro | RenderEngine or Maestro | Virtual Set (Unreal® Engine playout).

Scene Creation Software

The optional component is a scene creation software - Maestro | Designer. You can also use the Maestro | News plugin called SceneEdit to create your scenes.

Network Requirements

At least 1Gbps network connection should be provided between machines with Maestro | News components.

For network requirements of other components, please consult the appropriate documentation of these components.

Firewall

The below table shows firewall ports required for Maestro | News components.

Default Ports

Components Port(s) Description

Almost All 135-139 NetBIOS service, required for SMB file sharing.

445 SMB file sharing

1947 Connection to HASP License Manager

23456 Connection to license server

Controllers and editors, 1433-34 Connection to MS SQL server MOS plugins

8080 Connection to iNews Web Services

9500 Connection to ACS Bus (MediaCentral | UX) 2.7 and older, used only by old versions of Maestro | News

9900 Connection to ACS Bus (MediaCentral | UX) 2.8 or newer

9910 Connection to MediaCentral | Asset Management (formerly Interplay | MAM) Web Services over HTTP, affects MediaCentral | Asset Management version 5.9 or older

9911 Connection to MediaCentral | Asset Management Web Services over HTTPS, affects MediaCentral | Asset Management version 2017.1 (6.0) or newer

10001-10 Used by automation protocols

10002 Connection to local VideoEngine

10011-20 Connection to remote VideoEngine (using OCIP protocol)

16 Default Ports

Components Port(s) Description

15001-10 Streamed preview from VideoEngine

MOS Server 5002

6001-600x Communication with clients (e.g. Maestro | News Controller)

7101 Communication between service and GUI

10540- Lower and upper communication port with iNews MOS Gateway 10541

NLE 2310 Used by NLE protocol

OradControl 20002 Default port for connecting OradControl to Maestro | News Controller

HTML5 MOS Plugin 9030 Connection between HTML5 MOS Plugin and Maestro | News Bus Services running in REST mode

External components 8000 ACS Monitor web (MediaCentral | UX)

8080 VideoEngine Web Control Panel

8735-55 ReTalk2 (for Maestro | RenderEngine)

8745 ReTalkXML (for Maestro | RenderEngine)

8765-85 ReTalk3 (for Maestro | RenderEngine)

9901 MediaCentral | Asset Management Administrator web and Desktop web

9911 MediaCentral | Asset Management Control Center web

Most of components (both Maestro | News components and other components) can be reconfigured to use other port numbers.

To check what component is currently using the specified port, type: •on Windows: netstat -ano | findstr ":" (e.g.: netstat -ano | findstr ":8080"). The command returns the display protocol, source and destination; the last number is a PID of the process that is using the port. •on Linux: netstat -tulpn | grep (e.g. netstat -tulpn | grep 8080) The command returns the display protocol, source and destination, etc.; the last column is the name of the process that is using port.

Antivirus

Antivirus software may prevent some applications from running or block some ports. Make sure that you have added the required exceptions in your antivirus software. For more information, refer to your antivirus documentation.

17 Machine Requirements

The table below shows the hardware requirements for Maestro | News machines.

Machine Role Minimal Recommended

Maestro | News Single machine (single node): Redundant two nodes, each node specification: Server • Operating system: Windows server 2012 • Operating system: Windows Server 2016 • Processor: Dual Xeon e5 processor • Processor: Dual Xeon e5 processor • Memory: 32GB RAM • Memory: 32GB RAM • Disk: 500GB SSD System disk • Disk: 500GB SSD System disk • Network: 2x Gigabit Ethernet interfaces • Disk: Redundant RAID with 8TB of effective storage (note: only on one of the nodes) • Other: 2 free USB ports • Network: 2x Gigabit Ethernet interfaces • Power: Dual power supply • Other: 2 free USB ports • Additional software: MSSQL Standard Edition (with the right license dimensioning • Power: Dual power supply for the project) version 2012 • Additional software: MSSQL Standard Edition (with the right license dimensioning for the project) version 2016 These 2 nodes should share a storage cabinet (normally using FC) with at least 8TB of effective storage

Rendering • Operating system: Windows 10 • Operating system: Windows 7 64 bit SP1 Server • Processor: 6th generation Core i7 or Xeon • Processor: 6th generation Core i7 or Xeon with 4 cores (8 threads) with more than 4 cores (more than 8 threads) • Memory: 16 GB RAM • Memory: 24 GB RAM or more • Graphics card: GeForce GTX 1060 4GB • Graphics card: GeForce GTX 1070 8GB RAM or Quadro P2000 RAM or Quadro P4000 • HDD 7200 RPM, 512 GB • SSD 512 GB

Playout Station • Operating system: Windows 10 • Operating system: Windows 10 • Processor: Intel Core i5 6th generation • Processor: Intel Core i7 7th generation or comparable Xeon CPU • Memory: 16 GB RAM n The amount of required RAM depends on the • Memory: 16 GB RAM or more rundown size and the complexity of rundown items. • Disk: 500 GB SSD In general, you can assume that additional 4 GB of RAM is required for every 1000 items on your • Display: 24" 1920x1080 resolution capable opened rundown. monitor • Disk: 500 GB on 7200 RPM HDD • Peripherals: USB keyboard and mouse • Display: 21" 1920x1080 resolution capable • Graphics card: GeForce GTX 1070 8GB monitor RAM or Quadro P4000 • Peripherals: USB keyboard and mouse • Graphics card: GeForce GTX 1060 4GB RAM or Quadro P2000

18 Since the machines above also use additional components besides Maestro | News (e.g.: VideoEngine, Maestro | RenderEngine, NRCS clients), check the current requirements of these components in their respective documentation.

Component Dependencies

The table below illustrates the dependencies between Maestro | News components.

Dependencies

Components or Component Group Required Optional

Controllers and editors, • Avid HASP Driver • VideoEngine for Windows MOS plugins • MS SQL Database (see Maestro | News • Maestro | RenderEngine for Windows database) • Maestro | VirtualSet and Unreal Engine • Shared data These components are optional, but highly recommended in order to use basic important features, such as preview.

Maestro | News Bus • Maestro | News database n/a Services • Maestro | News RenderServer (only Client components)

Maestro | News GAM n/a n/a Access

Maestro | News NLE • Avid HASP Driver n/a • Maestro | News database • Maestro | RenderEngine for Windows • Media Composer or Adobe Premiere Pro or other supported NLE system

Maestro | News Render • Maestro | News database n/a Server • Maestro | News Render Server database • Maestro | RenderEngine for Windows • VideoEngine for Windows

HTML5 Cloud UX • MediaCentral | Cloud UX • Maestro | News Render Server Plugin

MOS Server • Maestro | News MOS database n/a

OradControl • Maestro | News Controller n/a

Maestro | News • MediaCentral | Cloud UX • Maestro | News Render Server HTML5 MOS Plugin • Maestro | News Bus Services • Avid HASP Driver • HTTP server that supports proxy

19 Components Prerequisites

The table below lists external prerequisites for Maestro | News components.

Component(s) Prerequisites

Maestro | News Bus Services • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) • Microsoft Visual C++ Runtime 14.0 (includes ATL and MFC) (x64) • Microsoft SQL Command Line Utilities 11 for SQL Server • Microsoft Office 2010 System Driver (x64)

Maestro | News Controller • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x86) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x64) • Microsoft Visual C++ Runtime 14.0 (includes ATL and MFC) (x64) • Microsoft SQL ODBC Driver 11 for SQL Server • Microsoft SQL Command Line Utilities 11 for SQL Server • Microsoft SQL Server 2012 Native Client • Microsoft SQL Local DB 12 for SQL Server (x64)

Maestro | News ENPS Plugin 32 bit • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) Maestro | News GAM Access Plugin 32 bit • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) Maestro | News iNews Plugin • Microsoft Visual C++ Runtime 14.0 (includes ATL and MFC) (x86) Maestro | News iNews Simple Plugin Maestro | News MOS28 Plugin Maestro | News PageBrowser Plugin 32 bit

Maestro | News ENPS Plugin 64 bit • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) Maestro | News GAM Access Plugin 64 bit • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x86) Maestro | News IPM • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x64) Maestro | News Journalist Station • Microsoft Visual C++ Runtime 14.0 (includes ATL and MFC) (x64) Maestro | News PageBrowser Plugin 64 bit Maestro | News NLE

20 Component(s) Prerequisites

Maestro | News Render Server • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x86) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x64) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x64) • Microsoft SQL Command Line Utilities 11 for SQL Server • Microsoft Visual C++ Runtime 14.0 (includes ATL and MFC) (x64)

Maestro | News HTML5 Cloud UX none Plugin

MOS Server • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x86) • Microsoft Visual C++ Runtime 10.0 (includes ATL and MFC) (x64)

OradControl none

Maestro | News HTML5 MOS Plugin none

Maestro | News Supported Products

Avid Software Products

For configurations with Avid software, Maestro | News is supported with the minimum version of the following products:

Avid Software Product Supported Software Versions

Avid Maestro | RenderEngine 2018.12

Avid Maestro | Designer 2018.12

Avid Automation Protocols

Avid VideoEngine for Windows 2019.1

Avid VideoEngine for Linux 2019.1

Avid Maestro | Virtual Set 2019.1 (uses Unreal Engine 4.20)

Avid MediaCentral | Cloud UX 2019.2

Avid MediaCentral | Asset Management (formerly 6.1 (2017.2), 2018.6, 2018.9, 2018.11 Avid Interplay | MAM)

Avid MediaCentral | Graphics Management (formerly 2018.11 Maestro GMAM)

Avid MediaCentral | Production Management 3.8, 4.0 (2017.2) (formerly Avid Interplay | Production)

21 Avid Software Product Supported Software Versions

Avid MediaCentral | Newsroom Management 7.0 (2018.6), 7.1 (2018.9), 7.2 (2018.11) (formerly Avid iNews)

Avid MediaCentral | Command (formerly Avid iNews 3.9 (2018.6), 3.11 (2018.11) Command)

Avid Media Composer 8.7

Notes: • Avid MediaCentral | UX is not supported in this Maestro | News release.

Third Party Software

Maestro | News 2019.2.0 supports integration with the following external components (this list is not complete):

Software Supported Version

AP ENPS 8.2

Octopus Newsroom 8.0

Annova OpenMedia 4.3

Adobe Premiere 11

Maestro | News 2019.2.0 could support but it has not been comprehensively tested against integration with the following external components:

Category Software

Newsroom Computer Systems Dalet+, Snews Anews, LifeNews, NorCom NC Power, Sobey, Dayang (NRCS)

Non-Linear Editing Systems (NLE) Newscutter, Quantel qEdit, GV Aurora, EVS Xedio, Sony SONAPS (Sony XPRINS), Sobey, Apple Final Cut

Studio automation Ross OverDrive, Vis Mosart, Sony ELC, Aveco ASTRA Studio, Grass Valley Ignite, Dalet Playout

MCR automation Imagine Communications (formerly Harris Broadcast), Snell Advanced Media, SGT, Aveco ASTRA, and Pebble Beach Systems

Traffic MediaGeniX and PROVYS

22 Automation Protocols

The below table lists the automation protocols supported by Maestro | News.

Protocols Supported (Yes / No)

Chyron Intelligent Interface yes (CII)

OradControl yes

3DPlay (for Maestro | Live yes and Maestro | TX)

Harris VDCP yes

ControlAir no (not supported since Maestro | News 7.2)

Sony no (not supported since Maestro | News 7.2)

NRCS Systems Supported by MOS Plugins

The below table lists the NRCS systems that are currently supported by the MOS plugins.

Supported MOS Protocol Protocols NRCSes Version

Maestro | News iNews Plugin Avid MediaCentral | Newsroom Management, 2.6 Octopus

Maestro | News iNews Simple Avid MediaCentral | Newsroom Management 2.6 Plugin

Maestro | News ENPS Plugin (32 bit AP ENPS (for version <= 6), Dalet, Sobey, Dayang, 2.6 and 64 bit) NorCom NC Power

Maestro MOS28 Plugin Annova OpenMedia, AP ENPS (for version >=7), 2.6, 2.8 Snews Anews

Maestro | News HTML5 MOS Annova NMS, Octopus, AP ENPS 2.8 Plugin

Support for Video Assets

Video Asset Sources

Video Asset on Graphic Item Video Asset as Video Item

Source Image Media Image Control Clip Control Control Image Sequence Clip

File system (G: drive / yes yes yes yes yes yes Control_Data)

VideoEngine database no no no yes no yes

23 Video Asset on Graphic Item Video Asset as Video Item

Source Image Media Image Control Clip Control Control Image Sequence Clip

MediaCentral | Asset yes yes yes yes no yes Management

MediaCentral | no no no no no yes Production Management

Video Asset Playout Engines

Video Asset on Graphic Item Place Image / Clip Control Media Control Video Asset as Video Item

Preview in the Controller Media Player VideoEngine n/a file selector

Browser panel in the n/a n/a VideoEngine Controller

Playout on Windows Media Player (not VideoEngine (in VideoEngine officially supported) Maestro | RenderEngine)

Playout on Linux Media Player VideoEngine (in VideoEngine (HDVG2,FSP) Maestro | RenderEngine)

Rendering in Render Media Player (not not supported yet not supported Server on Windows officially supported)

Rendering in NLE on Media Player (not not supported yet not supported Windows officially supported)

24 3 Installing Components

Topics in this chapter include: • Planning the Deployment • Verifying and Applying Requirements • Obtaining and Verifying Components • Installing Maestro | News Components • Applying Licenses • Testing Your Installation • Initial Configuration

Planning the Deployment

The deployment scenario highly depends on the customer needs, workflows and components used. This chapter shows only a few examples of simple deployment scenarios. Before reviewing the diagrams, see the Machine Roles chapter to understand what components are installed on which machine.

Customer environments are usually much more complex than shown below, so carefully plan your deployment.

Example Deployment Scenarios at Machine Roles Level

Simple Playout Controlling

Contains Maestro | News Server (with asset database and Shared Data), Playout station with Maestro | News Controller and several DVGs controlled by Maestro | News Controller. Integration with Assets, Production and Newsroom Management Systems

Integration with MediaCentral | Production Management, NEXIS, MediaCentral | Asset Management / MediaCentral | Graphics Management and MediaCentral | Newsroom Management.

The MediaCentral | Cloud UX server is required for integration between the Maestro | News Controller (on the Playout Station) and MediaCentral | Production Management. The Maestro | News Controller can use assets from MediaCentral | Production Management and MediaCentral | Asset Management. The Controller can also import and synchronize rundowns from MediaCentral | Newsroom Management (for MOS-less connection, the Maestro | News Server should have iNews Web Services deployed, otherwise - in a MOS-aware scenario - additional iNews MOS Gateway server is required and the MOS Server on the Maestro | News Server).

NLE Scenario

This scenario contains the Authoring station (with Maestro | Designer and Maestro | News PageEditor), Editing Station (with NLE software such Avid Media Composer with Maestro | NLE and Maestro | RenderEngine), Maestro | News Server (with Maestro database and Shared Data) and the optional DVGs.

26 Example Deployment Scenarios at Components Level

Minimal Scenario for the Maestro | News Controller

For the minimal deployment scenario of the Maestro | News Controller, the following additional components are required: MS SQL Server (for Maestro | News asset database), HASP Driver (for obtaining the license). Optional (but highly recommended) components are: Maestro | RenderEngine for Windows (for graphic items preview), VideoEngine (for video items preview, for support of video embedded on graphics items), Shared Data. All these components can be installed on a single machine.

Controlling Playout on DVG

When expanding your environment, moving Shared Data and Maestro | News database to a separate, dedicated server is the best option. Especially, when you want to use many Playout Stations, Editing Stations, Authoring Stations or Journalist Stations.

27 Integration with Avid MediaCentral | Cloud UX

28 HTML5 MOS Plugin integration with NRCS

29 ActiveX MOS Plugin Integration with Avid MediaCentral | Newsroom Management

Controller MOS-aware Integration with Avid MediaCentral | Newsroom Management

MOS-aware integration with MediaCentral | Newsroom Management requires the MOS Server to provide functionality of rundown synchronization with MediaCentral | Newsroom Management in the Maestro | News Controller.

30 Controller MOS-less Integration with Avid | Newsroom Management

MOS-less integration with MediaCentral | Newsroom Management requires the iNews Web Services to be deployed on the Java Application Container.

Direct integration with Avid MediaCentral | Asset Management

Integration with MediaCentral | Asset Management requires access to the Media assets data share from the Playout Station.

This connection type is not recommended and will be removed in future versions. Please use the REST connection type (using MediaCentral | Cloud UX) instead.

31 Integration with Avid MediaCentral | Asset Management using MediaCentral | Cloud UX (REST Connection)

Integration with MediaCentral | Asset Management requires access to the Media assets data share from the Playout Station.

32 Integration with Avid MediaCentral | Production Management and Avid NEXIS

Integration with MediaCentral | Production Management and NEXIS requires installation of NEXIS on the Playout Station, on the MediaCentral | UX Server and on the MediaCentral | Production Management Server.

Additionally, the MediaCentral | Production Connectivity Toolkit (PAMCTC) must be installed on the MediaCentral | UX Server and MediaCentral | Production Management Web Services must be installed on the MediaCentral | Production Management Server.

33 MOS-less integration with Avid MediaCentral | Command

The scenario below assumes that the Maestro | News Controller uses MOS-less connection to MediaCentral | Newsroom Management.

The MOS-aware (with MOS Server) scenario is also possible.

34 Integration with Avid Media Composer

35 Example of a More Complex Integration

This scenario includes a MOS-less integration of the Controller and the MOS Plugin with MediaCentral | Newsroom Management, integration with MediaCentral | Asset Management and MediaCentral | Production Management, as well as playout on FastServe | Playout.

Notes About Deploying in a Windows Domain Environment

If you plan to use Windows authentication for the Maestro | News components in a Windows Domain environment, please be aware that the Maestro | News Server (especially MS SQL database with Maestro | News databases) must be joined into the same domain as the machines with Maestro | News software (such as Maestro | News Controller).

36 Verifying and Applying Requirements

Before installing any component, verify the hardware and software requirements. Make sure you have installed the required dependencies and prerequisites.

Installing VideoEngine for Windows for Preview

When installing VideoEngine for Windows for preview purposes, make sure to select the “Maestro” profile. Default settings for this profile are shown below:

The following VideoEngine channels are used for preview:

Channel Preview Type

OUT1 Maestro | News Controller - video item preview in Browser panel

OUT2 Maestro | News iNews Plugin - video item preview

OUT3 Maestro | News Controller - clip preview in Media Selector dialog box

OUT4 Maestro | News iNews Plugin - clip preview in Media Selector dialog box

37 Installing VideoEngine for Windows for Maestro | News Render Server

When installing VideoEngine for Windows to use with Maestro | News Render Server, choose the “RenderServer” profile. Default settings for this profile are shown below:

38 Notes for Installing VideoEngine for Linux

When using both the VideoEngine and Maestro | RenderEngine on a DVG machine, select the SMIO Custom work mode to enable the VE-in-RE feature:

In this mode everything will be computed on the CPU, not on the DVG card.

In all other cases, select the DVG Maestro work mode:

In this mode, everything will be computed on the DVG card and the output can be grabbed from the DVG card out connector.

39 Installing Other Avid Components or Components From Other Vendors

To learn more about installing other Avid applications, refer to their respective documentation. Links are provided below:

Component Documentation

Avid MediaCentral | UX Avid MediaCentral Documentation

Avid MediaCentral | Avid iNews Documentation Newsroom Management

Avid MediaCentral | Asset Avid Interplay | MAM Documentation Management

Avid MediaCentral | Avid Interplay | Production Documentation Production Management

Avid MediaCentral | Avid iNews Command Documentation Command

Avid Media Composer Avid Media Composer Software 8.0 Documentation

Obtaining and Verifying Components

You can obtain Maestro | News installers from Avid in two forms: • With the Graphics Suite (contains also several other Avid components), • As separate installation packages.

Verifying the Integrity of the Installation Files

Installer files are shipped with additional MD5 checksum files. The checksum files have the same names as the installer files but have an appended md5 extension. Those files can be used to verify the integrity of the installer file.

The MD5 verifier tool is shipped with the Graphics Suite. You can also download the File Checksum Integrity Verifier directly from Microsoft and then copy the fciv.exe file to the location where files to be checked are stored.

To verify the MD5 checksum: 1. Open the Windows Command Prompt and change the current directory to the directory of the installer files. 2. Depending on the MD5 tool: t When using the bundled MD5 verifier, type: md5sum -c - as the result the installer file name should be displayed and the OK message. t When using the Microsoft File Checksum Integrity Verifier, type: fciv - as a result the MD5 hash and the installer file name should be displayed; then compare this MD5 hash with the one in the MD5 checksum file.

40 Installing Maestro | News Components

To run the installation process of the specified component, run the appropriate installer on the target Windows machine.

Component Installer File Name

Maestro | News Bus Services MaestroBusServices_2019_2_0_.exe

Maestro | News Controller Maestro64_2019_2_0_.exe

Maestro | News ENPS Plugin 32 bit MaestroENPSPlugin_2019_2_0_.exe

Maestro | News ENPS Plugin 64 bit MaestroENPSPlugin64_2019_2_0_.exe

Maestro | News GAM Access Plugin 32 bit MaestroGAMAccess_2019_2_0_.exe

Maestro | News GAM Access Plugin 64 bit MaestroGAMAccess64_2019_2_0_.exe

Maestro | News iNews Plugin MaestroINEWSPlugin_2019_2_0_.exe

Maestro | News iNews Simple Plugin MaestroINEWSSimplePlugin_2019_2_0_.exe

Maestro | News IPM MaestroIPM64_2019_2_0_.exe

Maestro | News Journalist Station JStation64_2019_2_0_.exe

Maestro | News MOS28 Plugin MaestroMOS28Plugin_2019_2_0_.exe

Maestro | News NLE MaestroNLE64_2019_2_0_.exe

Maestro | News PageBrowser Plugin 32 bit MaestroPageBrowserAx_2019_2_0_.exe

Maestro | News PageBrowser Plugin 64 bit MaestroPageBrowserAx64_2019_2_0_.exe

Maestro | News Render Server MaestroRenderServer64_2019_2_0_.exe

MOS Server MOSGateway2_2_0__.exe

41 Generic Installation Process

Generic Installation Process Steps: 1. If any of the prerequisites are missing, an appropriate message is displayed:

Cancel the installation and install the required prerequisites. An exception is allowed for the Microsoft SQL Local DB for SQL Server (x64) if you plan to use remote Maestro | News asset database instead of a local database. In this case click Next. An additional warning message appears:

Click OK to continue. 2. The “Welcome to Setup” window appears.

42 Click Next. 3. The “Setup Type” window appears:

In the “Setup Type” window, select the Typical option to install all program features and click Next. Select a different installation destination by going to the Custom Setup option.

43 4. For some installers (such as the MOS Plugin), there is an additional step which allows to select the type of application:

5. Further installation steps depend on the component you are currently installing. More information is provided in the following chapters of this document. 6. After selecting the necessary options for the component, the “Ready to Install” window appears where you can review the entered information. Click Next to continue.

44 7. The installation progress can be monitored in the following window:

8. When the installation is finished, the “Setup Complete” window appears. Click Finish to exit the installer.

45 Additional Steps Required for Specific Components

Maestro | News Bus Services

Maestro | News Bus Services includes the following applications: • Asset Access Service - Enables the Maestro | News HTML5 plugins (Maestro | News HTML5 MOS Plugin or Maestro | News HTML5 Cloud UX Plugin) to access the Maestro Database to browse for graphic assets. • Data Link Service - Provides access to data sources in the SQL database on the Maestro | News Server. These sources are used to populate graphics. • Media Browser Service - Provides access to Maestro | News assets (clips and images). • Render Service – Provides connection between Maestro | News HTML5 plugins and Maestro | News Render Server. • Maestro Monitor - A tool for controlling the above services.

46 Additional Installation Steps for Maestro Bus Services: 1. The “MaestroBusServices service type” is displayed.

If you plan to use MaestroBusServices with the Maestro | News HTML5 Cloud UX Plugin, then select the ACS BUS Services option and enter the following information: - ACS Gateway Host - Enter the IP address of the MediaCentral Platform Services server. If this is a cluster configuration, enter the IP address associated with the cluster (virtual IP address). - Port - Enter the port number used to communicate with the ACS Gateway. Port 9900 is typically used for this communication. If you plan to use MaestroBusServices with the Maestro | News HTML5 MOS Plugin, then select the REST Services option. Click Next to continue. 2. The “Access to MaestroAssets Database” window appears:

47 Enter the following information: - Server - Enter the IP address or host name of the server running the MSSQL Maestro | News Asset database, and the instance name of the database. Example: wavd-maestro01\maestro. - User - Enter the SQL user name to be used by the Maestro Bus Service to access the database. Example: sa - Password - Enter the password for the above user. - Name - Enter the name of the Maestro | News Asset database. Example: maestro_3 (default). - If you wish to verify the above settings, select the Verify database server connection check box. Click Next. 3. The “Access to MaestroRenderServer Database” window appears:

Enter the following information: - Server -host name (or IP address) and the instance name of Render Server database. - User - database user (default sa). - Password - database password (default maestro). - Show password - check this option if you want to see password in this window in the plain text. - Name - database name (default RenderServer). - If you wish to verify the above settings, select the Verify database server connection check box. Click Next.

48 Maestro | News Controller

Additional Installation Steps for the Maestro | News Controller: 1. The “Access to Shared Data” window appears:

If you have mapping of Shared Data already configured, select don’t map Shared Data. Otherwise, select the installed on other host (networked) option and enter the following parameters: - Host - host name or IP address of the machine with the Shared Data folder (usually Maestro | News Server machine) and sharing the content under the Data share name. - User - user name for the share. - Password - password for the user above. Click Next to continue. 2. The “Access to Maestro (x64) Database” window appears next:

Enter the following information: - Server - Enter the asset database host name (or IP address; usually Maestro | News Server machine) and the database instance name preceded with a backslash.

49 - Use Trusted Connection - enable this option if you wish to use a trusted connection to the database. - User - Enter the asset database user name (default sa). - Password - Enter the password for the above user (default maestro). - Show password- enable this option to see the password field in plain text to ensure that it has been entered correctly. Click Next. 3. The “Server - Database action” window appears if the database already exists:

Select Use existing if you want to use the existing content. Select Create new if you want to create a new database without any content. The existing database will be deleted. Click Next. 4. The Activate Maestro Monitor window appears:

Enable the Start Maestro Monitor on system start option, to monitor and restart the Maestro | News Controller application.

50 Maestro | News IPM

Additional Installation Steps for Maestro | News IPM: 1. The “Access to Maestro IPM (x64) Database” window appears:

Enter the required parameters: - Server - Enter the asset database host name (or IP address; usually Maestro | News Server machine) and the database instance name preceded with a backslash. - Use Trusted Connection - enable this option if you wish to use a trusted connection to the database. - User - Enter the asset database user name (default sa). - Password - Enter the password for the above user (default maestro). - Show password- enable this option to see the password field in plain text to ensure that it has been entered correctly. Click Next to continue.

51 Maestro | News ENPS Plugin (32 and 64 bit)

Additional Installation Steps for Maestro | News ENPS Plugin: 1. The “Setup Type” window appears:

Select the Maestro News MOS Plugin option to install the plugin with graphics and video items support. Select the FastServe Playout MOS Plugin to install the version of the plugin which does not support graphics items. n An appropriate license for the selected plugin type is required. Click Next to continue. 2. The “Access to Maestro ENPS Plugin Database” window appears:

Enter the required parameters:

52 - Server - Enter the asset database host name (or IP address; usually Maestro | News Server machine) and the database instance name preceded with a backslash. - Use Trusted Connection - enable this option if you wish to use a trusted connection to the database. - User - Enter the asset database user name (default sa). - Password - Enter the password for the above user (default maestro). - Show password- enable this option to see the password field in plain text to ensure that it has been entered correctly. Click Next to continue. 3. The “Configuration parameters for Maestro ENPS Plugin ” window is displayed:

If you wish to use the MOS server, then enter the MOS server host name and port in the MOS Server section. Select additional MOS item options in the MOS item section. Make sure to enter your MOS ID in the MOS ID field. Click Next.

Maestro | News GAM Access

No additional installation steps are required for Maestro | News GAM Access.

53 Maestro | News iNews Plugin

Additional Installation Steps for Maestro | News iNews Plugin: 1. The “Setup Type” window appears:

Enter the required parameters: - Server - Enter the asset database host name (or IP address; usually Maestro | News Server machine) and the database instance name preceded with a backslash.

54 - Use Trusted Connection - enable this option if you wish to use a trusted connection to the database. - User - Enter the asset database user name (default sa). - Password - Enter the password for the above user (default maestro). - Show password- enable this option to see the password field in plain text to ensure that it has been entered correctly. Click Next to continue. 3. The “Configuration parameters for Maestro iNEWS Plugin” window is displayed:

55 Maestro | News iNews Simple Plugin

Additional Installation Steps for the Maestro | News iNews Simple Plugin: 1. The “Setup Type” window appears:

Enter the required parameters: - Server - Enter the asset database host name (or IP address; usually Maestro | News Server machine) and the database instance name preceded with a backslash.

56 - Use Trusted Connection - enable this option if you wish to use a trusted connection to the database. - User - Enter the asset database user name (default sa). - Password - Enter the password for the above user (default maestro). - Show password- enable this option to see the password field in plain text to ensure that it has been entered correctly. Click Next to continue. 3. The “Configuration parameters for Maestro iNEWS Simple Plugin” window is displayed:

57 Maestro | News NLE

Additional Installation Steps for Maestro | News NLE: 1. The “Access to Maestro NLE (x64) Database” window appears:

58 Select additional options and click Next. 3. The desktop shortcut request window appears next:

Select the option to create a desktop shortcut to start Maestro NLE (x64). Maestro | News NLE will also be accessible from the Start menu. Click Next.

Maestro | News MOS28 Plugin

Additional Installation Steps for Maestro | News MOS28 Plugin: 1. The “Setup Type” window appears:

59 Click Next to continue. 2. The Access to Maestro MOS28 Plugin Database window appears:

If you wish to use the MOS server, then enter the MOS server host name and port in the MOS Server section.

60 Select additional MOS item options in the MOS item section. Make sure to enter your MOS ID in the MOS ID field. Click Next.

Maestro | News Page Browser (32 bit and 64 bit)

Additional Installation Steps for Maestro | News Page Browser: 1. The “Setup Type” window appears:

61 Enter the required parameters: - Server - Enter the asset database host name (or IP address; usually Maestro | News Server machine) and the database instance name preceded with a backslash. - Use Trusted Connection - enable this option if you wish to use a trusted connection to the database. - User - Enter the asset database user name (default sa). - Password - Enter the password for the above user (default maestro). - Show password- enable this option to see the password field in plain text to ensure that it has been entered correctly. Click Next to continue. 3. The “Configuration parameters for Maestro Page Browser Ax” window is displayed:

If required, select additional options and click Next.

62 Maestro | News Render Server

Additional Installation Steps for Maestro | Render Server: 1. The “MaestroRenderServer component categories” window appears:

Select the following options as required by your installation: Server components - This option installs the Maestro Render Server components on the local hard drive. Client component (optional) - This option installs the Maestro Render Server COM API component used by the Render Service. The Maestro Render Server Client components must be installed on the server that you plan to install the Render Service. The Server components must also be installed prior to installing the Render service. However, the Client software does not necessarily need to be installed on the same system as the Server software. Click Next. 2. The “MaestroRenderServer - Database access” window appears:

Enter the following information:

63 Host - Enter the host name of the server running the MSSQL Maestro Render Server database as well as the instance name of the database. Example: qa-mserver-f\maestro

The Maestro Render Server database is different than the Maestro Asset database. Verify that you are n entering the correct information on this page.

User - Enter the SQL user name to be used by the Render Service to access the database (default sa). Password - Enter the password for the above user (default maestro). Database name - Enter the name of the Maestro Render Server database (default RenderServer). Click Next. 3. Select whether you will use the existing database or create a new one.

Select the button to either Use existing or Create new.

If you select “Create new” and an existing database is in place, the database will be replaced and n the original data is unrecoverable. Make sure to select the correct option in this window.

Click Next. 4. The “Maestro Database Server” window appears:

64 Select the Native2 option. 5. The “Access to Maestro Database” window appears:

Enter the following information: - Server - Enter the IP address or host name of the server running the MSSQL Maestro Asset database as well as the instance name of the database. Example: qa-mserver-f\maestro - User - Enter the SQL user name to be used by the Maestro Bus Service to access the database. Example: sa - Password- Enter the password for the above user. Click Next.

65 Installing HTML5 MOS Plugin

Overview

Simplified architecture diagram:

To properly install and configure the HTML5 MOS Plugin, make sure: • Maestro | News Bus Services is installed in the REST Services mode and the SSL certificate is installed. • HTTP server that supports SSL and proxying, and an appropriate SSL certificate are installed and proxy is configured. • HTML5 MOS Plugin is unpacked into the HTTP server document root. • A default configuration is applied and your installation has been pre-tested without using any NRCS systems. • Maestro | News Render Server is configured for preview purposes and the preview has been tested.

The following prerequisites need to be met before installing and configuring the HTML5 MOS Plugin: • SSL Certificate (PFX/CER formats) with common name Maestro HTML5 Plugin (required only for production systems; for test systems you can generate simple certificate by yourself) needs to be installed. • SSL Certificate (CRT/KEY formats) with common name the same as FQDN of the website, where the HTML5 MOS Plugin will be available (required only for production systems; for test systems you can generate simple certificate by yourself) needs to be installed.

You can use other certificate file formats, but conversion / installation of other certificate formats is n not in scope of this document.

Install Maestro | News Bus Services

Follow the instructions from the Maestro | News Bus Services chapter, select the REST mode.

Configure Maestro | News Bus Services

To configure the Maestro | News Bus Services for the HTML5 Plugin: t Verify and change the asset browser root folders: a. Edit the SystemSettings.ini file of the Maestro Bus Services (file is located in :\Orad\MaestroBusServices). b. Look for the [AssetService] section and add or change the following entries:

66 - RootAsset\x\name - add a descriptive name. This name will be shown in the HTML5 MOS Plugin asset browser. - RootAsset\x\path - add the asset folder path (you can find / browse this path by going to the Maestro | News Controller and browsing for content in the Asset Browser). The x parameter is the next root folder number. c. Finally, update the root folders count in RootAsset\size.

Example configuration for two root folders: [AssetService] RootAsset\0\name=TEMPLATES RootAsset\0\path=/root/TEMPLATES RootAsset\1\name=MOS RootAsset\1\path=/root/WORKSPACE/MOS/Objects RootAsset\size=2

The example above will result (at the end of the installation) in the following content in the HTML5 MOS Plugin (the result will be sorted alphabetically, so the order of folders in the [AssetService] section is not important):

Install the Maestro | News Bus Services Certificate

Copy the Maestro HTML5 Plugin SSL certificate to the machine with your Maestro | News Bus Services installation (you need two files: one with pfx extension, one with cer extension).

67 To install the Maestro | News Bus Services certificate: 1. Double-click on the PFX certificate file, select Local Machine and click Next.

2. Browse for the certificate and click Next.

3. Type the certificate password and click Next.

68 4. Select Place all certificates in the following store and press Browse:

5. Select Trusted Root Certification Authorities and press OK:

6. Click Next and Finish the installation.

7. After successfully installing the certificate, obtain the certificate thumbprint. a. Open the Microsoft Management Console. b. In the Microsoft Management Console, go to File > Add/Remove Snap-in.... c. Double-click the Certificates option.

69 d. Choose Computer account, click Next. Select Local computer and click Finish.

e. After adding the certificate snap-in, click OK to close the Add/Remove Snap-ins window.

70 f. In the main Microsoft Management Console window, right-click on Certificates (Local Computer) and select the Find Certificates option.

g. In the search window, enter the Maestro HTML5 plugin phrase in the Contains text box and click Find now. Your certificate should appear in the results window.

h. Double-click on the certificate to display its properties and go to the Details tab.

i. Select the Thumbprint entry and copy the content of the panel below the list.

71 On some systems, the copied thumbprint may contain spaces and special characters (as shown n above). Paste the thumbprint into a text editor and remove the spaces and unwanted characters, leaving only the hexadecimal value(e.g. 6b0f3271d53d78904bd9fab91dd4fb064b0caee9).

8. Now, add the certificate for HTTP protocol using the netsh tool. Open the command line as an administrator and execute the following command: netsh http add sslcert ipport=0.0.0.0: certhash= appid={00000000-0000-0000-0000- 000000000000} certstorename=Root Where: - is a port for connecting to the Maestro Bus Services (default 9030). - is the thumbprint prepared in the previous step. 9. You should now see a message that the SSL Certificate has been added successfully. If you encounter any problems, ensure that your thumbprint does not contain any special (probably invisible) characters at the beginning. 10. Verify your installation. Open an internet browser and go to the following URL: https:// 127.0.0.1:9030/RESTApi/systems (change the port number if a different port has been during the configuration). You should see a response similar to the one below: {"data":{"systems":[{"name":"filesystem","type":"Local","__links":{"system ":"https://{serverIP}:9030/RESTApi/systems/filesystem"}}]}}

Install HTTP Web Server for Proxy Support

Install the HTTP server of your choice (Apache HTTPD Server is recommended). The chosen server must support SSL (HTTPS protocol) and proxying.

You need to configure your HTTP server to use HTTPS (SSL). Thus you should also obtain and install an appropriate SSL certificate.

Please note that you cannot use the port 9030 for HTTP server if you have Maestro | News Bus Services installed on the same machine, due to fact that Maestro | News Bus Services uses port 9030 for REST.

72 Configure HTTP Proxy

You should proxy all requests for resources: • /AssetAccessService/ • /RenderService/ •/DataLinkService/

to port 9030 on the host where Maestro | News Bus Services are running in the REST mode. Detailed configuration depends on the HTTP server.

Example Configuration for Apache HTTPD 2.2: 1. Enable the modules (and their dependencies) for HTTP proxy in the configuration file (on Windows default configuration file location is: c:\Program Files (x86)\Apache Software Foundation\Apache2.2\conf\httpd.conf): LoadModule proxy_module modules/mod_proxy.so

LoadModule proxy_ajp_module modules/mod_proxy_ajp.so

LoadModule proxy_balancer_module modules/mod_proxy_balancer.so

LoadModule proxy_connect_module modules/mod_proxy_connect.so

LoadModule proxy_ftp_module modules/mod_proxy_ftp.so

LoadModule proxy_http_module modules/mod_proxy_http.so

LoadModule proxy_scgi_module modules/mod_proxy_scgi.so

LoadModule ssl_module modules/mod_ssl.so

LoadModule deflate_module modules/mod_deflate.so

LoadModule headers_module modules/mod_headers.so 2. Configure proxy in your virtual host configuration: SSLProxyEngine on

ProxyRequests off

ProxyPass /AssetAccessService/ https://127.0.0.1:9030/ AssetAccessService/

ProxyPassReverse /AssetAccessService/ https://127.0.0.1:9030/ AssetAccessService/

ProxyPass /RenderService/ https://127.0.0.1:9030/RenderService/

ProxyPassReverse /RenderService/ https://127.0.0.1:9030/RenderService/

ProxyPass /DataLinkService/ https://127.0.0.1:9030/DataLinkService/

ProxyPassReverse /DataLinkService/ https://127.0.0.1:9030/ DataLinkService/

73 Unzip HTML5 MOS Plugin

If you are using Apache HTTPD 2.2 you can find the location of the web root by searching for DocumentRoot inside your virtual configuration file.

Test Your Installation

Start your HTTP server and open the start page (the location you configured as web root) in your Internet browser.

You should see the following plugin:

If you encounter a Network Error message - it means that there is no connection between the HTML5 MOS Plugin and Maestro | News Bus Services.

If no errors occur, you are ready to embed the plugin in your NRCS system.

Installing MediaCentral | Cloud UX Plugin

Overview

There is no separate installer for the HTML5 Cloud UX plugin. It is installed automatically (no separate prompt) when you add the Feature Packs to the MediaCentral | Cloud UX server. For more information, see “Running the Feature Pack Deployment Script” in the Avid MediaCentral | Cloud UX Installation Guide.

After you install and configure the plugin, you must import a license on the MediaCentral | Cloud UX server that contains both the Maestro News | MediaCentral and the Graphics Managament license types. Additionally, you must ensure that the appropriate entitlements are enabled for the user groups that need access to these features. For more information, see “Using the Licensing App” and “Using the User Management App” in the Avid MediaCentral | Cloud UX Installation Guide.

74 The HTML5 Cloud UX plugin requires: • Maestro | News Bus Services running in the ACS mode (usually installed on the Maestro | News Server machine). For more information, see the Maestro | News Bus Services chapter. • Maestro | News Render Server (for preview purposes) - with special settings in the registry and the rendering output mounting on the Cloud UX machine. For more information, see the Configuring Render Server for Cloud UX chapter.

Configuring Maestro Bus Services for Cloud UX

After a successful installation of the Maestro Bus Services in the ACS mode, you need to configure MaestroNewsSync (Sync Agent).

To configure Maestro Bus Services for Cloud UX: t Edit the following Sync Agent settings in the appsettings.json file, which is located in the following folder: C:\Orad\MaestroBusServices\SyncAgent\appsettings.json a. ConnectionStrings - change the connection details for the Maestro | News database according to your setup. b. AssetQueryOptions - this parameter is responsible for internal settings of MaestroNewsSync: - BatchSize - maximum number of items which can be sent in one command to search index. - AssetTypes - list of asset types, which should be included in a search, e.g. if only pages should be searchable in Cloud UX, then use the following definition: “AssetTypes”: [“PAGE”]. c. SourceStrings - this parameter represents the identity of Maestro | News assets in a Cloud UX search: - SystemId - this parameter should match the realm of MaestroCTMS service; leave it unchanged. - IndexId - same as SystemId. d. SearchService - set the value of the URI parameter to the uri of the search service in Cloud UX.

Configuring Render Server for Cloud UX

This topic describes how to configure the Maestro | News Render Server to work with MediaCentral | Cloud UX.

75 To configure Render Server to work with Cloud UX: 1. After a successful installation of the Render Server, set the CanvasFrameSharing and FastSingleImage options to true in the registry under the folder: HKLM\SOFTWARE\Orad\MaestroRenderServer\2019.2\.

2. After setting the FastSingleImage option to true, you need to set the appropriate resolution in the RenderEngine configuration. Change the resolution to HD720 in the RE.xml file. In the Layout section, set the value of the Name parameter to HD720.

3. Mount the rendering output on the Cloud UX machine. By default, the output is rendered to the RenderServerOut folder in your shared data (G: drive). a. With this default configuration, edit the /etc/fstab file on the Cloud UX machine and add the mount point of your shared data to /mnt/media/Control_Data. Example: ///Control_Data /mnt/media/Control_Data cifs username=,password=,rw,iocharset=utf8 0 0 b. Apply the mount point by typing: mount /mnt/media/Control_Data

76 Integration with MediaCentral | Cloud UX Rundown App

If you plan to integrate Maestro | News with the MediaCentral | Cloud UX Rundown app, you must edit the SYSTEM.MAP and SYSTEM.MOS-MAP story in your MediaCentral Newsroom Management system to include the Maestro News MOS ID. For more information about these SYSTEM files, or to see examples, see SYSTEM.MAP and SYSTEM.MOS-MAP sections in the System Files appendix of the MediaCentral | Newsroom Management Setup and Configuration Guide.

Notes About Running Installers

In case of a warning message is displayed by the Windows Defender on Windows 10:

Click the More info button, and select Run anyway.

User Account Control

The User Account Control (UAC) message can appears if UAC is enabled. Select Yes to run the installer.

77 Default Installation Folders

Components are installed to the following target folders:

Component Default Installation Folder

Maestro | News Bus Services :\Orad\MaestroBusServices\

Maestro | News Controller :\Orad\Maestro64_2019_2\

Maestro | News ENPS Plugin 32 bit :\Orad\MaestroENPSPlugin\

Maestro | News ENPS Plugin 64 bit :\Orad\MaestroENPSPlugin64\

Maestro | News GAM Access Plugin 32 bit :\Orad\MaestroGAMAccess_2019_2\

Maestro | News GAM Access Plugin 64 bit :\Orad\MaestroGAMAccess64_2019_2\

Maestro | News iNews Plugin :\Orad\MaestroINEWSPlugin\

Maestro | News iNews Simple Plugin :\Orad\MaestroINEWSSimplePlugin\

Maestro | News IPM :\Orad\MaestroIPM64\

Maestro | News Journalist Station :\Orad\JStation64_2019_2\

Maestro | News MOS28 Plugin :\Orad\MaestroMOS28Plugin\

Maestro | News NLE :\Orad\JStation64_2019_2\

Maestro | News PageBrowser Plugin 32 bit :\Orad\MaestroPageBrowserAx\

Maestro | News PageBrowser Plugin 64 bit :\Orad\MaestroPageBrowserAx64\

Maestro | News Render Server :\Orad\MaestroRenderServer64\ :\Orad\MaestroRCPlugin64\

MOS Server :\Orad\MOSGateway2\

HTML5 MOS Plugin Web root folder of the HTTP server

In addition, all the installers copy the installer files into the :\Orad\Installers\ folder.

Applying Licenses

License Types

Type Description

Version 2 - HASP 4 Uses local HASP 4 dongle

Version 2 - Hasp HL (V8) Uses local HASP HL dongle

Version 2 - Nodelock (Windows) Bound to specific machine, does not require dongle

78 Type Description

Version 3 - floating license May be used by any machine, does not require dongle on local machine but require license server

For more information, refer to the HASP Driver documentation.

Licenses List

License Types

Version 2 - Version 2 - Version 3 - License Component Module Name Version 2 - HASP HL Nodelock floating Options HASP 4 (V8) (Windows) license

Maestro | News Bus no license required Services

Maestro | News MaestroControllerXXXXMOS, Controller Automation, GPI, SceneEdit, Ticker, Morpho, Blend, Tweeter, Facebook, iMaestro1, iMaestro2, iMaestro3, iMaestro4, iMaestro5, iMaestro6, iMaestro7, iMaestro8

MaestroPageEditorXXXXSceneEdit, Tweeter, Facebook

FastServePlayout XXXXMOS, Automation, GPI, iMaestro1, iMaestro2, iMaestro3, iMaestro4, iMaestro5, iMaestro6, iMaestro7, iMaestro8c

MaestroControllerP XXXXTicker review

Maestro | News ENPS MaestroENPS XXXXTicker, Morpho, Plugin 32 bit Tweeter, Plugin Facebook

79 License Types

Version 2 - Version 2 - Version 3 - License Component Module Name Version 2 - HASP HL Nodelock floating Options HASP 4 (V8) (Windows) license

Maestro | News ENPS MaestroENPS XXXXTicker, Morpho, Plugin 64 bit Plugin Tweeter, Facebook

Maestro | News GAM no license required Access Plugin 32 bit

Maestro | News GAM Access Plugin 64 bit

Maestro | News MaestroINEWS XXXXTicker, Morpho, iNews Plugin Tweeter, Plugin Facebook

Maestro | News MaestroINEWS XXXXTicker, Morpho, iNews Simple Plugin Tweeter, SimplePlugin Facebook

Maestro | News IPMMaestroIPMXXXXnone

Maestro | News JStation X X - X Ticker, Morpho, Journalist Station Blend, Tweeter, Facebook

Maestro | News MaestroMOS28 XXXXTicker, Morpho, MOS28 Plugin Tweeter, Plugin Facebook

Maestro | News NLEMaestroNLEXXXXFeature0, Morpho, Tweeter, Facebook

MaestroNLEServer X X - X none

Maestro | News PageBrowser Plugin MaestroPage Morpho, 32 bit XXXXTweeter, BrowserAX Facebook Maestro | News PageBrowser Plugin 64 bit

Maestro | News no license required Render Server

MOS ServerMOSGatewayXXX-8 clients, 16 clients

Orad Control no license required

80 License Types

Version 2 - Version 2 - Version 3 - License Component Module Name Version 2 - HASP HL Nodelock floating Options HASP 4 (V8) (Windows) license

Maestro | News MaestroNews XXXX10 clients, 20 HTML5 MOS Plugin clients, 25 HTML5 clients, 50 clients, 100 clients, 150 clients, 200 clients, 250 clients, 300 clients, 350 clients

Maestro | News MediaCentral | Cloud UX licensing applies for this component HTML5 Cloud UX • MAESTRO NEWS MEDIACENTRAL - Enables the Graphics tab in the Asset Editor and Plugin enables the ability to drag and drop graphics into the Rundown App. • GRAPHICS MANAGEMENT - Enables you to browse and search Maestro News database.

Checking Available Licenses

Run the License Monitor (installed together with the HASP Driver). Look for the license module of your component:

Ensure that your license matches the version of your component and it has not expired.

81 Testing Your Installation

Testing ActiveX Controls

ActiveX controls can be tested from any ActiveX container (e.g.: Microsoft ActiveX Test Container). Run the container and select appropriate ActiveX:

ActiveX Control Component Class Name Name GUID

Maestro | News MaestroEditor maestroinewsax. 5B4E4114-AAC4-47CE-AB6E- iNews Plugin Class E88D00241479 MaestroEditor

Maestro | News Maestro Simple maestroinewsax. F6FD9972-6114-41FB-B41A- iNews Simple Plugin Editor D8CF29BAA5AA MaestroSimpleEdit or

Maestro | News ENPS MaestroENPS ENPSPluginAtl. DDB7B161-558D-40C9-B905- Plugin (32 bit and 64 Class 43E7D06B4EC5 MaestroENPS bit)

Maestro | News MaestroMOS Class MaestroMOS28. BB3E0F53-A4C9-413D-B060- MOS28 Plugin 2D467AC42414 MaestroMOS

Initial Configuration

The basic settings (i.e. database settings) of the components are configured during the installation process. However, for some components additional configurations steps may be required.

Configuring DVG to Play Maestro | News Assets

To play Maestro | News assets on DVG you must mount Shared Data on DVG under /Control_Data.

Mounting Shared Data: 1. Create a mount point on the DVG for the shared folder: mkdir /Control_Data 2. Edit the /etc/fstab file to automate the mapping shared folder on startup: vi /etc/fstab 3. Add an entry at the end of the file: /// /Control_Data cifs ro,user=,passwd=,iocharset=utf8 0 0 Where the following variables are used: - shared_folder_host is the IP address or host name where Shared Data is installed (usually Maestro | News Server). - shared_folder_name is the name of the shared folder on the host above (Data by default). - user_name - is the name of a Windows user that can access the shared folder above - user_password - is the password for the above user

82 Below is an example of the completed line: //192.168.10.99/Data /Control_Data cifs ro,user=Maestro,passwd=Avid123,iocharset=utf8 0 0 4. Save and exit the vi session. Press and type: :wq 5. Mount the volume: mount /Control_Data

Using MediaCentral | Asset Management Assets on Maestro | News Pages

If you want to use MediaCentral | Asset Management assets on Maestro | News pages you must also configure DVG to work with MediaCentral | Asset Management.

To configure DVG to work with MediaCentral | Asset Management: 1. Create a mount point on the DVG for the shared folder: mkdir -p //Data Where: - mam_shared_folder_host - host name of MediaCentral | Asset Management system. - mam_shared_folder_name - name of the asset share of MediaCentral | Asset Management system. 2. Edit the /etc/fstab file to automate the mapping shared folder on startup: vi /etc/fstab 3. Add an entry at the end of the file: //mam_shared_folder_host/mam_shared_folder_name /mam_shared_folder_host/ Data cifs username=,password=,rw,bg,iocharset=utf8 0 0 Where the following variables are used: - shared_folder_host - is the IP address or host name where Shared Data is installed (usually Maestro | News Server). - shared_folder_name - is the name of the shared folder on the host above (Data by default). - user_name - is the name of a Windows user that can access the shared folder above - user_password - is the password for the above user. Below is an example of the completed line: //qa-imam-d/Data /qa-imam-d/MediaAssetManager cifs username=mam_admin,password=Avid123,rw,bg,iocharset=utf8 0 0 4. Save and exit the vi session. Press and type: :wq 5. Mount the volume: mount /mam_shared_folder_host/Data

83 Configuring MediaCentral | Asset Management Share Access on Playout or Journalist Station

To use local preview of MediaCentral | Asset Management assets in the Maestro | News Controller or Maestro | News MOS Plugins, you must be authorized to the MediaCentral | Asset Management server. Follow the steps below on your machine with the Maestro | News Controller or Maestro | News MOS Plugins. Choose one of the available solutions: • Temporary solution • Permanent solution using the GraphicsSuite startup script • Permanent solution using the UI

To configure a temporary solution (authorization details will be forgotten after system restart): 1. Open the Windows command prompt. 2. Enter: net use \\ /user: Where: mam_host - host name or the IP of the MediaCentral | Asset Management server. user - enter the user name that can access the server above (default is mam_admin or mam_service). password - enter the password for the user above.

To configure a permanent solution using the GraphicsSuite startup script: 1. Open the following file using the Notepad or any other text editor. \Orad\Common Files\CyGLoginScript.cmd 2. Add the line at the end of the file with the command described in point 2 of temporary solution section above.

To configure a permanent solution using the UI: 1. For Windows 10: open the File Explorer, from the Home ribbon select Easy access/ Map as drive.

For Windows 7: open Windows Explorer, from the Tools menu select Map network drive.

84 2. The dialog box appears:

Select the drive of your choice (avoid G: because it is commonly used for Shared Data), enter the path to the MediaCentral | Asset Management share in the Folder field. Select the Reconnect at sign-in and Connect using different credentials check boxes, then click Finish. 3. The Enter Network Password dialog box appears:

Enter the credentials to the MediaCentral | Asset Management share (default mam_service / Avid123) then click OK. 4. You may be prompted to enter the credentials once again:

85 5. The content of the MediaCentral | Asset Management share will be displayed:

To verify the configuration in the Maestro | News Controller: 1. Configure access to MediaCentral | Asset Management in the settings of the Maestro | News Controller. Refer to the Maestro | News User Guide for detailed information.

Take note that MediaCentral | Asset Management 5.9 and older use port 9910, while MediaCentral| Asset Management 6.0 (2017.1) and newer use HTTPS protocol and port 9911. 2. Browse for video assets from the specified MediaCentral | Asset Management:

86 Double-click on the asset of your choice to preview it.

If you don’t have any assets in MediaCentral | Asset Management to use for your preview tests, you n can easily add them using the MAM watch folder. For more information, refer to the MediaCentral | Asset Management user guide.

Open the media asset shared folder, and navigate to Workspace\WatchFolder\WatchServiceMamImport\WatchFolder.

Then, navigate to the appropriate subfolder, put the supported file into this folder.

Login to the MediaCentral | Asset Management Desktop. In the Workspace panel expand, Import Monitoring, then expand a folder appropriate for the type of the file you are importing (e.g. Video file). Wait for the import to finis.

Using the Search pane, look for your imported file and drag it to the folder of your choice, e.g. Maestro GMAM / Clips. If you want to add a thumbnail to the imported clip, open this clip item in the MediaCentral | Asset Management Desktop. Go to the Essence tab and upload a thumbnail image as a new essence of preferred usage THUMB.

87 Configuring MAM File Transit using Maestro GMAM / MediaCentral | Asset Management

MAM file transit is a Maestro | News feature which allows to automatically export: • clips on Graphics Items • Video Items - only clips

From Maestro GMAM / MediaCentral | Asset Management to the target location (i.e. to the G: drive or a FastServe | Playout clips folder).

There is no support for exporting images or image sequences.

To configure MediaCentral | Asset Management to work with file transit from Maestro | News: 1. MediaCentral | Asset Management should have a target system defined as Maestro with fixed numerical code (key) 10. This code can be obtained from the MAM_export profile:

2. The file name pattern should be: {OrderID}\export.{FormatExt}

88 3. Create the following folder structure on the FTP share: a. CutTemp b. RestoreTemp c. StitchingTemp d. Target e. Target 4. Important: Ensure that the folder permissions allow to create subdirectories using an FTP connection. 5. Note about FastServe | Playout: FastServe | Playout has vsftpd configured. The example below uses administrator/ Avid123 ftp credentials, but they may be different (if you receive a message Received message too long 1416128883 while trying to login to the ftp, then you should check your /etc/passwd file on FastServe | Playout and set valid shell for your current user - e.g. /bin/sh instead of /sbin/ nologin). Remember to properly configure VSFTP (in file /etc/vsftpd.conf), e.g.: local_enable=YES write_enable=YES userlist_enable=YES tcp_wrappers=YES userlist_deny=NO local_root=/home/orad/ anon_root=/home/orad/ To start ftp daemon on FastServe | Playout, type: service vsftpd start 6. Open https://:9911/ControlCenter/web/. 7. Go to the SystemSettings and change the values for: a. Mam.Kit.FoundationBase.ExportFolder.FtpUri and b. Mam.Kit.FoundationBase.ExportTempFolder.FtpUri to ftp:// :@:/ 8. Open the MAM System Administrator (go to http://:9900/ LoginServiceWS/Admin/AdminStart.aspx, login then click on SystemAdministrator) 9. In the MAM System Administrator, select the MAM_Export profile. 10. Select the Node TargetSystems/Maestro. 11. Keys that need to be changed with example values: - CutPathFTP = {system:Mam.Kit.FoundationBase.ExportTempFolder.FtpUri}CutTemp - RestorePathFTP = {system:Mam.Kit.FoundationBase.ExportTempFolder.FtpUri}RestoreTemp - StitchingPathFTP = {system:Mam.Kit.FoundationBase.ExportTempFolder.FtpUri}StitchingTemp - TargetPath = {system:Mam.Kit.FoundationBase.ExportTempFolder.FtpUri}Target - TargetSystemType = ETM

89 - TranscodePathFTP = {system:Mam.Kit.FoundationBase.ExportTempFolder.FtpUri}TranscodeTemp - TransferProtocol = FTP 12. Select the profile WorkflowEngineWS_1 and click the Refresh Component Config button (little wrench with reload arrows)

To configure MAM file transit in Maestro | News: 1. Ensure that you have MediaCentral | Asset Management connection configured properly. Example:

2. Then in Maestro | News, go to Customize / Settings, open the MAM file transit tab, select the MAM file transit check box and enter the following parameters: a. select Central location if you want to export items from all channels into a single location or Distributed locations if you want to differentiate target locations based on the channel assigned to the items. b. Currently the location should be a number, which is taken from the MAM target destinations configuration. c. ACS gateway host - IP of the ACS bus (MediaCentral). d. ACS gateway port - 9500 for MediaCentral 2.7.x or older, 9900 for MediaCentral 2.8 or newer. e. User name - Administrator f. Zone Id - this is ICS Zone id (Interplay Communicaton Services Zone Id); g. Role - Administrator h. Transcoding system - selection a delivery format; must be numerical, set to 1. 3. Example configuration:

90 4. If you configure MAM file transit for REST MAM, then you have to create the following environment variables t REST_MAM_FT_TARGET_PATH -> ftp:// :@:/Target (for example ftp:// avid:Avid123@qa-mme-b:21/Target) t REST_MAM_FT_USAGE_CLASS -> EDIT

and change the Target system in the Maestro | News configuration:

91 To initiate MAM file transit in Maestro | News: t Add Video Items to the rundown and assign them to channels. The export should start automatically and quietly.

Track MAM file transit in Interplay MAM t Go to the MediaCentral | Asset Management web console, e.g. http://maestro-mam53:9900/ LoginServiceWS/start.aspx, and select Export / All destinations:

n If the Export monitor does not work, you can track exports via the Workflow Monitor: http:/:9900/WorkflowEngineWSAdmin/ WFEMonitor.htm?accesskey=abbf62ba-d8e7-41b9-bbf6- 0617568c99c6&productname=qa-gmam-a

92 Troubleshooting

This section describes the steps you can follow when you encounter any problems with the configuration. 1. Check the BPMController logs. If export process fails shortly after takeoff, it may be useful to check the logs of the BPMController MAM Service. Usually, you can find them in C:\ProgramData\Avid\MediaAssetManager\Logs\BPMController on the MAM server. If you find errors like the one below: [E] 2017-01-10T11:29:48.9120002+01:00 0019 Validation of UMS token failed via com.avid.ums.login.isTokenValid method. Not connected to the bus

[W] 2017-01-10T11:29:48.9120002+01:00 0019 Failed to invalidate UMS session '-3573785874236531818' in session cache. Not connected to the bus This means that the BPMController lost his connection to the bus. Restart the BPMController as described below. 2. Restart the BPMController. There are 2 ways to restart the Orchestration pool: Restart using the Web Client: - Type in a browser: https://:9911/ControlCenter/Web/ using your own MAM server name. - Click on the Service Controller button in the Dashboard. Type BPMController in the filter text box.

Restart using the Server Manager: - Go to the Server Manager. - Expand Tools and choose Internet Information Services (IIS) Manager. - Expand your server on the navigation tree and choose Application Pools. - Find and restart the MAM_6200_BPMController.

- To restart a service, right-click on it, click stop and then start.

93 In case MediaCentral | Asset Management is older than the 5.8 version, you have to restart n MAM_6100_Orchestration instead MAM_6200_BPMController. 3. Try to change the transcoding system.

Known Problems

This section describes known problems that have occurred during the configuration and presents an example solution for each of the listed issues.

Go to MediaCentral | Asset Management web console, e.g. http://:9900/LoginServiceWS/ start.aspx, select Export / All destinations.

1st Problem:

Solution: 1. Open the MAM System Administrator (go to http://:9900/ LoginServiceWS/Admin/AdminStart.aspx, login, then click on SystemAdministrator). 2. In the MAM System Administrator, select the MAM_Export profile. 3. Select the Node CommonSettings. 4. Change: RestorePathFTP = {system:Mam.Kit.FoundationBase.ExportTempFolder.FtpUri}RestoreTemp 5. Select the profile WorkflowEngineWS_1 and click the Refresh Component Config button (little wrench with reload arrows).

2nd Problem:

Explanation:

Missing codec...

If the file type is not listed in the TargetStreamTypes property, the system will chose the first one on the list. In this case it is JPG.

94 3. Select the Node TargetSystems/Maestro: - Originally: TargetStreamTypes = JPG,JPEG,PNG,TIF,BMP,MP4,MXF - After change (for example file.mov): TargetStreamTypes = JPG,JPEG,PNG,TIF,BMP,MP4,MXF,MOV 4. Select the profile WorkflowEngineWS_1and click the Refresh Component Config button (little wrench with reload arrows). 5. In case the problem still exists, you are probably missing codecs for this format.

3rd Problem:

Solution: 1. Open the MAM System Administrator (go to http://:9900/ LoginServiceWS/Admin/AdminStart.aspx, login, then click on Essence Management Administrator). 2. Select the Essence Server tab. 3. EssenceServerDiskWS_1 > HIRES > HIRES > Access.

95 4. Select New: - Name: FTP - Protocol: FTP - Base Path: Select HIRESUNC (UNC) › Edit - Role: read

5. The configuration is complete.

96 Configuring MediaCentral | Production Management and NEXIS Connection

To use local preview of MediaCentral | Production Management assets in the Maestro | News Controller or Maestro | News MOS Plugins: 1. MediaCentral | Cloud UX server must be configured to use MediaCentral | Production Management server of your choice. 2. You need to install and configure the NEXIS Client Manager on the machine with Maestro | News Controller / Maestro | News MOS Plugins. 3. Interplay Production Web Services must be properly configured on the MediaCentral | Production Management server. 4. You need to properly configure your local VideoEngine.

Checking MediaCentral | Production Management Configuration with MediaCentral | UX

For detailed information about configuring MediaCentral | Production Management with MediaCentral | Cloud UX, refer to the MediaCentral | Production Management Installation and Configuration guide and the MediaCentral | Cloud UX Installation and Configuration guides.

Configuration of the NEXIS Client Manager

For detailed information about installing and configuring the NEXIS client, refer to the NEXIS Client Manager Installation Guide. This chapter only shows an example of the most common and simple scenario.

To configure the Nexis Client Manager: 1. Install the NEXIS Client manager if it is not already installed. 2. Run the NEXIS Client Manager. 3. Select the NEXIS server from the Systems list. 4. Click the Connect to selected system(s) tool button. The System Login dialog box appears:

Enter valid NEXIS credentials, enable Auto connect if you wish to save the connection and click the Connect button.

97 5. The NEXIS Client Manager will populate the list of workspaces in the system of your choice.

Select the workspace associated with your MediaCentral | Production Management system. Then click on the Mount selected workspace(s) tool button. 6. The mounted workspace line will be shown using bold text. The Online column will show the drive on which the workspace is mounted on:

98 Checking status of Interplay Production Web Services

For detailed information about Interplay Production Web Services, refer to the MediaCentral | Production Management installation and configuration guides. This chapter shows only the example of the most common simple scenario.

To check the status of Interplay Production Web Services: 1. On the MediaCentral | Production Management server, open Services and look for Avid Interplay Web Services entry.

If the service is not running, start it. You can also set the startup type of the service to Automatic to make sure the service is always running. 2. On the MediaCentral | Production Management server, run the browser and point to http:// localhost:8080. If the page did not open, then either Avid Interplay Web Services is not running or you have specified a different port than the 8080 port in your Web Services configuration (to check it, open the file C:\ProgramFiles\Avid\Interplay Web Services\apache-tomcat\conf\server.conf in a text editor, look for the line

99 3. Click Edit Configuration and check if your configuration points to the correct WebServices Workgroup Name (workgroup used in MediaCentral | Production Management) and Primary Engine Hostname (should contain the host name of MediaCentral | Production Management).

Correct these settings if needed, then click Submit. 4. Click Home, then select Test Configuration.

Enter your credentials and click Test. 5. As a result, you should see at least one Asset Pass message.

If you do not see any message, then correct your settings.

100 Configuration of Local VideoEngine

This chapter only shows an example of the most common simple scenario.

To configure local VideoEngine: 1. On the machine with Maestro | News Controller / Maestro | News MOS Plugin, run the web settings of the local VideoEngine - open http://localhost:8080 and login. Select the Commander tab and expand the External sources section. For a more detailed description, refer to the FastServe | Playout Administrator’s Guide.

2. If you do not have a valid configuration of MediaCentral | Production Management here, click on Add new external source to setup a new connection.

101 t In the Name field, enter the System ID of the MediaCentral | Production Management system. t Enter the Address of the machine with MediaCentral | Production Management WebServices, followed by the port number, e.g. 10.1.1.1:8080, or http://:8080. Verify that you can access this URL from the machine with VideoEngine installed. Paste this URL into an internet browser and check the response. If the URL is not accessible, check your Avid Interplay Web Services container settings (Tomcat on the MediaCentral| Production Management system, located in C:\Program Files\Avid\Interplay Web Services\apache-tomcat\) and check your firewall. t In the Workgroup field, enter the MediaCentral | Production Management workgroup you will use. t Default path name is “/”. This setting does not need to be changed. t In the Username and Password fields, enter the MediaCentral | Production Management system credentials (the same you entered when testing the Avid Interplay Web Services). t Leave the Mapping src and Mapping dest fields empty. Click Add to finish the configuration and restart VideoEngine. A detailed description of the configuration between the VideoEngine and MediaCentral | Production Management systems is provided in the FastServe | Playout Administrator’s Guide.

Verifying the Configuration in the Maestro | News Controller

Configure the Maestro | News Controller to use the MediaCentral | Production Management system. For more detailed information, refer to the Maestro | News User Guide.

After configuring and applying your settings, go to the Browser panel and select Video items. Open the tab with the name you entered in the configuration.

102 If you do not see any content but you also do not see a warning that you are Disconnected, then it is possible that you are not authenticated to the MediaCentral | Production Management platform (Avid Interplay Administrator / User Management / User Authentication Providers / MediaCentral Platform Authentication).

Double-click on any clip and click the Play button. You should see a preview of your video asset.

Configuring MOS-less Communication with MediaCentral | Newsroom Management

Verifying MediaCentral | Newsroom Management WS API configuration

For detailed information about configuring MediaCentral | Newsroom Management WS API, refer to the MediaCentral | Newsroom Management user guide. This chapter only shows and example of the most common simple scenario for MediaCentral | Newsroom Management older than version 6.1.

103 To verify the MediaCentral | Newsroom Management WS API configuration: 1. Ensure that you have WS API enabled on the MediaCentral | Newsroom Management server. Login to the server using an SSH client to verify the license: su so status license 2. Show the content of the /site/config file (e.g. by typing cat/site/config) and check the WS API configuration - you should see the uncommented lines (numbers may differ in your configuration): host a a reslist 801:805 ; WSAPI and ; WSAPI ; api 801:805 - gnews - ; api

Configuring MediaCentral | Newsroom Management Web Services

For detailed information about installing and configuring MediaCentral | Newsroom Management Web Services refer to the MediaCentral | Newsroom Management user guide. This chapter only shows an example of the simple scenario using Tomcat Java application container run on the Maestro | News Server machine.

To configure MediaCentral | Newsroom Management Web Services: 1. Copy inewswebservices.war to any temporary location on the Maestro | News Server. 2. Install Java 7.0 or newer if it is not already alled (https://www.java.com/pl/download/) 3. Install Tomcat: a. Go to http://tomcat.apache.org/download-90.cgi. b. Download the32-bit/64-bit Windows Service Installer under 9.x / Binary Distributions / Core section. c. Run the installer. During the installation select the Host Manager.

104 d. Use the default settings for ports, in the User Name field enter tomcat, enter a password of your choice.

Alternative method: after installation change conf/tomcat-users.xml, e.g. by adding: e. On the last setup page, allow the installer to start Tomcat.

105 4. Deploy MediaCentral | Newsroom Management Web Services in Tomcat on the Maestro | News Server: a. Open a web browser (on the machine where you installed tomcat) and point to http:// 127.0.0.1:8080.

b. Click on the Manager App and enter your credentials (tomcat / your password). Please note, that the Tomcat Manager GUI is accessible only from a local host (you must change the context.xml file and then restart Tomcat to allow login from other hosts). c. In the Deploy / WAR file, click Browse and point to inewswebservices.war, then click Deploy. 5. Check if the WAR file was deployed correctly by typing the following phrase in your browser: http://127.0.0.1:8080/inewswebservice/services. You should see the following result:

106 Verifying the Connection from the Maestro | News Controller

Refer to the appropriate section in the Maestro | News User Guide. A shortened version of the procedure is presented below.

To verify the MediaCentral | Newsroom Management connection in Maestro | News Controller: 1. Open the Maestro | News Controller and configure the MediaCentral | Newsroom Management web services:

In the Webservice URL field, enter: http://:8080/inewswebservice/services.

107 In the MediaCentral | Newsroom Management Server Host field, enter the IP address of the MediaCentral | Newsroom Management Server system. In the MediaCentral | Newsroom Management user and password fields, enter the login credentials to the MediaCentral | Newsroom Management Server. Apply your settings by clicking OK. 2. Test the MediaCentral | Newsroom Management synchronization. Click on the Select MediaCentral | Newsroom Management rundown icon, select any rundown and press >>, then click OK.

3. The Rundown should be loaded into the Maestro | News Controller.

108 Configuring Maestro | News Render Server

Once installed, the Maestro Render Server must be configured to specify a rendering profile and a rendering channel.

Do not start RenderServer Server application using Remote Desktop Connection (RDP). Use c other remote access (e.g. VNC) instead.

To configure render settings: 1. Launch the Maestro Render Server software at: :\Orad\MaestroRenderServer64\RenderManager.exe 2. At the Login window, enter the following information: - Login and password: Enter the user (default sa) and password (default maestro) that can access the RenderServer database. - Server name: Enter the host name of the server running the Render Server database as well as the instance name of the database. Example: qa-mserver-f\maestro - Database name: Enter the name of the Render Server database (default RenderServer). - Server type: Select the MSSQL database. - Authentication: Select the SQL Server Authentication. 3. Click the Login button to log in and open the Maestro | News Render Server Manager. 4. Define a rendering profile to specify the format and resolution of the images to be processed by the Render Server. Begin by clicking on the Profiles tab. 5. Double-click on one of the predefined profiles or define a custom profile by pressing the “+” button in the tool bar.

6. Adjust the configuration of the profile. Enter the name and choose the encoding method for the profile. When choosing the Layout, note the selected frame rate. The frame rates in the Maestro | News Render Server, the Maestro | RenderEngine and the VideoEngine need to correspond. Do not configure the fields in such a way that the final resolution is too high. A high resolution image slows down the preview generation process. 7. Once the profile is complete, click OK.

109 8. Next, you must configure a rendering channel. Begin by clicking on the Channels tab. 9. Click the “+” button in the tool bar to create a new Render channel.

10. Adjust the configuration of the profile: - Channel name: Enter the name of the Render channel. The Channel name must not contain spaces. - Under the Maestro | RenderEngine category, verify that the Local check box is selected. This document instructs you to install the Maestro Render Server and the Maestro | RenderEngine on the same server. Selecting “Local” assumes this was completed. - Output id: enter VE1 to point to the default channel id in the Maestro | RenderEngine settings. - API port: set the API port to 8765 - FS port: set the FS port to 8755 - Verify or configure the Output folder. The default value configured for this field is “G:\RenderServerOut”. However, an alternate path can be specified if preferred. 11. Click OK to save the profile. 12. Finally, start the Maestro | News Render Server application as an administrator. Click the Setup button to access the Render Server Setup window.

110 13. Set the “Channels limit” (up to 4 channels can be configured). The “Channel 1 name” should already have been configured during the Render channel setup process. If the channel does not have a name, assign one at this time. 14. Click OK to save the Render Server Setup window. 15. Click the Start button to start the server. After a few moments, you should see an “All channels are active” message indicating that the channel creation process was successful. The following image depicts the completed configuration:

111 To check or change the Maestro | RenderEngine frame rate: 1. Go to C:\Orad\RenderEngine64\bin and open the xml file. 2. In the Video section, check the value of the FieldsPerSecond.

To check the VideoEngine frame rate: 1. Login to the VideoEngine Websettings. 2. Check the value of the FPS.

When adding a new profile or editing an existing profile in the Maestro Render Manager, please note the frame rate of the selected layout:

Using Multiple Maestro | News Render Servers with the Same Database

You can install many Maestro | News Render Servers on separate machines and connect them to the same database (both Maestro | News asset database and the Render Server database). It will increase the overall performance - the render jobs will be spread over the machines. However, there is no guarantee that the work will be equally balanced between the machines.

112 Configuring Maestro | News Bus Services

Enabling the Services

The Maestro Monitor appears in Windows Services as the “Avid Maestro Monitor Service”. This service starts automatically when Windows starts up. The Monitor service is responsible for starting the other Maestro | News services that appear in the Monitor tool.

Now that the Maestro | News software is installed, use the Maestro Monitor application to verify that all services and applications are running.

To enable the Maestro services: 1. Open the Maestro Monitor application: From the Windows Start menu at: Start / All Programs / Avid / MaestroMonitor - or - Through the executable in the system file structure: C:\Orad\MaestroBusServices\MaestroMonitor.exe The Monitor tool opens, showing the services and their current status:

2. Verify that the Recovery mode for each service is set to Restart and that the Startup mode is set to Automatic. The Maestro | News Controller service (MaestroCtrl60.exe) is not required to be actively running during normal Maestro | News operation. This item can be configured differently than the other services and is an exception to this verification step. 3. If any services or applications other than MaestroCtrl60.exe are not running, click the Start button to start the services.

Verifying the Installation

Avid provides a user interface called the Avid ACS Monitor which can be used to verify the status and configuration details of the MediaCentral Platform Services system. Access the ACS Monitor to verify the status of the services on the MediaCentral Server.

113 The ACS Monitor is a powerful tool capable of not only viewing, but also modifying the MediaCentral Platform Services environment. Modifying services through this tool could result in service or system failures.

Accessing the Avid ACS Monitor Tool

For a detailed description of the Avid ACS Monitor tool, see the MediaCentral | Cloud UX Installation Guide.

Configuring Maestro | News ActiveX MOS Plugins to Work in Octopus

For more information about configuring ActiveX MOS plugins in Octopus, refer to the Octopus user guide. In the default Octopus installation, you can find the documentation in the following folders on the Octopus Server: • C:\octopus\server\documentation\AdminGuide • C:\octopus\server\documentation\UserGuide

The configuration described below only covers the most common scenario for Octopus 8.

Checking Prerequisites

The following prerequisites need to be met before configuring the Maestro | News ActiveX MOS plugins: 1. Octopus Server installed, configured and running. 2. Octopus Client installed on your workstation. 3. MaestroINEWSPlugin Plugin installed and configured on your workstation. 4. Maestro | Server is configured. 5. The MOS Server is installed, configured and running.

114 Configuring the ActiveX MOS Plugins

Start the Octopus Client to perform the configuration.

To configure the ActiveX MOS Plugins: 1. Login to the Octopus Client. 2. Go to Administration > MOS Devices > Devices and add a new device by clicking on New.

3. On the Basic tab, set the following parameters: a. mosID - enter the MOS ID (default ORADMOS, same as for the MOS Server). b. ncsID - enter your Octopus ID (default OCTOPUS). c. Version - select 2.6. d. Media host, Rundown host - enter the IP address. e. Octopus media port, Octopus rundown port - default ports are 10740 and 10741. f. Octopus IP address - IP address of your Octopus instance. 4. On the MOS objects tab, enable the Supports mosListAll option:

115 5. On the Other tab, enable the Send and receive times in UTC option. 6. On the Rundowns tab, set the following parameters: a. Set the Refresh method to roCreate. b. Enable the Send roMetadataReplace option. c. Enable the Send broadcast channel name option.

7. On the Status tab, enable the Accepts on-air status option. 8. On the Channels tab, enable the Accepts channels incoming from MOS device option. 9. On the Placeholders tab, set the following parameters: a. Enable the Allow MOS object creation option. b. In the Naming pattern of created MOS object enter %CDAY%CMONTH-%NAME- %ELABEL

116 10. In the Activations tab, enable Octopus NEWS.

11. On the Plugins tab, set the following parameters: a. Enable the MOS objects from plugins are private option. b. Enable the Pass user domain to plugins option. c. Click on Add to add a plugin.

12. Configure the plugin as described below: a. In the Short name and Long name fields, enter the aliases for your plugin - it can be any name, this name will appear in Octopus. b. In the Type field, select Browser (ActiveX).

117 c. In the Version field, select 1.0 iNews. d. In the Platform field, select ActiveX. e. In the Placement field, select None. f. Enable the Show use option. g. In the Implementation field, enter the GUID of the MaestroINEWSPlugin, e.g.: {5B4E4114-AAC4-47CE-AB6E-E88D00241479}

Verifying the Configuration

To verify the configuration of the ActiveX MOS plugin, follow the steps below: 1. Select any rundown, select a story and edit a story. 2. Select the location of an object within text and right-click to display the context menu. 3. Select New / Create using to insert a new MOS object.

4. You should now see the ActiveX plugin content.

118 Configuring Maestro | News HTML5 MOS to Work in Octopus

For more information about configuring HTML5 MOS plugins in Octopus, refer to the Octopus user guide. In the default Octopus installation, you can find the documentation in the following folders on the Octopus Server: • C:\octopus\server\documentation\AdminGuide • C:\octopus\server\documentation\UserGuide

The configuration described below only covers the most common scenario for Octopus 8.

Checking Prerequisites

The following prerequisites need to be met before configuring the Maestro | News ActiveX MOS plugins: 1. Octopus Server installed, configured and running. 2. HTML5 MOS Plugin installed and configured (e.g. on the Maestro | News Server). 3. Octopus Client installed on your workstation. 4. Maestro | News Server is configured. 5. Maestro | News Bus Services are installed, configured and running in the REST mode. 6. MOS Server is installed, configured and running.

Configuring the Maestro | News HTML5 MOS Plugin

Start the Octopus Client and configure it as described in the chapter “Configuring the ActiveX MOS Plugins” on page 115.

To configure the Maestro | News HTML5 Plugin: 1. Edit your device, go to the Plugins tab and click Add. Enter the required parameters: a. In the Type field, select Browser (ActiveX). b. In the Version field, select 2.8_Web. c. In the Platform field, select Chrome (CEF). d. In the Placement field, select Modeless. e. Enable the Stretch when inline and Run in separate thread options. f. In the Implementation field enter, the URL of the Maestro | News HTML5 MOS Plugin.

119 2. Click OK to save the configuration and close the window.

Verifying the Configuration

To verify the configuration of the HTML5 MOS plugin, follow the steps below: 1. Select any rundown, select a story and edit it. 2. Select the location of an object within text and right-click on it to display the context menu. 3. Select New / Create using to insert a new MOS object.

4. You should now see the HTML5 plugin content.

120 Configuring Maestro | News ActiveX MOS Plugin to Work in AP ENPS

For more information about configuring ActiveX MOS plugins in AP ENPS, refer to the AP ENPS user guide. The chapter ENPS System Maintenance / MOS Configuration in the ENPS Operations Guide will be the most helpful source of information.

The configuration described below only covers the most common scenario for AP ENPS 8.2.1.

Checking Prerequisites

The following prerequisites need to be met before configuring the Maestro | News ActiveX MOS plugins: 1. ENPS Server installed, configured and running. 2. ENPS Client installed on your workstation. 3. Maestro | News MOS28 Plugin installed and configured on your workstation. 4. Maestro | News Server is configured.

Configuring the Maestro | News ActiveX Plugin for AP ENPS

For a detailed description of how to configure the ActiveX MOS plugins, refer to the AP ENPS documentation.

To configure the Maestro | News ActiveX Plugin: 1. Run ENPS System Maintenance. 2. Select MOS Configuration. 3. Add a new entry and set the required parameters: a. In the Address field, enter the name (it is recommended to use the same as MOS ID [default ORADMOS]). b. In the Description field, enter a short alias for your plugin. c. In the IP field, enter the IP Address of the ENPS Server. d. In the ActiveX field, enter MaestroMOS28.MaestroMOS.

121 e. In the MOS Version field, select 2.8. f. In the Modal UI ActiveX field, enter ENPSHTMLHost.

4. Save the changes and restart the ENPS server.

Verifying the Configuration

To verify the configuration of the ActiveX MOS plugin, follow the steps below: 1. Run the ENPS Client, login, and create a new rundown.

2. Name your rundown in the Title field, set the End Time to somewhere in the future.

122 3. Set the Add MOS Durations option to 1-Yes, in the MOS Allow field select your plugin as defined during the configuration, enable the MOS Control Active option. 4. Save your settings. 5. Insert a new row and select it.

6. Enable the MOS Control Active option if it is not enabled already.

7. Click in the row content area, then select MOS / .

123 Configuring Maestro | News HTML5 MOS to Work in AP ENPS

Checking Prerequisites

The following prerequisites need to be met before configuring the Maestro | News ActiveX MOS plugins: 1. ENPS Server installed, configured and running. 2. HTML5 MOS Plugin installed and configured (e.g. on Maestro | News Server). 3. ENPS Client installed on your workstation. 4. Maestro | News Server is configured.

Configuring the Maestro | News HTML5 MOS Plugin

For a detailed description of how to configure the ActiveX MOS plugins, refer to the AP ENPS documentation.

To configure the Maestro | News HTML5 Plugin: 1. Run ENPS System Maintenance. 2. Select MOS Configuration. 3. Add a new entry and set the required parameters: a. In the Address field, enter a name. b. In the Description field, enter a short alias for your plugin. c. Leave the IP field blank. d. In the ActiveX field, enter ENPSHTMLHost. e. In the Default Settings, set URL=. f. In the MOS Version field, select 2.8. g. In the Modal UI ActiveX field, enter ENPSHTMLHost.

h. In the Default Settings, set URL=. 4. Save the changes and restart the ENPS server.

124 Verifying the Configuration

To verify the configuration of the HTML5 MOS plugin, follow the steps below: 1. Run the ENPS Client, login, and create a new rundown.

2. Name your rundown in the Title field, set the End Time to somewhere in the future.

3. Set the Add MOS Durations option to 1-Yes, in the MOS Allow field select your plugin as defined during the configuration, enable the MOS Control Active option. 4. Save your settings. 5. Insert a new row and select it.

125 6. Enable the MOS Control Active option if it is not enabled already.

7. Click in the row content area, then select MOS / .

Configuring MOS Server and MOS-aware Communication with MediaCentral | Newsroom Management

Configuring the MOS Server

Start the Avid MOS Server to configure it.

To configure the MOS Server: 1. On the MOS tab, set the following options: a. NCS / Host - MediaCentral | Newsroom Management MOS Gateway IP address. b. NCS / ID - MediaCentral | Newsroom Management Server host name. c. MOS / MOS ID - Orad MOS ID, usually ORADMOS.

126 2. On the Database / GAM tab, set the following options: a. Database / Host - host name and instance name of the MOS database (CYBERGRAPHICS), example: qa-maestroserver-b\MAESTRO b. Database / Database Name - name of the MOS database, default is CYBERGRAPHICS. c. Database / User Name and Database / Password - user name and password to the MOS database, default is sa / maestro.

3. On the CygClients tab, set the IPs of your MOS Clients (IPs of machines where Maestro | News Controller applications are installed; only these applications will be able to receive rundowns).

127 4. Finally, go to the Service tab and start the service by clicking on Start Service. Look at the logs if there are any errors.

Configuring MediaCentral | Newsroom Management to Work with MOS Server

To configure MediaCentral | Newsroom Management to work with MOS Server: 1. Login to the MediaCentral | Newsroom Management Client (default user / password is avstar / avstar).

2. Go to SYSTEM / MOS-MAP and edit the following entry. a. between TABLE-START and TABLE-END insert a line with your ORAD MOS ID (default ORADMOS) and the name of the device: orad. example: ORADMOS orad

128 3. Go to SYSTEM / MAP and change the settings for the rundowns that you wish to monitor and synchronize: a. Add entries for any rundown you want to monitor, example: show.training.rundown show.training - monitor 1815 mossvr INEWSMOSGWHOSTNAME - - mos orad

n Please note that Simplified Metadata should be enabled in Maestro | News MOS Plugins:

129 Configuring ASF Graphics Device Service for MediaCentral | Command Integration

The Avid Services Framework (ASF) software and the ASF Graphics Device Service software are required when integrating the Maestro | News system using MediaCentral | Command.

Before installing the ASF software, ensure the following requirements are met: 1. The Maestro | News Server’s timezone is correct and that the date & time are correct. 2. The Maestro | News Server’s domain name extension is set, and that this server is defined in the DNS. 3. The network device used to connect to the ASF framework is on the top of the network adapter binding order.

To install Avid Services Framework Graphics Device Service: 1. Install the ASF software as an Avid Service Framework Client. Open the ASF Workgroup Properties and confirm the ASF workgroup name is correct, that the lookup server is defined, and that the System Check passes. 2. Install the MediaCentral | Command Graphics Device Service (GDS). 3. The Maestro | News installers provide a set of software components for the Command GDS plug-in. Copy the respective files from this set to the following folders: C:\Program Files (x86)\Avid\iNEWS Command\device\avidgraphicdeviceservice \bin\AppForAvidGraphicDeviceService.exe \lib\GraphicDeviceMaestroPlugin.dll \lib\GraphicDeviceMaestroPlugin.pdb \lib\codebase\avid_graphic_device_maestro_plugin-dl.jar \plugins\avid_graphic_device_maestro_plugin.ja 4. Using the ASF Workgroup Properties application, ensure that the GDS is enabled and running.

130 5. Run the ASF Service Configuration application to configure the GDS. 6. Select “Maestro” as the plug-in type.

7. Give this device an AMCP name. This name will be used when defining the device channels in Command

8. Set the IP address of the Maestro | News Server, i.e. the Maestro | News Server itself, if the GDS is running on the Maestro | News Server.

131 Configuring OradControl

To configure OradControl: 1. Run the Maestro | News Controller. 2. Configure your PGM channels if they are not already configured. 3. Go to Customize / Settings and select the Automation section. 4. Click on the plus (+) sign in the Automation devices group. A new row appears. In the Type column, select OradControl.

You can also change the name of your device by double-clicking on the name. 5. Connect the PGMs (select Control / Connect renderer(s)) 6. Your device name and its status will be displayed on the status bar . 7. Click on the device name on the status bar. The indicator should change its color to yellow which means that it is awaiting connections . 8. Run the OradControl application on your device. Enter the IP or host name of the machine with the Maestro | News Controller as well as the port (the same as entered in the configuration above). Finally, press Connect.

9. You should be able to see a list of rundowns loaded in the Maestro | News Controller (if you don't have any rundowns in the Maestro | News Controller, you can create a new one, then click the Refresh button in the OradControl application).

132 10. Click and hold on a rundown name, then release the mouse button. It should load into the OradControl application.

11. Perform some tests to check if everything is working correctly.

133 4 Upgrading Components

Topics in this chapter include: • Version Compatibility Matrix • Installing Several Versions of Specified Component • Migrating Maestro | News Asset Database

Version Compatibility Matrix

Different versions of Avid Maestro | News support different versions of other components, especially Avid Maestro | RenderEngine and Avid VideoEngine components. Also, the Asset and RenderServer databases differ between various versions of Maestro | News.

Maestro | News Maestro | Core

Asset RenderServer VideoEngine Maestro | Components database Database RenderEngine Maestro | Designer

2019.2 Native2 142 2.1 2019.1 2018.12 2018.12 IBIS iFind 4.5 (only Bus Services)

2018.11.x (>= Native2 142 2.1 2018.8 2018.12 2018.12 2018.11.1)

2018.11.0 Native2 142 2.0 2018.8 2018.12 2018.12

2018.6.x Native2 142 2.0 2018.5 2018.6 2018.6

(>=2018.6.3) 2018.8

2018.6.x Native2 142 2.0 2018.5.1 2018.6 2018.6 (<=2018.6.2)

7.5.x (>=7.5.1) Native2 142 2.0 4.2.3 7.3 1.3 4.2.5

7.5.0 Native2 142 2.0 4.2.3 7.3 1.3

7.4.x Native2 141 1.9 4.2.1 7.2 1.3

7.3.x Native2 136 1.6 4.0 7.1 1.2 Native 12

7.2.x Native2 133 1.4 4.0 7.1 1.2 Native 12 Maestro | News Maestro | Core

Asset RenderServer VideoEngine Maestro | Components database Database RenderEngine Maestro | Designer

7.1.x Native2 133 1.4 3.5 7.0 1.2 Native 12

7.0.x Native2 133 1.4 3.5 7.0 1.2 Native 12 IBIS iFind

6.9.x Native 12 1.4 not supported 6.10 1.0 IBIS iFind

6.8.x Native 12 1.4 not supported 6.9 3Designer 3.11 IBIS iFind

When upgrading Maestro | News components, the corresponding components must be upgraded too.

The MOS Server has a different versioning scheme than the Maestro | News components. For more n information, see “Components” on page 11.

Installing Several Versions of Specified Component

Some Maestro | News components can be installed in different versions on the same machine - but only if the release version is different for each component, e.g. version 7.3.x.x, 7.4.x.x and 7.5.x.x. In some cases it is not permitted due to fact that they register an ActiveX control under a specified name, and there cannot be more than one ActiveX control with the same name.

Components that can be installed in different versions on the same machine: • Maestro | News Controller • Maestro | News GAM Access 32 bit and Maestro | News GAM Access 64 bit • Maestro | News Journalist Station

When using several versions of a given component (not recommended), check the dependencies of that component, such as the Maestro | News database version, VideoEngine, Maestro | RenderEngine, Maestro | Designer.

You need to configure access to the Maestro | News database of the correct version and activate the specific version of Maestro | RenderEngine.

It is possible to have multiple versions installed on one machine, but it is not permitted to run n multiple version of the Maestro | News components simultaneously

Mixing versions of components in your environment is a configuration that is not supported by Avid.

135 Migrating Maestro | News Asset Database

Major changes were implemented between Maestro | News v5 and Maestro | News v.6/7 generation.

To properly migrate the Maestro | News asset database (Native) form Maestro | News 5.x versions, follow the below steps: 1. In Maestro | News 5.x, open the rundown you want to export and save if under Folder type. 2. Using Maestro | News 7.x version that supports Native database (7.3 or older) and connect to the Maestro | News 5 database directly. 3. Open the rundown and save it under a new name. 4. Using the Maestro Sync tool 7.x (7.3 or older) connect to the Maestro | News v5 database and export the saved rundown directly to maestro_2 on the SQL Server 2012 (or to a new SQL.light (db) file).

136 5 Maintenance

This chapter contains information on how to perform preventative maintenance on your Maestro | News system, as well as how to troubleshoot your system when problems or failures occur.

Topics in this chapter include: • Modifying the Installation • Logs and Crash Dumps • Test Tools • Importing Content • Recurring activities • Troubleshooting

Modifying the Installation

To modify, repair or uninstall a given component: 1. Run the component installer from :\Orad\Installers folder. Or open the Control Panel, select Programs and Features, select component then click Change. 2. The “Welcome to Maintenance” window appears.

3. Follow the instructions listed in the below topics.

Modifying the Installation

When you need to modify the component, select Modify in the Maintenance window. Click Next to open the configuration window. Complete the installation as described in the topic “Generic Installation Process” on page 42. Repairing the Installation

The repairing process copies all the files (except for the settings).

To repair the installation: 1. Select Repair, then click Next. For some components, additional window appears where you can enable the Maestro Monitor auto start:

Click Next to continue. 2. The “Ready to install” window appears:

Click Next to proceed. 3. When the installation has concluded, the “Setup Complete” appears. Click Finish to exit the installer.

138 Removing Components

When removing a component. the process deletes all component files and registry entries. When removing certain components, ActiveX controls are unregistered as well.

To uninstall components: 1. In the Maintenance window, select Remove. 2. In the Ready to install window, click Next. 3. After the component has been removed, a confirmation window is displayed:

4. Click Finish.

Notes

In some cases, the installer can ask you about the original setup sources folder:

139 Point to the folder where the original installer is located, then click OK.

Logs and Crash Dumps

Browsing Logs

Most of the log files can be browsed using the Avid Log Viewer application. This application is installed by several Maestro | News components. Look for the LoggerGUI.exe or LoggerGUI60.exe files in the target installation directory of the component.

Run the Avid Log Viewer, then go to the File / Open menu and select the log file (log files have an m6l extension, except for the MOS Server and MediaCentral | Maestro News logs).

Default location of the log files: • Most of the components: \logs • MediaCentral | Maestro News: there is no separate log file, for general log messages please look into: /var/log/avid/avid-interplay-central/interplay_central.log •MOS Server: :\Orad\MOSGateway2\Logs\

For information how to change the default location of log files in the Maestro | News Controller, Page Editor or Journalist Station, refer to the Maestro | News User Guide.

The list below presents default locations for logs of other Avid components: • Maestro | RenderEngine for Windows: :\Orad\RenderEngine64_\bin\ - look for *.log files (usually RE.log). • VideoEngine for Windows: - :\Orad\VEServerWin\VE\bin\ve.log - :\Orad\VEServerWin\VECommander\bin\OCIP.log - :\Orad\VEServerWin\VECommander\bin\commander.log

140 • Maestro | RenderEngine for Linux: /data/RE/bin - look for *.log files (usually RE.log or RE0.log) • VideoEngine Linux: - /data/VE/bin/ve.log - /data/VECommander/bin/OCIP.log - /data/VECommander/bin/commander.log

Crash Dumps

Some applications within components can catch abnormal operations and generate a crash dump file. In case of a crash, the component will display an appropriate message:

These dump files are very useful for the Maestro | News development team. They can help diagnose and fix the problem. Dump files of Maestro | News components are ZIP archives containing usually logs and settings files.

Browsing Logs and Checking Issues in HTML Components

In case of issues with Maestro | News HTML5 MOS Plugin, you can use the built-in development tools of your internet browser to diagnose the source of any issues.

You can filter messages in the Console tab to display only Maestro | News related logs by entering the phrase ‘maestro’ in the filter box.

141 Test Tools

There are several test tools shipped with various Maestro | News and other Avid components that can help to diagnose potential problems. The most important tools and their locations are: • Maestro | News Render Server component: - DB API Test Application Tool - Simulate client requests to Maestro | News Render Server - :\Orad\MaestroRenderServer64\DBAPITestApplication.exe • Automation Protocols component: - CII Test Tool - Simulate Chyron Intelligent Interface (CII) protocol requests - :\Orad\AutomationProtocols64\CIIAx\CII_Test.exe - VDCP Test Tool - Simulate Harris VDCP protocol requests - :\Orad\AutomationProtocols64\VdcpAx\VDCP_Test.exe

Basic Example of the DB API Test Application Tool

To work with the DB API Test Application Tool: 1. Run DB API Test Application tool and login to the Render Server database:

2. When the main window appears, choose the Clients (E|DBClient) tab if you want to simulate client requests:

142 Select the Client: ‘theClient_1’ check box, enter the item ID in the Data field and finally press Add & Start to send a request to the Maestro | News Render Server. The bottom panel displays log messages.

Basic Example Instruction of the CII Test Tool

Please note that CII test Tool requires .NET Framework 3.5 (includes .NET 2.0 and 3.0) to run. Make sure you have this required prerequisite installed first.

143 To work with the CII Test Tool: 1. Run the CII Test Tool:

2. Select Host and Port, then click Connect. 3. Enter the item ID in the appropriate field. 4. The allowed values display modes in the Display Mode field are: 1 - Cue, 2 - Play, 3 - Out, 4 - Preload.

The Play options (playWithPause, playNoPause) operate on the last cued item. The Abort option n (abortPlayingAnimation) operates on the last platyed item.

The readAndUpdate option has the same functionality as the Cue operation in the Maestro | News n Controller. The playNoPause option corresponds to Play and the abortPlayingAnimation functions in the same way as the Out option of the Maestro | News Controller.

Basic Example Instruction of the VDCP Test Tool

Please note that VDCP Test Tool requires .NET Framework 3.5 (includes .NET 2.0 and 3.0) to run. Make sure you have this required prerequisite installed first.

144 To work with the VDCP Test Tool: 1. Run the VDCP Test Tool

2. Select the Host and Port, then click Connect. 3. Enter the item ID in the appropriate field. 4. Execute the command of your choice (e.g. Cue, Play, Stop).

Importing Content

When importing content, remember to import both the asset database and the corresponding shared data files. Otherwise, the imported content cannot work properly.

Importing the Asset Database

Use the Maestro Sync Tool to import an asset database. Fore more information, refer to the Maestro | News User Guide.

Importing Shared Data

Compress your files into a ZIP archive. Unzip the archive on the dedicated computer, and copy the files into your Shared Data folder (usually the G: drive). Make sure to retain the correct directory structure.

Recurring activities

This chapter describes maintenance activities that should be performed periodically on systems containing Maestro | News components.

145 Cleaning the Maestro | News Render Server Database and Files

The RenderServer database contains render channels and rendering profiles previously created by the system administrator. It also stores old completed render jobs. It is very important to keep this database clean, as it used by the MaestroBusServices cache. The MaestroBusService uses cache to avoid rendering the same pages several times.

You can define whether you want to use cache in your installation. Add the following parameter to the MaestroBusService SystemSettings.ini file:

The ClipExpirationPeriod parameter determines how old (in days) the render jobs can be. You can disable cache by entering “-1” in this field.

The cleaning process is different for systems with enabled and disabled cache: • Disabled cache - Old render files can be simply removed from the assigned location. It is strongly recommended to clean the database periodically to reduce the database size. • Enabled cache - Remove the old render files only when they are older than the time set in the ClipExpirationPeriod parameter. If there is a need to remove all render files (server machine will be changed, etc.), you need to perform database cleaning immediately after deleting the files. Otherwise, you can encounter an “Unavailable graphic tile” error.

How to remove render files:

To find the location of the render files, run the MaestroRenderManager. Go to the “Completed” tab and find the “File Location” path. Jobs rendered from MediaCentral | Cloud UX have files placed in one folder, but renders from test application are placed directly in the result localization.

146 How to clean old completed render jobs from the RenderServer database?

To clean old RenderServer jobs from the database, you need to use the SQL Server Management Studio. Connect to the SQL server and find the RenderServer database. Run the following script: USE ; TRUNCATE TABLE dbo.CompletedRequests;

For example: USE RenderServer_76; TRUNCATE TABLE dbo.CompletedRequests;

These commands should not be run while other systems are requesting rendered data. Execute these n commands only when you are sure that no other system is accessing the rendering result.

Cleaning the Maestro | News Controller Rundowns

When rundowns come from automation systems, you should periodically check their size. According to the Maestro | News Controller requirements, you should assume that you require at least 4 GB of RAM for every 1000 items on your opened rundown. The exact required memory size may vary depending on the type and complexity of your items. If your rundown is about to exceed the number of items allowed by the size of the memory, then consider removing some items from the rundown. n Large rundowns can decrease the overall system performance. Review how fast your rundown is growing periodically to plan the frequency of cleaning.

Backup databases

For simple cases you can use the Maestro Sync plugin (available with the Maestro | News Controller component) to create asset database backup and to restore the backup.

For regular backups, it is recommended to use the standard MS SQL backup tools. Refer to the MS MQL backup guides.

You should also backup your Render Server and MOS Server databases.

This activity should be performed quite often - depending on the volume and severity of your data.

147 Backup Shared data files

Use 3rd party file-based backup tools to backup Shared Data.

This activity should be performed quite often - depending on the volume and severity of your data and durability / stability of your file storage.

Cleaning logs

You should periodically check the size of your logs folders and remove old logs. See the Logs and Crash Dumps chapter for the location of the logs folder.

Backup Stations

You can also use 3rd party “Shadow copy” software to create an exact copy of your stations (e.g. Playout or Editing station). Generally, such action should be performed before or after a major software update.

Other activities you should consider 1. Please disable all inactive or unused Media Central | Asset Management (Interplay| MAM), MediaCentral | Graphics Management (Maestro GMAM) and MediaCentral | Production Management (Interplay | PAM) systems in the Maestro | News Controller because when the Controller is trying to connect to an inactive system it may slow it down considerably. 2. If your Maestro | News Controller or any Maestro | News plugin freezes from time to time, then check your network bandwidth. Also check if no other application is utilizing the network bandwidth or the CPU. Especially, check the network capacity between your Playout / Editing station and the servers (database server and file server). 3. Large number of graphic pages / items stored in one asset folder may also decrease the performance. Use the AssetBrowser within the Maestro | News Controller to manage your stored items and consider creating new folders / sub folders and moving some items to new locations. 4. Review your data sources in Maestro | News Controller - the data source with data on a slow remote medium may cause serious performance decrease.

For the simplest cases using the Windows Task Manager's Performance tab should be enough to monitor your system performance, and the Processes tab for finding the software which can cause performance decrease.

Troubleshooting

Checking existing database version

To check the existing database version: 1. Login to your Maestro | News Server (your machine with the database). 2. Run the SQL Server Management Studio. 3. Login to the Maestro | News database instance (default credentials are sa / maestro; use the SQL Server Authentication)

148 4. Expand your instance / Databases.

5. To check the asset database version, right-click on dbo.Version table and choose Select Top 1000 Rows. 6. The query result will be shown:

149 7. Read the largest VersionNumber value on the Results pane (it might be many versions, remember to read largest version value). E.g.: the Maestro | News 7.5.x uses the asset database version 142.

Checking the RenderServer Database Version

You can see one or more RenderServer_x databases. Expand the database of your choice, and then expand / Tables.

To check the RenderServer database version: 1. Right click on dbo.RSVersion table and choose Select Top 1000 Rows.

2. A query result is displayed:

3. Read the largest Version value on the Results pane, for example: the Maestro | News 2019.2.x version uses RenderServer database version 2.1.

150 Changing Components Settings Manually

Any manual changes should be performed very carefully. It can lead to problems with c investigating errors.

Changing the Settings File

Most components have the SystemSettings.ini file in their target installation directory. This file is in the .ini format and can be edited using a text editor, such as Notepad.

Changing the Registry Entries

Most components have settings stored in the registry: • HKEY_CURRENT_USER\Software\Orad\ • HKEY_LOCAL_MACHINE\SOFTWARE\Orad\ • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Orad

These settings can be changed using a standard Windows tool called Registry Editor.

151