Avid® Maestro™ | Engine 4K

Setup Guide
Version 2019.12
Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

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

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

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

Copyright © 2019 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
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
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.

Avid Maestro | Engine 4K Setup Guide v2019.12 • Created 12/13/19 • This document is distributed by Avid in online (electronic)
form only, and is not available for purchase in printed form.

4
 Contents

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2 Avid Maestro | Engine 4K Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Unpacking and Inspecting Your Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Unpack and Inspect Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Unpacking Your Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Verifying Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Inspecting Components for Damage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Hardware Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Maestro | Engine 4K Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Server Front Panel and LED Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Drive Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Avid Maestro | Engine 4K Server - Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
USB Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
VGA Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
SDI Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 3 Installing the Server Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Electrostatic Discharge Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing Maestro | Engine 4K Hardware in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Rack-mount Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing the Drives in the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Cabling the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Maestro | Engine 4K Server Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connecting the Power Cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connecting Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connecting a Keyboard, Monitor, and Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connecting Video Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connecting SDI Video Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Turning On the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 4 Installing The Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5
 Configuring BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Loading the CentOS 7.4 Image on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Preparing a Boot-able USB Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring the Server for Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Hostname Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Installing Kernel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Installing libdvg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Verifying the Bus Location of UHD3 and NVIDIA Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Updating the modprobe.conf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing the NVIDIA Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing the UHD3 Card Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Flashing the Daughterboard Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Setting Up RAID-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Mounting of Shared Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installing RenderEngine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Installing Maestro | Engine 4K Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 5 Configuring the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring RenderEngine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Audio Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Dual Main - 16 IN x 12 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring Maestro | Engine Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Dual Main - UHD with Alpha - 8 IN X 4 OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configuring Maestro | Engine Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Dual Main - UHD with Alpha - 8 IN x 4 OUT HDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring Maestro | Engine Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
UHD Mixing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring Maestro | Engine Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
UHD with Mixing + HDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configuring Maestro | Engine Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
UHD with Mixing and 2Si Output + HDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring Maestro | Engine Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Connecting Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Starting RenderEngine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Appendix A Layout.xml Custom Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
HD1080_10Canvases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
UHDWithAlpha . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2SiWithAlpha. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6
Appendix B Telestration using Render Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Render Engine Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Maestro | Designer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
ReTalk3 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Appendix C Safety and Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Important Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Rack-Mount Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
EMC (Electromagnetic Compliance) and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
FCC Notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Canadian ICES-003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Class A Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Australian Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Environmental Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Disposal of Waste Equipment by Users in the European Union . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Proposition 65 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Perchlorate Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Recycling Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7
 Using This Guide

Congratulations on your purchase of an Avid Maestro | Engine 4K server.

This guide contains all the installation, configuration, and setup instructions you need to install and
setup the Avid product.

Symbols and Conventions

Avid documentation uses the following symbols and conventions:

Symbol or Convention Meaning or Action

n A note provides important related information, reminders,

recommendations, and strong suggestions.

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

A warning describes an action that could cause you physical harm.

w Follow the guidelines in this document or on the unit itself when
handling electrical equipment.

> This symbol indicates menu commands (and subcommands) in the

order you select them. For example, File > Import means to open the
File menu and then select the Import command.

This symbol indicates a single-step procedure. Multiple arrows in a list

indicate that you perform one of the actions listed.

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

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

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

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

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

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

Avid Maestro | Engine 4K (RMN: UHDS) is an all-in-one digital video rendering platform. It is
designed to meet the real-time graphic rendering needs of the broadcast industry.

Maestro | Engine works in concert with Maestro | RenderEngine software, providing advanced
graphics rendering in the highest quality possible—whether displayed onscreen or in the studio.

Maestro | Engine 4K is solidly built to withstand the demands of 24/7 operation. It features dual
power supplies, dual network interfaces, and software and hardware watchdogs, so should a system
go offline, your production will not be interrupted. And because all Maestro graphics suite
applications can control multiple Maestro | Engines 4K, you can use additional engines as live
backups to your on-air systems.

No need to install additional client software or have a systems administrator tethered to your machine
room to manage and configure settings. The engine uses a web-based interface for all systems
management, enabling you to set up and make changes to user access rights, video formats, genlock
sources, input and output mapping, and other settings from any computer or device on your
network—from anywhere inside or outside your facility.
Technical Specifications
The below table presents the current hardware specification of the Maestro | Engine 4K system.

Motherboard AIC Phoenix

Graphic Card 2 x NVIDIA RTX 2080

CPU 2 x Intel E5-2640 v4

Operating System CentOS 7.4 w/customized kernel

Memory 64 GB DDR4

Internal Storage 2 x 240 GB system disk (RAID 1)

Hard disks for clips storage
4 x 2 TB (RAID10)

Ethernet 2 x 1000 BASE-T (RJ-45)

2 x 10GB (SFP+, optical modules optional)

Ports 1 Serial
2 USB (front)
2 USB (rear)

Control interfaces 1 x Serial

4 x USB
2 x Ethernet (1Gbit)
VGA
IPMI

Supported Video Standard 3G: ST 425-1:2014 (Level A), ST 425-5:2019 (level A) Quad-link 3G
HD: ST 260:1999, ST 295:1997, ST 274:2008

Video in (mixer) Up to four (4) 3G

Video in (insertion) Up to 8 3G, up to 16 HD SDI inputs

Video output Up to 16 HD SDI Outputs

Up to 8 3G Fill and 8 3G Key Outputs
Up to 4 3G HDR and 4 3G HDR Key Outputs
(video key compositing configurable);
Internal linear keyer

Video references Bi / Tri level Sync

Audio Embedded audio support 24-bit/48 kHz in HD/ 3G

Clip Options Video to texture mapping of AVI, QuickTime, DV, DVC25, and MPEG files
(optional)

Video bypass Up to 2 Mechanical bypasses, Watchdog on each DSK

10
Size Height:5.25 in (133.4 mm)
Width: 17.4 in (443 mm)
Depth: 29.5 in (750 mm)
Weight: 59.5 lbs (27 kg) approximate

Power supply Redundant power supply: 100-240 V

Frequency: 47-63 Hz
2 x 1500W (max)

11
 2 Avid Maestro | Engine 4K Server Overview

This guide covers everything you need to know to unpack, install and configure your Maestro |
Engine 4K server hardware and software.

This chapter provides an overview of the Maestro | Engine 4K server, starting with how to unpack
and inspect your server.

Once you have unpacked and inspected your server, the features and hardware of the Maestro |
Engine 4K server are discussed.

Maestro | Engine 4K server uses a 3U chassis containing four hard drives for clips storage, with
quick access to the front panel for disk replacement.

To safeguard system integrity, Maestro | Engine 4K runs on two system disks, using separate RAID
10 protection, and a dual hot swap power supply.

Topics in this chapter include:

• Unpacking and Inspecting Your Server
• Hardware Components

Unpacking and Inspecting Your Server

This topic provides information on how to unpack your server and associated components, and
inspect it to verify that you have received the appropriate components for your order, and that the
components are not damaged in any way.

Unpack and Inspect Checklist

The following table provides a checklist of tasks that must be performed when unpacking and
inspecting your Maestro | Engine 4K server.

b Unpack your Maestro | Engine 4K server, as described in “Unpacking Your Server” on page 13.

b Verify that you have all of the correct boxes and components, as described in “Verifying
Components” on page 13.

b Verify that the components are not damaged, as described in “Inspecting Components for Damage”
on page 14.
Unpacking Your Server

Before you unpack your server and components, make sure the location is free of clutter and dust.
Also, make sure you have clean power and a monitor nearby.

n The drives that were shipped with this server are pre-configured for use with this server only.
Therefore, when installing the drives, make sure to use these drives only.

To unpack your server:

1. Open the box.
2. Remove the server chassis and all components from the box.
Avid recommends that you keep all packaging materials for at least 90 days. If you need to return
a server to Avid Technology, Inc., the server and all components must be repackaged in its
original packaging material to ensure that there is no damage during shipment.
3. Remove all of the boxes, and lay them out so you can verify that you have received all of the
components that should have been shipped.
4. Once all of the components have been unpacked, visually inspect the chassis to make sure that it
is free of any scratches and dents, that there are straight connectors on the back, and that the
power-supply securing screws are not bent.
5. The next step is to verify that you have received all of the items particular to your order. For
more information, see “Verifying Components” on page 13.

Verifying Components

Once you have unpacked everything, verify that you have the following components:

Maestro | Engine Component List

Part Name

Maestro | Engine 4K Server

SATA Drives (4)

Power cables (2)

Rack mount kit (rails, clips, and screws)

Rack Rail adapter hardware (e.g., Round Hole adapters)

Service ID card

Customer Letter

c If you are missing any of these components, contact Avid Customer Support before proceeding.

n ReadMe files are not in the box. They can be found online. You should always check online for the
most up-to-date release notes or ReadMe because the online version is updated whenever new
information becomes available. To view these online versions, visit the Knowledge Base at
www.avid.com/readme.

13
Inspecting Components for Damage

Once you have verified that all of your components have been shipped, you must verify that they are
not damaged.

To inspect components for damage:

1. Visually inspect all of the hardware components listed in the previous section to make sure that
none of them were damaged during shipment.
2. If you received a hardware component that was damaged, contact Avid Customer Support.

Hardware Components
Maestro | Engine 4K Front Panel
The front of the Maestro | Engine 4K server provides access to the power button, activity LEDs,
storage error LED, and two USB sockets.

Each drive can be locked and unlocked with the use of a key that is provided with your server.

Front of the Server (front panel removed)

Regarding media drives, each media drive has a blue and red LED on the bottom front of the drive.
The left LED (blue) is lit when a drive has power and flashes when the drive is in use. The right LED
(red) is lit when an error is detected with the drive and the drive needs to be replaced. Details on the
media drive LED indicators are in the following table.

14
 Media Drive Example

• The left Power/Activity LED (blue) is solid when a drive has power and flashes when the drive
is in use.
• The right Fault LED (red) is lit when an error is detected, or if the drive is rebuilding or
initializing. It flashes fast when it is initializing or rebuilding an array. It flashes slow when there
is a suspected problem with the drive.

Server Front Panel and LED Control Panel

The server has one power button on the top right part of the server. The front panel also contains
activity LEDs, storage error LED, and two USB sockets.

Server Front View and LED Control Panels

The following table describes the LED Control Panels shown in the previous figure.

LED Control Panel

Letter Description Description

A Red System error LED Illuminates red when an error is detected with the
server (fan, power supply, temperature, voltage).

B Power LED Illuminates green when the server is powered on.

C System Drive activity LED Indicates drive activity from the onboard SATA
controller and blinks when either of the system
Power button
drives is being accessed.

D_E USB Socket Two USB sockets.

15
 LED Control Panel

Letter Description Description

F Non-maskable Interrupt Push for the highest priority interrupt in the

system.

G System Reset Push this button for a system reset.

Drive Array

For Maestro | Engine 4K server data integrity, RAID 10 configuration consisting of 4 striped disks
with dual parity is created.

n The media drives have been pre-RAIDed at the factory to save time installing and configuring your
server.

Avid Maestro | Engine 4K Server - Rear Panel

The rear panel of the Maestro | Engine 4K server provides access to the power supplies, 10 and 1
gigabit (Gb) Ethernet ports, VGA port, serial port, two USB connectors for the keyboard, mouse. The
availability of the Reference IN and Loop sockets, Video Inputs and Outputs depends on the chosen
specification.

Each of these components is described in the topics below.

16
Power Supplies

There are two power supplies accessible from the rear of the Maestro | Engine 4K server.

If a failure occurs on either one of the power supplies, you can pull the failed power supply out of the
server, and install a replacement power supply without turning off the Maestro | Engine 4K server.

All server operations continue to run uninterrupted.

Ethernet Ports

The Maestro | Engine 4K server is equipped with 4 Ethernet Ports (2 x10GB and 2 x1GB).

USB Ports

There are two USB ports located on the rear of the Avid Maestro | Engine 4K server.

17
VGA Port

There is one VGA port located on the rear of the Avid Maestro | Engine server.

Serial Port

There is one Serial port located on the rear of the Avid Maestro | Engine server.

Reference

There is one Reference input and one Reference loop port located on the rear of the Avid Maestro |
Engine server.

If the server is the last device in your reference loop, terminate the remaining Ref Loop through a
connector with an 75 ohm-rated terminator.

18
SDI Connections

SDI inputs and outputs connectors are linked to Maestro | Engine 4K input and output channels.

19
 3 Installing the Server Hardware

This chapter describes how to install a Maestro | Engine 4K server on your site.

Topics in this chapter include:

• Electrostatic Discharge Precautions
• Installing Maestro | Engine 4K Hardware in a Rack
• Installing the Drives in the Server
• Cabling the Server
• Turning On the Server

Electrostatic Discharge Precautions

Electrostatic discharge (ESD) can damage disk drives, cards, and other parts. Avid recommends that
you perform all procedures in this chapter only at an ESD workstation. If one is not available,
provide some ESD protection by wearing an antistatic wrist strap attached to chassis ground (any
unpainted metal surface) on your server when handling parts.

ESD and handling PCIe Cards

Always handle cards carefully. They can be extremely sensitive to ESD. Hold cards only by their
edges. After removing a card from its protective wrapper or from the server, place the card
component side up on a grounded, static free surface. Use a conductive foam pad if available but not
the card wrapper. Do not slide the card over any surface.

Installing Maestro | Engine 4K Hardware in a Rack

The Maestro | Engine 4K server is designed for 19-inch racks and requires three EIA rack units (3U),
or 180 mm of rack space. Dimensions of the Maestro | Engine 4K server are: Height 180mm; Width
443mm, Depth 580mm, Weight 17kg (approx.).

The Maestro | Engine 4Kserver includes rack mounting slide rails. The standard rail configuration is
for racks with square mounting holes. The rack-mounting kit requires inner slide rails be mounted to
the Maestro | Engine 4K server and the outer slide rails are mounted to the rack. Once both, the inner
and outer rails are in place, slide the server with the inner rails attached into the outer rails. Secure the
server in the rack so it does not slide forward.

c The Maestro | Engine 4K server is designed to be installed horizontally in a rack. Installing the
Maestro | Engine 4K on an angle or in a sloped console causes the internal drives to wear faster
than the intended life of the drive.

w To ensure the stability of the rack enclosure, start from the bottom when you install the rack
components in the rack enclosure.
Rack-mount Requirements
• Elevated Operating Ambient — If installed in a closed or multi-unit rack assembly, the operating
ambient temperature of the rack environment might be greater than room ambient. Therefore,
consider installing the equipment in an environment compatible with the maximum ambient
temperature (Tma) specified by the manufacturer.
• Reduced Air Flow — Installation of the equipment in a rack should be such that the amount of
air flow required for safe operation of the equipment is not compromised.
Airflow is from the front of the server to the rear. Make allowances for cooling air to be available
to the front panel surface and no restrictions at the rear.
• Mechanical Loading — Mounting of the equipment in the rack should be such that a hazardous
condition is not achieved due to uneven mechanical loading.
Make sure your rack enclosure is stable enough to prevent tipping over when one or more Avid
Maestro | Engine servers are extended on the sliding rails.
• Circuit Overloading — Consideration should be given to the connection of the equipment to the
supply circuit and the effect that overloading of the circuits might have on overcurrent protection
and supply wiring. Appropriate consideration of equipment nameplate ratings should be used
when addressing this concern.
• Reliable Grounding — Reliable grounding of rack-mounted equipment should be maintained.
Particular attention should be given to supply connections other than direct connections to the
branch circuit (for example, use of power strips).
• Inside Enclosure Access — If you want to extend the enclosure, and remove the top cover, you
must allow 0.5 in (1.3 cm) clearance on top of the enclosure for cover removal.
• Ventilation is handled through the sides of the unit; incoming air from the left, and cooling fans
on the right.
• If the Server is installed in a closed or multi-unit rack assembly, the operation's ambient
temperature of the rack may be greater than room ambient. Verify that the temperature in the
rack always stays within the 5C° to 40C° range.

c To prevent overheating, ensure there is enough room for ventilation.

Installing the Drives in the Server

This topic contains information on inserting drives in the Maestro | Engine 4K server.

n The drives that were shipped with this server are pre-configured for use with this server only.
Therefore, when installing the drives, make sure to use these drives only.

To install a drive in the Maestro | Engine server:

1. Locate the data drives that came with your Maestro | Engine 4K server.
2. Select one drive.
3. Push the drive carrier latch in to release the handle and pull the handle completely open to insert
the drive carrier.
4. Make sure the drive LEDs are on the bottom before you begin to slide the drive into the server.

21
 n When you are installing drives in the Avid Maestro | Engine 4K server, begin the installation at the
bottom of a column of drives. Make sure the first drive you install is level and flat as you insert it into
the server.

c Do not force a drive into a slot. If you are having problems installing a drive, check to make
sure it is level and flat as you insert it into the server, that the drive carrier latch is open and at
a 45 degree angle to the drive carrier, and that the LEDs are on the bottom of the drive carrier.

5. Slide the drive into the open drive slot in the server until it stops. Approximately 1/2 inch of the
drive carrier should be outside the server.
6. Push the handle into the drive carrier. This seats the drive in the server. You’ll hear a click when
the drive is fully seated and the handle latches in place.
7. Repeat steps 2 to 6 for the remaining drives.

Cabling the Server

Once the Maestro | Engine 4K server is securely installed in the rack, and the drives are installed, you
are now ready to connect the appropriate cables to the rear panel of the server to the external devices
for your particular site. This section contains the cabling diagrams and instructions for your Maestro
| Engine 4K server.

Maestro | Engine 4K Server Connection Information

The rear panel of the Maestro | Engine 4K server provides access to the power supplies, 1 gigabit
(Gb) Ethernet ports, VGA port, serial port, two USB connectors for the keyboard, mouse, Reference
IN and Loop sockets, and Video Inputs and Outputs.

Connecting the Power Cords

Your Maestro | Engine 4K server has two power supplies. If your local power distribution is not
compatible with the supplied cords, you must provide your own IEC power cables that are
compatible with your country's power system.

To connect/reconnect power:
1. Attach the power cords to both power receptacles on the rear of the server.
2. Connect the other end of both power cords to a properly grounded stable power source.

c For maximum power protection, Avid recommends a surge protected un-interruptible power
supply (UPS).

22
 c To avoid the risk of electrical shock and fire, inspect the system power cord and plug routinely.
Ensure they are not damaged in any way.

When all necessary connections have been completed and configured, switch on the Server by
pressing the POWER button on the front panel.

w This unit has two connections to the main supply. For protection against electric shock,
disconnect both electric cords before service.

c Do not remove the power module without gloves. The cover of the power module serves as a
heat-sink for cooling. Temperature can reach 60°C under full load condition. If removed, put
aside the power module until cool, and prevent anyone from touching it until it is cooled.

c Risk of explosion if lithium battery on motherboard is replaced by an incorrect type. Dispose of

used batteries according to the instructions.

Connecting Network
The Maestro | Engine 4K server comes equipped with two 1 Gigabit Ethernet ports.

The Server includes two network interface cards (NIC) for communication with the control hosts and
the general network.

To connect the Ethernet:

1. Your Ethernet switch should be rack mounted. Leave adequate room at the front for cables and at
the back for air circulation.
2. Locate Category 5E, 6, or 6A Ethernet cable(s).
3. Attach the other end of the Ethernet cable to suitable port in your switch.

Connecting a Keyboard, Monitor, and Mouse

You need to provide a standard USB compatible keyboard, monitor and mouse to access the Maestro
| Engine 4K server. The keyboard and mouse plug directly into either of the USB ports on the rear of
the chassis. Or, if you have a splitter, you can connect both to one USB connector and leave the other
USB connectors open for other purposes (such as connecting a removable USB hard drive).

n There are four USB ports on the Maestro | Engine 4K server (two on the rear and two on the front).

To connect a keyboard, monitor, and mouse to the server:

1. Place the monitor on a shelf, and the keyboard and mouse on a sliding tray in the rack. These
items are optional and can be purchased locally or from Avid.
2. Attach the VGA connector on the monitor cable to the VGA port on the back of the server.
Secure the connector with the thumbscrews on the connector.
3. Insert the other end of the USB adapter cable into one of the USB connectors on the back of the
server.

23
Connecting Video Reference
To work properly, the Maestro | Engine 4K server must receive a valid reference (Genlock) signal.

When using an analog GENLOCK source, you can connect one ANALOG REF plug as the input and
the other ANALOG REF connector on the rear panel will automatically serve as the output (Loop).

When using Analog GENLOCK, it is obligatory to put a 75-Ohm termination on the REF out.

Connecting SDI Video Inputs and Outputs

The Input/ Output connections vary according to the current settings.

To connect SDI video output cables on the chassis:

1. Ensure that you have proper SDI video (75 ohm-rated) interface coaxial cables available.
2. Connect the SDI output signal to an outgoing SDI output on the server.
3. Connect the other end of all SDI output cables to your devices that are receiving the output
signal from the server.

To connect SDI video input cables on the chassis:

1. Ensure that you have proper SDI video (75 ohm-rated) interface coaxial cables available.
2. Connect the SDI input signal to an incoming SDI output on the server.
3. Connect the other end of all SDI input cables to your devices that are sending the input signal to
the server.

Turning On the Server

When you turn on the power to your Maestro | Engine 4K server, you must do it in the following
order so that it will see all of its connected components.

To turn on the power for each component:

1. Make sure you have all your network cables connected.
2. Push the power button at the top right on the front of the your server.

24
 4 Installing The Operating System

This topic provides information on how to install the required software system on a Maestro | Engine
4K server. After performing this procedure, you will need to install the RenderEngine, and
reconfigure the software settings.

c The procedures included in this topic should be conducted by Avid Support personnel.

Installation Checklist
Having your hardware received, the first step to perform is to connect power cables, network cable,
VGA monitor and USB keyboard and power the system on, as described in the topic “Installing the
Server Hardware”.

The following table provides a checklist of tasks that must be performed when installing the
operating system for the first time on a Maestro | Engine 4K machine.

b Configure BIOS settings, as described in the topic Configuring BIOS.

b Install the CentOS 7 operating system provided by Avid. For more information, see Loading the CentOS 7.4
Image on the Server.

b Set up your Maestro | Engine 4K system, as described in “Configuring the Server for Your Network”.
Setting up your system involves the following:
• Assigning/ adjusting the IP address, gateway and DNS settings,
• Assigning/ changing the computer name (host name).

b If required, update the kernel as described in the topic Installing Kernel.

b Update libdvg, as described in the topic Installing libdvg.

b Check the PCI connections as described in Verifying the Bus Location of UHD3 and NVIDIA Cards.

b Edit the modprobe.conf file, as described in the topic Updating the modprobe.conf File.

b Install the NVIDIA Linux driver, as described in the topic Installing the NVIDIA Driver.

b Install the firmware for each UHD3 board and the daughterboards, as described in the topic Installing the UHD3
Card Firmware.

b If you don't have RAID yet, then create RAID10 for HDDs for Clips. See Setting Up RAID-10.

b Mount Control Data, as described in the topic Mounting of Shared Data.

b Install Maestro | RenderEngine, as described in the topic Installing RenderEngine. Make sure you have the
required licenses for RenderEngine and SharedLib.

b Install the Maestro | Engine Manager to further configure your system, as described in Installing Maestro | Engine
4K Manager.
Configuring BIOS
In the event that you need to reimage your Maestro | Engine 4K server, you should first check your
BIOS version before installing the CentOS 7 software. If the installed version is older than
Phaev086, update it.

If the installed version is correct, configure it as described below.

To configure BIOS:
1. Turn on or restart your Maestro | Engine 4K server.
2. Press the Esc button during the server start.
3. Press the SCU button on the screen.

4. Set the following parameters:

a. Go to SCU (BIOS) > Advanced > Advanced Power Management Configuration > EIST
(GV3) [Enable].
b. Then go to CPU P State Control. Change CPU P State Control options to:
- PL2_SAFETY_NET_ENABLE [Enable]
- Energy efficient P-state [Enable]
- Boot performance mode [Max Performance]
- Turbo Mode [Enable]
c. Go to Boot > Boot Type and change it to Legacy Boot Type.
d. Go to Boot > USB Boot and change it to Enabled.
5. Exit -> Exit Saving Changes = Yes.

26
Loading the CentOS 7.4 Image on the Server
Install the CentOS 7 image from the provided bootable drive. Insert the USB drive into one of the
USB ports and reboot the server. No additional steps are required during the installation.

c Before proceeding with the installation, disconnect the clips drives from the motherboard.

In case you need to prepare a bootable drive for the installation, follow the procedures described
below.

Preparing a Boot-able USB Drive

The boot-able USB drive should be delivered to you, but in case you need to prepare such drive,
follow the procedure below.

This topic contains information on how to prepare a bootable USB drive to reinstall CentOS 7 on
your system.

Using Linux

Using the dd command, convert an USB drive of at least 8GB:

Using the Windows Win32DiskImager

Win32DiskImager is a Windows program for saving and restoring images from removable drives. It
can be used to write boot images to a USB flash device, making it bootable.

27
Configuring the Server for Your Network
The following topics provide information how to configure the Maestro | Engine 4K server for your
network.

IP Configuration
Open the ifcfg files for each Ethernet port and update the network information there.

To assign an IP address:
1. Navigate to the network-scripts folder:
cd /etc/sysconfig/network-scripts
2. Open the ifcfg-ethX (replace X with your eth number) files:
vim ifcfg-ethX
3. Change the IP address. Obtain proper parameters from your network administrator.

4. Set a proper value for the DNS and Gateway parameters.

GATEWAY=X.X.X.X
DNS=X.X.X.X
DEFROUTE="yes"
5. To save and exit the file, type
:wq!
and press Enter.

Hostname Assignment
After assigning the IP address, set the hostname.

To change the host name:

1. Set the hostname with the hostnamectl command:
hostnamectl set-hostname NEW_HOST_NAME --static

c If you want to change the hostname of the machine after installing RAID-10 (software), you
will need to remove and install the RAID again.

2. Reboot the machine and connect to the new IP address.

28
Installing Kernel
If your Linux is freshly installed, use the newest available kernel.

n The installation process described in this chapter assumes that the machine is installed from scratch.
If this is not the case, remove all previous rpm installations to avoid problems.

To install kernel:
1. Download the following file:
kernel-3.10.0-693.5.2.el7.Avid.x86_64.rpm
2. Execute the following command:
rpm -ivh kernel-3.10.0-693.5.2.el7.Avid.x86_64.rpm
3. Reboot your server.

Installing libdvg
The next step is to install the latest libdvg middleware.

n When performing an upgrade of the operating system instead of a clean installation, make sure to
remove the previous version of libdvg before installing the newest version.

To uninstall libdvg:
1. Check the current version with the following command:
rpm -qa | grep libdvg
The command returns the libdvg package name.
2. Copy the libdvg package name and execute the following command:
rpm -e libdgv_package_name

To install libdvg:
1. Download the following file:
libdvg-813.1-16.el7.centos.x86_64.rpm
2. Execute the following command:
rpm -I libdvg-813.1-16.el7.centos.x86_64.rpm
3. Reboot your server.

29
Verifying the Bus Location of UHD3 and NVIDIA Cards
After installing libdvg, check on which PCI slots the uhd boards and NVIDIA cards are currently
configured.

To check the NVIDIA and uhd cards bus location on PCI:

1. Verify the location of UHD3 cards by executing the following command:
lspci | grep -i orad
Check the response:
04:00.0 Bridge: Orad Hi-Tec Systems Device 1980 (rev 12)
86:00.0 Bridge: Orad Hi-Tec Systems Device 1980 (rev 12)
2. Verify the location of NVIDIA cards by executing the following command:
lspci | grep -i nvidia
Check the response:
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1e87 (rev a1)
87:00.0 VGA compatible controller: NVIDIA Corporation Device 1e87 (rev a1)

Updating the modprobe.conf File

The next step involves checking if the DVG modules are enabled in the modprobe.conf file.

To add DVG modules to the modprobe.conf file:

1. Open the modprobe.conf file:
vim /etc/modprobe.d/modprobe.conf
2. Add the following:
alias char-major-121 dvgg
options dvgg major=121

alias char-major-122 dvgh

options dvgh major=122 only_bus=0x04
alias char-major-123 dvgi
options dvgi major=123 only_bus=0x86

options nvidia nv_pbo_cached=1

3. Save the file and exit vim.

30
Installing the NVIDIA Driver
This topic describes how to install the NVIDIA driver.

n When performing an upgrade of the operating system instead of a clean installation, make sure to
remove the previous versions of the NVIDIA driver before installing the newest version.

To install the NVIDIA driver:

1. Install the NVIDIA driver by copying the tgz file to /data/public and extract it to the
data/ folder.
cd /data
tar xzvf data/public/nvidia-410.78-1.0.tgz
2. Change the current location to /data/NVIDIA-Linux-x86_64-410.78 and run the
NVIDIA driver installer.
cd /data/NVIDIA-Linux-x86_64-410.78
./orad-installer
3. Answer YES to all the installer questions.
4. After the installation completes, verify that the NVIDIA driver version is AvidVer: 1.0.
modinfo nvidia | grep AvidVer

Installing the UHD3 Card Firmware

This topic describes how to install the latest firmware of the DVG cards.

n If an uhd card already has a different firmware installed, please remove it first. There could be a
number of firmwares installed on each board. Delete them in a descending order, start with the
highest firmware number to the lowest.

To remove an UHD3 card firmware:

1. Check the current configuration of the UHD3 card (for domain 0 in this example):
setenv DVG_DOMAIN 0
dvgflash -board 0 -reconf -list
2. Delete the second firmware installed on the board first:
dvgflash -board 0 -delete 2
3. Delete the first firmware installed on the board:
dvgflash -board 0 -delete 1

c Never delete the 0 element in the board as this will lead to board damage!

To burn new firmware:

1. To flash new firmware for domain 0:
setenv DVG_DOMAIN 0
dvgflash -board 0 -reconf -list
dvgflash -board 0 -write /data/public/uhd3_gfx_3814.bin -quick

31
 2. To flash new firmware for domain 1:
setenv DVG_DOMAIN 1
dvgflash -board 0 -reconf -list
dvgflash -board 0 -write /data/public/uhd3_gfx_3814.bin -quick

n To run graphics applications with domains on Maestro | Engine 4K Dual Channel, please note the
following: graphics card PCI bus for Domain O is 04:00 and graphics card PCI bus for Domain 1 is
03:00.

Flashing the Daughterboard Firmware

This topic describes how to install the latest firmware on the daughterboards.

n If a daughterboard already has a different firmware installed, please remove it first. There could be a
number of firmwares installed on each board. Delete them in a descending order, start with the
highest firmware number to the lowest.

To remove an existing firmware:

1. Check the current configuration of the board:
dvgflash -board 0 -reconf -list
2. Switch to the daughterboard firmware and display a list:
dvgflash -board 0 -slaveselect 1 -list
3. Delete the current firmware for the 1st and 2nd boards (replace X with the board number):
dvgflash -board 0 -slaveselect 1 -delete X

To burn new firmware:

1. To flash new firmware for the daughterboards (replace X with the board number):
dvgflash -board X -slaveselect 1 -write /data/public/dp_v14.bin -quick
2. Verify the current firmware version (replace X with the board number):
dvgflash -board X -slaveselect 1 -list
The results should be similar to the output below:

32
Setting Up RAID-10
If you don't have RAID yet, then create RAID10 for HDDs for Clips.

To create RAID:
t Use the following scripts: create_raid_10_ver2_1.sh and remove_raid.sh for an
automated creation and removal of RAID-10.

Mounting of Shared Data

This topic describes how to mount the Shared Data component on your machine.

To mount Shared Data manually:

1. Create a file containing the user account data (user name, password and domain) and save it to a
chosen location (such as /etc/credentials).
username=
password=
domain=
2. Create the /Control_Data directory and modify the access permissions by changing chmod to
777.
3. Mount the Shared Data:
mount -v -t cifs //WINDOWS_IP/SHAREDDIRECTORY /Control_Data/ -o credentials=/
etc/.credentials -o sec=ntlm
You should receive the following result if the mounting was successful.
mount.cifs kernel mount options: ip=WINDOWS_IP,unc=//WINDOWS_IP/
SHAREDDIRECTORY,sec=ntlm,user=YOURUSER,domain=YOURDOMAIN,pass=********

To mount Shared Data automatically:

1. Create a file containing the user account data (user name, password and domain) and save it to a
chosen location (such as /etc/credentials).
username=
password=
domain=
2. Create the /Control_Data directory and modify the access permissions by changing chmod to
777.
3. Edit the /etc/fstab file and add the following line:
//WINDOWS_IP/SHAREDDIRECTORY /Control_Data cifs credentials=/
etc/.credentials,rw,uid=1000,gid=1000,vers=2.0,nounix,iocharset=utf8,file_m
ode=0777,dir_mode=0777,sec=ntlm 0 0
4. Mount the Shared Data using the following command:
mount /Control_Data

n If you have a “mount error(13): Permission denied”, you can try to change the sec= parameter to
one from the list below:

33
Installing RenderEngine
Now, you can install Maestro | RenderEngine for Linux.

To install RenderEngine for Linux:

1. Download the installer of the Installation Manager for RenderEngine on Linux.
2. Run the installer and follow the steps of the installation using default settings.
3. Run the newly installed RenderEngineLinux_InstallationManager located in the C:\Program
Files\Avid\RenderEngineLinux folder.
4. Click on New Host, then enter the address of the Maestro | Engine 4K machine where
RenderEngine is going to be installed.

If there is an older version of RenderEngine already installed on the machine, uninstall it. Back
up the current RenderEngine settings, if required.

5. Select the created host and click Install RenderEngine.

34
 6. Exit the installer.

Installing Maestro | Engine 4K Manager

The Maestro | Engine Manager (MEM) is a web-based configuration tool that allows to setup your
Maestro | Engine machine.

To install Maestro | Engine Manager on your Maestro | Engine 4K machine:

1. Download the installer of the Installation Manager for Maestro | Engine Manager.
2. Run the installer and follow the steps of the installation using default settings.
3. Run the newly installed InstallationManager for MaestroEngineManager.
4. Click on New Host, then enter the address of the Maestro | Engine 4K machine where the MEM
is going to be installed.

If there is an older version of MEM already installed on that particular machine, uninstall it.
5. Select the created host and click Install.
6. Exit the installer.

35
 5 Configuring the Server

After installing the operating system and the RenderEngine on your Maestro | Engine 4K machine,
the next step is to configure it according to your requirements.

The following topics are discussed:

• Configuring RenderEngine
• Starting RenderEngine

Configuring RenderEngine
General Settings
First, open the /data/RE/bin/start.sh script file to enable and configure the
RCTL_PLUGIN. Then, you need to update the started.sh file. Finally, create a new apply-
phy.sh file and execute it.

Enable the RCTL_PLUGIN in start.sh:

t Open the /data/RE/bin/start.sh file and enable the RCTL_PLUGIN, as shown below:
set RCTL_PLUGIN=1

Edit the started.sh script file:

t Add the following line at the end of the script:
/usr/dvg/apply-phy.sh $DOMAIN 2>&1 | sed 's/^/'$PREFIX'/'

Create and execute the apply-phy.sh script:

1. Create a new apply-phy.sh file and add the following content inside of it:
#!/bin/sh

#BOARD=0
#if [ $# -ge 1 ]; then
# BOARD=$1
#fi

#continuned on the following page

pushd /usr/dvg
for i in 0 1
do
BOARD=$i
echo "Looping ... number $BOARD"

./rctlsend localhost i2cw $BOARD 7 0xe0 0 1

./rctlsend localhost i2cw $BOARD 7 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 7 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 7 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 7 0xe0 0 2
./rctlsend localhost i2cw $BOARD 7 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 7 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 7 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 7 0xe0 0 4
./rctlsend localhost i2cw $BOARD 7 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 7 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 7 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 7 0xe0 0 8
./rctlsend localhost i2cw $BOARD 7 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 7 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 7 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 8 0xe0 0 1
./rctlsend localhost i2cw $BOARD 8 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 8 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 8 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 8 0xe0 0 2
./rctlsend localhost i2cw $BOARD 8 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 8 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 8 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 8 0xe0 0 4
./rctlsend localhost i2cw $BOARD 8 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 8 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 8 0x3a 0x31 0x40
#
./rctlsend localhost i2cw $BOARD 8 0xe0 0 8
./rctlsend localhost i2cw $BOARD 8 0x3a 0xff 0x05
./rctlsend localhost i2cw $BOARD 8 0x3a 0x30 0x27
./rctlsend localhost i2cw $BOARD 8 0x3a 0x31 0x40

37
 done

popd

2. Place the apply-phy.sh file in the /usr/dvg/ folder and execute the script:
chmod a+x /usr/dvg/apply-phy.sh

Audio Configuration
To support all the required audio sources, the /data/RE/bin/AudioMixer.xml file needs to
be modified. To allow audio from 8 insertions the following entries needs to be modified:

38
Dual Main - 16 IN x 12 OUT
The 16 X12 configuration is mainly used for video wall setup. It allows grabbing 16 inputs and
produces 12 HD outputs (including a preview for the Maestro | PowerWall workflow).

n In case of the 1080p standard, the maximum number of outputs is 8, and the maximum number of
inputs is 8 as well.

c In Dual Main configurations, it is highly recommended to use 2 preview outputs. This means
that there will be 6 PGM outputs + 2 PVW outputs in 1080p, and 10 PGM outputs + 2 PVW
outputs in 1080i.

Start.sh Configuration

First, open the /data/RE/bin/start.sh script file to add supplementary variables required for
this configuration to work.

Edit the start.sh file:

1. Add the following variables at the beginning of the start.sh script:

setenv DVG_DUAL_MAIN Required for the dual GPU+DVG configuration.

setenv HDVG_VIDIN_PBO_ALIASING Required to enable 16 insertions for both cards.
setenv DVGCE_DECODER_THREADS 4 Required to enable multithread clip decoding.
setenv HDVG_ENABLE_YUV_CLIPS Required to improve clip performance during playout

n It might introduce peaks when loading clips.

#setenv HDVG_DBG_FLAGS 0x20000000 Required to enable pre-allocated textures for clips.

n It cannot be used with the YUV mode, but it can reduce peaks
when loading clips.

setenv DVG_CONN_DVI 0 Required to set the proper connector (DisplayPort)

2. Uncomment the LD_PRELOAD setting in multi GL mode to avoid losing performance:

setenv LD_PRELOAD /data/RE/lib_extern/libglsquared64.so

39
 RE.xml Configuration
Then, open the RE.xml file to set the required layout and enable CPU cores logging. In our example,
a custom layout HD1080_10CANVASES is set and layout auto detection is disabled.

c When configuring canvases in dual main configuration, please remember to avoid crossed
routings between the cards as it costs additional performance. Try to optimize layout, so one
canvas is always routed to outputs from range 1-6 OR 9-14 as canvas will be rendered only on
one graphic card in such case.

Edit the RE.xml file:

t Open the /data/RE/bin/RE.xml file and set the desired layout.
<Layout
ConfigPathName="Layout.xml"
DetectName="No"
Name="HD1080_10CANVASES"
Log="Yes"
AutoReactivateScenes="No"
/>

n If your Layout.xml file does not contain the HD1080_10Canvases configuration, copy it from
“Layout.xml Custom Configurations” on page 67 and paste it to the Layouts node.

t Enable CPU cores logging.

<Cores
ConfigPathName="Cores.xml"
Log="Yes"
SetPriority="Yes"
MaxProcessPriority="Realtime"
MaxThreadPriority="Realtime"
Limit="*"
/>
t Enable multi-rendering, as shown below.
<Renderer
ContextPlugin="EbREOpenGL">
<Thread
On="Yes">
<Multi On="Yes" Count="2" Scissor="Yes" SkipUnrelatedCanvas="Yes"/>
<DetectLongCommands On="No" Ms="1"/>
</Thread>

40
 Cores.xml Configuration
Then, open the Cores.xml file to verify the RE threads affinity .

Verify the Cores.xml file:

t Open the /data/RE/bin/Cores.xml file and in the <DualGPU> section verify the
affinity settings:
<!-- One RE working on two GPUs -->
<DualGPU>
<Config HyperThreading="Yes,No" CoresCount="4-24" UseRealtimeGroup="Yes">
<NormalAffinity Value="1,5-24"/>
<RealtimeAffinity Value="2-4"/>
</Config>
</DualGPU>

Configuring Maestro | Engine Manager

The Maestro | Engine Manager is a web-based configuration tool that allows to setup your Maestro |
Engine 4K machine. Install the Maestro | Engine Manager as described in the Installing Maestro |
Engine Manager topic.

In our example configuration below, the render channels parameter is set to 6, which means in Dual
Main setup the total number of outputs will be 12 (outputs 1 to 6 on the1st dvg board and outputs 9 to
14 on the 2nd dvg board).

Global

Set the Genlock type required for your configuration. When selecting a 1080i format, the Frame
Rendering option is automatically set to Auto (Off). Select an SDR(8-bit) color model and color
space for your Inputs and Outputs.

41
Board 1

Set as many Fill Only insertions as required by your configuration. Render channels parameter is set
to 6, which means in DualMain setup that the total number of outputs will be 12 (outputs 1 to 6 on 1st
dvg board and outputs 9 to 14 on 2nd dvg board).

Board 1 - Advanced

In this case, Auto output type is enabled and all Outputs are automatically set to Graphics type.

42
Board 2

Set as many Fill Only insertions on the second card as required by your configuration. Make sure that
the Pipeline and GFX Optimized options are enabled.

Audio Presets, Controller Presets, Frame Accuracy, Clips

You can leave the default options for the Audio Presets, Controller Presets, Frame Accuracy and
Clips options if there are no special requirements.

43
Dual Main - UHD with Alpha - 8 IN X 4 OUT
The configuration described here allows grabbing 16 inputs and produces 4 UHD outputs.

Start.sh Configuration

First, open the /data/RE/bin/start.sh script file to add supplementary variables required for
this configuration to work.

Edit the start.sh file:

t Add the following variables at the beginning of the start.sh script:

setenv DVG_DUAL_MAIN Required for the dual GPU+DVG configuration.

setenv HDVG_VIDIN_PBO_ALIASING Required to enable 16 insertions for both cards.
setenv DVGCE_DECODER_THREADS 4 Required to enable multithread clip decoding.
setenv HDVG_ENABLE_YUV_CLIPS Required to improve clip performance during playout

n It might introduce peaks when loading clips.

#setenv HDVG_DBG_FLAGS 0x20000000 Required to enable pre-allocated textures for clips.

n It cannot be used with the YUV mode, but it can reduce peaks
when loading clips.

setenv DVG_CONN_DVI 0 Required to set the proper connector (DisplayPort)

t Uncomment the LD_PRELOAD setting in multi GL mode to avoid losing performance:

setenv LD_PRELOAD /data/RE/lib_extern/libglsquared64.so

RE.xml Configuration
Then, open the RE.xml file to set the required layout and enable CPU cores logging. In our example,
a custom layout UHDWithAlpha is set and layout auto detection is disabled.

Edit the RE.xml file:

t Open the /data/RE/bin/RE.xml file and set the desired layout.
<Layout
ConfigPathName="Layout.xml"
DetectName="No"
Name="UHDWithAlpha"
Log="Yes"
AutoReactivateScenes="No"
/>

n If your Layout.xml file does not contain the UHDWithAlpha configuration, copy it from “Layout.xml
Custom Configurations” on page 67.

44
 t Enable multi-rendering, as shown below.
<Renderer
ContextPlugin="EbREOpenGL">
<Thread
On="Yes">
<Multi On="Yes" Count="2" Scissor="Yes" SkipUnrelatedCanvas="Yes"/>
<DetectLongCommands On="No" Ms="1"/>
</Thread>

t Enable CPU cores logging.

<Cores
ConfigPathName="Cores.xml"
Log="Yes"
SetPriority="Yes"
MaxProcessPriority="Realtime"
MaxThreadPriority="Realtime"
Limit="*"
/>
Cores.xml Configuration
Then, open the Cores.xml file to verify the RE threads affinity .

Check the Cores.xml file:

t Open the /data/RE/bin/Cores.xml file and in the <DualGPU> section verify the
affinity settings:
<DualGPU>
<Config HyperThreading="Yes,No" CoresCount="4-24"
UseRealtimeGroup="Yes">
<NormalAffinity Value="1,5-24"/>
<RealtimeAffinity Value="2-4"/>
</Config>
</DualGPU>

Configuring Maestro | Engine Manager

The Maestro | Engine Manager is a web-based configuration tool that allows to setup your Maestro |
Engine 4K machine. Install the Maestro | Engine Manager as described in the Installing Maestro |
Engine Manager topic.

45
Global

In UHD scenarios, a 1080p (@50 or @59 HZ) format needs to be selected. The Frame Rendering
option is automatically set to Auto (On). Set the Genlock type required for your configuration.
Select an SDR (8-bit) color model and color space for your Inputs and Outputs.

Board 1

For this scenario, the Alpha Rendering option is enabled. Set as many insertions as required by your
configuration. When disabling an Input, all inputs below will be disabled as well. Setting the Render
Channels value to 2, allows to set up a total number of 4 outputs.

46
Board 1 - Advanced

In this case, Auto output type is enabled and all required Outputs are automatically set to Graphics
type.

Board 2

Set as many Fill Only insertions on the second card as required by your configuration. Make sure that
the Pipeline and GFX Optimized options are enabled.

Audio Presets, Controller Presets, Frame Accuracy, Clips

47
Dual Main - UHD with Alpha - 8 IN x 4 OUT HDR
The configuration described here allows grabbing 16 inputs and produces 4 UHD outputs, with the
linear workflow enabled.

Start.sh Configuration

First, open the /data/RE/bin/start.sh script file to add supplementary variables required for
this configuration to work.

Edit the start.sh file:

1. Add the following variables at the beginning of the start.sh script:

setenv DVG_DUAL_MAIN Required for the dual GPU+DVG configuration.

setenv HDVG_VIDIN_PBO_ALIASING Required to enable 16 insertions for both cards.
setenv DVGCE_DECODER_THREADS 4 Required to enable multithread clip decoding.
setenv HDVG_ENABLE_YUV_CLIPS Required to improve clip performance during playout.

n It might introduce peaks when loading clips.

#setenv HDVG_DBG_FLAGS 0x20000000 Required to enable pre-allocated textures for clips.

n It cannot be used with the YUV mode, but it can reduce peaks
when loading clips.

setenv DVG_CONN_DVI 0 Required to set the proper connector (DisplayPort).

2. Uncomment the LD_PRELOAD setting in multi GL mode to avoid losing performance:

setenv LD_PRELOAD /data/RE/lib_extern/libglsquared64.so

Edit the RE.xml file:

t Open the /data/RE/bin/RE.xml file and set the desired layout.
<Layout
ConfigPathName="Layout.xml"
DetectName="No"
Name="UHDWithAlpha"
Log="Yes"
AutoReactivateScenes="No"
/>

n If your Layout.xml file does not contain the UHDWithAlpha configuration, copy it from “Layout.xml
Custom Configurations” on page 67.

48
t Enable multi-rendering, as shown below.
<Renderer
ContextPlugin="EbREOpenGL">
<Thread
On="Yes">
<Multi On="Yes" Count="2" Scissor="Yes" SkipUnrelatedCanvas="Yes"/>
<DetectLongCommands On="No" Ms="1"/>
</Thread>
t Enable CPU cores logging.
<Cores
ConfigPathName="Cores.xml"
Log="Yes"
SetPriority="Yes"
MaxProcessPriority="Realtime"
MaxThreadPriority="Realtime"
Limit="*"
/>
t Enable the Linear Workflow.
<LinearWorkflow
On="Yes"
RenderingSpace="Rec.2020"
Format="16F">
<FormatDetails>
<HdrPq ReferenceWhiteNits="100" PeakWhiteNits="4000" />
<HdrHlg ReferenceWhiteNits="100" PeakWhiteNits="1000" />
</FormatDetails>
</LinearWorkflow>
Cores.xml Configuration
Then, open the Cores.xml file to verify the RE threads affinity .

Edit the Cores.xml file:

t Open the /data/RE/bin/Cores.xml file and in the <DualGPU> section verify the
affinity settings:
<DualGPU>
<Config HyperThreading="Yes,No" CoresCount="4-24"
UseRealtimeGroup="Yes">
<NormalAffinity Value="1,5-24"/>
<RealtimeAffinity Value="2-4"/>
</Config>
</DualGPU>

49
Configuring Maestro | Engine Manager

The Maestro | Engine Manager is a web-based configuration tool that allows to setup your Maestro |
Engine 4K machine. Install the Maestro | Engine Manager as described in the Installing Maestro |
Engine Manager topic.

Global

In UHD scenarios, a 1080p (@50 or @59 HZ) format needs to be selected. The Frame Rendering
option is automatically set to Auto (On). Set the Genlock type required for your configuration.
Select an HDR (10-bit) color model and color space for your Inputs and Outputs.

Board 1

50
For this scenario, the Alpha Rendering option is enabled. Set as many insertions as required by your
configuration. When disabling an Input, all inputs below will be disabled as well. Setting the Render
Channels value to 2, allows to set up a total number of 4 outputs.

Board 1 - Advanced

Make sure that the Pipeline and GFX Optimized options are enabled.

Board 2

Set as many insertions as required for your configuration. Our scenario uses 4 insertions on each
board.

51
Audio Presets, Controller Presets, Frame Accuracy, Clips

52
UHD Mixing
This chapter describes how to configure Maestro | Engine 4K in DualMain using an UHDWithAlpha
layout, with mixing enabled.

Start.sh Configuration

First, open the /data/RE/bin/start.sh script file to add supplementary variables required for
this configuration to work.

Edit the start.sh file:

t Add the following variables at the beginning of the start.sh script:

setenv DVG_DUAL_MAIN Required for the dual GPU+DVG configuration.

setenv HDVG_VIDIN_PBO_ALIASING Required to enable 16 insertions for both cards.
setenv DVGCE_DECODER_THREADS 4 Required to enable multithread clip decoding.
setenv HDVG_ENABLE_YUV_CLIPS Required to improve clip performance during playout.

n It might introduce peaks when loading clips.

#setenv HDVG_DBG_FLAGS 0x20000000 Required to enable pre-allocated textures for clips.

n It cannot be used with the YUV mode, but it can reduce

peaks when loading clips.

setenv DVG_CONN_DVI 0 Required to set the proper connector (DisplayPort).

setenv DVG_UNIFIED_OUTPUT_CLOCKING Required to set unified clocking on outputs.

t Uncomment the LD_PRELOAD setting in multi GL mode to avoid losing performance:

setenv LD_PRELOAD /data/RE/lib_extern/libglsquared64.so

RE.xml Configuration
Then, open the RE.xml file to set the required layout and enable CPU cores logging. In our example,
a custom layout UHDWithAlpha is set and layout auto detection is disabled.

Edit the RE.xml file:

t Open the /data/RE/bin/RE.xml file and set the desired layout.
<Layout
ConfigPathName="Layout.xml"
DetectName="No"
Name="UHDWithAlpha"
Log="Yes"
AutoReactivateScenes="No"
/>

n If your Layout.xml file does not contain the UHDWithAlpha configuration, copy it from “Layout.xml
Custom Configurations” on page 67.

53
 t Enable multi-rendering, as shown below.
<Renderer
ContextPlugin="EbREOpenGL">
<Thread
On="Yes">
<Multi On="Yes" Count="2" Scissor="Yes" SkipUnrelatedCanvas="Yes"/>
<DetectLongCommands On="No" Ms="1"/>
</Thread>
Cores.xml Configuration
Then, open the Cores.xml file to verify the RE threads affinity .

Edit the Cores.xml file:

t Open the /data/RE/bin/Cores.xml file and in the <DualGPU> section verify the
affinity settings:
<DualGPU>
<Config HyperThreading="Yes,No" CoresCount="4-24"
UseRealtimeGroup="Yes">
<NormalAffinity Value="1,5-24"/>
<RealtimeAffinity Value="2-4"/>
</Config>
</DualGPU>

Configuring Maestro | Engine Manager

The Maestro | Engine Manager is a web-based configuration tool that allows to setup your Maestro |
Engine 4K machine. Install the Maestro | Engine Manager as described in the Installing Maestro |
Engine Manager topic.

Global

In UHD scenarios, a 1080p (@50 or @59 HZ) format needs to be selected. The Frame Rendering
option is automatically set to Auto (On). Select an SDR (8-bit) color model and color space for your
Inputs and Outputs. Set the Genlock type to DIGITAL to synchronize Maestro | Engine 4K to the
incoming signal of mixing.

54
Board 1

Activate mixing on Outputs 1 and 3, set Compositing as the Output type and connect mixing sources
to Inputs 7 and 8 on both DVG boards. Outputs 5-8 can be left with default options because they are
not used in this scenario.

Board 1 - Advanced

Make sure that the Pipeline and GFX Optimized options are enabled.

55
 Board 2

Set as many insertions as required for your configuration. Our scenario uses 4 insertions on each
board.

n If mixing sources from the second board are not displayed on output, add the following line at the end
of the start.sh file:

sleep 30;

/usr/dvg/rctlsend localhost chaninroute 1 1

Audio Presets, Controller Presets, Frame Accuracy, Clips

56
UHD with Mixing + HDR
This chapter describes how to configure Maestro | Engine 4K in DualMain using an UHDWithAlpha
layout, with mixing and linear workflow enabled.

Start.sh Configuration

First, open the /data/RE/bin/start.sh script file to add supplementary variables required for
this configuration to work.

Edit the start.sh file:

t Add the following variables at the beginning of the start.sh script:

setenv DVG_DUAL_MAIN Required for the dual GPU+DVG configuration.

setenv HDVG_VIDIN_PBO_ALIASING Required to enable 16 insertions for both cards.
setenv DVGCE_DECODER_THREADS 4 Required to enable multithread clip decoding.
setenv HDVG_ENABLE_YUV_CLIPS Required to improve clip performance during playout.

n It might introduce peaks when loading clips.

#setenv HDVG_DBG_FLAGS 0x20000000 Required to enable pre-allocated textures for clips.

n It cannot be used with the YUV mode, but it can reduce

peaks when loading clips.

setenv DVG_CONN_DVI 0 Required to set the proper connector (DisplayPort).

setenv DVG_UNIFIED_OUTPUT_CLOCKING Required to set unified clocking on outputs.

t Uncomment the LD_PRELOAD setting in multi GL mode to avoid losing performance:

setenv LD_PRELOAD /data/RE/lib_extern/libglsquared64.so

RE.xml Configuration
Then, open the RE.xml file to set the required layout and enable CPU cores logging. In our example,
a custom layout UHDWithAlpha is set and layout auto detection is disabled.

Edit the RE.xml file:

t Open the /data/RE/bin/RE.xml file and set the desired layout.
<Layout
ConfigPathName="Layout.xml"
DetectName="No"
Name="UHDWithAlpha"
Log="Yes"
AutoReactivateScenes="No"
/>

n If your Layout.xml file does not contain the UHDWithAlpha configuration, copy it from “Layout.xml
Custom Configurations” on page 67.

57
 t Enable multi-rendering, as shown below.
<Renderer
ContextPlugin="EbREOpenGL">
<Thread
On="Yes">
<Multi On="Yes" Count="2" Scissor="Yes" SkipUnrelatedCanvas="Yes"/>
<DetectLongCommands On="No" Ms="1"/>
</Thread>
t Enable Linear Workflow (HDR).
<LinearWorkflow
On="Yes"
RenderingSpace="Rec.2020"
Format="16F">
<FormatDetails>
<HdrPq ReferenceWhiteNits="100" PeakWhiteNits="4000" />
<HdrHlg ReferenceWhiteNits="100" PeakWhiteNits="1000" />
</FormatDetails>
</LinearWorkflow>

Cores.xml Configuration
Then, open the Cores.xml file to verify the RE threads affinity .

Edit the Cores.xml file:

t Open the /data/RE/bin/Cores.xml file and in the <DualGPU> section verify the
affinity settings:
<DualGPU>
<Config HyperThreading="Yes,No" CoresCount="4-24"
UseRealtimeGroup="Yes">
<NormalAffinity Value="1,5-24"/>
<RealtimeAffinity Value="2-4"/>
</Config>
</DualGPU>

Configuring Maestro | Engine Manager

The Maestro | Engine Manager is a web-based configuration tool that allows to setup your Maestro |
Engine 4K machine. Install the Maestro | Engine Manager as described in the Installing Maestro |
Engine Manager topic.

58
Global

In UHD scenarios, a 1080p (@50 or @59 HZ) format needs to be selected. The Frame Rendering
option is automatically set to Auto (On). Select an HDR color model (10-bit) and color space for
your Inputs and Outputs. Set the Genlock type to DIGITAL to synchronize Maestro | Engine 4K to
the incoming signal of mixing.

Board 1

Activate mixing on Outputs 1 and 3, set Compositing as the Output type and connect mixing sources
to Inputs 7 and 8 on both DVG boards. Outputs 5-8 can be left with default options because they are
not used in this scenario.

Board 1 - Advanced

Make sure that the Pipeline and GFX Optimized options are enabled.

59
 Board 2

Set as many insertions as required for your configuration. Our scenario uses 4 insertions on each
board.

n If mixing sources from the second board are not displayed on Output, add the following line at the
end of the start.sh file:

sleep 30;

/usr/dvg/rctlsend localhost chaninroute 1 1

Audio Presets, Controller Presets, Frame Accuracy, Clips

60
UHD with Mixing and 2Si Output + HDR
The 2Si format offers an alternative way of sending the UHD signal, in comparison to the standard
four quadric HD signals (being left-top, right-top, left-bottom and right-bottom parts of UHD).

In the 2Si mapping, each of the four HD signals contains every fourth pixel of the source canvas.
When a Maestro | Engine 4K output is configured in the 2Si format, mixing also has to be delivered
using Si.

Start.sh Configuration

First, open the /data/RE/bin/start.sh script file to add supplementary variables required for
this configuration to work.

Edit the start.sh file:

t Add the following variables at the beginning of the start.sh script:

setenv DVG_DUAL_MAIN Required for the dual GPU+DVG configuration.

setenv HDVG_VIDIN_PBO_ALIASING Required to enable 16 insertions for both cards.
setenv DVG_CONN_DVI 0 Required to set the proper connector (DisplayPort).

setenv DVG_UNIFIED_OUTPUT_CLOCKING Required to set unified clocking on outputs.

t Uncomment the LD_PRELOAD setting in multi GL mode to avoid losing performance:

setenv LD_PRELOAD /data/RE/lib_extern/libglsquared64.so

RE.xml Configuration
Then, open the RE.xml file to set the required layout and enable CPU cores logging. In our example,
a custom layout 2SiWithAlpha is set and layout auto detection is disabled.

Edit the RE.xml file:

t Open the /data/RE/bin/RE.xml file and set the desired layout.
<Layout
ConfigPathName="Layout.xml"
DetectName="No"
Name="2SiWithAlpha"
Log="Yes"
AutoReactivateScenes="No"
/>

n If your Layout.xml file does not contain the 2SiWithAlpha configuration, copy it from “Layout.xml
Custom Configurations” on page 67 and paste it to the Layouts node.

61
 t Enable multi-rendering, as shown below.
<Renderer
ContextPlugin="EbREOpenGL">
<Thread
On="Yes">
<Multi On="Yes" Count="2" Scissor="Yes" SkipUnrelatedCanvas="Yes"/>
<DetectLongCommands On="No" Ms="1"/>
</Thread>

t Enable Linear Workflow (HDR).

<LinearWorkflow
On="Yes"
RenderingSpace="Rec.2020"
Format="16F">
<FormatDetails>
<HdrPq ReferenceWhiteNits="100" PeakWhiteNits="4000" />
<HdrHlg ReferenceWhiteNits="100" PeakWhiteNits="1000" />
</FormatDetails>
</LinearWorkflow>

Configuring Maestro | Engine Manager

The Maestro | Engine Manager is a web-based configuration tool that allows to setup your Maestro |
Engine 4K machine. Install the Maestro | Engine Manager as described in the Installing Maestro |
Engine Manager topic.

62
Global

In UHD scenarios, a 1080p (@50 or @59 HZ) format needs to be selected. The Frame Rendering
option is automatically set to Auto (On). Select an HDR color model (10-bit) and color space for
your Inputs and Outputs. Set the Genlock type to DIGITAL to synchronize Maestro | Engine 4K to
the incoming signal of mixing.

Board 1

Activate mixing on Outputs 1 and 3, set Compositing as the Output type and connect mixing sources
to Inputs 7 and 8 on both DVG boards. Outputs 5-8 can be left with default options because they are
not used in this scenario.

63
 Board 1 - Advanced

Make sure that the Pipeline and GFX Optimized options are enabled.

Board 2

Set as many insertions as required for your configuration. Our scenario uses 4 insertions on each
board.

n If mixing sources from the second board are not displayed on Output, add the following line at the
end of the start.sh file:

sleep 30;

/usr/dvg/rctlsend localhost chaninroute 1 1

64
 Audio Presets, Controller Presets, Frame Accuracy, Clips

Connecting Sources

Connect mixing sources to inputs 7 and 8 on both DVG boards. Outputs are available on SDI
connectors 1, 3, 9 and 11.

n If 2Si sources are not connected to mixing inputs in a correct order, it will lead to bad mixing quality
on the output.

Example

Output1 on the source goes to input 8 on the first DVG board - red;

Output2 on the source goes to input 7 on the first DVG board - green;

Output3 on the source goes to input 8 on the second DVG board- yellow;

Output4 on the source goes to input 7 on the second DVG board- blue.

After enabling the 2Si format on the output monitor, mixing should be displayed as shown below.

65
Starting RenderEngine
After applying the configuration, you can start the RenderEngine.

To start RenderEngine:
t Use the following commands:
cd /data/RE/bin
./start.sh
- or -
t Login to Maestro | Engine Manager of your machine, and start RenderEngine using the bottom
panel buttons.

When RenderEngine is started, verify the cores settings in RE.log.

66
A Layout.xml Custom Configurations

HD1080_10Canvases
<HD1080_10CANVASES>
<Canvases>
<Canvas Id="Canvas1">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas2">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas3">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas4">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas5">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas6">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas7">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas8">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas9">
<Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas10">
 <Size X="1920" Y="1080"/>
</Canvas>
<Canvas Id="Canvas1Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas2Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas3Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas4Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas5Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas6Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas7Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas8Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas9Pvw">
<Size X="240" Y="135"/>
</Canvas>
<Canvas Id="Canvas10Pvw">
<Size X="240" Y="135"/>
</Canvas>
</Canvases>

<Routings>
<Routing Id="1->1" CanvasId="Canvas1" CopyMode="RGB"
OutputId="Output1" MipMaps="No"/>

68
 <Routing Id="2->2" CanvasId="Canvas2" CopyMode="RGB"
OutputId="Output2" MipMaps="No"/>
<Routing Id="3->3" CanvasId="Canvas3" CopyMode="RGB"
OutputId="Output3" MipMaps="No"/>
<Routing Id="4->4" CanvasId="Canvas4" CopyMode="RGB"
OutputId="Output4" MipMaps="No"/>
<Routing Id="5->5" CanvasId="Canvas5" CopyMode="RGB"
OutputId="Output5" MipMaps="No"/>
<Routing Id="6->6" CanvasId="Canvas6" CopyMode="RGB"
OutputId="Output9" MipMaps="No"/>
<Routing Id="7->7" CanvasId="Canvas7" CopyMode="RGB"
OutputId="Output10" MipMaps="No"/>
<Routing Id="8->8" CanvasId="Canvas8" CopyMode="RGB"
OutputId="Output11" MipMaps="No"/>
<Routing Id="9->9" CanvasId="Canvas9" CopyMode="RGB"
OutputId="Output12" MipMaps="No"/>
<Routing Id="10->10" CanvasId="Canvas10" CopyMode="RGB"
OutputId="Output13" MipMaps="No"/>
<Routing Id="1->1Pgm" CanvasId="Canvas1" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="0" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="2->2Pgm" CanvasId="Canvas2" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="240" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="3->3Pgm" CanvasId="Canvas3" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="480" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="4->4Pgm" CanvasId="Canvas4" CopyMode="RGB"
OutputId="Output8" MipMaps="No">

69
 <OutputRectangle>
<Pos X="720" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="5->5Pgm" CanvasId="Canvas5" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="960" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="6->6Pgm" CanvasId="Canvas6" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="1200" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="7->7Pgm" CanvasId="Canvas7" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="1440" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="8->8Pgm" CanvasId="Canvas8" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="1680" Y="60"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="9->9Pgm" CanvasId="Canvas9" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="0" Y="260"/>
<Size X="240" Y="135"/>

70
 </OutputRectangle>
</Routing>
<Routing Id="10->10Pgm" CanvasId="Canvas10" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="240" Y="260"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="1->1Pvw" CanvasId="Canvas1Pvw" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="0" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="2->2Pvw" CanvasId="Canvas2Pvw" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="240" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="3->3Pvw" CanvasId="Canvas3Pvw" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="480" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="4->4Pvw" CanvasId="Canvas4Pvw" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="720" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>

71
 <Routing Id="5->5Pvw" CanvasId="Canvas5Pvw" CopyMode="RGB"
OutputId="Output8" MipMaps="No">
<OutputRectangle>
<Pos X="960" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="6->6Pvw" CanvasId="Canvas6Pvw" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="1200" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="7->7Pvw" CanvasId="Canvas7Pvw" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="1440" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="8->8Pvw" CanvasId="Canvas8Pvw" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="1680" Y="600"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="9->9Pvw" CanvasId="Canvas9Pvw" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>
<Pos X="0" Y="800"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
<Routing Id="10->10Pvw" CanvasId="Canvas10Pvw" CopyMode="RGB"
OutputId="Output16" MipMaps="No">
<OutputRectangle>

72
 <Pos X="240" Y="800"/>
<Size X="240" Y="135"/>
</OutputRectangle>
</Routing>
</Routings>
<Outputs>
<Output Id="Output1">
<WindowRectangle>
<Pos X="0" Y="0"/>
<Size X="1920" Y="1080"/>
</WindowRectangle>
</Output>
<Output Id="Output2">
<WindowRectangle>
<Pos X="1920" Y="0"/>
<Size X="1920" Y="1080"/>
</WindowRectangle>
</Output>
</Outputs>
<Stereo>
<Pair
LeftEyeCanvas=""
RightEyeCanvas=""
/>
</Stereo>
</HD1080_10CANVASES>

73
UHDWithAlpha
<Layout Name="UHDWithAlpha">
<Canvases>
<Canvas Id="Canvas1">
<Size X="3840" Y="2160"/>
<Interlace Mode="Auto" Shift="1.000"/>
</Canvas>
</Canvases>
<Routings>
<Routing Id="1->1" CanvasId="Canvas1" CopyMode="Color" MipMaps="No"
OutputId="Output1">
<CanvasRectangle>
<Pos X="0" Y="0"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
<Routing Id="1->1Alpha" CanvasId="Canvas1" CopyMode="Alpha" MipMaps="No"
OutputId="Output1Alpha">
<CanvasRectangle>
<Pos X="0" Y="0"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
<Routing Id="1->2" CanvasId="Canvas1" CopyMode="Color" MipMaps="No"
OutputId="Output2">
<CanvasRectangle>
<Pos X="0" Y="1080"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
<Routing Id="1->2Alpha" CanvasId="Canvas1" CopyMode="Alpha" MipMaps="No"
OutputId="Output2Alpha">
<CanvasRectangle>
<Pos X="0" Y="1080"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
<Routing Id="1->3" CanvasId="Canvas1" CopyMode="Color" MipMaps="No"
OutputId="Output3">
<CanvasRectangle>
<Pos X="1920" Y="0"/>
<Size X="1920" Y="1080"/>

74
 </CanvasRectangle>
</Routing>
<Routing Id="1->3Alpha" CanvasId="Canvas1" CopyMode="Alpha" MipMaps="No"
OutputId="Output3Alpha">
<CanvasRectangle>
<Pos X="1920" Y="0"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
<Routing Id="1->4" CanvasId="Canvas1" CopyMode="Color" MipMaps="No"
OutputId="Output4">
<CanvasRectangle>
<Pos X="1920" Y="1080"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
<Routing Id="1->4Alpha" CanvasId="Canvas1" CopyMode="Alpha" MipMaps="No"
OutputId="Output4Alpha">
<CanvasRectangle>
<Pos X="1920" Y="1080"/>
<Size X="1920" Y="1080"/>
</CanvasRectangle>
</Routing>
</Routings>
<Stereo>
<Pair LeftEyeCanvas="" RightEyeCanvas=""/>
</Stereo>
</Layout>

75
2SiWithAlpha
<Layout Name="2SiWithAlpha">
<Canvases>
<Canvas Id="Canvas1">
<Size X="3840" Y="2160"/>
<Interlace Mode="Auto" Shift="1.000"/>
</Canvas>
</Canvases>
<Routings>
<Routing Id="1->1" CanvasId="Canvas1" Mapping="2Si-1"
CopyMode="Color" MipMaps="No" OutputId="Output1"/>
<Routing Id="1->1Alpha" CanvasId="Canvas1" Mapping="2Si-1"
CopyMode="Alpha" MipMaps="No" OutputId="Output1Alpha"/>
<Routing Id="1->2" CanvasId="Canvas1" Mapping="2Si-2"
CopyMode="Color" MipMaps="No" OutputId="Output2"/>
<Routing Id="1->2Alpha" CanvasId="Canvas1" Mapping="2Si-2"
CopyMode="Alpha" MipMaps="No" OutputId="Output2Alpha"/>
<Routing Id="1->3" CanvasId="Canvas1" Mapping="2Si-3"
CopyMode="Color" MipMaps="No" OutputId="Output3"/>
<Routing Id="1->3Alpha" CanvasId="Canvas1" Mapping="2Si-3"
CopyMode="Alpha" MipMaps="No" OutputId="Output3Alpha"/>
<Routing Id="1->4" CanvasId="Canvas1" Mapping="2Si-4"
CopyMode="Color" MipMaps="No" OutputId="Output4"/>
<Routing Id="1->4Alpha" CanvasId="Canvas1" Mapping="2Si-4"
CopyMode="Alpha" MipMaps="No" OutputId="Output4Alpha"/>
</Routings>
<Outputs>
<Output Id="Output1">
<WindowRectangle>
<Pos X="0" Y="0"/>
<Size X="1920" Y="1080"/>
</WindowRectangle>
</Output>
<Output Id="Output2">
<WindowRectangle>
<Pos X="1920" Y="0"/>
<Size X="1920" Y="1080"/>
</WindowRectangle>
</Output>

76
 <Output Id="Output3">
<WindowRectangle>
<Pos X="0" Y="1080"/>
<Size X="1920" Y="1080"/>
</WindowRectangle>
</Output>
<Output Id="Output4">
<WindowRectangle>
<Pos X="1920" Y="1080"/>
<Size X="1920" Y="1080"/>
</WindowRectangle>
</Output>
</Outputs>
<Stereo>
<Pair LeftEyeCanvas="" RightEyeCanvas=""/>
</Stereo>
</Layout>

77
B Telestration using Render Engine

You can use the iPad Telestrator app to draw on Render Engine output.

The following topics are discussed in this chapter:

• Render Engine Preparation
• Maestro | Designer Configuration
• ReTalk3 Commands

Render Engine Preparation

To start interaction with the iPad app, you need to modify RE\bin\RE.xml file first.

To prepare the Render Engine:

1. Open the RE\bin\RE.xml file.
2. Enable the following options in the Interaction section:

<Interaction
On="Yes"
DefaultCoordSystem="Screen"
DefaultHandler="Multitouch"
MouseCursorVisible="Yes"
...
<Handler Name="Telestrator" Accessible="Yes" />
...
<Handler Name="Multitouch" Accessible="Yes" />
...
<Devices>
...
<Device Name="TUIO" Params="-port 3333" On="Yes" Active="Yes"/>
...
</Devices>
</Interaction>
 3. In the Fileframe section, make sure the following options are set:
<FileFrame
On="Yes"
Pathname="I:\snapshot.jpg"
Step="50">
<SrcRectangle>
<Pos X="0" Y="0"/>
<Size X="1920" Y="1080"/>
</SrcRectangle>
<DstSize Width="1024" Height="768"/>
</FileFrame>
4. In the Telestrator section, check the following options:
<Telestrator
Log="Yes"
Activated="Yes"
Visible="Yes"
UndoLevels="5"
/>

Then, open the RE\bin\Interaction.xml file and modify it according to your requirements.

Configuring Arrow Parameters

To modify the parameters of arrows, modify the RE/bin/Telestrator.xml file. The content
of the file represents parameters for all 6 styles.

79
Each section starts with StyleX content set of parameters to control the shape of arrows.

<Plane X="0.0" Y="0.0" Z="1.0"/>

<SegmentDivision Value="4"/>

<WidthDivision Value="16"/>

<BackBias Value="0.5"/>

<BackDivision Value="4"/>

<Scale Value="0.1"/>

<Type Value="Extrusion"/>

<Head

Length="14.0"

Width="8.0"

Bias="0.7"

BackOffset="4.0"

/>

<Tail

Length="8.0"

Width="4.0"

Bias="0.3"

BackOffset="2.0"

/>

<Body

StartWidth="3.0"

EndWidth="1.5"

Bias="0.5"

DistributionDistance="2.0"

/>

<Shadow Active="Yes">

<Color R="0.4" G="0.4" B="0.4" A="1.0"/>

<Plane X="0.0" Y="0.0" Z="1.0"/>

<Offset X="0.01" Y="0.01" Z="-0.01"/>

</Shadow>

80
Maestro | Designer Configuration
Use Template\Telestrator to create a new scene or add a Telestrator_Layer asset from Misc to
extend an existing scene.

In the Telestrator layer, you can change the color of the arrows by modifying the Materials (color,
textures) corresponding styles.

In the Telestrator.xml file, you can modify all other parameters, such as shadows color, start/
end shape, body parameters and others.

ReTalk3 Commands
Using PuTTy, send commands directly to the Render Engine.

To load a scene and start the interaction send the following commands:
[1] Scene.Load(PathName="G:\Projects\SceneDir\SceneName");

[2] Viewport.ActivateScene(Canvas="Canvas1", Channel=3,

Scene="G:\Projects\SceneDir\SceneName");

[3] Viewport.Telestrator.SetScene(Canvas="Canvas1", Viewport="Full",

Value="G:\Projects\SceneDir\SceneName");

[4] Viewport.Telestrator.SetIsActivated(Canvas="Canvas1", Value="Yes");

[5] Viewport.Telestrator.SetIsVisible(Canvas="Canvas1", Value="Yes");

[6] Interaction.SetCurrentManipulator(Value="Telestrator");

81
C Safety and Regulatory Information

This document contains safety and regulatory information for Avid Maestro | Engine 4K hardware.

Important Safety Instructions

1. Read these instructions.
2. Keep these instructions.
3. Heed all warnings.
4. Follow all instructions.
5. Do not use this equipment near water.
6. Clean only with dry cloth.
7. Do not block any ventilation openings. Install in accordance with the manufacturer's
instructions.
8. Do not install near any heat sources such as radiators, heat registers, stoves, or other equipment
(including amplifiers) that produce heat.
9. Protect power cords from being walked on or pinched particularly at plugs, convenience
receptacles, and the point where they exit from the equipment.
10. Only use attachments/accessories specified by the manufacturer.
11. For products that are not rack-mountable: Use only with a cart, stand, tripod, bracket, or table
specified by the manufacturer, or sold with the equipment. When a cart is used, use caution when
moving the cart/equipment combination to avoid injury from tip-over.
12. Unplug this equipment during lightning storms or when unused for long periods of time.
13. Refer all servicing to qualified service personnel. Servicing is required when the equipment has
been damaged in any way, such as power-supply cord or plug is damaged, liquid has been spilled
or objects have fallen into the equipment, the equipment has been exposed to rain or moisture,
does not operate normally, or has been dropped.
14. For products that are a Mains powered device: The equipment shall not be exposed to dripping
or splashing and no objects filled with liquids (such as vases) shall be placed on the equipment.

c To reduce the risk of fire or electric shock, do not expose this equipment to rain or moisture.Do
not defeat the safety purpose of the polarized or grounding-type plug. A polarized plug has two
blades with one wider than the other.A grounding type plug has two blades and a third
grounding prong. The wide blade or the third prong are provided for your safety. If the
provided plug does not fit into your outlet, consult an electrician for replacement of the
obsolete outlet.

15. For products containing a lithium battery:

c Danger of explosion if battery is incorrectly replaced. Replace only with the same or equivalent
type.

16. For products with a power switch: It should remain accessible after installation.
 17. The equipment shall be used at a maximum ambient temperature of 40° C.
18. This unit may be provided with a power supply cord set suitable for 120V AC input only (for
U.S.A.and Canada). For other than U.S.A. and Canada, a qualified person must provide for use
with this unit, an appropriate, approved power supply cord set which is in compliance with the
end use country requirements and has a minimum cross-sectional area of 1.0mm2.
19. For products with more than one power cord:

c This unit has more than one power supply cord. Disconnect two power supply cords before
servicing to avoid electrical shock.

c Cet appareil comporte plus d'un cordon d'alimentation. Afin de prévenir les chocs électriques,
débrancher les deux cordons d'alimentation avant de faire le dépannage.

20. For products with an operator-accessible fuse:

c For continued protection against risk of fire, replace only with same type and rating of fuse.

c Pour ne pas compromettre la protection contre les risques d'incendie, remplacer par un fusible
de m?me type et de m?me caractéristiques nominales.

Rack-Mount Requirements
1. Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly, the operating
ambient temperature of the rack environment might be greater than room ambient. Therefore,
consider installing the equipment in an environment compatible with the maximum ambient
temperature (Tma) specified by the manufacturer.
2. Reduced Air Flow - Installation of the equipment in a rack should be such that the amount of air
flow required for safe operation of the equipment is not compromised.
3. Mechanical Loading - Mounting of the equipment in the rack should be such that a hazardous
condition is not achieved due to uneven mechanical loading.
4. Circuit Overloading - Consideration should be given to the connection of the equipment to the
supply circuit and the effect that overloading of the circuits might have on overcurrent protection
and supply wiring. Appropriate consideration of equipment nameplate ratings should be used
when addressing this concern.
5. Reliable Earthing - Reliable Earthing of rack-mounted equipment should be maintained.
Particular attention should be given to supply connections other than direct connections to the
branch circuit (for example, use of power strips).

EMC (Electromagnetic Compliance) and Safety

Avid declares that this product complies with the following standards regulating emissions,
immunity and product safety:
• FCC Part 15 Class A
• ICES-003 Class A
• EN55032 Class A

83
 • EN55103-1 E4
• EN55024
• EN55103-2 E4
• AS/NZS CISPR 32 Class A
• CISPR32 Class A
• VCCI Class A
• IEC/EN/UL60950-1
• CAN/CSA-C22.2 No. 60950-1-07

This equipment has been tested to comply with USA and Canadian safety certification in accordance
with the specifications of UL Standards: IEC/UL60950-1 and Canadian CAN/CSA-C22.2 No.
60950-1-07. Avid Inc. has been authorized to apply the appropriate UL & CUL mark on its
compliant equipment.

(EMC, Safety and RoHS)

Avid is authorized to apply the CE (Conformité Europénne) mark on this compliant equipment
thereby declaring conformity to EMC Directive 2014/30/EU, Low Voltage Directive 2014/35/EU
and RoHS Recast Directive 2011/65/EU.

FCC Notice
Class A Equipment

This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference, in which case
the user will be required to correct the interference at personal expense.

Cables
Connections to Avid hardware must be made with shielded cables with metallic RFI/EMI connector
hoods in order to maintain compliance with FCC Rules and Regulations.

Canadian ICES-003
Class A Equipment
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing
Equipment Regulations.

84
 Cet appareil numérique de la classe A respecte toutes les exigences du R?glement sur le matériel
brouilleur du Canada.

Australian Compliance

Environmental Compliance
Disposal of Waste Equipment by Users in the European Union
This symbol on the product or its packaging indicates that this product must not be disposed of with
other waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over
to a designated collection point for the recycling of waste electrical and electronic equipment. The
separate collection and recycling of your waste equipment at the time of disposal will help conserve
natural resources and ensure that it is recycled in a manner that protects human health and the
environment. For more information about where you can drop off your waste equipment for
recycling, please contact your local city recycling office or the dealer from whom you purchased the
product.

Proposition 65 Warning
This product contains chemicals, including lead, known to the State of California to cause cancer and
birth defects or other reproductive harm. Wash hands after handling.

Perchlorate Notice
This product may contain a lithium coin battery. The State of California requires the following
disclosure statement: "Perchlorate Material - special handling may apply, See www.dtsc.ca.gov/
hazardous waste/perchlorate "

Recycling Notice

85