Avid Maestro | Newsresources.avid.com/SupportFiles/attach/Maestro/Maestro_News... · Avid Maestro |...

Avid Maestro | News
Installation and Configuration Guide
Version 2018.6

Legal NoticesProduct 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.

Copyright © 2018 Avid Technology, Inc. and its licensors. All rights reserved.

Copyright 2003-2007 of MOG Solutions

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.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:

Copyright © 1988–1997 Sam Leffler Copyright © 1991–1997 Silicon Graphics, Inc.

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.

This Software may contain components licensed under the following conditions:

Copyright (c) 1989 The Regents of the University of California. All rights reserved.

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.

Copyright (C) 1989, 1991 by Jef Poskanzer.

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.

Copyright 1995, Trinity College Computing Center. Written by David Chappell.

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.

Copyright 1996 Daniel Dardailler.

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.

Modifications Copyright 1999 Matt Koss, under the same license as above.

2

http://www.avid.com/US/about-avid/legal-notices/patent-marking

Copyright (c) 1991 by AT&T.

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 Altura Software, Inc. for the use of its Mac2Win software and Sample Source Code:

©1993–1998 Altura Software, Inc.

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/).

© DevelopMentor

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

COPYRIGHT file which is included in the distribution:

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.

Portions copyright © 2012 Avid Technology, Inc.

3

http://www.apache.org/

http://jcifs.samba.org/

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 v2018.6 • Created 6/28/18 • 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Maestro | News Supported Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Avid Software Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Third Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Automation Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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 | UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

HTML5 MOS Plugin integration with NRCS and MediaCentral | Cloud UX . . . . . . . . . . . . 29

MOS Plugin Integration with Avid MediaCentral | Newsroom Management . . . . . . . . . . . . 30

Controller Integration with Avid MediaCentral | Newsroom Management using MOS Server. . 30

Controller MOS-less Integration with Avid | Newsroom Management . . . . . . . . . . . . . . . . 31

Integration with Avid MediaCentral | Asset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Integration with Avid MediaCentral | Production Management and Avid NEXIS . . . . . . . . 32

MOS-less integration with Avid MediaCentral | Command . . . . . . . . . . . . . . . . . . . . . . . . . 33

Integration with Avid Media Composer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Example of a More Complex Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Verifying and Applying Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Installing VideoEngine for Windows for Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Installing VideoEngine for Windows for Maestro | News Render Server . . . . . . . . . . . . . . . . . . . 37

Notes for Installing Video Engine for Windows for Maestro | News Render Server. . . . . . . 37

Notes for Installing VideoEngine for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing other Avid components or Components from other Vendors . . . . . . . . . . . . . . . . . . . . 40

Obtaining and Verifying Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Verifying the Integrity of the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Installing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Installing Maestro | News from the GraphicsSuite Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Component Names Used by the GraphicssSuite Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installing Maestro | News from Individual Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Additional Steps Required for Specific Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Maestro | News Bus Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Maestro | News Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Maestro | News IPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Maestro | News ENPS Plugin (32 and 64 bit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Maestro | News GAM Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Maestro | News iNews Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Maestro | News iNews Simple Plugin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Maestro | News NLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Maestro | News MOS28 Plugin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

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

Maestro | News Render Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

MediaCentral | Maestro News. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Installing HTML5 MOS Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Notes About Running Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Applying Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

License Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

6

Licenses List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Checking Available Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Testing Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuring DVG to Play Maestro | News Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Using MediaCentral | Asset Management Assets on Maestro | News Pages . . . . . . . . . . . . . . . . . 89

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

Configuring MAM file transit using Maestro GMAM / MediaCentral | Asset Management . . . . 94

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Known Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Configuring MediaCentral | Production Management and NEXIS Connection . . . . . . . . . . . . . 103

Checking MediaCentral | Production Management Configuration with MediaCentral | UX 103

Configuration of the NEXIS Client Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Checking status of Interplay Production Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuration of Interplay Production Connectivity Toolkit (PAMCTC) . . . . . . . . . . . . . 108

Configuration of Local VideoEngine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Configuring MOS-less Communication with MediaCentral | Newsroom Management . . . . . . . 109

Veryfing MediaCentral | Newsroom Management WS API configuration . . . . . . . . . . . . . 109

Configuring MediaCentral | Newsroom Management Web Services. . . . . . . . . . . . . . . . . . 110

Verifying the Connection from the Maestro | News Controller . . . . . . . . . . . . . . . . . . . . . . 113

Configuring Maestro | News Render Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring Maestro | News Bus Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Enabling the Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Verifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Accessing the Avid ACS Monitor Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Configuring MediaCentral | Maestro News . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Mounting Shared Data share. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Mounting Render Server output share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Updating gateway configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Enabling MediaCentral | Maestro News plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Configuring users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Configuring the MediaCentral | UX System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Using MediaCentral | Asset Management Assets on Maestro | News Pages . . . . . . . . . . . . 126

Veryfing the MediaCentral | UX Sequence sSettings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Configuring MOS Plugin to Work with MediaCentral | UX Desktop App . . . . . . . . . . . . . . . . . 128

Configuring Maestro | News ActiveX MOS Plugins to Work in Octopus. . . . . . . . . . . . . . . . . . 130

Checking Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Configuring the ActiveX MOS Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

7

Verifying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Configuring Maestro | News HTML5 MOS to Work in Octopus . . . . . . . . . . . . . . . . . . . . . . . . 135


Configuring the Maestro | News HTML5 MOS Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135


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


Configuring the Maestro | News ActiveX Plugin for AP ENPS. . . . . . . . . . . . . . . . . . . . . . 137


Configuring Maestro | News HTML5 MOS to Work in AP ENPS . . . . . . . . . . . . . . . . . . . . . . . 140


Configuring the Maestro | News HTML5 MOS Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140


Configuring MOS Server and MOS-aware Communication with MediaCentral | Newsroom Manage-ment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Configuring the MOS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Configuring MediaCentral | Newsroom Management to Work with MOS Server . . . . . . . 144

Configuring ASF Graphics Device Service for MediaCentral | Command Integration. . . . . . . . 146

Configuring OradControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Chapter 4 Upgrading Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Version Compatibility Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Installing Several Versions of Specified Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Migrating Maestro | News Asset Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Chapter 5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Modifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Modifying the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Repairing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Removing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Uninstalling MediaCentral | Maestro News . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Logs and Crash Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Browsing Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Crash Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Browsing Logs and Checking Issues in HTML Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Test Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Basic Usage Instruction of the DB API Test Application Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Basic Usage Instruction of the CII Test Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Basic Usage Instruction of the VDCP Test Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Importing Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Recurring activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

8

Cleaning the Maestro | News Render Server Database and Files. . . . . . . . . . . . . . . . . . . . . . . . . 162

Cleaning the Maestro | News Controller Rundowns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Backup databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Backup Shared data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Cleaning logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Backup Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Other activities you should consider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Checking existing database version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Checking the RenderServer Database Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Changing Components Settings Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

9

Using This Guide

Symbols and Conventions

Avid documentation uses the following symbols and conventions:

Symbol or Convention Meaning or Action

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

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

wA warning describes an action that could cause you physical harm. 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 only), (Macintosh), or (Macintosh only)

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

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 an experienced personnel or by Avid support team members.

Version

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

Components

Full List of Components

The Maestro | News v2018.3 system includes the following 18 components (listed in an alphabetical order):

• Maestro | News Bus Services

• Maestro | News Controller

• Maestro | News ENPS Plugin 32 bit

• Maestro | News ENPS Plugin 64 bit

• Maestro | News GAM Access Plugin 32 bit

• Maestro | News GAM Access Plugin 64 bit

• Maestro | News iNews Plugin

• Maestro | News iNews Simple Plugin

• Maestro | News IPM

• Maestro | News Journalist Station

• Maestro | News MOS28 Plugin

• Maestro | News NLE

• Maestro | News PageBrowser Plugin 32 bit

• Maestro | News PageBrowser Plugin 64 bit

• Maestro | News Render Server

• MediaCentral | Maestro News

• MOS Server

• Orad Control

• Maestro | News HTML5 MOS Plugin

The Maestro | News Controller can be run in 3 modes:

• Standard Mode (Controller + PageEditor),

• PageEditor Only,

• FastServe | Playout Mode

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.

• MediaCentral | Maestro News can be referred to as "MaestroUX" in other documents.

Component Groups

Some components may be grouped in the following way:

Machine Roles

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

Component Group Name Components

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

- MOS Plugins

(both ActiveX and HTML5 plugins)

Maestro | News ENPS Plugin 32 bit, Maestro | News ENPS Plugin 64 bit, Maestro | News iNews Plugin, Maestro | News iNews Simple Plugin, Maestro | News MOS28 Plugin, Maestro | News HTML5 MOS Plugin

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

- MediaCentral | UX integration

Maestro | News Bus Services, MediaCentral | Maestro News

12

Applications within Components

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

Machine Role Main Components and other Software

- Maestro 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 | Render Engine for Windows

- Playout Station Maestro | News Controller, VideoEngine for Windows and Maestro | Render Engine for Windows

- Editing Station NLE software (e.g. MediaComposer), Maestro | News NLE and Maestro | Render Engine for Windows

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

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

- DVG HDVG or Blend or FastServe | Playout

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 32 bit

ENPS MOS ActiveX Plugin 32 bit

- Maestro | News ENPS Plugin 64 bit

ENPS MOS ActiveX Plugin 64 bit

- Maestro | News GAM Access Plugin 32 bit

GAM Access ActiveX Plugin 32 bit, GAM Accessor Test Tool

- Maestro | News GAM Access Plugin 64 bit

GAM Access ActiveX Plugin 64 bit, GAM Accessor Test Tool

- Maestro | News iNews Plugin

iNews MOS ActiveX Plugin

- Maestro | News iNews Simple Plugin

iNews Simple MOS ActiveX Plugin

- Maestro | News IPM Maestro IPM Server

- Maestro | News Journalist Station

Journalist Station, Log Viewer

13

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 at:

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

- Maestro | News MOS28 Plugin

MOS 2.8 ActiveX Plugin

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

- Maestro | News PageBrowser Plugin 32 bit

Page Browser ActiveX plugin 32 bit

- Maestro | News PageBrowser Plugin 64 bit

Page Browser ActiveX plugin 32 bit

- Maestro | News Render Server

Render Server, Render Manager, DB API Test Application Tool

- MediaCentral | Maestro News

MaestroUX Main Plugin, maestro-ux Plugin, maestro-ux-media-browser Plugin

- MOS Server MOS Gateway Service, MOS Gateway GUI

- OradControl OradControl Application

- Maestro | News HTML5 MOS Plugin

HTML5 MOS Plugin

Component Applications

14

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

2 Requirements


• 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 | Render Engine) require their own licenses.

Database Server

Most components require a database (on the Microsoft SQL Server) in order to work. Maestro | News works with three 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.

Shared Data

Most components require Shared Data to work properly. Shared data is a folder (usually 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 and Maestro | Render Engine.

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, MOS plugins

1433-34 Connection to MS SQL server

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 (formerly Interplay MAM) 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

16

Most of components (both Maestro | News components and non Maestro | News 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 ":<port_number>" (e.g.: netstat -ano | findstr ":8080").

The command returns the display protocol, source and destination etc.; the last number is a PID of the process that is using the port.

• on Linux: netstat -tulpn | grep <port_number> (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.

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

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-10541

Lower and upper communication port with iNews MOS Gateway

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 Video Engine Web Control Panel

8735-55 ReTalk2

8745 ReTalkXML

8765-85 ReTalk3

9901 MediaCentral | Asset Management (formerly Interplay MAM) Administrator web and Desktop web

9911 MediaCentral | Asset Management (formerly Interplay MAM) Control Center web

Default Ports

Components Port(s) Description

17

Machine Requirements

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

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

Machine Role Minimal Recommended

Maestro Server Single machine (single node):

• Operating system: Windows server 2012

• Processor: Dual Xeon e5 processor

• Memory: 32GB RAM

• Disk: 500GB SSD System disk

• Disk: Redundant RAID with 8TB of effective storage

• Network: 2x Gigabit Ethernet interfaces

• Other: 2 free USB ports

• Power: Dual power supply


Redundand two nodes, each node specification:

• Operating system: Windows server 2012

• Processor: Dual Xeon e5 processor

• Memory: 32GB RAM

• Disk: 500GB SSD System disk

• Network: 2x Gigabit Ethernet interfaces

• Other: 2 free USB ports


• Additional software: MSSQL Standard Edition (with the right license dimensioning for the project)

These 2 nodes should share a storage cabinet (normally using FC) with at least 8TB of effective storage

Rendering Server

• Operating system: Windows 7 64 bit SP1

• Processor: 6th generation Core i7 or Xeon with 4 cores (8 threads)

• Memory: 16 GB RAM

• Graphics card: GeForce GTX 960

• Operating system: Windows 7 64 bit SP1

• Processor: 6th generation Core i7 or Xeon with more than 4 cores (more than 8 threads)


• Graphics card: GeForce GTX 960 or higher

Playout Station • Operating system: Windows 7 64 bit SP1 or Windows 10

• Processor: Intel Core i5 3rd generation


n The amount of required RAM depends on the rundown size and the complexity of rundown items. In general, you can assume that additional 4 GB of RAM is required for every 1000 items on your opened rundown.

• Disk: 500 GB on 7200 RPM HDD

• Display: 21" 1920x1080 resolution capable monitor

• Peripherals: USB keyboard and mouse

• Graphics card: NVIDIA GeForce GTX 650 2GB

• Operating system: Windows 10

• Processor: Intel Core i7 7th generation or comparable Xeon CPU

• Memory: 16 GB RAM or more

• Disk: 500 GB SSD

• Display: 24" 1920x1080 resolution capable monitor

• Peripherals: USB keyboard and mouse

• Graphics card: NVIDIA GeForce GTX 1050 2GB or above

18

Component Dependencies

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

Components Prerequisites

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

Dependencies

Components or Component Group Required Optional

Controllers and editors, MOS plugins

• Avid HASP Driver

• MS SQL Database (see Maestro | Newsdatabase)

• Shared data

• VideoEngine for Windows

• Maestro | RenderEngine for Windows

Those components are in fact optional, but highly recommended in order to use basic important features, e.g. preview

Maestro | News Bus Services

• Maestro | News database

• Maestro | News RenderServer (only Clientcomponents)

n/a

Maestro | News GAM Access

n/a n/a

Maestro | News NLE • Avid HASP Driver n/a

Maestro | News Render Server

n/a

Media Central | Maestro News

n/a

MOS Server n/a

OradControl n/a

Maestro | News HTML5 MOS Plugin


• Maestro | Render Engine for Windows

• MediaComposer or Adobe Premiere Pro or other supported NLE system

• MediaCentral | UX


• Maestro | News Render Server database

• Maestro | RenderEngine for Windows

• VideoEngine for Windows

• MediaCentral | UX


• Maestro | News MOS database


• MediaCentral | Cloud UX™


• Avid HASP Driver

• HTTP server that supports proxying

• Maestro | News Render Server

19

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 SQL ODBC Driver 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

Maestro | News GAM Access Plugin 32 bit

Maestro | News iNews Plugin

Maestro | News iNews Simple Plugin

Maestro | News MOS28 Plugin

Maestro | News PageBrowser Plugin 32 bit

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





Maestro | News IPM

Maestro | News Journalist Station


Maestro | News NLE





Maestro | News Render Server • Microsoft Visual C++ Runtime 8.0 (includes ATL and MFC) Service Pack 1 (x86)






MediaCentral | Maestro News none

20

Maestro | News Supported Products

Avid Software Products

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

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



OradControl none

Maestro | News HTML5 MOS Plugin none

Component(s) Prerequisites

Avid Software Product Supported Software Versions

Avid Maestro | Render Engine 2018.6

Avid Maestro | Designer 2018.6

Avid Automation Protocols

Avid VideoEngine for Windows 2018.6

Avid VideoEngine for Linux 2018.6

Avid MediaCentral | UX 2.10

Avid MediaCentral | CloudUX 2018.6

Avid MediaCentral | Asset Management (formerly Avid Interplay | MAM)

5.9, 6.0 (2017.1), 6.1 (2017.2), 2018.4

Avid MediaCentral | Production Management (formerly Avid Interplay | Production)

3.8, 4.0 (2017.2)

Avid MediaCentral | Newsroom Management (formerly Avid iNews)

6.1, 6.3 (2017.2)

Avid MediaCentral | Command (formerly Avid iNews Command)

3.7 (2017.1)

Avid MediaComposer 8.7

21

Notes:

• In the past, there was also a customized version of Avid MediaCentral | Asset Management called Maestro GMAM with its own versioning. Now, the customized (for Maestro | News) settings are included in Avid MediaCentral | Asset Management as the Maestro GMAM package.

• Ibis iFind is not supported since Maestro | News 7.4.

• MediaCentral | UX versions 2.9 and older and the MediaCentral | Cloud UX are not supported in this Maestro | News release.

Third Party Software

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

Maestro | News should also support, but the version 2018.6 has been not tested against integration with the following external components:

Automation Protocols

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

Software Supported Version

AP ENPS 8.2

Octopus Newsroom 8.0

Annova OpenMedia 4.3

Adobe Premiere 11

Category Software

Newsroom Computer Systems (NRCS)

AP ENPS, Octopus, Annova OpenMedia Dalet+, Snews Anews, LifeNews, NorCom NC Power, Sobey, Dayang

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

Studio automation Ross OverDrive, Vis Mosart, Sony ELC (is this still supported?), 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

Protocols Supported (Yes / No)

Chyron Intelligent Interface (CII)

yes

OradControl yes

22

NRCS Systems Supported by MOS Plugins

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

Support for Video Assets

Video Asset Sources

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

yes

Harris VDCP yes

ControlAir no (not supported since Maestro | News 7.2)

Sony no (not supported since Maestro | News 7.2)

Protocols Supported (Yes / No)

Protocols NRCSesSupported MOS Protocol Version

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

2.6


Avid MediaCentral | Newsroom Management 2.6

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

AP ENPS (for version <= 6), Dalet, Sobey, Dayang, NorCom NC Power

2.6

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

2.6, 2.8

Maestro | News HTML5 MOS Plugin

Octopus, AP ENPS 2.8

Source

Video Asset on Graphic Item Video Asset as Video Item

Image Control Clip Control

Media Control Image

Image Sequence Clip

File system (G: drive / Control_Data)

yes yes yes yes yes yes

Video Engine database yes yes yes yes no yes

MediaCentral | Asset Management

yes yes yes yes no yes

MediaCentral | Production Management

no no no no no yes

23

Video Asset Playout Engines

PlaceVideo Asset on Graphic Item

Video Asset as Video ItemImage / Clip Control Media Control

Preview in the Controller file selector

Media Player Video Engine n/a

Browser panel in the Controller

n/a n/a Video Engine

Playout on Windows Media Player (not officially supported)

Video Engine (in Render Engine)

Video Engine

Playout on Linux (HDVG2,FSP)

Media Player Video Engine (in Render Engine)

Video Engine

Rendering in Render Server on Windows

Media Player (not officially supported)

not supported yet not supported

Rendering in NLE on Windows

Media Player (not officially supported)

not supported yet not supported

24

3 Installing Components


• Planning the Deployment

• Verifying and Applying Requirements

• Obtaining and Verifying Components

• Installing 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 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, Maestro GMAM / MediaCentral | Asset Management and MediaCentral | Newsroom Management.

The MediaCentral | UX server is required for integration between the Maestro | News Controller (on Playout Station) and MediaCentral | Production Management. The Maestro | News Controller can use assets from MediaCentral | Production Management and Maestro GMAM / MediaCentral | Asset Management. The Controller can also import and synchronize rundowns from MediaCentral | Newsroom Management (for MOS-less connection, the Maestro 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 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 | Render Engine), Maestro 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 license). Optional (but highly recommended) components are: Maestro | RenderEngine for Windows (for graphics items preview), VideoEngine (for video items preview, for support of video embeeded on graphics items), Shared Data. All of 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 separate dedicated server is the best option, especially when you want to use many Playout Stations, Editing Stations, Authoring Stations or Journalist Stations.

27

HTML5 MOS Plugin integration with NRCS and MediaCentral | Cloud UX

29

MOS Plugin Integration with Avid MediaCentral | Newsroom Management

Controller Integration with Avid MediaCentral | Newsroom Management using MOS Server

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.

Integration with Avid MediaCentral | Asset Management

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

31

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.

In addition 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.

32

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.

33

Integration with Avid Media Composer

34

Example of a More Complex Integration

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

35

Verifying and Applying Requirements

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

Installing VideoEngine for Windows for Preview

When installing VideoEngine for Windows to use with Maestro | News Controller or Maestro | News Plugins for preview purposes, be aware that the VideoEngine should be installed using the “Maestro” profile. Default settings for this profile are shown below:

36

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:

Notes for Installing Video Engine for Windows for Maestro | News Render Server

When installing Video Engine for Windows for workflows with Maestro | News Render Server, select the “RenderServer” profile and the default settings for this profile:

37

Notes for Installing VideoEngine for Linux

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

38

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

In other cases, select the DVG Maestro work mode:

In this case everything will be computed on 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:

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 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 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 <name_of_md5_checksum_file> - 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 <name_of_installer_file> - 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.

Component Documentation

Avid MediaCentral | UX Avid MediaCentral Documentation

Avid MediaCentral | Newsroom Management

Avid iNews Documentation

Avid MediaCentral | Asset Management

Avid Interplay | MAM Documentation

Avid MediaCentral | Production Management

Avid Interplay | Production Documentation

Avid MediaCentral | Command Avid iNews Command Documentation

Avid Media Composer Avid Media Composer Software 8.0 Documentation

40

http://avid.force.com/pkb/articles/en_US/user_guide/Avid-MediaCentral-Documentation

http://avid.force.com/pkb/articles/en_US/user_guide/Avid-iNEWS-Documentation

http://avid.force.com/pkb/articles/en_US/readme/Avid-Interplay-MAM-Documentation

http://avid.force.com/pkb/articles/en_US/ReadMe/Avid-Interplay-Production-Documentation

http://avid.force.com/pkb/articles/en_US/user_guide/Avid-iNEWS-Command-Documentation

http://avid.force.com/pkb/articles/en_US/readme/Media-Composer-Software-8-0-Documentation

Installing Components

Installing Maestro | News from the GraphicsSuite Installer

The procedure below describes how to install Maestro | News using the GraphicsSuite installer.

To install Maestro | News from the GraphicsSuite:

1. Run the GraphicsSuite installer: GSetup_<version>.exe.

2. If User Access Control (UAC) is enabled, you will be prompted to disable it:

Click OK to switch off the UAC.

3. If your hardware lacks a supported graphics card, an appropriate warning message is displayed:

Make sure to install a supported graphics card if you plan to use Maestro | RenderEngine with Maestro | News components.

n You can also use Maestro | Render Engine on a remote machine that contains a supported graphics card.

4. If you are not running either Microsoft Windows 2008 Server, Microsoft Windows 7 or Microsoft Windows XP, the following warning message will be displayed:

5. The “Welcome to AVID Graphics Setup” window is displayed:

41

Click Next.

6. The “New installers found” window is displayed:

The GraphicsSuite installer copies all component installers into the local hard drive to speed up the installation process. This process may take a considerable amount of time and requires a sufficient amount of free space.

42

7. You can select which installers should be copied to the local hard drive.

Make sure to include all prerequisites for the selected components (as described in “Components Prerequisites” on page 19), especially 3rd party libraries. The list shows the component installers file names, not the component names. Refer to the Installer File Names in this guide to match required components.

Click Next to continue.

8. The copying process is started.

43

9. After the installers are copied to the local drive, the “Setup Type” window appears:

Choose the Select components to be installed option and click Next.

10. In the following window, select additional components to be installed from all tabs. If the component is already installed, its version is displayed in the Already installed column.

Click Next to continue the installation.

11. If any of the selected components are already installed, a warning message is displayed:

44

Click Cancel to clear these components, or you can click OK to include these components in the scripted installation feature.

12. In the “Summary” window, review the information you have entered and click Next to begin the installation.

If the installation summary contains any errors, click the Back button to return to a previous step and correct the error


13. The “3rd parties runtime selection” window appears. Select the required prerequisite components and click Next to continue.

45

14. Review the information in the Runtime Summary window.

Select whether you wish to install runtimes now, before any CyberGraphics component installation, or you wish to install runtimes later during the scripted installation. Click Next to continue.

15. In the “Ready to create installation script” window, review the information once again and click Next to start the installation script.

46

16. In the “SharedData: Installation details” window, select the drive for the Shared Data and choose whether you wish to rename an existing folder or merge the content with the existing folder. Click Next to continue.

17. Further steps depend on the selected components. Refer to the Additional Steps Required for Specific Components chapter for more information.

18. Finally, the “Ready to create installation script” window appears. Click Next to begin the installation.

47

19. The “Graphics Suite Setup installation batch complete” window appears:

Select one from two options:

- Start the batched file based installation

- Clear this option if you do not wish to install now but wish to use the generated batch file later.

Click Install.

20. The installation progress can be monitored:

48

21. Additional windows can appear during the installation:

Proceed with installing the runtimes by clicking Next in all following windows.

49

Click Finish.

22. Also other additional windows can appear, depending on the components you selected. If you cancel the installation for any of the components, an appropriate warning dialog is displayed:

Click OK to start installation of this component again or click Cancel to proceed to the next installer.

23. After the installation is completed, a summary window is displayed showing the installed and omitted components:

50

Click Finish to exit the installer.

Component Names Used by the GraphicssSuite Installer

The list below provides information about the names of components used by the GraphicsSuite installer:

Tab Component Name in the Installer Component

Environment SharedData Shared Data

HASPdriver HASP Driver

Main Products MaestroDesigner Maestro | Designer

Maestro64 Maestro | News Controller

MaestroIPM64 Maestro | News IPM

VEServer VideoEngine for Linux

VEServerWin VideoEngine for Windows

Render Engine RenderEngine64 Maestro | RenderEngine for Windows

RenderEngine4Linux64 Maestro | RenderEngine for Linux

Plugins MOSgateway2 MOS Server (formerly MOS Gateway 2)

MaestroENPSplugin Maestro | News ENPS Plugin 32 bit

MaestroENPSplugin64 Maestro | News ENPS Plugin 64 bit

MaestroiNEWSsimplePlugin Maestro | News iNews Simple Plugin

JStation64 Maestro | News Journalist Station

MaestroMOS28Plugin Maestro | News MOS28 Plugin

51

Installing Maestro | News from Individual Installers

To run installation process of the specified component, run the appropriate installer on the target Windows machine (for installing MediaCentral | Maestro News packages, refer to the Configuring MediaCentral | Maestro News section):

Installer File Names

MaestroPageBrowserAx Maestro | News PageBrowser Plugin 32 bit

MaestroPageBrowserAx64 Maestro | News PageBrowser Plugin 64 bit

MaestroGAMAccess Maestro | News GAM Access Plugin 32 bit

MaestroGAMAccess64 Maestro | News GAM Access Plugin 64 bit

MaestroRenderServer64 Maestro | News Render Server

Plugins2 AutomationProtocols64 Automation Protocols

AutomationService Automation Service

MaestroBusServices Maestro | News Bus Services

NLE MaestroNLE64 Maestro | News NLE

Tab Component Name in the Installer Component

Component Installer File Name

Maestro | News Bus Services MaestroBusServices_7_5_2_<build>.exe

Maestro | News Controller Maestro64_7_5_2_<build>.exe

Maestro | News ENPS Plugin 32 bit MaestroENPSPlugin_7_5_2_<build>.exe

Maestro | News ENPS Plugin 64 bit MaestroENPSPlugin64_7_5_2_<build>.exe

Maestro | News GAM Access Plugin 32 bit MaestroGAMAccess_7_5_2_<build>.exe

Maestro | News GAM Access Plugin 64 bit MaestroGAMAccess64_7_5_2_<build>.exe

Maestro | News iNews Plugin MaestroINEWSPlugin_7_5_2_<build>.exe

Maestro | News iNews Simple Plugin MaestroINEWSSimplePlugin_7_5_2_<build>.exe

Maestro | News IPM MaestroIPM64_7_5_2_<build>.exe

Maestro | News Journalist Station JStation64_7_5_2_<build>.exe

Maestro | News MOS28 Plugin MaestroMOS28Plugin_7_5_2_<build>.exe

Maestro | News NLE MaestroNLE64_7_5_2_<build>.exe

Maestro | News PageBrowser Plugin 32 bit MaestroPageBrowserAx_7_5_2_<build>.exe

Maestro | News PageBrowser Plugin 64 bit MaestroPageBrowserAx64_7_5_2_<build>.exe

Maestro | News Render Server MaestroRenderServer64_7_5_2_<build>.exe

52

Generic Installation Process

1. If any of the prerequisites is not installed, an appropriate message is displayed:

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

Click OK to continue.

2. The “Welcome to <component> Setup” window appears.

MediaCentral | Maestro News maestro-ux-2.10_2.5.0_<build_identifier>.noarch.rpm

MaestroUX-2-4.0.v<build_identifier>.x86_64.rpm

maestro-ux-media-browser-2.10_2.5.0_<build_identifier>.noarch.rpm

MOS Server MOSGateway2_2_0_<patch>_<build>.exe

Component Installer File Name

53

Click Next.

3. The “Setup Type” window appears:

Select Typical if you do not want to change the default installation drive (C:) or select Custom Setup to appoint a new installation drive. Click Next to continue.

4. In case you selected the Custom Setup option, choose the Destination Folder in the following window and click Next:

54

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

6. Further installation steps depend on the component you are currently installing. More information is provided in the following chapters of this document.

7. 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.

55

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

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

56

Additional Steps Required for Specific Components


Maestro | News Bus Services includes the following applications:

• Asset Access Service - Enables the Maestro UX plug-in 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 server. These sources are used to populate graphics.

• Media Browser Service - Provides access to Maestro assets (clips and images).

• Render Service – Provides connection between Maestro UX and Maestro Render Server

• Maestro Monitor - A tool for controlling the above services.

Additional Installation Steps

1. The “MaestroBusServices ACS Gateway settings” is displayed.

Enter the following information:

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.


2. The “Access to MaestroAssets Database” window appears next:

58


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: 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 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:

59


Server -host name (or IP) 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.

60

Maestro | News Controller

Additional Installation Steps:

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 Server machine) and sharing the content under the Data share name.

User - user name for the share.

Password - password for the user above.


2. The “Access to Maestro (x64) Database” window appears next:

61


Server - Enter the asset database host name (or IP address; usually Maestro 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.

3. The “Server - Database action” window appears if the database already exists:

62

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, which gives you the possibility to monitor and restart the Maestro | News Controller application.

63

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 Server machine) and the database instance name preceded with a backslash.


User - asset database user name (default sa).

Password - password for the user above (default maestro).

Show password - enable this option to see the password field in plain text to ensure that the password has been entered correctly.


64

Maestro | News ENPS Plugin (32 and 64 bit)


1. The “Access to Maestro ENPS Plugin <architecture> Database” window appears:


Server - enter the asset database host name (or IP address; usually Maestro Server machine) and the database instance name preceded with a backslash.






2. The “Configuration parameters for Maestro ENPS Plugin <architecture>” window is displayed:

65

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.

66



1. The “Access to Maestro iNews Plugin Database” window appears:


Server - enter the asset database host name (or IP address; usually Maestro Server machine) and the database instance name preceded with a backslash

Use Trusted Connection - select this check box if you wish to use a trusted connection to the database.





2. The “Configuration parameters for Maestro iNEWS Plugin” window is displayed:

67




Click Next.



1. The “Access to Maestro iNEWS Simple Plugin Database” window appears:

68








2. The “Configuration parameters for Maestro iNEWS Simple Plugin” window is displayed:




Click Next.

69

Maestro | News NLE


1. The “Access to Maestro NLE (x64) Database” window appears:








2. The “Maestro NLE (x64): Avid AVX plugin default settings” window is displayed:

70

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.

71



1. The Access to Maestro MOS28 Plugin Database window appears:








2. The “Configuration parameters for Maestro MOS28 Plugin” window is displayed:

72




Click Next.

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


1. The “Access to Maestro Page Browser Ax Database” window appears:

73








2. The “Configuration parameters for Maestro Page Browser Ax” window is displayed:

If required, select additional options and click Next.

74


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:

75


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

n The Maestro Render Server database is different than the Maestro Asset database. Verify that you are 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. If the installer detects that the MaestroRenderServer database already exists, a window appears asking if you want to either use the existing database or create a new database.

76

Select the button to either Use existing or Create new.

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

Click Next.

4. The “Access to Maestro Database” window appears:


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

77

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.

MediaCentral | Maestro News

The Maestro UX plug-in software includes three .rpm files that need to be installed on the MCS (MediaCentral | UX) server:

• maestro-ux-<version>.noarch.rpm

• maestro-ux-media-browser-<version>.noarch.rpm

• MaestroUX-<version>.x86_64.rpm

Before you can start the installation, you must copy the RPM files to your MediaCentral | UX (MCS) server. For more information, see Copying Software to the MCS Server in the MediaCentral | UX Installation Guide.

If you are running a cluster, complete the process below on the master and slave nodes only. Complete the process on the slave node first and then repeat the process on the master node.

1. Navigate to the directory where the installer files have been copied. Example:

cd /media/installers

2. Three .rpm files are required to be installed on the MCS server. Install the files with the following commands:

rpm -ivh maestro-ux-<version>.noarch.rpm

rpm -ivh maestro-ux-media-browser-<version>.noarch.rpm

rpm -ivh MaestroUX-<version>.x86_64.rpm

Installing HTML5 MOS Plugin

Overview

Simplified architecture diagram:

Install Maestro | News Bus Services

Follow the instructions from the Maestro | News Bus Services chapter.

Configure Maestro | News Bus Services to Run in the REST mode

1. Stop the Bus Services using the Maestro Monitor tool.

2. Stop the Avid Maestro Monitor Service using the Windows Services tool.

78

3. Open the Registry Editor and change the following keys by adding the following phrase at the end of each key -REST (preceded with a space):

- HKEY_LOCAL_MACHINE\SOFTWARE\Orad\MaestroMonitor\Applications\AssetService\Startup command

- HKEY_LOCAL_MACHINE\SOFTWARE\Orad\MaestroMonitor\Applications\DataLinkService\Startup command

- HKEY_LOCAL_MACHINE\SOFTWARE\Orad\MaestroMonitor\Applications\MediaBrowserService\Startup command

- HKEY_LOCAL_MACHINE\SOFTWARE\Orad\MaestroMonitor\Applications\RenderService\Startup command

4. Start the Avid Maestro Monitor Service using the Windows Services tool.

5. Start the Bus Services using Maestro Monitor tool.

79

Install HTTP Web Server for Proxy Support

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.

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/

80

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

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

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.

Additional Notes about Running Maestro | News Bus Services in the REST mode

Instead of changing registry entries, you can also run each of the services manually with the -REST parameter. Open the command line and change the directory to the Maestro | News Bus Services target folder, e.g.:

cd c:\Orad\MaestroBusServices\

Then run the services you wish to use (first ensure that the service is not running already), e.g.:

AssetService.exe -REST

DataLinkService.exe -REST

MediaBrowserService.exe -REST

81

RenderService.exe -REST

n If the services were changed manually and the registry has not been amended, then the Maestro Monitor will automatically restart the service in a standard (non-REST) mode in case of a failure.

Notes About Running Installers

In case of a warning message 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.

82

Default Installation Folders

Components are installed to the following target folders:

In addition, all of the installers (except MediaCentral | Maestro News) copy the installer files into the <drive>:\Orad\Installers\ folder.

Component Default Installation Folder

Maestro | News Bus Services <drive>:\Orad\MaestroBusServices\

Maestro | News Controller <drive>:\Orad\Maestro64_7_5\

Maestro | News ENPS Plugin 32 bit <drive>:\Orad\MaestroENPSPlugin\

Maestro | News ENPS Plugin 64 bit <drive>:\Orad\MaestroENPSPlugin64\

Maestro | News GAM Access Plugin 32 bit <drive>:\Orad\MaestroGAMAccess_7_5\

Maestro | News GAM Access Plugin 64 bit <drive>:\Orad\MaestroGAMAccess64_7_5\

Maestro | News iNews Plugin <drive>:\Orad\MaestroINEWSPlugin\

Maestro | News iNews Simple Plugin <drive>:\Orad\MaestroINEWSSimplePlugin\

Maestro | News IPM <drive>:\Orad\MaestroIPM64\

Maestro | News Journalist Station <drive>:\Orad\JStation64_7_5\

Maestro | News MOS28 Plugin <drive>:\Orad\MaestroMOS28Plugin\

Maestro | News NLE <drive>:\Orad\MaestroNLE64_7_5\

Maestro | News PageBrowser Plugin 32 bit <drive>:\Orad\MaestroPageBrowserAx\

Maestro | News PageBrowser Plugin 64 bit <drive>:\Orad\MaestroPageBrowserAx64\

Maestro | News Render Server <drive>:\Orad\MaestroRenderServer64\

<drive>:\Orad\MaestroRCPlugin64\

MediaCentral | Maestro News /opt/avid/avid-interplay-central/plugins/com.avid.maestro/

/opt/avid/avid-interplay-central/plugins/com.avid.maestro.browser/

/opt/avid/share/nginx/plugins/maestro-ux/

/opt/avid/share/nginx/plugins/maestro-ux-media-browser/

MOS Server <drive>:\Orad\MOSGateway2\

HTML5 MOS Plugin Web root folder of the HTTP server

83

Applying Licenses

License Types

For more information, refer to the HASP Driver documentation.

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

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

84

Licenses List

Component Module Name

License Types

License OptionsVersion 2 -

HASP 4

Version 2 - HASP HL (V8)

Version 2 - Nodelock (Windows)

Version 3 - floating license


no license required

Maestro | News Controller

MaestroController X X X X MOS, Automation, GPI, SceneEdit, Ticker, Morpho, Blend, Tweeter, Facebook, iMaestro1, iMaestro2, iMaestro3, iMaestro4, iMaestro5, iMaestro6, iMaestro7, iMaestro8

MaestroPageEditor X X X X SceneEdit, Tweeter, Facebook


MaestroENPS

Plugin

X X X X Ticker, Morpho, Tweeter, Facebook



no license required



MaestroINEWS

Plugin



MaestroINEWS

SimplePlugin


Maestro | News IPM MaestroIPM X X X X none

Maestro | News Journalist Station

JStation X X - X Ticker, Morpho, Blend, Tweeter, Facebook

85


MaestroMOS28

Plugin


Maestro | News NLE MaestroNLE X X X X Feature0, Morpho, Tweeter, Facebook

MaestroNLEServer X X - X none


MaestroPage

BrowserAXX X X X

Morpho, Tweeter, Facebook



no license required

MediaCentral | Maestro News

no license required

MOS Server MOSGateway X X X - 8 clients, 16 clients

Component Module Name

License Types

License OptionsVersion 2 -

HASP 4

Version 2 - HASP HL (V8)

Version 2 - Nodelock (Windows)

Version 3 - floating license

86

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.

87

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:

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:

//<shared_folder_host>/<shared_folder_name> /Control_Data cifs ro,user=<user_name>,passwd=<user_password>,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 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

Component Class NameActiveX Control Name GUID


MaestroEditor Class

maestroinewsax.

MaestroEditor

5B4E4114-AAC4-47CE-AB6E-E88D00241479


Maestro Simple Editor

maestroinewsax.

MaestroSimpleEditor

F6FD9972-6114-41FB-B41A-D8CF29BAA5AA

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

MaestroENPS Class

ENPSPluginAtl.

MaestroENPS

DDB7B161-558D-40C9-B905-43E7D06B4EC5


MaestroMOS Class MaestroMOS28.

MaestroMOS

BB3E0F53-A4C9-413D-B060-2D467AC42414

88

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 <ESC> 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 /<mam_shared_folder_host>/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.


vi /etc/fstab


//mam_shared_folder_host/mam_shared_folder_name /mam_shared_folder_host/Data cifs username=<user_name>,password=<user_password>,rw,bg,iocharset=utf8 0 0


- shared_folder_host - is the IP address or host name where Shared Data is installed (usually Maestro 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.


//qa-imam-d/Data /qa-imam-d/MediaAssetManager cifs username=mam_admin,password=Avid123,rw,bg,iocharset=utf8 0 0



mount /mam_shared_folder_host/Data

89

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 \\<mam_host> /user:<user> <password>

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.

<drive>\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.

90

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 Connecto 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:

91

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:

92

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

n If you don’t have any assets in MediaCentral | Asset Management to use for your preview tests, you 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.

93

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 target location (i.e. to G: drive or 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}

94

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/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://<mam_ip_host_name>: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://<user>:<password>@<machine_name>:<port>/

8. Open the MAM System Administrator (go to http://<mam_ip_or_host_name>: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

95

- 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. Omit the fields in IBIS RabbitMQ. Example:

96

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://<user>:<password>@<machine_name>:<port>/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:

97

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:/<MAM_NAME>:9900/WorkflowEngineWSAdmin/WFEMonitor.htm?accesskey=abbf62ba-d8e7-41b9-bbf6-0617568c99c6&productname=qa-gmam-a

98

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://<mamserver>: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

99

n In case MediaCentral | Asset Management is older than the 5.8 version, you have to restart 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://<IP>:9900/LoginServiceWS/start.aspx, select Export / All destinations.

1st Problem:

Solution:

1. Open the MAM System Administrator (go to http://<mam_ip_or_host_name>:9900/LoginServiceWS/Admin/AdminStart.aspx, login, then click on SystemAdministrator).


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 TargetStreamTypes property, then the system will chose the first one on the list. In this case is JPG.

Solution:

1. Open the MAM System Administrator (go to http://<mam_ip_or_host_name>:9900/LoginServiceWS/Admin/AdminStart.aspx, login, then click on SystemAdministrator).


100

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://<mam_ip_or_host_name>:9900/LoginServiceWS/Admin/AdminStart.aspx, login, then click on Essence Management Administrator).

2. Select the Essence Server tab.

3. EssenceServerDiskWS_1 › HIRES › HIRES › Access.

101

4. Select New:

- Name: FTP

- Protocol: FTP

- Base Path: Select HIRESUNC (UNC) › Edit

- Role: read

5. The configuration is complete.

102

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 | 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. Interplay Production Connectivity Toolkit (PAMCTC) must be installed and configured on the MediaCentral | UX server.

5. 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 | UX, refer to the MediaCentral | Production Management Installation and Configuration guide and the MediaCentral | UX Installation and Configuration guides. This chapter shows only an example of the most common simple scenario.

To check the MediaCentral | Production Management Configuration:

1. Run the Interplay Administrator (usually installed on the MediaCentral | Production Management server).

2. Select Interplay Server > User Management > User Authentication Providers.

3. Ensure that MediaCentral Platform Authentication and Avid NEXIS / ISIS Authentication check boxes are selected and the corresponding Server 1 fields contain valid values:

t The Avid MediaCentral Platform Servers / Server 1 should point to your MediaCentral | UX via HTTPS protocol: https://<mediacentral_host>

t The Avid NEXIS / ISIS Servers / Server 1 should contain your NEXIS host name or IP address

4. Go back to main menu by clicking the Menu button. Select Interplay Server > Site Settings > MediaCentral Platform Services Settings.

5. Ensure that all settings have valid values - point to your ACS Bus (on MediaCentral | UX):

103

The ACS Bus AMQP URL field should point to the ACS url using the amqp protocol: amqp://<mediacentral_host>/acs.

You should also fill the fields in MediaCentral Playback Service and MediaCentral | UX Messaging groups.

6. Login (using SSH software, such as PuTTY) to the MediaCentral | UX server and check if the NEXIS Client installed is in the correct version that matches your NEXIS Server version:

rpm -qa | egrep -i 'isis|nexis'

Also ensure that the NEXIS Client service is started:

service avid-isis status

If the service is not started, then start it:

service avid-isis start

7. Login to the MediaCentral | UX web interface as an Administrator and select the System Settings layout. Select the MCPS / Playback Service section. Ensure that your workgroup and storage configurations are correct.

The Status column on the Storage Location list should also display Connected.

8. Check your player settings in the MCPS/Player section.

9. If everything is configured correctly, you should be able to see the preview of clips registered in MediaCentral | Production Management that are stored in NEXIS.

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 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:

104

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

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:

105

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 started then 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 <Connector port= and check the port; to change the port modify it in this file then restart Avid Interplay Web Services).

106

3. Click Edit Configuration and check if your configuration points to the correct WebServices Workgroup Name (workgroup you use 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 yoour 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.

107

Configuration of Interplay Production Connectivity Toolkit (PAMCTC)

For detailed information about installing and configuring PAMCTC, refer to the appropriate installation guide. This chapter only shows an example of the most common simple scenario.

To check if Interplay Production Connectivity Toolkit is installed execute a command on MediaCentral | UX machine:

1. Login via SSH to MediaCentral | UX, then type:

rpm -qa | grep avid-pam

The Output should contain (versions may differ):

avid-pam-1.0.2_v20170703_154516-1.noarch

If Interplay Production Connectivity Toolkit is not installed, you need to install it first.

2. Verify your Interplay Production Connectivity Toolkit settings. To do this, execute a command:

cat /opt/avid/etc/avid/avid-pam.rc

The output should looks like the example below (individual settings may differ):

export ACS_GATEWAY_HOST=127.0.0.1

export ACS_GATEWAY_PORT=9900

export ACS_BUS_QUERY_TIMEOUT=10000

export PAMCTC_IP_HOST=qa-ipam-d

export PAMCTC_IP_ENGINE_DB_GUID=F134F98F-9DEB-4208-BC82-13FE5C1AC726

export PAMCTC_THUMBNAIL_DEFAULT_WIDTH=170

export PAMCTC_THUMBNAIL_DEFAULT_HEIGHT=97

Where the most important settings are:

- ACS_GATEWAY_HOST - IP or host name of theACS BUS (usually the same as MediaCentral | UX).

- ACS_GATEWAY_PORT - ACS BUS port, default 9900.

- PAMCTC_IP_HOST - Host name of the MediaCentral | Production Management Engine

- PAMCTC_IP_ENGINE_DB_GUID - MediaCentral | Production Management Engine GUID (to get it, login to Interplay Access, right-click on the database and select Advanced. Select Get/Set Property; inside the Get/Set property dialog, look for the property named CMS_NS_Property_Project_GUID).

3. Finally, check if the Interplay Production Connectivity Toolkit is running. Execute the following command:

service avid-pam status

If the Interplay Production Connectivity Toolkit is not running, start it using the following command:

service avid-pam start

If you want the service to start automatically after machine restart, then enter the following command:

chkconfig avid-pam on

4. Note: if you change any of the Interplay Production Connectivity Toolkit settings, you need to restart this service - to do this enter the following command:

service avid-pam restart

108

5. Additionally, you can check the status of the Interplay Production Connectivity Toolkit using the ACS Monitor. Navigate in your browser to http://<mediaceentral>:8000, then enter the phrase ‘pam’ in the ACS monitor filter box and click Apply. You should see the following avid.pam entry:

If the avid.pam entry is not present, then the Interplay Production Connectivity Toolkit is not started. If you cannot see ACS Monitor at all, it means that the corresponding MediaCentral service is not started. Start it on the MediaCentral | UX machine using the following command:

service avid-acs-monitor start

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.

2. 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.

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 Platform MediaCentral | Production Management (Avid Interplay Administrator / User Management / User Authentication Providers / MediaCentral Platform Authentication).

3. 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

Veryfing 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.

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

109

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 installed (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.

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

110

Alternative method: after installation change conf/tomcat-users.xml, e.g. by adding: <user username="tomcat" password="Avid123" roles="tomcat"/>

e. On the last setup page, allow the installer to start Tomcat.

111

4. Deploy MediaCentral | Newsroom Management Web Services in Tomcat on the Maestro | News Server:

a. Open a web browser (on 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:

112

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 Webservice URL field, enter http://<Maestro_server_IP_or_host_name>:8080/inewswebservice/services.

113

In the MediaCentral | Newsroom Management server host field, enter the IP of the MediaCentral | Newsroom Management Server system.

In the MediaCentral | Newsroom Management user and password fields, enter 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.

Configuring Maestro | News Render Server

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

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

114

To configure render settings:

1. Launch the Maestro Render Server software at:

<drive>:\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 (the player mechanism in MediaCentral | UX currently supports the TGA with Alpha preset). When choosing the Layout, note the selected frame rate. The frame rates in Maestro Render Server, the Render Engine and the Video Engine 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.

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.

115

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 Render Engine category, verify that the Local check box is selected.

This document instructs you to install the Maestro Render Server and the Render Engine on the same server. Selecting “Local” assumes this was completed.

- Output id: enter VE1 to point to the default channel id in the Render Engine 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.

116

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:

117

To check or change the Render Engine frame rate:

1. Go to C:\Orad\RenderEngine64<version>\bin and open the xml file.

2. In the Video section, check the value of the FieldsPerSecond.

To check the Video Engine frame rate:

1. Login to the Video Engine 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 many Maestro | News Render Servers with the same database to improve performance

You can install many Maestro | News Render Servers on separate machines and connect them to the same database (both Maestro asset database and 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.

118

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

Through the ACS Monitor 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.

119

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

The ACS Monitor is not enabled by default and must be started manually.

To enable and access the ACS Monitor:

1. Log in to the MCS server as the Linux ‘root’ user. If you have a clustered configuration, log into the master node.

2. Start the avid-acs-monitor service:

service avid-acs-monitor start

3. Open a web browser and enter the following address to access the Avid ACS Monitor:

http://<server>:8000

Where is the host name or IP address of your MediaCentral server or cluster master node.

The Avid ACS Monitor page appears, allowing you to review the system configuration.

If you do not see the list of attributes on the left side of the page, refresh the browser page.

4. Enter “[mM]aestro” (without the quotes) in the search field at the top of the page and click Apply to find the Maestro services.

120

5. Verify that the status column for each of the services reports a status of “ok”.

6. Once you have verified the status of all services, close the ACS monitor and stop the avid-acsmonitor service on the MCS server:

service avid-acs-monitor stop

Troubleshooting

If the services start and stop immediately without any error message, ensure that the services can access the ACS Bus. Login to your MediaCentral | UX server using an SSH client, then check if the file /etc/sysconfig/avid-acs-gateway has a correct and uncommented entry ACS_SECURITY_FULL_TRUST_IPV4_MASK_LIST (this entry should contain mask that include the server with Maestro | News Bus Services). If not, then add the entry and restart the ACS Gateway:

service avid-acs-gateway restart

For more details, please see the chapter Configuring MediaCentral | Maestro News / Updating the gateway configuration.

Configuring MediaCentral | Maestro News

To apply an initial configuration of MediaCentral | Maestro News complete these steps:

1. Mounting Shared Data share

2. Mounting Render Server output share

3. Updating gateway configuration

4. Enabling MediaCentral | Maestro News plugins

5. Configuring users

6. Configuring the MediaCentral | UX System Settings

7. Veryfing MediaCentral | UX sequence settings

121

Mounting Shared Data share


To mount shared data:

1. Create a mount point on the MCS server for the shared folder:

mkdir /Control_Data


vi /etc/fstab


//<shared_folder_host>/<shared_folder_name> /Control_Data cifs ro,user=<user_name>,passwd=<user_password>,iocharset=utf8 0 0


- shared_folder_host - is the IP address or host name where Shared Data is installed (usually Maestro 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.


//192.168.10.99/Data /Control_Data cifs ro,user=Maestro,passwd=Avid123,iocharset=utf8 0 0



mount /Control_Data

Mounting Render Server output share


To mount the Render Server output share:

1. Create a mount point on the MCS server for the shared folder:

mkdir /Control_Data/RenderServerOut


vi /etc/fstab


//<shared_folder_host>/<shared_folder_name> /Control_Data/RenderServerOut cifs ro,user=<user_name>,passwd=<user_password>,iocharset=utf8 0 0


- shared_folder_host - is the IP address or host name of the server hosting the output produced by Maestro | News Render Server (usually Rendering Server with Maestro | News Render Server itself).

122

- shared_folder_name - is the name of the shared folder on the host above (RenderServerOut 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.


//192.168.10.99/Data /Control_Data/RenderServerOut cifs ro,user=Maestro,passwd=Avid123,iocharset=utf8 0 0



mount /Control_Data/RenderServerOut

Updating gateway configuration

Update the avid-acs-gateway configuration file with the IP address of the Maestro server. For more information, see Configuring Access for External Systems in MediaCentral | UX Installation Guide.


To update gateway configuration:

1. Using the Linux text editor, vi, open the configuration file for editing:

vi /etc/sysconfig/avid-acs-gateway

2. Locate the following line in the configuration file:

#export ACS_SECURITY_FULL_TRUST_IPV4_MASK_LIST="127.0.0.1/25;"

3. Activate (uncomment) this line by removing the “#” in front of it.

4. Add the IP address of the Maestro server to this line, followed by a semicolon:

export ACS_SECURITY_FULL_TRUST_IPV4_MASK_LIST=”127.0.0.1/25;<ip>;”

In the following example, 192.168.10.99 is the IP address of the server

export ACS_SECURITY_FULL_TRUST_IPV4_MASK_LIST="127.0.0.1/ 25;192.168.10.99;"

Do not remove the 127.0.0.1/25 address from this line. This address is required for MediaCentral Platform Services to operate.

5. Save and exit the vi session. Press and type: :wq

6. Restart the avid-acs-gateway service to enable the change:

service avid-acs-gateway restart

If you are configuring MediaCentral | Maestro News for a MediaCentral cluster, restart the cluster resource associated with the avid-acs-gateway service. Only complete this step once, after having updated the avid-acs-gateway configuration file on both the master and slave nodes. The following command can be issued from any cluster node:

crm resource restart AvidGatewayEverywhere

The Cluster Resource Monitor can be used to review the status of the cluster and clear any fail-counts.

123

Enabling MediaCentral | Maestro News plugins


To enable the MediaCentral | Maestro News plugin:

1. Use the MediaCentral Configurator tool to enable the Maestro plug-ins. Start the Configurator by typing the following at the Linux prompt:

/opt/avid/avid-interplay-central/configurator

The configuration UI appears.

2. Enable the MaestroUX and MaestroAssetBrowser options in the Configurator and select OK.

Use the Up and Down arrow keys to move between the options, Left and Right arrow keys to move between OK and Cancel, SPACEBAR to toggle the asterisks, and press Enter to confirm.

a. Asterisk = enabled

b. No Asterisk = disabled

For more information, see Working with the MediaCentral | UX Configurator in the MediaCentral | UX Installation Guide.

Configuring users

For each MediaCentral user that will require access to Maestro UX pane, a corresponding user should be created with Maestro | News Admin tool. If the user is not recognized by the Maestro Server, the user will not see anything in Maestro asset list window. For details instructions on creating users, see the Access and Permissions chapter of the Maestro | News User Guide.

Please note that the machine on which the MaestroAdmin is running may also require to be included in MediaCentral | UX's gateway configuration (see Updating gateway configuration) in order to use / import MediaCentral platform users.

Configuring the MediaCentral | UX System Settings

With the software installed on the MediaCentral | Maestro News and MCS server, the final step in the process involves configuring the new MediaCentral | Maestro News System Setting within MediaCentral UX.

To configure the Maestro system setting:

1. Sign in to MediaCentral | UX as a user with administrator-level access.

For details on this process, see Signing into MediaCentral | UX in the MediaCentral | UX Installation Guide.

2. Select System Settings from the Layout selector in the top-right corner of the interface. This layout only appears if you are logged in as a user with administrator rights.

124

3. In the Settings pane, select Maestro.

4. Configure the MOS options:

a. MOS Object Timebase: Select either NTSC or PAL

b. MOS ID: This is the ID of the Orad MOS Gateway.

c. Enable page parameters in the item’s title: When selected, the Maestro page control's values are added to the MOS item’s title.

d. Save item in asset DB: When selected, users must manually save the graphic before the Drag option (puzzle-piece icon) is available in the interface. When deselected, users can drag directly to rundown without saving:

e. Create new item on edit: This option determines if a new Maestro Page Item is created when editing an item from an MediaCentral | Newsroom Management rundown. The check box for this option only appears if the “Save item in asset DB” option is selected.

5. Configure the Render Server options:

a. Render server profile: When clicking the Play button in the Maestro Browser pane, this profile is used to create the graphic on the Maestro Render Server. Once the render is complete, the asset is loaded in the media pane.

Enter the name of the render profile, TIFF for example, that you altered or created during the process for “Configuring the Maestro Render Server”.

b. Single image preview: Instead of a sequence of images representing the complete graphic animation, just one frame (the “representative frame” that is marked in Page editor for every template) is used as preview. This option provides preview much faster (nearly immediate) and reduces network demand on the MediaCentral server.

6. Click Apply to save your changes.

7. Once the System Settings have been applied, sign out of MediaCentral UX.

8. Restart the avid-interplay-central service to enable the changes.

t If running a single server configuration:

service avid-interplay-central restart

125

t If running a clustered configuration, issue the following command on any node in the cluster:

crm resource restart AvidIPC

9. Sign back in to MediaCentral UX as any user. Icons representing the Maestro Asset database (Maestro) and filesystem assets (CLIPS and IMAGES) should appear in the Launch pane of the MediaCentral UX user interface.

Additionally, a new “Maestro Browser” pane that enables users to edit and create rendered previews of Maestro | News assets should be available from the Panes menu.

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 MediaCentral | UX with MediaCentral | Asset Management. Please refer to the MediaCentral | UX Installation and Configuration Guide.

To use MediaCentral | Asset Management assets on Maestro pages:

1. Mount the MediaCentral | Asset Management share on the MediaCentral | UX machine (for a cluster configuration, mount it on the master and slave nodes):

a. Create the following directory: mkdir /voll/<mam_system_id>

mkdir /vol1/5BB40ECCF3324B4D89AF557F2A9B2A9A

b. Add an entry in fstab:

//<mam_host>/<mam_share>/ /vol1/<mam_system_id> cifs ro,user=<mam_share_user>,password=<mam_share_password>

Example:

//qa-imam-d/Data/ /vol1/5BB40ECCF3324B4D89AF557F2A9B2A9A cifs ro,user=mam_service,password=Avid123

c. Mount using the following command:

mount /vol1/<mam_system_id>

Example:

mount /vol1/5BB40ECCF3324B4D89AF557F2A9B2A9A

2. Configure MediaCentral | Asset Management in MediaCentral | UX System Settings:

126

3. Now you can select a MAM asset and try to display it in the preview. If the configuration contains any errors, the preview might be faulty as well.

Veryfing the MediaCentral | UX Sequence sSettings

In order to use Maestro | News graphics on sequences in MediaCentral | UX you should have an appropriate editing setting enabled.

To enable editing:

1. On the MediaCentral | UX server, open the following file:

/etc/sysconfig/avid-common-params

2. Ensure that you have set the following parameters:

# Enable Graphics Rendering

export AVID_GRAPHIC_ENABLED=true

export AVID_GRAPHIC_BKG_RENDER_DISABLED=true

export AVID_ENABLE_INTERNAL_CACHE_RENDER=true

export AVID_PLAYER_LOG_MODIFIED_TIMELINE=true

export AVID_REMOTE_PROXY_DISABLED=true

127

Troubleshooting

1. When the Maestro | News system in the Launch panel appears as Maestro (N/A) - using the ACS Monitor make sure that the avid.maestro.asset service is present. If it is not present there, then you need to correct your Maestro | News Bus Services settings. Please refer to the chapter Troubleshooting / Changing settings manually and correct the settings for Maestro | News Bus Services.

2. When the Maestro | News system in the Launch panel appears as Maestro (authentication failed) - ensure that you created the required user in the correct database. The user credentials should be the same as the MediaCentral | UX login.

Configuring MOS Plugin to Work with MediaCentral | UX Desktop App

To configure the MOS plugin:

1. Ensure that you have MediaCentral | UX installed and working properly.

2. Install MediaCentral | UX Desktop App:

a. Modify the file InstallMediaCentral.cmd- update the line with SERVERLIST to point to your existing MediaCentral | UX server, e.g.

"%ScriptDIR%\MediaCentral_UX_Win.exe" /s /v"/qb SERVERLIST="""MCUX_2_10_5=http://qa-mcux-i""""

b. Run file InstallMediaCentral.cmd

3. Install Maestro | News MediaCentral | Newsroom Management Plugin.

4. If you have MediaCentral | Maestro News plugins installed on MediaCentral | UX, then login via SSH to your MediaCentral | UX server, run /opt/avid/avid-interplay-central/configurator and disable them:

You will be prompted to restart Interplay Services, please restart.

Please note that the above might be not enough if the MediaCentral | UX Desktop App will try to use MediaCentral | Maestro News plugin instead of the Maestro | News MediaCentral | Newsroom Management Plugin. In such cases, uninstall MediaCentral | Maestro News plugin completely from MediaCentral | UX.

5. Run the MediaCentral | UX Desktop App.

You need to run MediaCentral | UX Desktop App with the current directory changed to the target installation directory. If you want to see the logs, you can retrieve them using the command prompt:

cd "C:\Program Files (x86)\Avid\MediaCentralUX"

MediaCentralUX.exe

128

6. Login, then open the View menu and select the Mos Enabaled option.

7. Click View / Reload.

8. Now you can open Maestro | News items.

9. The final steps is to enable simplified metadata in the Maestro | News MediaCentral | Newsroom Management Plugin settings. Select any Maestro | News item and open it. Right-click on the bottom bar and open the Preferences.

129

Select the Metadata section:

Select the Enable item metadata check box and enable the Simplified metadat radio button, then click OK.

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. Maestro | News MOS28 Plugin installed and configured on your workstation.

130

4. Maestro | Server is configured.

5. The MOS Server is installed, configured and running.

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:

131

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

132

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).

133

c. In the Version field select 1.0 iNews.

d. In the Platform field select ActiveX.

e. In the Placement field select Modal.

f. Enable the Show use option.

g. In the Implementation field, enter the GUID of the Maestro | News MOS28 Plugin, 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 <Plugin name> to insert a new MOS object.

4. You should now see the ActiveX plugin content.

134

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.



1. Octopus Server installed, configured and running.

2. HTML5 MOS Plugin installed and configured (e.g. on 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 131.

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.

135

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


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 <Plugin name> to insert a new MOS object.

4. You should now see the HTML5 plugin content.

136

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.



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.


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.

137

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.


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.

138

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 / <plugin name>.

139

Configuring Maestro | News HTML5 MOS to Work in AP ENPS



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.


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=<URL_of_plugin>.

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=<URL_of_plugin>.

4. Save the changes and restart the ENPS server.

140


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.

141

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

7. Click in the row content area, then select MOS / <plugin name>.

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.

142

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 GygClients 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).

143

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

144

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:

145

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. Run 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.

146

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 Server, i.e. the Maestro server itself, if the GDS is running on the Maestro Server.

147

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 (same you entered in the configuration above). Finally, press Connect.

148

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).

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.

149

4 Upgrading Components


• 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 | Render Engine and Avid VideoEngine components. Also, the Asset and RenderServer databases differ between various versions of Maestro | News.

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

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

Maestro | News

VideoEngine

Maestro | Core

ComponentsAsset database

RenderServer Database

Maestro | RenderEngine Maestro | Designer

2018.6 2018.6 2018.6 2018.6

7.5.x (>= 7.5.1)Native2 v142 2.0 4.2.3 7.3

1.4

7.5.01.3

7.4.x Native2 v141 1.9 4.2.1 7.2

7.3.x Native2 v136 or Native v12

1.6

4.0 7.1 1.2

7.2.x Native2 v133 or Native v12

1.4

7.1.x

3.57.0.x Native2 v133 or Native v12 or IBIS iFind

7.0 1.1

6.9.x Native v12 or IBIS iFind

not supported 6.10 1.0

6.8.x Native v12 or IBIS iFind

not supported 6.9 3Designer 3.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 that one ActiveX control with the same name.

Components that can be installed in different versions on the same machine:


• 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.

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

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

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).

152

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.


• 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 <drive>:\Orad\Installers folder. Or open the Control Panel, select Programs and Features, select component then click Change.

2. The “Welcome to <component name> 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 “Installing Maestro | News from Individual Installers” on page 52.

Repairing the Installation

The repairing process copies all the files (except 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:


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.

154

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.

Uninstalling MediaCentral | Maestro News

To remove MediaCentral | Maestro News:

1. Check the installed file versions:

rpm -qa | grep -i maestro

155

2. Uninstall the files with the following commands:

rpm -e maestro-ux-<version>.noarch.rpm

rpm -e maestro-ux-media-browser-<version>.noarch.rpm

rpm -e MaestroUX-<version>.x86_64.rpm

Notes

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

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: <target_installation_folder>\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: <drive>:\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.

156

The list below presents default locations for logs of other Avid components:

• Maestro | RenderEngine for Windows: <drive>:\Orad\RenderEngine64_<version>\bin\ - look for *.log files (usually RE.log).

• VideoEngine for Windows:

- <drive>:\Orad\VEServerWin\VE\bin\ve.log

- <drive>:\Orad\VEServerWin\VECommander\bin\OCIP.log

- <drive>:\Orad\VEServerWin\VECommander\bin\commander.log

• 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

• MediaCentral | UX: /var/log/avid/

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 MediaCentral | Maestro News or Maestro | News HTML5 MOS Plugin, you can use the built-in development tools of your internet browser to diagnose the source of any issues.

157

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

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 - <drive>:\Orad\MaestroRenderServer64\DBAPITestApplication.exe

• Automation Protocols component:

- CII Test Tool - Simulate Chyron Intelligent Interface (CII) protocol requests - <drive>:\Orad\AutomationProtocols64\CIIAx\CII_Test.exe

- VDCP Test Tool - Simulate Harris VDCP protocol requests - <drive>:\Orad\AutomationProtocols64\VdcpAx\VDCP_Test.exe

158

Basic Usage Instruction 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:

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.

159

Basic Usage 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.

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.

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

n The readAndUpdate option has the same functionality as the Cue operation in the Maestro | News 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 Usage 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.

160

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.

161

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 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) old 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 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 | UX have files placed in one folder, but renders from test application are placed directly in the result localization.

162

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 <database_name>;

TRUNCATE TABLE dbo.CompletedRequests;

For example:

USE RenderServer_76;

TRUNCATE TABLE dbo.CompletedRequests;

n These commands should not be run while other systems are requesting rendered data. Execute these 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 periodidcally 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.

163

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) 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. Please disable VideoEngine for Windows if it is not going to be used for a longer period of time (some of the VideoEngine applications may decrease the overall system performance) Stop the WinAppStarter service and close the VideoEngine application processes (for details refer to the FastServe | Playout Setup Guide).

3. 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).

4. 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.

5. 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 Server (your machine with the database).

2. Run the SQL Server Management Studio.

164

3. Login to the Maestro | News database instance (default credentials are sa / maestro; use the SQL Server Authentication)

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:

165

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:

166

3. Read the largest Version value on the Results pane, e.g.: the Maestro | News 7.5.x usesRenderServer database version 2.0.

Changing Components Settings Manually

c Any manual changes should be performed very carefully. It can lead to problems withinvestigating 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.

167

Avid Maestro | Newsresources.avid.com/SupportFiles/attach/Maestro/Maestro_News... · Avid Maestro |...

Documents

Transcript of Avid Maestro | Newsresources.avid.com/SupportFiles/attach/Maestro/Maestro_News... · Avid Maestro |...