iNEWSCommandv27 ICG

Avid iNEWS Command
Installation and Configuration Guide
Legal Notices
Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement. Avid products or portions thereof are protected by one or more of the following United States Patents: 4,970,663; 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364; 5,654,737; 5,715,018; 5,719,570; 5,724,605; 5,726,717; 5,729,673; 5,745,637; 5,752,029; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,999,406; 6,038,573; 6,061,758; 6,141,007; 6,211,869; 6,532,043; 6,546,190; 6,596,031; 6,636,869; 6,747,705; 6,763,523; 6,766,357; 6,813,622; 6,847,373; 7,081,900; RE40,107; 7,403,561; 7,433,519; D352,278; D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912. Other patents are pending. This document is protected under copyright law. An authorized licensee of Avid iNEWS Command may reproduce this publication for the licensees 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 Avid iNEWS Command. 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 2010 Avid Technology, Inc. and its licensors. All rights reserved.
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 19881997 Sam Leffler Copyright 19911997 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. 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.:

2006 Nexidia. All rights reserved. Manufactured under license from the Georgia Tech Research Corporation, U.S.A. Patent Pending.
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 resellers failure to perform resellers obligation; or any damages arising from use or operation of resellers 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 resellers 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:
19931998 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.
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, 192XD I/O, 888 I/O, Adrenaline, AirPlay, AirSPACE, AirSPACE HD, AirSpeed, ALEX, Alienbrain, AniMatte, AudioMarket, AudioPages, AudioSuite, AudioVision, AutoSync, Avid, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, AVIDdrive, Avid DS Assist Station, Avid EditStar, Avid Learning Excellerator, Avid Liquid, Avid Liquid Chrome Xe, Avid MEDIArray, Avid Mojo, AvidNet, AvidNetwork, Avid NewStar, Avid Remote Response, AVIDstripe, Avid Unity, Avid Unity ISIS, Avid VideoRAID, Avid Xpress, AVoption, AVX, Beauty Without The Bandwidth, Blacktooth, Boom, C|24, CamCutter, CaptureManager, ChromaCurve, ChromaWheel, Command|24, Conectiv, CountDown, DAE, Dazzle, Dazzle Digital Video Creator, Deko, DekoCast, D-Fi, D-fx, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Intelligent Noise Reduction, DigiDrive, DigiLink, DigiMeter, DigiSerial, Digital Nonlinear Accelerator, DigiTranslator, DINR, DNxchange, do more, DVD Complete, D-Verb, Eleven, Equinox, EveryPhase, ExpertRender, Fastbreak, Fast Track, FieldPak, Film Composer, FilmScribe, Flexevent, FluidMotion, FXDeko, G7, G-Rack, HD Core, HD Process, HDPack, Hollywood DV-Bridge, Hybrid, HyperControl, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, iNEWS, iNEWS Assign, iNEWS ControlAir, Instantwrite, Instinct, Intelli-sat Broadcasting Recording Manager, Intelli-Sat, InterFX, Interplay, inTONE, Intraframe, iS9, iS18, iS23, iS36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, Lightning, ListSync, Lo-Fi, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, M-Audio, M-Audio Micro, Maxim, Mbox, MCXpress, Media Browse, Media Composer, MediaDock, MediaDock Shuttle, Media Fusion, Media Illusion, MediaLog, Media Reader, Media Recorder, MEDIArray, MediaShare, MediaStream, Media Suite, Meridien, MetaFuze, MetaSync, MicroTrack, Midiman, MissionControl, Mix Rack, MixLab, Moviebox, Moviestar, NaturalMatch, Nearchive, NetReview, NewsCutter, Nitris, NRV-10 interFX, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Palladium, Pinnacle, Pinnacle DistanTV, Pinnacle Geniebox, Pinnacle HomeMusic, Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle PCTV, Pinnacle PCTV HD Ultimate Stick, Pinnacle PCTV Nano Stick, Pinnacle PCTV To Go, Pinnacle Scorefitter, Pinnacle Studio, Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle VideoSpin, ProEncode, ProServices, ProSessions, Pro Tools, QuietDrive, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, RetroLoop, rS9, rS18, Salesview, Sci-Fi, Scorch, Scorefitter, ScriptSync, SecureProductionEnvironment, Session, Show Center, Sibelius, SIDON, Soft SampleCell, Soft-Clip Limiter, Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, Starplay, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, Strike, Structure, Studiophile, SubCap, Sundance Digital, Sundance, Symphony, SYNC HD, SynchroScience,
SynchroScope, Syntax, Targa, TDM FlexCable, Thunder, Titan, Titansync, TL Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, Torq, Torq Xponent, Transfuser, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Venom, VideoRAID, Video Slave Driver, VideoSPACE, VideoSpin, Vortx, Xdeck, X-Form, Xmon, Xponent, X-Session, and X-Session Pro are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.
Footage
Arri Courtesy of Arri/Fauer John Fauer, Inc. Bell South Anticipation Courtesy of Two Headed Monster Tucker/Wayne Atlanta/GMS. Canyonlands Courtesy of the National Park Service/Department of the Interior. Eco Challenge British Columbia Courtesy of Eco Challenge Lifestyles, Inc., All Rights Reserved. Eco Challenge Morocco Courtesy of Discovery Communications, Inc. Its Shuttletime Courtesy of BCP & Canadian Airlines. Nestl Coffee Crisp Courtesy of MacLaren McCann Canada. Saturn Calvin Egg Courtesy of Cossette Communications. Tigers: Tracking a Legend Courtesy of www.wildlifeworlds.com, Carol Amore, Executive Producer. "The Big Swell" Courtesy of Swell Pictures, Inc. Windhorse Courtesy of Paul Wagner Productions. Arizona Images KNTV Production Courtesy of Granite Broadcasting, Inc., Editor/Producer Bryan Foote. Canyonlands Courtesy of the National Park Service/Department of the Interior. Ice Island Courtesy of Kurtis Productions, Ltd. Tornados + Belle Isle footage Courtesy of KWTV News 9. WCAU Fire Story Courtesy of NBC-10, Philadelphia, PA. Women in Sports Paragliding Courtesy of Legendary Entertainment, Inc. News material provided by WFTV Television Inc.
GOT FOOTAGE?
Editors Filmmakers Special Effects Artists Game Developers Animators Educators Broadcasters Content creators of every genre Just finished an incredible project and want to share it with the world? Send us your reels and we may use your footage in our show reel or demo!* For a copy of our release and Avids mailing address, go to www.avid.com/footage. *Note: Avid cannot guarantee the use of materials submitted.
Avid iNEWS Command v2.7 Installation and Configuration Guide 0130-30466-01 Created 9/9/10 This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.
Contents
Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 How to Order Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 1
Installing and Configuring the Command Server . . . . . . . . . . . . . . . . . . 17

System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Checklist: Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Checklist: Command Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Copying Install CD to Local Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Installing the License Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Configuring the License Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Adding the Temporary Command License . . . . . . . . . . . . . . . . . . . . . . . . . 35 Generate an Activation File for a Full Command License . . . . . . . . . . . . . . 36 Add the Permanent Command License. . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Installing Avid iNEWS Command on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Configuring the iNEWS Command Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Configuring the System Administration Password . . . . . . . . . . . . . . . . . . . . . . . 47 Configuring the Time Synchronization Service . . . . . . . . . . . . . . . . . . . . . . . . . 48 Configuring AirSpeed Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Configuring Avid Video Device Services (VDS) . . . . . . . . . . . . . . . . . . . . . . . . . 50 Configuring VDS for Omneon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Configuring VDS for Harris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Wiring Serial Connections for Avid Video Device Services (for VDCP) . . . 55 Configuring VDS for VDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Configuring VDCP for Redundant Mirrored Playback . . . . . . . . . . . . . . . . . 58 Transfer Status Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Configuring Avid Interplay Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7
Configuring the Avid UMD Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Configuring UMD for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Configuring the Lookup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Configuring a Second Command System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Chapter 2
Installing and Configuring the AirSpeed Multi Stream . . . . . . . . . . . . . . 71

Checklist: Installing the AirSpeed Multi Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Installing AirSpeed Multi Stream Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Checklist: Configuring the AirSpeed Multi Stream . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Configuring Properties for Interplay Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Configuring the AirSpeed Multi Stream Device Service . . . . . . . . . . . . . . . . . . . . . . 80 Configuring Properties for Command Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Working with Play While Record on AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter 3
Installing and Configuring the Deko. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Command with Avid Deko Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Checklist: Installing the Deko . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Installing Avid Deko Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Installing the DekoMOS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Connecting the Net HASP Dongle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Installing the DekoMOS Gateway and Net HASP Software . . . . . . . . . . . . . . 101 Confirming the NetHASP License Manager Configuration . . . . . . . . . . . . . . . 102 Installing the DekoMOS Macro Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Checklist: Configuring the Deko . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Configuring the DekoMOS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Deko and Deko Select Subfolders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Configuring the DekoMOS Macro Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Configuring Styles on the DekoMOS Macro Server . . . . . . . . . . . . . . . . . . . . 113 Configuring Avid Workgroup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Configuring the Deko Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Configuring the Avid Deko Renderer Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Creating Graphic Styles in Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 4
Installing and Configuring the Thunder. . . . . . . . . . . . . . . . . . . . . . . . . 123

Checklist: Installing and Configuring the Thunder. . . . . . . . . . . . . . . . . . . . . . . . . . 124 Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Installing Avid Thunder Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Configuring Avid Workgroup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Configuring the Thunder Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Configuring the Thunder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Creating the ThunderMOS.cfg File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Creating the ThunderMOS.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Chapter 5
Installing the Command Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Checklist: Installing the Command Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Installing Avid iNEWS Command on the Workstation. . . . . . . . . . . . . . . . . . . . . . . 149 Configuring Avid Workgroup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Setting up Device Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Setting up Channel Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Chapter 6
Installing GDS and GIE for Chyron. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Checklist: Installing the GDS and GIE for Chyron. . . . . . . . . . . . . . . . . . . . . . . . . . 170 Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Installing Avid Graphic Device Service on the Chyron . . . . . . . . . . . . . . . . . . . . . . 175 Installing the Avid Graphic Inventory Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Configuring the Avid Graphic Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Configuring the Graphic Inventory Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Importing Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Working with Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Working with Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Configuring Command for Chyron Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Configuring the LUCI Plug-in for Chyron ActiveX Support . . . . . . . . . . . . . . . . 195
Chapter 7
Integrating with Avid iNEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Editing the SYSTEM.MAP Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Editing the SYSTEM.MOS-MAP Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Setting up the Plug-ins in iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Installing and Configuring Avid Thunder Select . . . . . . . . . . . . . . . . . . . . . . . . 202
9
Installing and Configuring Avid Deko Select . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Configuring Gateway Settings from an ini File . . . . . . . . . . . . . . . . . . . . . 206 Monitor Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Creating a Monitor Server for Each Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Using the list Command to View Assigned Mailboxes. . . . . . . . . . . . . . . . . . . 211 Queue Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Chapter 8
Configuring Playout Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Controling Playout via the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Disabling a Command Workstations Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Checklist: Setting up an X-keys USB Keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Installing an X-keys USB Keypad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Mapping Indices to Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Programming the X-keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Checklist: Setting up the GPI Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Configuring the GPI Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Restarting the GPI Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Confirming Successful Setup of a GPI Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 Mapping Events to Actions for a GPI Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Enabling the GPI Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Configuring GPI Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Configuring for Newswheel Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Checklist: Setting up the Maney Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Configuring the PCI Card for a Maney Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Restarting the Maney Panel Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Confirming Successful Setup of a Maney Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Mapping Events to Actions for a Maney Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 9
Integrating with ENPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Configuring ENPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Configuring MOS Settings in Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Configuring Command for Deko Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Configuring Command for MOS Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Chapter 10
Confirming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Monitoring System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
10
Viewing Status of Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Confirming Command Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Testing Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
11
12
Using This Guide

Congratulations on your purchase of your Avid iNEWS Command system. Avid iNEWS Command offers a considerable amount of functionality for the state-of-the-art newsroom, including newsroom system integration and playout control. With Command, newsroom personnel can easily create and manage playlists. This publication provides information on how to install and configure the Command system.
The documentation describes the standard features of a basic system configuration. Therefore, your system might contain certain features and hardware that are not covered in the documentation.
Symbols and Conventions

Avid documentation uses the following symbols and conventions:
Symbol or Convention Meaning or Action
n c w
>
A note provides important related information, reminders, recommendations, and strong suggestions. 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. Follow the guidelines in this document or on the unit itself when handling electrical equipment. This symbol indicates menu commands (and subcommands) in the order you select them. For example, File > Import means to open the File menu and then select the Import command. This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.
(Windows), (Windows only), (Macintosh), or (Macintosh only)
This text indicates that the information applies only to the specified operating system, either Windows or Macintosh OS X.
Symbol or Convention Meaning or Action
Bold font Italic font

Courier Bold font
Bold font is primarily used in task instructions to identify user interface items and keyboard sequences. Italic font is used to emphasize certain words and to indicate variables. Courier Bold font identifies text that you type. 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.
Ctrl+key or mouse action
If You Need Help

If you are having trouble using your Avid product: 1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow. 2. Check the latest information that might have become available after the documentation was published: If the latest information for your Avid product is provided as printed release notes, they ship with your application and are also available online. If the latest information for your Avid product is provided as a ReadMe file, it is supplied on your Avid installation CD or DVD as a PDF document (README_product.pdf) and is also available 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, select ReadMe from the Help menu, or visit the Knowledge Base at www.avid.com/readme. 3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues. 4. Visit the online Knowledge Base at www.avid.com/onlinesupport. Online services are available 24 hours per day, 7 days per week. Search this online Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read or join online message-board discussions.
How to Order Documentation

To order additional copies of this documentation from within the United States, call Avid Sales at 800-949-AVID (800-949-2843). If you are placing an order from outside the United States, contact your local Avid representative.
14
Avid Training Services
Avid Training Services

Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment. To learn about Avid's new online learning environment, Avid Learning Excellerator (ALEX), visit http://learn.avid.com. For information on courses/schedules, training centers, certifications, courseware, and books, please visit www.avid.com/training or call Avid Sales at 800-949-AVID (800-949-2843).
15
16
1 Installing and Configuring the Command Server

Avid iNEWS Command is a device automation system that integrates with any iNEWS or MOS-enabled newsroom computer system (NRCS) and provides broadcasters precise control over a range of playout devices, including video servers, still stores, and character generators in a broadcast news environment. Backup services and mirrored playout make this system reliable while the user interface allows you to control multiple production devices. Avid iNEWS Command also works with Avid Service Framework applications and services to ensure you always have the best system performance. This chapter contains the following main sections: System Architecture Checklist: Before you Begin Checklist: Command Server Installation Copying Install CD to Local Directory Installing Avid Service Framework Installing the License Service Installing Avid iNEWS Command on the Server Configuring the iNEWS Command Server Configuring a Second Command System
System Architecture
The basic iNEWS Command system is comprised of servers that run a variety of Command services, workstations that run the client software, and devices, such as Avid AirSpeed video servers, Thunder production servers, and Deko graphics systems. Avid iNEWS Command is scalable and can adapt to work in traditional newsroom-based playlist creation to production-centric workflows where running orders are created inside the iNEWS Command playback application. All of the services can run on a single computer, or they can be spread out across multiple computers with redundant services configured as backups to take control if any or all of the primary services should become unavailable. An example of a basic Command system architecture is shown in the following illustration:
Avid recommends having all primary Command services on one designated primary server with the backup services running on other backup servers. Command determines primary and backup roles based on the length of time the service has been running. The server that has been running longer is the primary. Therefore, to get all primary services on one server, it is necessary to start the primary server first; when all services have started, start the backup servers. This is the only way to ensure all services on the primary server take on the primary role, which allows for more consistent behavior during times when redundancy is needed, and it helps simplify any necessary troubleshooting efforts.
18
Checklist: Before you Begin
Checklist: Before you Begin

Before you start to install software and configure the Command Server(s), ensure the following tasks are completed.
Tasks
Assign a static IP address to each server. If the server has dual network cards, you must disable the unused connection. The Avid Service Framework relies heavily on DNS name resolution to discover and communicate with Avid Service Framework and Command services.
Establish the DNS server and ensure all computers with Command services or applications are entered in the DNS table with reverse lookup enabled. Avoid the use of host files. Make sure that your TCP/IP settings have the correct primary and alternate DNS addresses. Also, ensure the Advanced TCP/IP settings (on the DNS tab) are set to the following: The Append these DNS suffixes option is selected and the domain is listed, preferably first. The Register this connections addresses in DNS check box is selected. (Optional) The Use this connections DNS suffix in DNS registration check box is selected.
If Command will be used to control a third-party video device via VDCP, ensure the serial card is installed and configured in the computer that will run the Avid Video Device service.
Avid iNEWS Command only supports the Digi Accele Port card for VDCP playout control.
Some Avid Interplay products, such as Instinct, Assist, and Access use Service Framework. Avid iNEWS Command also uses Service Framework; however, the two versions might not be compatible. Consult with Avid Customer Support to determine Service Framework compatibility when Avid Interplay products are installed in the same workgroup. It might be necessary to:
Tasks
Use a separate workgroup for the Command system. Install Command on separate machines that run Service Framework compatible with Command.
19
Checklist: Command Server Installation

Determine which computer or computers will serve as iNEWS Command Servers and, if installing on a redundant system, decide which one will run the primary services; you should install on the primary server first, then the backup server(s).
If you want to copy the installation CD to a specified location on your network to alleviate or reduce having to manually insert the CD into actual computers on site, see Copying Install CD to Local Directory on page 22. On the Command Server, complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily link to a topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Install Avid Service Framework. Install the License service. Configure the License service.
Installing Avid Service Framework on page 24 Installing the License Service on page 30 Configuring the License Service on page 35 Adding the Temporary Command License on page 35 Generate an Activation File for a Full Command License on page 36 Add the Permanent Command License on page 38 Installing Avid iNEWS Command on the Server on page 40 Configuring the iNEWS Command Server on page 47
Add temporary license. Generate an activation file for a full license. Add the permanent license.
Install Avid iNEWS Command. For redundancy, repeat this procedure on the second server. Configure the Command Server.
All settings in Command and Service Framework are case sensitive. Ensure that case matches in all configuration settings.
Set the system administrator password. (Optional) Configure the Time

Synchronization service.
Configuring the System Administration Password on page 47 Configuring the Time Synchronization Service on page 48
n
20
Installation and configuration of the Time Synchronization service only applies to sites that do not already have a method for synchronizing PC clocks on the network.
Checklist: Command Server Installation
Tasks
Refer to...
(Optional) Configure the Lookup tab in

Workgroup Properties.
Configuring the Lookup Tab on page 66 Configuring a Second Command System on page 69 Configuring AirSpeed Device Services on page 49 Configuring VDS for Omneon on page 50 Configuring VDS for VDCP on page 57
(Optional) Configure the system name. Configure the AirSpeed device services. Configure the Avid Video device services.
For information on how to configure the Avid Video device service for the Harris NEXIO plug-in, see the third-party documentation provided by the Harris Corporation.
(Optional) Configure the Interplay Agent

services. for Under Monitor Display or In Monitor Display devices.
Configuring Avid Interplay Agent Services on page 60 page 63
(Optional) Configure the UMD device service Configuring the Avid UMD Device Service on
21
Copying Install CD to Local Directory

The autorun feature on the Avid iNEWS Command installation CD enables you to copy all necessary files to a local directory on your network. From that location, you can then access product documentation and run the installer applications on computers across your local area network.
To copy the CD to a local directory:
1. Insert the Command installation CD. The autorun installation program starts and displays the following screen.
2. Click the Copy This CD To A Local Directory button. The Browse For Folder dialog box appears.
22
Copying Install CD to Local Directory
3. Select a local directory. If one does not exist, you can make a new folder. 4. Click OK. A progress bar will appear as the files are copied.
For upgrades, some files might already exist on your computer. If so, a dialog box (like the one shown below) will notify you of this and ask for your overwrite approval of existing files with those on the CD.
5. When the Copy Complete dialog box appears indicating a successful copy, click OK.
23
Installing Avid Service Framework

Avid Service Framework consists of applications and services which provide dynamic discovery and lookup mechanisms, a scalable notification system, a centralized configuration tool, diagnostic logging for workgroup-enabled applications and services, system health monitoring, and so on. Some of the services are known collectively as Support services. The Support services are viewed, monitored, and configured using the Service Framework applications.
Avid strongly recommends the installation of the Avid Service Framework applications, which take up almost no space or overhead on the hard drive and can prove vital in troubleshooting integration issues, etc. Those most vital to iNEWS Command are:
Major Services Description Server Workstation
Avid Lookup Service This service enables communication between all Command and Framework services running in the workgroup. Without it, there is no communication between services. Only two should be installed in a workgroup. System Configuration This service sets the configuration settings for all configurable services. The Avid Service Configuration application is used to enter configuration information that the System Configuration service will carry out and set in the registry. Without it, the workgroup cannot function. Only two should be installed in a workgroup.
Each computer (server and workstation) running Avid iNEWS Command software requires at least the core components of Service Framework and must be able to connect to a computer running the Avid Lookup service.
Avid Service Framework and Avid iNEWS Command must be installed individually on each computer; do not use drive image software as a substitute for installation. Avid does recommend making a image of the hard drive after installation, but not before.
24
To install the Avid Service Framework software:
1. Insert the Command installation CD (or access the install program from the network).
When installing Service Framework on Command Servers, use only the installer provided on the Command installation CD and not any other software DVD that might be supplied with other Avid products, such as AirSpeed Multi Stream. The autorun installation program starts and displays the following screen.
The Command Documentation button will open a window displaying the contents of the Doc folder on the Command installation CD in which product documentation is provided in PDF format. If the autorun does not begin, manually navigate to and run the ServiceFrameworkSetup.exe install program. 2. Click the Avid Service Framework button.
Other dialog boxes could appear depending on whether older versions of Service Framework, the License service, or Command are found on the server, particularly if upgrading existing software. If one appears, read it carefully and reply accordingly with regard to upgrades, etc.
25
A splash graphic will appear briefly as the installer prepares the InstallShield Wizard. Then the Welcome dialog box appears.
3. Click Next. The Workgroup Name dialog box opens.
4. Set the location to which Avid Service Framework will be installed and click Next.
26
5. Type a new or existing workgroup name in the field.
Do not install iNEWS Command in an Avid Interplay workgroup. Because iNEWS Command is mission critical, Avid recommends you make it a separate workgroup from any existing Interplay workgroups. Make a note regarding the workgroup name so that it can be entered during other Avid Service Framework installations. You must use the same workgroup name on all computers and devices that are connected in your Command architecture. The workgroup name is case sensitive.
If you are updating the Service Framework software, the installer remembers the last installed value. If the workgroup name was changed after the install, the installer will not be aware of the change. 6. Click Next.
27
The Options dialog box opens.
7. Select the option: Typical Avid Server Install and click Next. The Custom Setup dialog box opens.
On the Command Server, you must ensure the Lookup Service and System Configuration are selected. For more information about them, see the table on page 24.
28
The following table includes additional applications and services that Avid strongly recommends be installed on the serversince they do not take up any overhead and are useful in troubleshooting situations.
Applications and Services
Description
Server
Workstation
Service Configuration This application is used to configure settings and host names for Framework and Command services in the workgroup. For instance, configuring the Command system to work with a GPI panel requires defining certain parameters through the Avid Service Configuration application. Avid recommends installing this application on the Command Server. Health Monitor This application allows you to see the status of Command and Framework services health statistics throughout the workgroup. Avid recommends installing this application on the Command Server.
Diagnostics
This application is used to view Avid log files (.alf) when troubleshooting. Avid recommends installing this application on the Command Server. This service reports machine information to the Health Monitor, including disk, memory, and network status. You can also monitor specific services on that local machine. Avid recommends installing this service on the Command Server.
Machine Monitor
29
The following table describes some minor services that are generally considered optional or are not recommended at sites under certain circumstances. If concerned about overhead, you should not install these services.
Minor Services Description
Email Alerter
This service sends a notification email if one of the services in the workgroup has a warning or critical status. It is seldom installed on the Command Server. This service provides an interface to send health monitoring information to industry standard SNMP manager applications. It is seldom installed on the Command Server. This service should only be installed if you do not already use something to synchronize your PC clocks on the network. If you use NTP or some other method for time synchronization, do not install this service.
SNMP Gateway
Time Synchronization
c Serious problemsiscan occur if more than one service for time synchronization installed.
Multicast Repeater This service is required only when a workgroup must span subnets or domains. It is seldom installed on the Command Server.
8. Click Next and follow the installation instructions to complete the installation.
You might be required to restart your system to complete the installation. After installation, verify that the services are running on each computer where Service Framework services were installed.
Installing the License Service

The Avid License service manages the site licenses for Command Workstations as well as CG and video devices that interface with the Command system. This service must be installed on the computer running the Command Server software, but is not necessary on any other computer; however, two instances of this service can be installed for redundancy. Some configuration is required after installation.
To install the License service:
1. Insert the Command installation CD (or access the install program from the network). The autorun installation program starts and displays the following screen.
30
The Command Documentation button will open a window displaying the contents of the Doc folder on the Command installation CD in which product documentation is provided in PDF format. If the autorun does not begin, manually navigate to and run the Avid_License_Setup.exe install program. 2. Click the Avid License Service button. If Avid Service Framework is not already installed, a warning dialog box will appear.
If it does, click OK and install Avid Service Framework before restarting this installation. See Installing Avid Service Framework on page 24 for more information.
31
Other dialog boxes could appear depending on whether older versions of Service Framework, the License service, or Command are found on the server, particularly if upgrading existing software. If one appears, read it carefully and reply accordingly with regard to upgrades, etc. If all prerequisite installations are in order, and the installation can proceed, a splash graphic will appear briefly as the installer prepares the InstallShield Wizard. Then the Welcome dialog box appears.
3. Click Next. The Destination Folder dialog box appears.
32
4. Do one of the following: t t Accept the default location for the destination folder by clicking Next. Click the Change button to select a different location, then click Next.
The Ready to Install the Program dialog box appears.
5. Click Install. A new dialog box will appear indicating the progress of the install.
33
6. When the InstallShield Wizard Completed dialog box appears, click Finish.
34
Configuring the License Service

After installing the service, some configuration is required, using the Avid Service Configuration application. This application should already be installed on a PC on the same network, but might not necessarily be installed on the same computer as the Command Server software or the License service. Configuring the Avid License service involves three tasks: Adding the Temporary Command License Generate an Activation File for a Full Command License Add the Permanent Command License
Adding the Temporary Command License To get you started with Avid iNEWS Command, Avid provides you with a Command temporary (TEMP) license to use until your get your full Command license.
To add the temporary license:
1. Save the license file to My Documents on the Command Server. 2. Open the the Avid Service Configuration application. 3. On the Hosts tab, navigate to and select the Avid License Service. 4. Click the Add License File button. 5. In the Add Licenses dialog box, select the license file and click Add Licenses.
Your license file information will appear.
35
6. Click Apply.
The temporary license Avid provides gives full Command functionality for thirty (30) days.
Generate an Activation File for a Full Command License On systems with redundant configurations, the activation file for a full license must be generated on the primary server.
36
To generate an activation file:
1. Open the Service Configuration application.
2. On the Hosts tab, navigate to and select the Avid License Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Allow Unrestricted Security dialog, click Yes. 5. Click the Generate Activation File button.
37
6. Review and edit the required information, as well as contact information, if necessary. You can also add comments.
Do not remove any information that is already supplied in the fields. 7. Click the Generate Activation File button to create the .act file and select where you want to save it on your PC. 8. Zip the file and then e-mail that .zip file to your respective Avid manufacturing site. Ensure the subject line of the e-mail contains your site name and Command Activation File.
Add the Permanent Command License

To activate the full license:
1. When you receive your permanent .lic file from Avid, save it to My Documents on the same Command Server where the activation file was created. 2. Open the the Avid Service Configuration application. 3. On the Hosts tab, navigate to and select the Avid License Service. 4. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 5. On the Allow Unrestricted Security dialog, click Yes.
38
6. Select an existing TEMP license and click Delete Selected Licenses. Repeat until all of the TEMP licenses are gone. 7. Click the Add License File button. The Add Licenses dialog box appears.
8. Select the full Command license file, and click Add Licenses. Your licensing configuration details will appear.
39
9. Click Apply.
To verify that an installed service is running, you must use the Avid Workgroup Properties application.
Installing Avid iNEWS Command on the Server

This section contains the procedure for installing the Command Server software, along with some device services that must run on the server, if used with specific devices, such as Avid AirSpeed video servers or third-party video devices controlled via VDCP.
If you are upgrading, open Avid Workgroup Properties and stop all services first and then close the application when youre done.
40
To install the software on a Command Server:
The Command Documentation button will open a window displaying the contents of the Doc folder on the Command installation CD in which product documentation is provided in PDF format. 2. Click the Avid iNEWS Command button. If Avid Service Framework is not already installed, a warning dialog box will appear.
41
Other dialog boxes could appear depending on whether older versions of Service Framework, the License service, or Command are found on the server, particularly if upgrading the Command Server software. If one appears, read it carefully and reply accordingly with regard to upgrades, etc. If all prerequisite installations are in order, and the Command Server installation can proceed, a splash graphic will appear briefly as the installer prepares the InstallShield Wizard. Then the Welcome dialog box appears. 3. Click Next. The License Agreement appears.
4. Read the License Agreement, accept the terms, and click Next.
You can print the terms if you want to read them later or keep a copy for your records. If you do not accept the terms, the installation program will not continue. The Destination Folder dialog box opens.
42
5. Do one of the following: t t Click Change to designate an install directory, and then click Next. Accept the default location by clicking Next.
6. Select Server Installation and click Next.
43
7. The Custom Setup dialog box appears with the default services selected for a server installation. However, you can modify the selections to customize your installation. To learn more about a service, click any service listed and view a Feature Description provided along the right side of the dialog box.
n
44
If installing Avid iNEWS Command to interface with a MOS-based newsroom computer system, such as ENPS, you must select Avid MOS Communication Service and deselect Avid iNEWS Communication Service.
By default, two Avid AirSpeed device services are installed as part of the Server Installation set. If more are needed, you can add them by clicking the plus [+] next to that service and selecting more. If you are not using Command to control any Avid AirSpeed video servers, then click the plus and deselect them.
Although not selected by default with a server installation, Avid does recommend installing the Avid iNEWS Command Workstation software on the server as well, because it can be useful in some troubleshooting situations. If your site intends to control third-party video device(s) via VDCP, ensure that the Avid Video device service is selected for installation. Add one for each deviceup to five possible per serverby clicking the plus [+] next to that service and selecting more. By default, this device service is not installed.
For redundancy when using VDCP, Avid recommends mirrored playback with the Avid Video device service on the primary Command Server running the primary video server and another Avid Video Device service on the backup Command Server running the mirrored video server. These services will run parallel to each other, not as primary/backup services. This ensures the most seamless transition should the primary server fail. If it does, the backup server continues, allowing for mirrored-only playback. If your site intends to display the timecode for playing video in the control room on a video monitor or on a multipurpose text display device located next to or under the video monitor, the Avid UMD device service must be selected for installation. It is not selected to be installed by default. When timecodes are displayed on a video monitor, the monitor is considered an In Monitor Display device (or IMD). When displayed separately, the device is considered an Under Monitor Display device (or UMD). When the UMD device service is selected for installation, the Avid UMD device service is installed along with Avids TSL plug-in. Both are needed for Command integration with UMD or IMD devices. After installation, additional configuration is also necessary. For more information, see Configuring the Avid UMD Device Service on page 63. If your site intends to control playback via a Maney panel, ensure that the Avid Maney Panel device service is selected for installation. It must be installed on the computer where the Measurement Computing PCI card is physically located. If an alternative GPI device will be used for playback control, select the GPI device service for installation. By default, neither of these two services are installed. If your site intends to view thumbnails of media items, such as graphics from an Avid Deko or video from Avid AirSpeed video servers, ensure that either or both of the following services are installed: For thumbnail integration with an Avid AirSpeed, install the Avid Interplay Agent service. This service will require some configuration after installation on each Command Server. For more information, see Configuring Avid Interplay Agent Services on page 60.
45
For thumbnail integration with an Avid Deko, install the Avid Deko Renderer service. By default, this service is pre-configured to automatically locate the DekoMOS Gateway on the network. You can verify the setting via the Avid Service Configuration application. For more information, see the Avid iNEWS Command Administration Guide.
By default, these two services are not installed.
The Deko Renderer service does not take up a HASP license seat. 8. Click Next.
9. When the Ready to Install the Program dialog box appears, click Install. 10. When the installation is complete, click Finish. To verify that installed services are running, you must use the Avid Service Framework Workgroup Properties application.
46
Configuring the iNEWS Command Server

After installation, some configuration is required on each iNEWS Command Server. This section covers defining the password for system administrators, configuring the system name, and some servicessuch as the Time Synchronization and AirSpeed device services.
Configuring the System Administration Password

Modifying system settings in Avid iNEWS Command requires an administrator password (if set), which is configured through the Service Configuration application of Avid Service Framework.
To change or set up the system administration password:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration.
2. On the Hosts tab, navigate to and select the Avid System Configuration Service. 3. Select the Administrator Password tab. 4. Type in an alphanumeric password and retype it. 5. Click Apply.
Click the Reset button to restore to password to the default blank password.
47
Configuring the Time Synchronization Service

This service should only be installed and configured if you do not already use something to synchronize your PC clocks.
To configure the Time Synchronization service:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration.
2. On the Hosts tab, navigate to and select the Avid Time Synchronization Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. Select the Master Mode check box. 5. Select the Get Time Sync reference from an NTP Server check box and enter the name of that server on your system. 6. Click Apply.
After you configure the Time Synchronization service on the primary Command Server, you will need to install the service on all other Command Servers, workstations and devices, which will be in Slave Mode by default.
48
Configuring AirSpeed Device Services

After any device service is installed for Avid AirSpeed video servers, some additional configuration is required, using the Avid Service Configuration and Avid Workgroup Properties applications of Avid Service Framework. For more information, see the Avid Service Framework Users Guide.
To configure the AirSpeed device services:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the AirSpeed Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Device Settings tab, enter the device name for the respective device. 5. Click Apply. You can then close the Avid Service Configuration application. 6. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 7. Click the Advanced button. 8. After the Avid Services dialog box opens, select the device, then stop and restart it.
For Command upgrades, the AirSpeed device server hostname might revert back to the local server host name and must be reset, using the Avid Service Configuration application.
To configure the AirSpeed Control Configurations:
1. On the AirSpeed, select Setup > Channels.
49
2. Set Control Configurations to Local/Network Record or Play. It is the only configuration supported with Command.
Avid recommends that you do not use VDCP to control AirSpeed video servers.Unrestricted VDCP is not supported for on-air broadcasting.
Configuring Avid Video Device Services (VDS)

The Avid iNEWS Command user interface lets you integrate with some third-party video devices via the network or via Video Disk Control Protocol (VDCP). For this integration to work, however, some configuration of the device service is required, which varies depending on the type of integration. The following sections contain information related to Command integration with Omneon or Harris devices, as well as others that use VDCP. Configuring VDS for Omneon The Avid Video device service has a plug-in that allows for network-based control of Omneon Spectrum and Media Deck. Selecting the Omneon plug-in also means that the Video device service is fully redundant, like other Command services. For the plug-in to work, however, some configuration is required, using the Avid Service Configuration application of Avid Service Framework. For more information about this application, see the Avid Service Framework Users Guide.
To configure the Avid Video device service for Omneon network control:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid Video Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Plug-in Chooser tab, select the Omneon plug-in and click Apply. By default this selection is set to none.
50
5. Click Apply. The Change Plug-in dialog box will appear.
6. Click Yes. This will restart the device service.
After you select a plug-in, you must click Apply and let the service restart before proceeding. 7. On the Avid Video Device Service Settings tab, enter the name of the device, which must match the name used for the device channel in the Command system settings.
51
8. Set the Frame rate accordingly, and leave the Drop Frame check box selected. 9. Set timeout in seconds for cue, start (play), pause, and eject. 10. Transfer Status is a feature that only works with Interplay. It is dependent on the Interplay Agent service getting metadata from Interplay. Select the check box only if this is the case with your system. For more information, see Transfer Status Icon on page 59. 11. Enter the machine name or IP address of the Omneons Media Director. This information is obtainable via the Omneon System Manager software. 12. Leave the Clip Directory field blank to accept the default or enter another pathname for the directory that will hold all of the media clips. An example of the clip directory is: /OMN/clip.dir. 13. Omneon usually stores clip information in MOV or MXF formats. The extension for the default format is .mov.mxf so that either format is recognized. 14. Edit and add channel indices accordingly: The first channel index will appear automatically with the player information filled in, but it can be modified as needed. The channel index values must match the channel index value when you add the device channel in Command. Command is case sensitive, so the case must match exactly. Enter the name for each player. This information is also obtainable via the Omneon System Manager software. Use the Add button to add more. To change a setting, click on it and select the proper index being used from the list that appears.
52
15. Click Apply and then click Yes when asked to restart the device service. You can then close the Avid Service Configuration application.
For a redundant configuration, you can apply these settings to the second device service by clicking the Apply To... button. If the Apply To... button is dimmmed, make a bogus change, such as adding a splace to a setting and deleting it, and then moving to a different field. Then click the Apply To... button and navigate to the second device service. 16. Confirm configuration by viewing the service in Health Monitor. The service will appear connected with a green checked icon displayed when it is working properly.
If using the Avid Video device service to control an Omneon, and if you want to use Commands system setting, Hold Last Framethe default for which is five secondsyou must configure the setting, Advance-to-Cued, to zero on the Omneon device. Avid also recommends setting Last Frame Freeze to zero because Command sets that time period. After the Video device service has been configured, you must add device channels and channel groups in Command. This can be done from a Command Workstation.
To add device channels and channel groups for Omneon integration:
1. At a Command Workstation, click Tools > System Settings. The System Settings dialog box appears. 2. Expand Channel. 3. Select Device Channels. 4. Click Add.
5. Enter the channels name. 6. Enter the devices name. This name must match the device name that was entered during configuration of the Video device service. 7. For Device type, select Other Video.
53
8. Set the Channel Index to 1, 2, or 3, depending on which player you are controlling. 9. (Optional) Add notes. 10. Click OK. The Add Device Channel dialog box closes. Repeat these steps to add more device channels. 11. On the System Settings dialog box, click Apply so that you can add the new device channels to a channel group. 12. On the left side of the System Settings dialog box, select Group. 13. Click Add to create the channel group. 14. Enter the name of the channel group. 15. Click Add and select the appropriate channel. Repeat as necessary. 16. Click OK, and then OK again to save the settings. 17. Create a standalone playlist, add items, and test playout to confirm functionality. With Omneon network control, Command users can make subclips. The subclip feature will create a new media item on the Omneon video server. It is not a master clip with specific pointers.
To create a subclip:
1. At a Command Workstation, open an item in the Media Viewer. 2. Click the Subclip button. 3. Give the subclip a name and click OK. It should appear in the Inventory panel shortly.
The Subclip button will appear when controlling other devices via the Video device service, but only functions when creating subclips on an Omneon device.
Configuring VDS for Harris Like Omneon, there is a third-party plug-in that can be used for Command integration with a Harris Nexio device. The Harris plug-in is distributed by the Harris Corporation; users should contact the Harris Corporation for more information.
As with all third-party devices, users need to purchase a 3P device channel for each channel that is going to be controlled by Command. For the plug-in to work, some configuration is required, using the Avid Service Configuration application of Avid Service Framework. The following graphic shows sample settings for the Avid Video device service with the Harris plug-in chosen.
54
For detailed information on how to configure the Avid Video device service for the Harris NEXIO plug-in, see the third-party documentation provided by the Harris Corporation.
Wiring Serial Connections for Avid Video Device Services (for VDCP) Before configuring Command for VDCP control, ensure the serial cables are correct, according to the specifications provided in this section. The external connector and cable are customer supplied. A shielded cable must be used on the connector to maintain RFI compliance. The shield of the cable should be connected to the connectors shield or shell. This table is for cabling with a 25-pin, female-ended connector (shown) to the Digi Acceleport RS422 card on the Command Server via the octopus cable:
13 1
25
14
Pins #
Wire Color
Signal
1 2
Not used Red
TxD+
55
Pins #
Wire Color
Signal
3 4 - 13 14 15 16 17 - 25
Yellow Not used Green Not used Black Not used
RxD+ TxD RxD
This table is for cabling with a Sony-standard, 9-pin, male-ended connector (shown) to the video server:
5 1
Pins #
Wire Color
Signal
1 2 3 4-6 7 8 9
Not used Black Red Not used Yellow Green Not used
RxDTxD+ RxD+ TxD
Video pinouts are manufacturer specific, but in all tested devices, they used the Sony standard wiring provided in this section.
56
For serial connections not specifically covered in this section, the follow table applies:
DB-25 Video Server
Rx+ RxTx+ Tx-
Tx+ TxRx+ Rx-
Configuring VDS for VDCP For integration with third-party video devices that use VDCP, its important to confirm that the device is set to VDCP control.
To configure the Avid Video device services:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid Video Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Avid Video Device Service Settings tab, enter the name of the device, which must match the name used for the device channel in the Command system settings.
57
5. Set the Frame rate accordingly, and leave the Drop Frame check box selected. 6. Set timeout in seconds for cue, start (play), pause, and eject. 7. Transfer Status is a feature that only works with Interplay. It is dependent on the Interplay Agent service getting metadata from Interplay. Select the check box only if this is the case with your system. For more information, see Transfer Status Icon on page 59. 8. An inventory port is mainly used to create standalone playlists, or to view items in the Inventory panel at a Command Workstation. Enter a COM port if you want to use one port for inventory. Leave it blank if you want to use all available channels for playback.
If the Avid Video device service is configured with playback channels only (no inventory port), you will not see the devices playback inventory in the Inventory panel at a Command Workstation. Despite this, the playlist in Command will still reflect inventory status, and an unavailable item promptly changes to available once it is transferred to the device. 9. Edit and add port connections accordingly: The first channel index will appear automatically with the port information filled in, but it can be modified as needed. The channel index values must match the channel index value when you add the device channel in Command. Use the Add Port Connection button to add more port connections. To change a serial port setting, click on it and select the proper port being used for serial control from the list that appears. For instance, if the serial cables are connected to the first three ports (P1,P2, and P3), these would correspond to COM 3, COM 4, and COM 5. The Windows operating system uses COM 1 and COM 2 by default. To change a video port setting, click on it and type a new value. Typically, video ports are set to 1, 2, 3, and 4.
10. Click Apply. You can then close the Avid Service Configuration application. 11. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 12. Click the Advanced button. 13. After the Avid Services dialog box opens, select the device, then stop and restart it. 14. Confirm configuration by viewing the service in Health Monitor. The service will appear connected with a green checked icon displayed when it is working properly. Configuring VDCP for Redundant Mirrored Playback Avid recommends mirrored playback for users who want redundant functionality for devices with VDCP control.
58
To configure VDCP devices for redundant mirrored playback:
1. Install and configure the VDS that controls the primary device channels of the primary Command Server. 2. Install and configure the VDS that controls the mirrored device channels on the backup server.
The mirror VDS should use a different device name, such as device2, from the primary VDS. The mirror VDS will run as an active primary service, even though its running on the backup server. 3. In the event of a primary server failure, users should switch to mirror-only playback.
Transfer Status Icon Command can show the transfer status of items that are sent to playback from Interplay. Command displays the transfer status iconan orange arrowin the Inventory panel to denote that the item is transferring.
The transfer status relies on the metadata (such as thumbnail, slug, format, and so forth) arriving from Interplay, and when it arrives, changes the status from the transferring arrow to the green check mark. This integration requires the following: Interplay, using the Send to Playback feature. Configuring the Avid Interplay Agent service to get metadata from Interplay The transfer status being selected in the configuration of the Avid Video device service.
59
To see the transfer status icon, the user needs to have the Inventory panel open and the correct channel group selected at a Command Workstation.
Selecting a different channel group will interrupt this process and cause the transfer status icon to change to a green check mark, even if the transfer has not completed. There are a few situations where the transfer status will show false positive, meaning that it reports that the item is transferring when it really isn't. The remedy for these situations is to choose a different channel group and then go back to the original channel group, or close and open the Inventory panel. Omneon subclipsbecause subclips are not sent to playback; Interplay does not contain metadata. Transfers from one Omneon to anotherbecause items are not sent to playback; Interplay does not contain metadata. Failed retrieval of the metadata from Interplay.
The Harris plug-in also has a Transfer Status checkbox, but it works differently. The Harris NXOS manages transfer status without involvement from Interplay.
Configuring Avid Interplay Agent Services

The Avid Interplay Agent service is installed at sites that want to utilize thumbnail images in Command from video on AirSpeed video servers. It connects and logs in to the Interplay engine to retrieve thumbnail images of AirSpeed media. It also works for the Video device service to collect more information from Interplay, so any third party video devices with Interplay systems will display thumbnails, slugs (title), and format information in the Command playlist. After the service is installed on the Command Server, some additional configuration is required, using the Avid Service Configuration application of Avid Service Framework. For more information, see the Avid Service Framework Users Guide.
On systems with multiple Command Servers, you must configure the Avid Interplay Agent service on each of them.
To configure the Interplay Agent services:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid Interplay Agent Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK.
60
4. If the Allow Unrestricted Security dialog box appears, click Yes. 5. On the Settings tab in the Login Credentials section, enter the following information: a. b. Server Name - This is the name of the asset manager server also known as the Interplay Server running the Interplay Administration application. Database - By default, this is AvidWG. It is the asset manager project. You can obtain the name of the project database via the Interplay Administration application on the Interplay Server. User Name - This should be the Avid Interplay administrators user name, not the Command administrators user name.
c.
d. Password - This should be the Avid Interplay administrators password, not the Command administrators password.
6. In the Video Devices section, click Add. The Add Video Device dialog box appears.
61
Adding a video device is not necessary when integrating with an AirSpeed video server. 7. Enter the devices name exactly as it appears in the Avid Video device service. 8. In the Catalog field, enter the name of the folder (inside the Catalogs folder) where items are being transferred to in Interplay. This should match the playback catalog in the Avid Transfer Engine. If the destination folder is more than one layer deep, use a forward slash (/) as the directory separator, such as omneoncat/1A. You do not need to specify the Catalogs folder itself.
If the playback catalog is not already configured, it must be set up correctly via the Tranfer Engine Configuration application, which runs on the Transfer Engine Server. The procedure for this is provided next. 9. Click OK. 10. Click Apply. You can then close the Avid Service Configuration application.
To configure the playback catalog on the Transfer Engine Server:
1. Start the Transfer Engine Configuration application. 2. In the Playback section, click Add. The Playback Device dialog box appears.
3. Select the Enable Playback Catalog Name check box and, in the text field below that, enter the same destination folder used to configure the Interplay Agent device service, such as omneoncat/1A.
62
The device name in the Playback Device dialog box is not the same as the Interplay Agent device name. This one is specific to Transfer Manager. 4. Click OK.
Configuring the Avid UMD Device Service

The Avid iNEWS Command user interface lets you control Under Monitor Display (UMD) or In Monitor Display (IMD) devices via the TSL UMD protocol, developed by Television Systems Limited, so that the clips title, the countdown timecodethe one showing the remaining durationand the tally light for playing video can be displayed on or near the video monitor in the control room. Without the Avid UMD device service and Avids TSL plug-in, the timecodes for playing video appear only on the Command Workstation. In general, the device service communicates through a third-party intermediate device, such as TallyMan manufactured by Television Systems Limited. With the TallyMan, one cable is run to the TallyMan and other cables run from it to each UMD. The Avid UMD device service, along with Avids TSL plug-in, is installed from the Command installation CD on the iNEWS Command Server. For more information, see Installing Avid iNEWS Command on the Server on page 40. After installation, additional configuration of the device service is required, using the Avid Service Configuration application of Avid Service Framework. For more information about this application, see the Avid Service Framework Users Guide. Configuration of the device service is covered in the following procedure.
To configure the Avid UMD device service(s):
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid UMD Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK.
Avids TSL plug-in is preselected for you on the Plug-in Chooser tab. 4. On the Avid UMD Device Service Settings tab, the Service Name should be set to a unique name that represents the current instance of the device service. By default, it first appears as Service Name. 5. The Show Duration check box determines if the duration of a clip is displayed when a clip is cued. For 8-character displays, if Show Duration is left unchecked, the clips title or ID is displayed as determined in the step 6. If Show Duration is selected, then instead of the clips title or ID, the total clip duration is shown in an abbreviated timecode format (hh:mm:ss with no frames) when a clip is cued.
63
For 16-character displays, the clips title or ID are always shown. So, if Show Duration is left unchecked, the full 16 characters are used to display the clips title or ID. If Show Duration is selected, then an abbreviated timecode in the format mm:ss is shown (or hh:mm:ss if needed for clips longer than an hour) along with a shortened version of the clips title or ID. The two are separated by one space. 6. Select the Display Name. Options are: Title or ID. If Title is chosen, and Show Duration is not selected, then the clips title will be displayed when a clip is cued. If ID is chosen, and Show Duration is not selected, then the clips video ID will be displayed when a clip is cued.
When a clip title is displayed, only the rightmost eight characters show up in an 8-character display, so if the clips title is longer than 8 characters it will be truncated. Generally the rightmost characters will be more unique, making it easier to identify the clip. There is no indication when a clips title is truncated. For 16-character displays, the number of characters is determined by whether the duration is shown and the length of that duration. For instance, you could see 10 characters of either the clips title or video ID followed by a space and the duration in an mm:ss format, as shown in the following example: p-politics 01:32 If the clips duration is longer than an hour, the duration will appear as hh:mm:ss, and the clips title or ID will be truncated to eight characters.
64
7. For every under monitor display you want to operate, click Add UMD Device to add a new row to the table from which you can then edit the information in each column. Each device is assigned its own device number; that is, the Device column is filled out automatically, starting with one (1), and is not used in the services configuration. 8. The Channel Index lets you associate a device with a device channel index in Command. Options in this drop-down list include numerical values of one (1) through 16. The channel index, which corresponds to a playout channel, is set in Commands System Setting dialog box under the Channel > Indices category. You can access that dialog box by clicking Tools > System Settings.
Four columns shown in the previous graphic (Type, Hostname/IP, UMD Address, and Tally) relate to the TSL plug-in. If an alternative third-party plug-in is used, what you see might vary. 9. Set the Type according to what kind of UMD device you are using. The Type column can be set to one of three options: t t t t Single 8 for 8-character display Dual 8 Left for 16-character display, access leftmost 8 characters Dual 8 Right for 16-character display, access rightmost 8 characters Single 16 for 16-character display
10. The Hostname/IP column is most commonly set to tallyman, but can be an IP address instead of the devices hostname. The device service uses port 8900 by default; however, if a different port needs to be specified, you can add it to the end of the hostname, such as tallyman:1001. 11. The UMD address can be set to numerical values of zero (0) through 126. When using TallyMan, except for Dual 8 Left and Dual 8 Right types, which share an address, each UMD device should have a unique address.
If you do not know the UMD address for your device, unplug and reconnect the Ethernet connection. Watch the devices display; it will show its UMD address as Addr plus a numerical value, such as: Addr 001. 12. The Tally column is a drop-down list that relates to tally indicator control for Command. Its options are: one (1) through two (2). UMD devices often have two tally indicator lights. If set to one, Command will use the left light. If set to two, the right tally light is used. For TallyMan, however, you will have to choose which light to use when you set up the TallyMan. 13. Click Apply. You can then close the Avid Service Configuration application.
You can reconfigure UMD devices without having to restart the device service.
65
Configuring UMD for Redundancy The Avid UMD device service supports redundancy, but some configuration is required.
To configure for redundancy:
1. Configure both device services to have the same service name, such as UMD1. 2. Restart the services. After the service name is set, it should not be necessary to restart services for the remaining changes to occur; clicking Apply is all that is necessary. 3. Configure the remaining fields on the primary service and click Apply. 4. Make a bogus change, such as adding a space after the host name and then removing it. 5. Click the Apply To button and check the backup device service.
For Ethernet control and redundancy to work, you must upgrade the Tallyman TM1 devices software to version 1.7.4 and then configure it for Ethernet control. Please see Tallyman documentation for more information. Avid also recommends the Tallyman device be in the same subnet as the Command Server, to minimize the possibility of lost packets.
Configuring the Lookup Tab

If setting up redundant systems that are in different subnets, you must add both server names to the Lookup tab in Avid Workgroup Properties. The following procedure should be completed on both the primary and backup Command Servers.
To configure the Lookup tab:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 2. On the Lookup tab, click the Add button under the Workgroup section. The Add Workgroup dialog box will open on top of the Avid Workgroup Properties window, as shown:
66
3. Enter the name of the workgroup and click OK. It will appear in the Workgroup section of the Avid Workgroup Properties window. 4. Click the Add button under the Lookup services section (above the Apply button).
67
The Add Lookup Service dialog box will open.
5. Enter the full domain name of the current server, such as: cmdsvr1.avidbroadcast.com. 6. Leave the port setting as is. 7. Select the Expected check box. 8. Click OK. 9. Repeat steps 4 - 8 to add any other Command Server that is running the Lookup service. 10. Click OK on the Avid Workgroup Properties window. 11. Click Yes, when prompted to restart all services.
68
Configuring a Second Command System
Configuring a Second Command System

A second Command system is for controlling an independent system, like a second studio, in the same workgroup. It is not the same as a redundant system, in which the backup server uses the same system name as the primary server. In Command, the system name is numeric, such as 1, 2, 3, and so forth.
For a more meaningful name, a system alias can be configured, which appears in the status bar of the Command user interface. For more information on system aliases, see the Avid iNEWS Command Administration Guide. Multiple Avid iNEWS Command systems usually belong to the same workgroup. If two or more systems are in the same workgroup, each of the Command systems must have a unique, numeric name, which is assigned by Avid manufacturing. After installing Command on a computer that will be part of a second system, you will need to change the system name by editing the commandsystemname.xml file, which by default is installed in the following location:
C:\Program Files\Avid\iNEWS Command To change the system name:
1. Navigate to: C:\Program Files\Avid\iNEWS Command. 2. Right click the commandsystemname.xml file and choose Properties. 3. Deselect the Read-only check box and click OK. 4. Open the commandsystemname.xml file in Notepad. The text in the file will appear as shown:
5. Using numerals only, change the number (shown highlighted in the graphic) located between the tags: <NAME> </NAME>. When setting up a second system, the number must be 2 to match the license. Subsequent systems must be 3, 4, and so forth.
69
6. Select File > Save. 7. Close all workstation sessions and restart all Command and Avid Service Framework services on that computer.
The commandsystemname.xml file must be changed on all computers that are part of the second Command system.
70
2 Installing and Configuring the AirSpeed Multi Stream

AirSpeed Multi Stream is a digital recorder or playback device designed to work seamlessly in Avid Unity environments (Avid Unity ISIS and Avid Unity MediaNetwork). Multi Stream lets you capture incoming media directly into Avid shared storage or play out media to air. Depending on your model, the AirSpeed Multi Stream supports up to six simultaneous channels of playout. Media can be captured directly into Avid Unity workspaces unattended, freeing the Avid editing system for editing. You can use the Avid editing system to edit the captured media into sequences and send the sequence back to the Multi Stream for playout, then use Avid iNEWS Command to manage the playout of the sequence. For the interface to work, however, some software installation and configuration is required. Multi Stream has special requirements that are different from an Airspeed setup. Multi Stream can join two Avid Service Framework workgroups, the Interplay workgroup and the Command workgroup. Multi Streams primary workgroup must be the Interplay workgroup so ingests are transferred to Unity and media sent to playback are transferred to Multi Stream. The AirSpeed Multi Stream device service can be configured to join multiple workgroups. The main reason for joining a second workgroup will be to join the Command workgroup. Because Multi Stream is communicating with two workgroups, both need to be added to the Lookup tab in the Workgroup Properties application. This chapter contains the following main sections: Checklist: Installing the AirSpeed Multi Stream Installing Avid Service Framework Installing AirSpeed Multi Stream Device Services Checklist: Configuring the AirSpeed Multi Stream Configuring Properties for Interplay Workgroup Configuring the AirSpeed Multi Stream Device Service Configuring Properties for Command Workgroup Working with Play While Record on AMS
Checklist: Installing the AirSpeed Multi Stream

Ensuring integration with devices, such as the AirSpeed Multi Stream, requires installation of various components and services, as well as some configuration. Using the Multi Stream as the example of a device, the following is a checklist of activities an installer should verify to ensure a successful installation. Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Rack, cable, and connect the Multi Stream to the The documentation that came with your Avid network. AirSpeed Multi Stream for more information. Install the core components of Avid Service Framework on the Multi Stream. Install the Multi Stream software. Install AirSpeed Multi Stream device service from the Avid iNEWS Command software installation CD. Installing Avid Service Framework on page 73 The documentation that came with your Avid AirSpeed Multi Stream for more information. Installing AirSpeed Multi Stream Device Services on page 76
After installation, some configuration is required. For more information, see Checklist: Configuring the AirSpeed Multi Stream on page 78.
Regardless of whether the AirSpeed Multi Stream is a capture and/or playback server, ensure it is in the Interplay workgroup. If it is a playback server that will be controlled by iNEWS Command, it must be configured to join a second workgroupthe same workgroup as the Command servers. The AirSpeed Multi Stream device service can be configured to be controlled by up to two Command systems.
72

Each computer and device running Avid iNEWS Command software requires at least the core components of Service Framework and must be able to connect to a computer running the Avid Lookup service. This includes the AirSpeed Multi Stream, which will be running the AirSpeed Multi Stream device service for Command.
To install the Service Framework Software:
1. Insert the AirSpeed Multi Stream installation DVD.
Do not install Service Framework on the Multi Stream from the Command installation CD. Use the installer bundled with the AirSpeed Multi Stream software. Also, when Service Framework is upgraded for Multi Stream, be sure to upgrade only the components for which the update is designed. 2. Navigate to the directory called Avid_Framework_Workstation. 3. Double-click the program: Setup.exe. The Introduction window opens.
4. Click Next. The Workgroup Name dialog box opens.
73
5. Set the location to which Avid Service Frameworkwill be installed and click Next.
6. Type a new or existing workgroup name in the field. This is the primary AirSpeed Multi Stream workgroup, which should be the Avid Interplay workgroup. You must use the same workgroup name on all Interplay clients that are connected in your Command architecture. The workgroup name is case sensitive. You can either create a new workgroup or join an existing one. If you are creating a new workgroup, make a note regarding the workgroup name so that it can be
74
entered during other Avid Service Framework installations. Later, youll configure a secondary workgroup for the AirSpeed Multi Stream device service, which will be the Command workgroup.
If you are updating the Service Framework software, the installer remembers the last installed value. If the workgroup name was changed after the install, the installer will not be aware of the change. 7. Click Next. The Custom Setup dialog box opens.
8. Click Next. 9. Click Install to complete the installation. After installation, verify that the services are running as expected on each computer in the workgroup. For more information, see Viewing Status of Services on page 265.
75
Installing AirSpeed Multi Stream Device Services

The Command installation CD provides for installation of services associated with various production devices, such as the AirSpeed Multi Stream.
Unlike other device services, the AirSpeed Multi Stream device service is not part of the Command installation program. Its a separate install program, located on the CD.
To install the AirSpeed Multi Stream device service on the Multi Stream:
1. Insert the Command installation CD (or access the install program from the network). 2. Navigate to and double-click on AvidAirSpeedMultiStreamDeviceService.exe. 3. After the Welcome dialog box appears, click Next. The License Agreement appears.
4. Read the License Agreement, accept the terms, and click Next. If you do not accept the terms, the installation program will not continue.
You can print the terms if you want to read them later or keep a copy for your records. 5. When the Ready to Install the Program dialog box appears, click Install.
76
Installing AirSpeed Multi Stream Device Services
A progress bar is provided to show the current status of the installation.
6. When the installation is complete, click Finish. To verify that installed services are running, you must use the Avid Workgroup Properties application.
77
Checklist: Configuring the AirSpeed Multi Stream

For integration between Command and AirSpeed Multi Stream to succeed, some configuration is required. Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
All settings in Command and Framework are case sensitive. Ensure that case matches in all configuration settings.
Tasks
Refer to...
Configure the properties for the Interplay workgroup in which the AirSpeed Multi Stream resides. Configure the AirSpeed Multi Stream device service. Configure the properties for the Command workgroup if Command will be used to control the AirSpeed Multi Stream for playback.
Configuring Properties for Interplay Workgroup on page 79 Configuring the AirSpeed Multi Stream Device Service on page 80 Configuring Properties for Command Workgroup on page 82
Add the AirSpeed Multi Stream to the list of The Avid iNEWS Command Administration Guide devices and channels in Command. Also, add the channels to a channel group in Command.
78
Configuring Properties for Interplay Workgroup
Configuring Properties for Interplay Workgroup

AirSpeed Multi Stream must be installed in an Avid Interplay workgroup. If the Multi Stream will be controlled by Command, then the AirSpeed Multi Stream device service should be configured to join a second workgroupthe same workgroup as the Command Servers. See Configuring Properties for Command Workgroup on page 82 for more information.
To configure the properties for the Interplay Workgroup on the AirSpeed Multi Stream:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 2. On the Lookup tab, select the Interplay workgroup listed in the Workgroup section.
The Interplay workgroup is the same workgroup named during the installation process of Avid Service Framework on the AirSpeed Multi Stream. See Installing Avid Service Framework on page 73 for more on that procedure. 3. On the Lookup tab, click the Add button under the Lookup services section (located above the Apply button, and not the one to the far left). The Add Lookup Service dialog box will open on top of the Avid Workgroup Properties window, as shown:
79
4. Enter the fully qualified domain name of the server running the Lookup service for the workgroup. 5. Leave the port setting as is. 6. Select the Expected check box. 7. Click OK. 8. (Optional) If running multiple Lookup services, repeat steps 2 - 7 to add another server that is running the Lookup service for the workgroup. 9. Click OK on the Avid Workgroup Properties window. 10. Click Yes, when prompted to restart all services.
Configuring the AirSpeed Multi Stream Device Service

After any device service is installed for Avid AirSpeed video servers, some additional configuration is required, using the Avid Service Configuration and Avid Workgroup Properties applications of Avid Service Framework.
To configure the AirSpeed Multi Stream device services:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the AirSpeed Multi Stream Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Device Settings tab, enable the second workgroup and enter the name of the Command workgroup. 5. If the AirSpeed Multi Stream will be controlled by two Command systems, enable the second system and enter the numerical value of that system, such as 2. Options include 1-10. The default Command system number is 1. 6. If using CaptureManager for ingest control, enable it and enter the hostname of the CaptureManager server.
80
Configuring the AirSpeed Multi Stream Device Service
An example of these settings is shown in the following graphic.
7. Click Apply.
Upon applying the new settings, and if the CaptureManager is enabled, the system will append a port number to the end of the hostname you entered for the CaptureManager Server. 8. You can then close the Avid Service Configuration application.
81
Configuring Properties for Command Workgroup

AirSpeed Multi Stream must be installed in an Avid Interplay workgroup; however, if the Multi Stream will be controlled by Command, then the AirSpeed Multi Stream device service should be configured to join a second workgroupthe same workgroup as the Command Servers. If the AirSpeed Multi Stream device is in a different subnet than the Command Servers, you must add the server names to the Lookup tab in Avid Workgroup Properties on the Multi Stream.
Avid recommends, for servers and workstations joining multiple workgroups, you configure the Lookup tab to specify the FQDN of the Lookup services in both workgroups regardless of whether the server or workstation is in the same subnet as the Lookup service.
To configure the properties for the Command Workgroup on the AirSpeed Multi Stream:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 2. On the Lookup tab, click the Add button under the Workgroup sectionthe far left button at the bottom.
82
Configuring Properties for Command Workgroup
The Add Workgroup dialog box will open on top of the Avid Workgroup Properties window, as shown:
3. Enter the name of the Command workgroup. It is case sensitive. 4. Click OK. The name you entered will appear in the Workgroup section of the Avid Workgroup Properties window. 5. Click the Add button under the Lookup services section (located above the Apply button, and not the one to the far left).
83
The Add Lookup Service dialog box will open on top of the Avid Workgroup Properties window, as shown:
6. Enter the fully qualified domain name of the server running the Lookup service for the Command workgroup. 7. Leave the port setting as is. 8. Select the Expected check box. 9. Click OK. 10. (Optional) If running multiple Lookup services, repeat steps 2 - 7 to add another server that is running the Lookup service for the Command workgroup. 11. Click OK on the Avid Workgroup Properties window. 12. Click Yes, when prompted to restart all services.
84
Working with Play While Record on AMS
Working with Play While Record on AMS

This section provides additional information to help clarify the existing Play While Record feature when used with an AirSpeed Multi Stream video server. Command supports the Play While Record workflow with AMS. Once an item starts recording on the AMS, it appears within the Command Inventory Panel within approximately 10 seconds. Once it appears in Command, users can open the item in the Media Viewer to adjust the Mark In point, and then play the item.
This requires an available playback channel on the AMS that is recording the item. A Mark Out point is not required, only a Mark In timecode. To set the Mark In point for an item that is recording, it needs to be added to a Command playlist (via ENPS, iNEWS, or a Standalone playlist). Once there and available, you can double-click the item and type the Mark In point. If you want to open the item in the Media Viewer and use the Jog to set the Mark In point, you have to configure a Browse channel as part of the Command playlist. It can either be a Browse channel that is part of the Playback channel groupsuch as, Channels AB for playback and C for browseor with Command v2.6, you can configure a Playback channel group (AB) and a separate Browse-only group (C). The Browse-only channel group also needs to be added to the playlist.
To play while record on AMS:
1. Configure an AMS video server so that it has a record and playback channel. This means that the AMS Device Service needs to be part of the Command workgroup, and the playback channel needs to be in a Command channel group. 2. After the item starts recording, it should appear in Command's inventory within approximately 10 seconds. 3. After the item is available, it can be played at any time. The countdown clock time will be erratic, because the duration is being updated while the item is playing. 4. When the recording is stopped, the total time code gets updated one last time, Command then stops at the recording's stopping point, and then follows the Command hold last frame setting.
To play while record with Avid iNEWS:
1. Add the items ID to the Video ID column of the iNEWS playlist and load the show. 2. Start recording the item on the AMS, using the Video ID that you entered in the iNEWS playlist.
85
3. After the item becomes available, you can play it, and optionally double-click the item to enter the Mark In point.
To play while record with ENPS:
1. Do an object autocreate to create a Video ID. 2. Start recording, using the autocreated Video ID. 3. After the item becomes available, you can play it, and optionally double-click the item to enter the Mark In point.
To play while record with a standalone playlist:
1. Add the item to a standalone playlist (Alt+Ins). 2. Start recording, using the Video ID that you used in the standalone playlist. 3. After the item becomes available, you can play it, and optionally double-click the item to enter the Mark In point.
86
3 Installing and Configuring the Deko

The Avid iNEWS Command user interface allows you to control multiple production devices, such as Deko character generators. For the interface to work, however, some software installation and configuration is required. This chapter contains the following main sections: System Architecture Checklist: Installing the Deko Installing Avid Service Framework Installing Avid Deko Device Service Installing the DekoMOS Gateway Installing the DekoMOS Macro Server Checklist: Configuring the Deko Configuring the DekoMOS Gateway Configuring the DekoMOS Macro Server Configuring Avid Workgroup Properties Configuring the Deko Device Service Configuring the Avid Deko Renderer Service Creating Graphic Styles in Command
System Architecture
Understanding the relationship of Avid iNEWS Command to other aspects of the newsroom environment, such as Avid Deko systems, is helpful. Your newsroom computer system such as Avid iNEWS (or ENPS) organizes the newsroom. There is two-way communication between the iNEWS Server and other workstations running the iNEWS and iNEWS Command client software in regard to production and management of playlists. Each iNEWS Workstation can have the Deko Select plug-in, functioning as part of the user interface that enables a journalist to drag and drop any Deko graphics template into a news story and alter replaceable text or graphics in the selected template. The Deko Select plug-in communicates with the DekoMOS Gateway. The DekoMOS Gateway is the essential interface for integration of the newsroom computer system and Command with various Deko components in regard to the creation, modification, and playout of graphic elements in newsroom playlists. The DekoMOS Gateway manages configuration information and presents logs of DekoMOS activity and connections. The DekoMOS Macro Server, installed on all Deko devices used for playout, allows Command to communicate with the Dekos. The DekoMOS Macro Server receives and processes macro commands. It also acts as a client to the DekoMOS Gateway to retrieve a list of defined styles. Through this integration, Command can control playback of graphics on Deko systems and drive up to nine channels of Deko across multiple systems from a single user interface.
In this explanation, the term Deko refers to any one of these products: Deko 3000, Deko 3000 Hybrid, Deko 3000 HD, FXDeko II, Deko 2200, Deko 1000, Deko 1000 Hybrid, Deko 1000 HD, and Deko 550.
88
System Architecture
Command with Avid Deko Overview

This section contains an overview of each component involved in a Command/Deko workflow and the main purpose each serves.
Component Description
DekoMOS Gateway
Defines Deko styles Equates channel number (1-9) with a MOS ID Provides inventory to the Avid Deko Select plugin in iNEWS
SYSTEM.MOS-MAP equates the MOS ID with the channel group in
Avid iNEWS
Command
SYSTEM.MAP associates the newsroom rundown with the channel group and assigns a style
Avid Deko Select Avid iNEWS Command
Used to choose the channel number and style for an item that is dragged into the newsroom rundown. Creates channel groups Creates graphic environments (also known as styles in Deko) for standalone playlists Sends playout control commands to the Avid Deko device Inventory is copied from this device to the DekoMOS Gateway. Deko software provides graphics for on-air playout. Gets style list from DekoMOS Gateway Sets style paths for replaceable, static graphics, motions, and so forth Sends inventory to the Inventory Manager in Command
Avid Deko
DekoMOS Macro Server
89
Checklist: Installing the Deko

Ensuring integration with devices, such as the Avid Deko, requires installation of various components and services, as well as some configuration. Using the Avid Deko as the example of a device, the following is a checklist of activities an installer should verify to ensure a successful installation. Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Connect the Deko to the network. Install the Deko software. Install the core components of Avid Service Framework on the Deko.
The documentation that came with your Avid Deko for more information.. Installing Avid Service Framework on page 91
Install Deko device service from the Avid iNEWS Installing Avid Deko Device Service on page Command software installation CD. 95 Install the DekoMOS Gateway. This requires a dongle. Install DekoMOS Macro Server on the Deko. Installing the DekoMOS Gateway on page 101 Installing the DekoMOS Macro Server on page 102
After installation, some configuration is required. For more information, see Checklist: Configuring the Deko on page 103. For more information on installation of the Avid Deko Select plug-in, see Setting up the Plug-ins in iNEWS on page 201.
90

Each computer and device running Avid iNEWS Command software requires at least the core components of Service Framework and must be able to connect to a computer running the Avid Lookup service.
To install the Service Framework software:
Other dialog boxes could appear depending on whether older versions of Service Framework are found, particularly if upgrading existing software. If one appears, read it carefully and reply accordingly with regard to upgrades, etc.
91
3. Click Next. The Destination Folder dialog box opens.
n
92
If space is a concern on the C drive, install in the D:\Avid\Service Framework\ directory. You will need to create these directories.
4. Set the location to which Avid Service Frameworkwill be installed and click Next. The Workgroup Name dialog box opens.
5. Type the name of the Command workgroup in the field.
93
7. Select the option: Avid Service Framework Client and click Next. The Custom Setup dialog box opens.
94
Installing Avid Deko Device Service
By default, the Time Synchronization service is selected to be installed; however, this service should only be installed if you do not already use something to synchronize your PC clocks. If you use NTP or some other method for time synchronization, do not install this service. For more information about the services in this dialog box, see the tables in page 24. 8. Click Next and follow the installation instructions to complete the installation.

The Command installation CD provides for installation of services associated with various production devices, such as the Avid Deko.
To install the Deko device service on the Deko:
95
96
You can print the terms if you want to read them later or keep a copy for your records. The Destination Folder dialog box opens.
If space is a concern on the C drive, install in the D:\Avid\iNEWS Command\ directory. You will need to create these directories. 5. Do one of the following: t t Click Change to designate an install directory, and then click Next. Accept the default location by clicking Next.
97
6. When the Options dialog box opens, select Avid Deko.
The Custom Setup dialog box will appear.
98
The Help button opens a dialog box that provides descriptions of the various install states available for a custom installation as indicated by the icons. The Space button opens a dialog box that provides information on whether the computers destination drive has enough disk space available to install the current selection of features.
7. Click Next.
99
8. When the Ready to Install the Program dialog box appears, click Install. 9. When the installation is complete, click Finish. To verify that installed services are running, you must use the Avid Service Framework Workgroup Properties application.
100
Installing the DekoMOS Gateway
Installing the DekoMOS Gateway

The Net HASP dongle, supplied by Avid, as well as the HASP License software and driver are part of the DekoMOS Gateway installation. Therefore, installing the DekoMOS Gateway is three-fold: Connecting the Net HASP Dongle Installing the DekoMOS Gateway and Net HASP Software Confirming the NetHASP License Manager Configuration
For thumbnails of Deko graphics to appear in Command, the DekoMOS Gateway must be in the same domain as the Command Server(s). The DekoMOS Gateway can not be installed on either the iNEWS or ENPS Servers and should not be installed on the Command Server. Avid recommends installing the DekoMOS Gateway on its own dedicated computer with a network connection to the Deko. The selected computer should be running Windows 2003 Server operating system, not Windows XP. Otherwise, because of Windows limitations, the number of clients allowed to connect simultaneously is limited to ten.
Connecting the Net HASP Dongle

The Net HASP dongle included with your Deko system should be connected to the computer where you will install the DekoMOS Gateway software.
To connect the Net HASP Dongle:
Connect the dongle to either the parallel port or one of the USB ports on the back of the machine. The Net HASP dongle enables the Deko Select option for the newsroom workstations.
The Net HASP License Manager, the driver for the Net HASP, installs automatically with the DekoMOS Gateway software.
Installing the DekoMOS Gateway and Net HASP Software

To install the DekoMOS Gateway on a dedicated computer:
1. Insert the Deko Select installation CD in the computers CD-ROM drive (or access the program from the network). 2. Navigate to and run the DekoMOSGateway.exe install program. 3. Click OK and follow the instructions on the screen to install the software.
101
Avid recommends selecting Service as the installation option for the Net HASP License Manager. After installing, you should confirm that the Net HASP License Manager is running and that it is configured to use TCP/IP.
Confirming the NetHASP License Manager Configuration

You will need to confirm that the NetHASP License Manager is both running and configured properly.
To confirm activation and configuration of the NetHASP License Manager:
Right-click the NetHASP License Manager icon (circled in red below) in the system tray at the bottom of your screen and select Show.
The Net HASP License Manager window opens. You should see the words Server is listening to TCP/IP: Loaded and Net HASP License Manager is now - Active.
Installing the DekoMOS Macro Server

The DekoMOS Macro Server should be installed on each Deko used for playout to air.
To install the DekoMOS Macro Server on the Deko:
1. Insert the Deko Select installation CD in the Deko devices CD-ROM drive. 2. Navigate to and run the DekoMOSMacroServer.exe program. 3. Click OK or press Enter. 4. Follow the on-screen prompts to complete the installation.
102
Checklist: Configuring the Deko
Checklist: Configuring the Deko

For integration between Command and Deko to succeed, some configuration is required. Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
All settings in Command and Framework are case sensitive. Ensure that case matches in all configuration settings.
Tasks
Refer to...
Configure the DekoMOS Gateway. Configure the DekoMOS Macro Server. Configure the styles in the DekoMOS Macro Server. Configure Avid Workgroup Properties for the Deko. Configure the Deko device service. Add the MOS-IDs for Command channel group(s) to the SYSTEM.MOS-MAP story in Avid iNEWS.
Configuring the DekoMOS Gateway on page 104 Configuring the DekoMOS Macro Server on page 111 Configuring Styles on the DekoMOS Macro Server on page 113 Configuring Avid Workgroup Properties on page 115 Configuring the Deko Device Service on page 117 Editing the SYSTEM.MOS-MAP Story on page 200
(Optional) If you intend to use standalone Creating Graphic Styles in Command on page playlists in Command or use the Avid Deko 119 Select plug-in with ENPS and Avid iNEWS Command, create the same stylesconfigured in the DekoMOS Macro Serveras graphic styles in Command.
103
Configuring the DekoMOS Gateway

Templates exist on both the DekoMOS Gateway and the Deko device. The DekoMOS Gateway is then used to supply thumbnail graphics and handle file requests from plug-ins at multiple workstations, thus relieving such burden from the actual device that might be busy during playout. Duplication of assets on the gateway and device is not automatic; therefore, it must be maintained manually. After the DekoMOS Gateway is installed, you need to configure various settings in the software. This section covers only those settings that directly impact integration with Command.
For more information on how to configure the DekoMOS Gateway and for further explanation of the settings available for configuration that are not covered in this book, see the Avid Deko Select Installation and Users Guide.
To configure the DekoMOS Gateway:
1. Determine if the DekoMOS Gateway is running. If the DekoMOS Gateway is not running, click the Start button and select Programs > Avid Systems > DekoMOS > DekoMOS Gateway. If the DekoMOS Gateway is running, maximize the window by right-clicking on the icon (shown below next to the clock) in the taskbars system tray.
2. If you have not previously configured DekoMOS Gateway, or if it is missing any required information, the DekoMOS Gateway Configuration dialog box will automatically open when the application starts. If it does not open, do one of the following: t t Click the Configure button. Press Alt+C.
104
3. Select the General tab.
4. In the Paths area, enter settings as follows: t In the XML Storage Folder text box, enter or browse to the pathname of the folder for storing active rundowns. If you enter a folder name that does not exist, when you click OK, the system will prompt you with a question asking if you would like the system to create this folder. This path should be local to the DekoMOS Gateway computer and therefore begin with a drive letter, such as C:. In the User Settings Storage Folder text box, enter or browse to the pathname of the folder for storing individual user client settings. If you enter a folder name that does not exist, when you click OK, the system will prompt you with a question asking if you would like the system to create this folder. This path should be local to the DekoMOS Gateway computer and therefore begin with a drive letter, such as C:.
In most cases, these are left at the default settings. The remaining settings on the General tab can also be left at the defaults.
105
5. Select the Connections tab.
6. In the Primary NCS area, enter localhost for the address. 7. Avid recommends leaving the port settings in the Primary NCS and Listening Ports areas set to the defaults. 8. In the Net HASP Settings area: t The IP address text box automatically defaults to the address of the current computer. Ensure that the address is correct and belongs to the DekoMOS Gateway computer with the Net HASP License Manager software installed. If not, enter it. Keep the default setting of 475 in the Port field to indicate the port number where the Net HASP checks for connections. This can be changed if you receive an error message.
9. In the MOS IDs area, enter the Gateway ID and set the NCS ID to localhost. This setting enables every template that is dragged and dropped into a story to use the specified ID.
The Gateway ID must match the MOS ID specified in the SYSTEM.MOS-MAP story in the iNEWS newsroom computer system. 10. Select the MOS ID per Ch radio button to enable users the ability to drag and drop templates into specific channels. Once you select this radio button, the dialog box changes to reveal the Assign Channel IDs button.
106
11. Click the Assign Channel IDs button. The Configure Channel IDs dialog box opens.
12. For each channel listed in the Ch column (that is, 1, 2, 3, 4...), in the Gateway ID column, enter a corresponding MOS ID for the channels you want to use. With MOS ID per Ch selected and channel IDs configured, the MOS ID of the templates that are dragged and dropped into a story will vary depending on the channel with which the template was dropped.
The channel IDs configured in the DekoMOS Gateway must be added to the SYSTEM.MOS-MAP story in the iNEWS newsroom computer system. For more information, see Editing the SYSTEM.MOS-MAP Story on page 200. 13. Click OK to return to the DekoMOS Gateway Configuration dialog box.
107
14. Select the Reject items with unknown Gateway IDs check box unless you are using Avid Deko Select with an ENPS system and MOS Redirection. 15. Click the Browser/Editor tab. 16. In the Graphic Browsers area, click the Add button. The Add Graphic Browser dialog box opens.
17. Type <manual> in the Alias field. 18. Type <manual> in the AppID field. 19. Click OK. The settings you entered will appear in the corresponding columns in the Graphic Browsers area.
n
108
Setting Graphic Browsers to <manual> enables the Deko Select plug-in for manual entry of replaceable graphic names or numbers.
20. Click the Client Styles tab.
21. Click the Add button. The Add Style dialog box opens.
22. Enter a style name in the Style Name text box (with no spaces) and click OK. This is the name that will appear in the Deko Select plug-in on the newsroom computer system workstations and in the Avid iNEWS Command Inventory.
The Deko style is also referenced by the DekoMOS Macro Server and must be in the iNEWS SYSTEM.MAP story for each rundown using the Deko with Command. For more information, see Configuring Styles on the DekoMOS Macro Server on page 113. 23. If the style name you just added is not displayed in the Style Name text box on the Client Styles tab, click the Down arrow beside the text box to select it from a list of style names. 24. In each of the four Folder text boxes, enter the path that the style should reference or press the button to the right of each text box to navigate to the appropriate folder.
109
All newsroom computer system workstations will locate the elements for display in these folders.
Avid recommends that they reside on the computer where the DekoMOS Gateway is installed. All folders should be shared for Read Only access. This ensures that the graphics remain as they were created while allowing access to those graphics. For best performance, files for playout are stored on the Deko. Duplicate files stored on the DekoMOS Gateway are accessed by the Deko Select plug-in. The path you enter must be a UNC path and not a drive letter path. The format for a UNC path is \\server\volume\directory and is not case-sensitive. For example:
\\Shared1_svr\Shared1\WGroups
25. On the Control Room tab, enter a name for a control room. 26. Click OK.
Deko and Deko Select Subfolders

Users can organize their templates into subfolders, both on the DekoMOS Gateway and the Deko device itself. Command supports the use of subfolders with the Deko for both hand-entered (*CG) and Deko Select items.
n
110
The Deko and DekoMOS Gateway must have a uniform subfolder structure so, for instance, an item in the Sports\Score subfolder on the Deko must also be in the Sports\Score subfolder on the DekoMOS Gateway.
Configuring the DekoMOS Macro Server
For hand-entered items, the subfolder must be added prior to the template in the iNEWS production cue. For example, the SPORTS folder is a subfolder of the base template directory, and the SCORE folder is in the SPORTS folder. F_SCORE1 is the name of the template, which contains four fields.
*cg SPORTS\SCORE\F_SCORE1 FIELD1 FIELD2 FIELD3 FIELD4

To configure the DekoMOS Macro Server:
1. Do one of the following: t If the DekoMOS Macro Server is not running, access the configuration window by clicking the Start button and select Programs > Avid > DekoMOS > DekoMOS Macro Server. Double-click the desktop icon. If the DekoMOS Macro Server is running and is visible in the system tray, click the DekoMOS symbol in the system tray to maximize the application.
t t
The DekoMOS Macro Server window appears. The top portion of the window displays a log of DekoMOS Macro Server activity. The XML commands that the DekoMOS Macro Server is executing are shown in the white text area. Blue text indicates that things are OK. Red text indicates that there is a problem. The Gateway/Style status icon appears green on connection; it does not stay green.
111
2. To specify that this log shows data communication in full xml view, select Details, near the bottom right of the window. Or, deselect Details to show a simple one line view. To clear the information displayed here, click the Clear button. 3. In the Gateway Address text box, type the IP address or host hame of the machine running the DekoMOS Gateway. 4. The Playback Port text box and the Local IP Port text box are 10544 and 10543, respectively, by default. Do not change these port numbers unless you receive an error message. The Playback Port number must be the same number you typed during DekoMOS Gateway configuration as the Playback Port. 5. Click the Apply button below the Gateway Address text box. 6. Click Enable Logging if you want all logged information about DekoMOS Macro Server activity to be automatically sent to the folder Avid\DekoMOS\Logs. 7. Click Start Minimized to specify that upon starting the DekoMOS Macro Server will not display this window, but will appear in the system tray.
112
You can verify that the DekoMOS Macro Server is communicating with the Gateway. When the Macro Server is first started and correctly communicating with the DekoMOS Gateway, the Gateway/Styles status icon turns green for a few seconds, then appears grayed out. If there is no communication, it will appear red, indicating that there is a problem talking to the Gateway. You can verify that the DekoMOS Macro Server can confirm the existence of scheduled graphics, graphic assets, and clips. The status icons next to Template Graphics File Monitoring, and Replacement Graphic File Monitoring should be green. The DekoMOS Macro Server must be able to monitor these files to communicate information to Avid iNEWS Command.
Configuring Styles on the DekoMOS Macro Server

The same style names, but with local paths, must be configured on the Macro Server as they were configured on the DekoMOS Gateway. For best performance, files for playout are stored on the Deko; duplicate files, stored on the Gateway, are accessed by the Deko Select plug-in.
To configure styles and corresponding local paths:
1. Do one of the following: t If the DekoMOS Macro Server is not running, access the configuration window by clicking the Start button and select Programs > Avid > DekoMOS > DekoMOS Macro Server. Double-click the desktop icon. If the DekoMOS Macro Server is running and is visible in the system tray, click the DekoMOS symbol in the system tray to maximize the application.
t t
The DekoMOS Macro Server window appears. 2. Click the Styles button. The Deko Style Settings dialog box opens.
113
3. To configure styles defined in the DekoMOS Gateway, select the Style Name from the list and then set the appropriate paths that this style will use. Although you should use the same paths as set in the DekoMOS Gateway for that style, paths should be local to this computer for best performance. 4. In the Additional Macro Commands text box, type additional commands to send to Deko when the style is selected. This is useful for opening any show-specific presets or other files. 5. Click Apply to apply settings for a style. 6. Click OK when you have finished configuring styles.
To retrieve styles recently configured in DekoMOS Gateway and add them to the list of styles in the Deko Style Settings window:
Click the Refresh Styles List button in the Deko Style Settings window.
114
Configuring Avid Workgroup Properties

If the Deko device is in a different subnet than the Command Servers, you must add the server names to the Lookup tab in Avid Workgroup Properties on the Deko.
To configure Avid Workgroup Properties on the Deko:
3. Enter the name of the workgroup. It is case sensitive. 4. Click OK. The name you entered will appear in the Workgroup section of the Avid Workgroup Properties window. 5. Click the Add button under the Lookup services section (above the Apply button). The Add Lookup Service dialog box will open on top of the Avid Workgroup Properties window, as shown:
115
6. Enter the full domain name of the server running the Lookup service for the workgroup, such as: cmdsvr1.avidbroadcast.com. 7. Leave the port setting as is. 8. Select the Expected check box. 9. Click OK. 10. Repeat steps 5 - 9 to add another server running the Lookup service for the workgroup. 11. Click OK on the Avid Workgroup Properties window. 12. Click Yes, when prompted to restart all services.
116
Configuring the Deko Device Service
Configuring the Deko Device Service

After any device service is installed for Deko character generators, some additional configuration is required, using the Service Configuration application of Avid Service Framework. For more information, see the Avid Service Framework Users Guide.
To configure the device service:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. Navigate to and select the Avid Deko device service. 3. When prompted for the administrator password, enter it. 4. Enter the host name for the respective device. 5. Enter the name of the DekoMOS Gateway computer. 6. Select the appropriate device mode.
In single channel mode, items with motions and/or clips are rendered when cued and then paused at the first frame. In dual channel mode, items are not rendered until they are played. 7. Click Apply. You can then close the Avid Service Configuration application. 8. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 9. Click the Advanced button. 10. After the Avid Services dialog box opens, select the device, then stop and restart it.
117
Configuring the Avid Deko Renderer Service

The Avid Deko Renderer service is installed at sites that want to integrate with an Avid Deko and utilize thumbnail images. After the service is installed on the Command Server, additional configuration should not be necessary. By default, this service is pre-configured to automatically locate the DekoMOS Gateway on the network. However, if the service was installed and cannot locate the DekoMOS Gateway, you can manually configure it to do so via the Avid Service Configuration application.
The Deko Renderer service does not take up a HASP license seat.
To configure Deko Renderer services:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid Deko Renderer Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. If the Allow Unrestricted Security dialog box appears, click Yes. On the Settings tab, youll see the service set to Automatically.
118
Creating Graphic Styles in Command
5. Select Manually. 6. Enter the host name or IP address for the DekoMOS Gateway computer. 7. Click Apply. You can then close the Avid Service Configuration application.
You might need to restart the service after applying any changes. For redundant systems, ensure that all Deko Renderer services on every Command Server are set the same.

If you plan to create and use standalone playlists at a Command Workstation or use a Avid Deko Select plug-in with ENPS integration, you must create graphic styles in Command that match the styles configured on the DekoMOS Macro Server.
To add a graphic style:
1. Select Tools > System Settings.
2. Select Playlist.
119
3. Click the Add button. A style will appear in the Styles list as shown:
4. By default, the name of any added style is Style, but that can be changed. To do so, double-click on the name in the list and retype the new name. 5. After multiple styles are added, use the Default style drop-down list to select which one the system should use as a default. 6. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
7. Enter the administrator password and click OK. If you did not configure a password, leave it blank. For more information on styles, see the Avid Deko Select Users Guide.
120
The set of graphics styles specified in the system settings in the Playlist category will appear as options in various parts of the Command user interface, such as: the Default style list (shown in the previous graphic), the Default graphics style list in the the MOS > General category of the System Settings dialog box (shown in the graphic in Configuring MOS Settings in Command on page 256), and in the Playlist Properties dialog box.
121
122
4 Installing and Configuring the Thunder

The Avid iNEWS Command user interface allows you to control multiple production devices, such as Thunder production servers. For the interface to work, however, some software installation and configuration is required. This chapter contains the following main sections: Checklist: Installing and Configuring the Thunder Installing Avid Service Framework Installing Avid Thunder Device Service Configuring Avid Workgroup Properties Configuring the Thunder Device Service Configuring the Thunder Creating the ThunderMOS.cfg File Creating the ThunderMOS.ini File
Checklist: Installing and Configuring the Thunder

Ensuring integration with devices, such as the Avid Thunder, requires installation of various components and services, as well as some configuration. The following is a checklist of activities an installer should verify to ensure a successful installation and configuration. Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Connect the Thunder to the network. Install the Thunder software.
The documentation that came with your Avid Thunder for more information.
Thunder integration with Command and iNEWS requires an SQL server and ODBC connection. For information on SQL server and ODBC configuration, see the Avid Thunder Products Users Guide, and the Avid On-Air Graphics Setup and Configuration Guide. Install the core components of Avid Service Framework on the Thunder. Install Thunder device service from the Avid iNEWS Command software installation CD. Configure Avid Workgroup Properties for the Thunder. Installing Avid Service Framework on page 125 Installing Avid Thunder Device Service on page 129 Configuring Avid Workgroup Properties on page 135
All settings in Command and Framework are case sensitive. Ensure that case matches in all configuration settings. Configure the Thunder device service. Configure the Thunder. Create the ThunderMOS configuration file. Create the ThunderMOS.ini file. Configuring the Thunder Device Service on page 137 Configuring the Thunder on page 138 Creating the ThunderMOS.cfg File on page 140 Creating the ThunderMOS.ini File on page 141
124

125
n
126
127
128
Installing Avid Thunder Device Service

The Command installation CD provides for installation of services associated with various production devices, such as the Avid Thunder.
To install the Thunder device service on the Thunder:
129
130
You can print the terms if you want to read them later or keep a copy for your records. The Destination Folder dialog box opens.
131
6. When the Options dialog box opens, select Avid Thunder.
The Custom Setup dialog box will appear.
132
133
7. Click Next.
8. When the Ready to Install the Program dialog box appears, click Install. 9. When the installation is complete, click Finish. To verify that installed services are running, you must use the Avid Workgroup Properties application.
134

If the Thunder device is in a different subnet than the Command Servers, you must add the server names to the Lookup tab in Avid Workgroup Properties on the Thunder.
To configure Avid Workgroup Properties:
3. Enter the name of the workgroup. 4. Click OK. The name you entered will appear in the Workgroup section of the Avid Workgroup Properties window. 5. Click the Add button under the Lookup services section (above the Apply button). The Add Lookup Service dialog box will open on top of the Avid Workgroup Properties window, as shown:
135
6. Enter the full domain name of the server, such as: cmdsvr1.avidbroadcast.com. 7. Leave the port setting as is. 8. Select the Expected check box. 9. Click OK. 10. Repeat steps 5 - 9 to add another Command Server if necessary. 11. Click OK on the Avid Workgroup Properties window. 12. Click Yes, when prompted to restart all services.
136
Configuring the Thunder Device Service
Configuring the Thunder Device Service

After any device service is installed for Thunder production servers, some additional configuration is required, using the Service Configuration of Avid Service Framework. For more information, see the Avid Service Framework Users Guide.
To configure the device service:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. Navigate to and select the Avid Thunder device service. 3. When prompted for the administrator password, enter it. 4. On the Device Settings tab, enter the host name for the respective device.
5. Specify the number of hardware channels. Do not include the software channel when counting the number of hardware channels. 6. Select the frame rate: either 30 or 25. 7. Specify whether you want to enable drop frames: Yes or No. 8. Set ID selection to Automation.
137
9. Click Apply. You can then close the Avid Service Configuration application. 10. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Workgroup Properties. 11. Click the Advanced button. 12. After the Avid Services dialog box opens, select the Avid Thunder device service, then stop and restart it.
Configuring the Thunder

Configuring a MOS connection for the Thunder is accomplished at the device, using the Thunder software application.
To configure the Thunder:
1. Open the Thunder software application. 2. Select File > Preferences > Protocol Setup to configure a MOS connection. The Protocol Setup dialog box opens.
138
Configuring the Thunder
3. In the Protocol Setup dialog box, do the following: Select a channel (1-8) in the Channel area. Set Protocol to ThunderNET. If you intend to use a different database for the channel, enter it in the Database (Blank = default DB) field.
4. Leave the rest of the settings as is. 5. Repeat step 3 for all physical channels, plus an extra channel that is used by Command to send inventory and transport commands. Normally, there are two hardware channels and one software channel. 6. Click OK. 7. Select File > Preferences > Channel Configuration. The Channel Configuration dialog box opens.
8. Set the Hdw Channel to correspond to the channels you set protocols for in step 3. The physical channels should be set to Hdwr; the extra channel should be set to Soft. 9. Uncheck the channels in the MiniMon column that you will not be using. 10. Click OK. 11. In the Thunder directory, right-click on the database that you intend to use and set it as the default database.
139
Creating the ThunderMOS.cfg File

If you intend to use the Thunder Select plug-in at your newsroom workstations, you must create the ThunderMOS.cfg file and configure it for each Thunder server. The ThunderMOS.cfg file contains information that allows workstations with Thunder Select plug-ins to find your various Thunder servers and browse their respective MOS databases. This information is set up in one line per Thunder server.
To configure the ThunderMOS.cfg file:
1. On the Thunders C drive create a folder called ThunderCFG, if one doesnt already exist, and ensure it is shared across the network for read access. Only one cfg file is necessary per iNEWS newsroom computer system.
The cfg file can reside in any shared network folder, as long as every workstation with the Thunder Select plug-in can access that folder. However, Avid recommends that it reside on the Thunder for easy maintenance reasons. 2. Ensure that the E drive is also shared across the network. This is because the cfg file will point the Thunder Select plug-in to the E drive for access to clips and the clip database. 3. Create a file called: ThunderMOS.cfg in the C:\ThunderCFG folder. 4. Open it with Notepad. 5. Add a line in the ThunderMOS.cfg with the following information: An arbitrary name for the Thunder that the journalists will easily recognize. This part is seen in the drop-down list of the Thunder Select plug-in on the iNEWS Workstation (shown below). It can be any name, such as: 5PM, Control Room A, Sports, and so forth. The MOS ID, such as MOSIDTHDR_A. This must be added to the MOS-Map story in the SYSTEM.MOS-MAP directory in iNEWS. The full UNC path to the Thunder database specified when you set up the MOS protocol. This part appears next to the drop-down list in the plug-in (shown below). Make sure it corresponds to the Thunder specified by the MOS ID.
Each of these values must be separated by a semi-colon and appear all on one line. For example: 5PM;MOSIDTHDR_A;\\ThxlxxA\E\5PM\5PM.pff The following graphic shows the Thunders arbitrary name and the full UNC path to the Thunder database as they might appear in the Thunder Select plug-in:
140
Creating the ThunderMOS.ini File
Due to the nature of the MOS configuration, you can only have one database per Thunder server. Although you can add multiple databases in the cfg file and the workstations will browse the databases correctly, the MOS metadata will not be properly transmitted between the iNEWS and Thunder servers. 6. If you: have a security database, type the correct path on a separate line below the Thunder lines. do not have a security database, delete the whole line starting with SecurityDB=
Your finished ThunderMOS.cfg file might look like this:
7. Save the ThunderMOS.cfg file.
Creating the ThunderMOS.ini File

If you intend to use the Thunder Select plug-in at your newsroom workstations, you must create the ThunderMOS.ini file on each Thunder device. The ThunderMOS.ini file identifies the location of the default database by pointing to the ThunderMOS.cfg file.
To create the ThunderMOS.ini file:
1. On the Thunders C drive, in the Thunder directory (C:\Thunder), create a file called ThunderMOS.ini. 2. Open it with Notepad. 3. Add a single line with the full UNC path to the ThunderMOS.cfg file, using the following format:
\\<machine name>\<directory>\<file name>
141
Your finished ThunderMOS.ini file might look like this:
4. Save the ThunderMOS.ini file.
142
5 Installing the Command Workstation

The Avid iNEWS Command user interface allows you to control multiple production devices from a single workstation running the client software. This chapter contains the following main sections: Checklist: Installing the Command Workstation Installing Avid Service Framework Installing Avid iNEWS Command on the Workstation Configuring Avid Workgroup Properties Setting up Device Channels Setting up Channel Groups
Checklist: Installing the Command Workstation

Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Install the core components of Avid Service Framework. Install Avid iNEWS Command. Configure Avid Workgroup Properties.
Installing Avid Service Framework on page 145 Installing Avid iNEWS Command on the Workstation on page 149 Configuring Avid Workgroup Properties on page 155
All settings in Command and Framework are case sensitive. Ensure that case matches in all configuration settings. Map the actual channels for the various production devices, such as Deko character generators or AirSpeed video servers, to names. Create channel groups. Setting up Device Channels on page 157
Setting up Channel Groups on page 160
144

145
n
146
147
148
Installing Avid iNEWS Command on the Workstation

This section provides the standard procedure for installing the Command software on a Windows-based computerWindows XP SP2, Windows Vista, or Windows Server 2003designated as a Command Workstation.
To install the software on a Command Workstation:
1. Insert the Command installation CD (or access the install program from the network). The InstallShield Wizard starts and displays the Welcome screen. 2. Click Next.
149
The License Agreement appears.
You can print the terms if you want to read them later or keep a copy for your records.
150
The Destination Folder dialog box opens.
151
5. Select Workstation Only and click Next. The Custom Setup dialog box appears with the default services selected for installation of client software. However, you can modify the selections to customize your installation. To learn more about a service, click any service listed and view a Feature Description provided along the right side of the dialog box.
152
153
6. Click Next.
7. When the Ready to Install the Program dialog box appears, click Install. 8. When the installation is complete, click Finish. After the installation, if you need to alter the system name from the default, which is command, see the procedure provided in Configuring a Second Command System on page 69.
154

If the Command Workstation is in a different subnet than the Command Servers, you must add the server names to the Lookup tab in Avid Workgroup Properties on the workstation.
To configure Avid Workgroup Properties:
3. Enter the name of the workgroup. 4. Click OK. The name you entered will appear in the Workgroup section of the Avid Workgroup Properties window. 5. Click the Add button under the Lookup services section (above the Apply button).
155
The Add Lookup Service dialog box will open on top of the Avid Workgroup Properties window, as shown:
6. Enter the full domain name of the server running the Lookup service, such as: cmdsvr1.avidbroadcast.com. 7. Leave the port setting as is. 8. Select the Expected check box. 9. Click OK. 10. Repeat steps 5 - 9 to add another server running the Lookup service. 11. Click OK on the Avid Workgroup Properties window. 12. Click Yes, when prompted to restart all services.
156
Setting up Device Channels

Avid iNEWS Command enables system administrators to map actual channels from a device, such as an Avid Deko or AirSpeed video server to a name of your choosing. This name can then be used to create channel groups or assign channel-specific actions to keys on a USB keypad at the Command Workstation. For more information on channel groups, see Setting up Channel Groups on page 160. Also, see Mapping Indices to Channel Names on page 220 and Programming the X-keys on page 221 for more information on assigning channel-specific actions to keypad keys.
To map device channels to names:
1. Open the Command Workstation application. 2. Select Tools > System Settings. The System Settings dialog box appears.
3. Expand Channel. 4. Select Device Channels.

157
5. Click Add.
6. Enter the channels name, which can be any alpha-numeric character(s), based on the following guidelines:
Channel Index Channel Name
Device Type
Description
n n
All channel names within a single device type must be unique. 0 1 1 2 Avid Deko devices begin channel designations at zero (0); however, the name of the first channel can be one.
Deko
Deko
Both channel names for a Deko must be numeric to match the channel selection available through the Deko Select plug-in inside of the iNEWS newsroom computer system. 2 3 A B AirSpeed video servers begin channel designations at one (1); however, the first channel is reserved for video ingest. So the first available channel for playout or browse purposes would be channel 2. All supported third-party video devices begin channel designations at one (1). The channel index values here must match the channel index values set for the Avid Video device service in Avid Service Configuration. Avid Thunder begins channel designations at one (1). The channel names must be in the following format: aPlay, bPlay, cPlay, 1, 2...8, or pgm (for program).
AirSpeed AirSpeed
VDCP VDCP
1 2
A B
Thunder Thunder
1 2
aPlay bPlay
Avid recommends against using numeric names for the Thunder to avoid confusion with channel names for any Avid Deko device.
158
Device Type
Channel Index
Channel Name
Description
Multi Stream Multi Stream Multi Stream Multi Stream Multi Stream Multi Stream
1 2 3 4 5 6
A B C D E F
AirSpeed Multi Stream video servers have six playout channels, which must be indexed from 1 to 6. The channel names can be anything, but a typical example is alphabetic names from A through F.
7. Select the name and type of the device from the lists. The device name is the host name for the device, such as deko3000. If it does not appear in the list, you must enter it.
For third-party video devices controled via VDCP, the device name must match the device name set for the Avid Video device service in Avid Service Configuration. 8. Select the channel index, using the Channel index spinbox. 9. Enter any notes you want, which can help identify the device should future alterations be necessary. 10. Click OK. 11. Repeat steps 5 through 10 for each device channel, as needed. 12. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
13. Enter the administrator password and click OK. Until this procedure is completed, device channels cannot be added to a channel group.
Before you can delete a device channel, you must first delete that channel from that channel from any channel groups or delete the channel group(s) that use the channel.
159
Setting up Channel Groups

A channel group is a cluster configured with one or more device channels composed from compatible video servers or character generators. Many channel groups can be created from the same pool of resources, and different groups can use the same resources to serve different operational needs.
Each channel group must contain a single type of device. For instance, a channel group called AS is a grouping of channels from two or more AirSpeed video servers, while a different channel group named CG is a grouping of channels on a Deko character generator. AirSpeed channels provide one of the best examples of the way in which channel groups provide control configurations; they do not guarantee media availability, which is the role of the AirSpeed studio configuration. For example, a station has two AirSpeed video servers, each with two channels that are numbered 2 and 3. (With AirSpeed video servers, the first channel is reserved for ingest.) Lets call the first AirSpeed AS1 and the second AS2. With channel groups on Command, the stations system administrator can set up numerous different channel groups and call them anything, such as:
Channel Names
Channel Group
Actual Device Channels
Channel Type
AS-Noon
A B C
AS1 - channel 2 AS1 - channel 3 AS2 - channel 2 AS1 - channel 2 AS1 - channel 3 AS2 - channel 2 AS2 - channel 3 AS1 - channel 2 AS2 - channel 2 AS1 - channel 3 AS2 - channel 3
Playout Playout Browse Playout Playout Playout Playout Playout Mirrored Playout Mirrored
AS-5PM
A B C D
AS-10PM
A C B D
160
The following graphic shows a more visual example of how multiple channel groups can be created from the same four AirSpeed video server channels.
The first group shows a single channel group configured to create four playback channels called A, B, C, and D. The next set shows two groups, representing control rooms, with two playback channels each. Alternatively, the groups can be created from any combination of channels and used to support simultaneous two-channel playout from two control rooms sharing the same resources. The last set shows four channel groups, each controlling a single channel. The following graphic shows a more visual example of how channel groups are used to mirror playout for redundancy.
The first group creates a two channel playout solution with both channels mirrored on a secondary video server for maximum reliability. Whenever a video clip is cued and played on either of the primary channels, the same clip is also cued and played on the corresponding mirror channels. The other two groups depict single channel solutions with redundancy.
161
All of these channel groups can exist at the same time, although they cannot necessarily all be on air simultaneously. Channels must be created before they can be assigned to channel groups. For more information on how to create channels, see Setting up Device Channels on page 157.
The first eight (8) characters of a channel groups name must be unique to match the eight-character device name in the iNEWS newsroom computer system. For instance, a channel group name in Command that is ASNoonMirrored will appear as ASNoonMi in iNEWS. System administrators can create channel groups via the System Settings dialog box.
To create channel groups:
1. Select Tools > System Settings. The System Settings dialog box appears. 2. Expand Channel. 3. Select Groups.
162
4. Click Add. The Add New Channel Group to Playlist dialog box opens.
5. Enter the name of the new channel group and any notes you want. Names of channel groups can be upper or lowercase and contain any alpha-numeric character. Avoid using spaces in, before, or after the name. If interfacing with the Avid iNEWS newsroom computer system, it is best to make the channel groups name less than eight characters. 6. Click Add to add a channel to the group.
If channels have not been created, they cannot be assigned to channel groups; therefore, the Add button will be disabled if no channels exist in the system. For more information on how to create channels, see Setting up Device Channels on page 157.
163
7. In the Channel Detail section, select the following:

Channel Detail Description
Channel Type
Select the appropriate channel type, based on: Standard - This is the channel type selected for playout. Browse - This is the channel type selected for changing In and Out points of pre-existing clips for preview or editing purposes only. This does not apply to playout operations. Hotswap - This is the channel type selected for emergency backup channel assignment.
Primary Mirrored Preview
Select the channel designated as the primary playout channel for the device. (Optional) If mirrored playout is to be used, select the devices channel designated for mirrored playout. (Optional) Select which device channel to use for displaying the headframe of the next media event in the playlist.
8. Repeat steps 6 and 7 as needed. You can use the Up and Down buttons to rearrange the order of channels in the group. 9. Click OK. This will close the Add New Channel Group to Playlist dialog box. The new channel group will appear in the System Settings dialog box. 10. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
11. Enter the administrator password and click OK.
c
164
Until the Apply or OK button is clicked and administrator password supplied, the channel group(s) are not created.
To edit a channel group:
1. Select Tools > System Settings. The System Settings dialog box appears.
2. Expand Channel. 3. Select Groups. 4. Select the channel group from the list on the right. 5. Click Edit.
165
The Edit Channel Group dialog box appears.
6. You can rename the channel group, add notes, rearrange the order of channels by using the Up and Down buttons, add or delete channels, or alter the channel details for each channel in the group. 7. After editing the channel group, click OK. 8. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
166
Until the Apply or OK button is clicked and administrator password supplied, the changes in the system settings are not saved.
To delete a channel group:
1. Select Tools > System Settings. The System Settings dialog box appears.
2. Expand Channel. 3. Select Groups. 4. Select the channel group from the list on the right. 5. Click Delete. 6. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK.
167
The system will prompt you for the administrator password.
Until the Apply or OK button is clicked and administrator password supplied, the channel group(s) are not deleted from the system settings.
168
6 Installing GDS and GIE for Chyron

The Avid iNEWS Command user interface lets you control third-party graphics devices via the Graphic device service (GDS). The Graphic Inventory Editor application is also provided with Avid iNEWS Command and is used to manage the inventory that Command needs to control any third-party graphics device that uses Intelligent Interface. This chapter provides instructions for installing both the device service and the editor application as well as configuration information needed to use these new tools when integrating Command with a Chyron graphics device. This chapter contains the following main sections: Checklist: Installing the GDS and GIE for Chyron Installing Avid Service Framework Installing Avid Graphic Device Service on the Chyron Installing the Avid Graphic Inventory Editor Configuring the Avid Graphic Device Service Configuring the Graphic Inventory Editor Configuring Command for Chyron Integration
Checklist: Installing the GDS and GIE for Chyron

Complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily access a linked topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Avid strongly recommends installing Avid Service Framework (ASF), the Graphic device service, and the Graphic Inventory Editor (GIE) on the Chyron itself. If controlling more than one device, then ASF, the device service, and GIE should be installed on each device.
Tasks
Refer to...
Install the core components of Avid Service Framework on the device. Install the Graphic device service on the device. Install the Graphic Inventory Editor on the device.
Installing Avid Service Framework on page 171 Installing Avid Graphic Device Service on the Chyron on page 175 Installing the Avid Graphic Inventory Editor on page 180
All settings in Command and Framework are case sensitive. Ensure that case matches in all configuration settings. Configure the Graphic device service. Configure the Graphic Inventory Editor. Configure the systems setting in Command and the device, using the Lyric software, for Chyron Integration. Configuring the Avid Graphic Device Service on page 181 Configuring the Graphic Inventory Editor on page 184 Configuring Command for Chyron Integration on page 192
170

171
4. Set the location to which Avid Service Framework will be installed and click Next.
172
The Workgroup Name dialog box opens.
173
174
Installing Avid Graphic Device Service on the Chyron

This section provides the standard procedure for installing the device service on a Chyron.
To install the software on a Command Workstation:
1. Insert the Command installation CD (or access the install program from the network). When the autorun program starts, select the Avid iNEWS Command button. The InstallShield Wizard starts and displays the Welcome screen. 2. Click Next.
175
The License Agreement appears.
You can print the terms if you want to read them later or keep a copy for your records.
176
The Destination Folder dialog box opens.
177
5. Select Workstation Only and click Next. The Custom Setup dialog box appears with the default services selected for installation of client software. However, for Chyron integration, you must modify the selections to customize your installation. 6. When the Custom Setup dialog box appears, deselect Avid iNEWS Command Workstation so that it is not installed. 7. Expand Avid Graphic Device Service and select Avid Graphic Device Service 01.
178
The Help button opens a dialog box that provides descriptions of the various install states available for a custom installation as indicated by the icons. The Space button opens a dialog box that provides information on whether the computers destination drive has enough disk space available to install the current selection of features. 8. Click Next.
179
9. When the Ready to Install the Program dialog box appears, click Install. 10. When the installation is complete, click Finish. You are now ready to install the Graphic Inventory Editor (GIE).
Installing the Avid Graphic Inventory Editor

After installing the Avid Graphic device service on the Chryron, you need to install and configure the GIE application.
The GIE application is not needed for Command integration with Avid Deko products or third-party graphics plug-ins. For users upgrading from ControlAir, the GIE application replaces data in the SYSTEM.RESOURCE queue in the Avid iNEWS newsroom computer system.
To install the Avid Graphic Inventory Editor:
1. Insert the Command installation CD (or access the install program from the network). The autorun installation program starts.
n
180
If the autorun does not begin, manually navigate to and run the AvidGraphicInventoryEditorSetup.exe install program from the CD.
Configuring the Avid Graphic Device Service
2. Click the Avid Graphic Inventory Editor button. 3. When the Welcome dialog box appears, click Next. 4. Read and accept the license agreement, and then click Next. 5. The default Destination folder is:
C:\Program Files\Avid\Graphic Inventory Editor\
You can change the location first or accept the default by clicking Next. 6. When the Ready to Install the Program dialog box appears, click Install. 7. When the installation is complete, click Finish. When installed, a separated icon for the GIE is made available on the desktop or in the Start menu.

After the installations are complete, for the integration to succeed, some additional configuration is required, using the Avid Service Configuration application of Avid Service Framework. For more information about th ASF application, see the Avid Service Framework Users Guide.
To configure the Graphic device service:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid Graphic Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Plug-in Chooser tab, select a plug-in only if you intend to use one provided by a third-party vender. By default this selection is set to none.
If you select a plug-in, click Apply and the let the service restart before proceeding.
181
5. On the Device Settings tab, enter a name for the device. This name will be used later when configuring the systems settings in Command.
6. Set the Channel count to the number of channels your device will use, which is usually 1 or 2. 7. On the Graphic Settings tab, for Device profile, select Chyron.
Options include Chyron and Vizrt because both Chyron and Vizrt profile files are installed with the Avid Graphic device service.
182
8. In the Connection Settings section, select Telnet and enter the machines name for Host. 9. The Graphic device service with Intelligent Interface protocol uses an XML file to keep inventory information. The easiest way to create it is to make a new text file and then rename it, changing the .txt tag to an .xml tag.
Avid recommends keeping your inventory XML file in a dedicated folder, such as C:\Command\Styles\templates.xml. 10. Set the Inventory path to the XML file that you just created. 11. Leave the Case-sensitive check box unselected, so that inventory items are not case sensitive.
For information about the Add unplayable playlist items... check box, see Configuring the LUCI Plug-in for Chyron ActiveX Support on page 195.
183
Configuring the Graphic Inventory Editor

The configuration of the Graphic Inventory Editor (GIE) involves multiple procedures that are covered in this section in a standard workflow. Configuration is done on the device, using the GIE application. The GIE application provides a multi-tabbed user interface for managing graphic inventory. Those tabs are: Templates and Styles. For more information about each tab in the GIE application, see the following sections: Working with Templates on page 188 and Working with Styles on page 190. The first step in the configuration process is to identify a path to your graphic inventory.
To specify the inventory path:
1. Click the Start button and select Programs > Avid > Avid Graphic Inventory Editor. 2. Click the Browse button. 3. In the Browse dialog box, navigate to the XML file specified earlier in the Avid Service Configuration application. 4. Click Open. After an inventory path is set, the New and Import buttons are enabled.
184
Importing Inventory
The following procedure only applies to sites converting from ControlAir to Command.
To import graphic inventory from SYSTEM.RESOURCE:
1. At an iNEWS Workstation, check for errors by turning on the monitor server on any iNEWS rundown and reading the messages sent back from that utility program; look for any problems with SYSTEM.RESOURCE. 2. Fix the problems before proceeding. 3. Export all stories in SYSTEM.RESOURCE as RTF files. This can be done in a single operation by selecting all of them in the queue and selecting File > Export. 4. Open the Graphic Inventory Editor. 5. Click the Templates tab. 6. Click the Import button.
185
7. Select the RTF file you just saved. 8. Click Open. An Import Templates dialog box appears.
9. Choose from among the devices provided; these are devices known to iNEWS. You can select multiple devices by pressing the Shift or Control keys down while making your selections. With Command, these individual devices will be converted to styleslower thirds and stills, for example. 10. Click Import. The inventory of templates will appear on the Templates tab in the Graphic Inventory Editor window.
186
The GIE application will allow the importation of templates that might share the same name of existing templates. If duplicates result from the importation or creation of templates, a Bad Names dialog box will appear to warn you that this issue must be resolved before the Graphics device service will work.
187
Working with Templates A template is a graphic with a pre-set look and fields (or layers) for replaceable data, such as text or video clips. Templates can be grouped together to form a style, such as a set of graphics designed for a specific show. This section provides additional details on the Templates tab in the Graphic Inventory Editor and how to manage templates in the Command inventory. You can create a new template, copy an existing template, or delete templates from the inventory. Although you can also add or remove templates from a style, you must do that on the Styles tab.
You can also import a list of templates from a pre-existing inventory in an Avid iNEWS newsroom computer system. For more information, see Importing Inventory on page 185.
188
To create a new template:
1. Click the New button at the bottom of the Templates tab. A new blank row will appear in the list of templates. 2. Type the name of the new template in the Name column. 3. Fill in the address information for the template. For Chyron integration, the address must match the address of the template on the Chyron. 4. Set the field count to a numerical value. This number must match the number of replaceable fields in the graphic. 5. Set the Play count to a numerical value. This number must match the number of triggers in the itemthat is the number of times an operator must press Play to get through all of the effects in the template. 6. Select the check box in the Persistent column if the template is one that will remain onscreen while other graphics are played and ejected. An example of a persistent template is a LIVE graphic that remains onscreen during a live broadcast while other location or name graphics are also aired as lower-thirds. 7. (Optional) Type a meaningful description of what the template is used for, such as: Lower-third Location with two fields. 8. Click Save.
To copy a template:
1. Select a template from the list of templates on the Templates tab. 2. Click Copy. 3. Click in the Name and Address fields to rename the copy. 4. (Optional) Modify the other fields associated with the copied template as needed. 5. Click Save.
To delete a template:
1. Select a template from the list of templates on the Templates tab. 2. Click Delete
If deleting a template that has already been assigned to a style, a warning will appear to notify you of the assignment and confirm the deletion. If confirmed, the template is deleted from the inventory as well as the style. However, to clarify, deleting a template in the GIE application does not remove the corresponding file from the Chyron graphics device.
189
Working with Styles A style sets the path to the actual graphics files on the Chyron; therefore, all templates need to be added to a style before they can be played. The style also needs to be set in iNEWS in SYSTEM.MAP. This section provides additional details on the Styles tab in the Graphic Inventory Editorshown belowand how to manage styles in the Command inventory. You can create a new style, copy or edit an existing style, and delete styles from the inventory.
To create a style:
1. Click the New button at the bottom of the Styles tab. A new blank row appears in the list of styles. 2. Type the name of the new style in the Name column. 3. Fill in the path information for the style. The path is the location on the actual graphics device where the styles are stored.
190
4. From the Templates list, select the template or templates you want to add to the new style.
You can use Ctrl+A, Shift+click, or Ctrl+click to make your selection. 5. Click Add. 6. (Optional) To remove a template from the style, select it from the New list and click Remove. 7. Click Save.
To copy a style:
1. Select a style from the list of styles on the Styles tab. 2. Click Copy. 3. Click in the Name field to rename the copy. 4. (Optional) Add or remove templates from the copied style as needed. 5. Click Save.
To delete a style:
1. Select a style from the list of styles on the Styles tab. 2. Click Delete.
Deleting a style in the GIE does not remove anything from the actual graphics device. It deletes the style from the inventory (located in the root directory on the PC) than Command uses to control the device. After you have created all of the styles, you need to define them in Command.
To add styles to a Command Workstation:
1. Select Tools > System Settings. 2. Select Playlist. 3. In the Graphics Style section, click the Add button to add styles to the list.
The default style must also be defined in SYSTEM.MAP in iNEWS. For instance: video ABCD cg cg 1 2 A ;
hyperx WAVD; microx STILLS;
191
To assign a style for a standalone playlist:
1. Right-click on the playlists channel group icon. 2. Select Edit properties for this channel group. The Playlist Channel Group Properties dialog box appears. 3. Enter the style. 4. Click OK. The following list contains further guidelines related to Chyron playback. Numeric only items do not need to be added to the GIE. Numeric only items will show up originally as unavailable in the Command playlist, even if the item exists on the Chyron graphics device. Lock the channel group; this will make Command check for availability and correct the status. In Command, page numbers are written when the playlist is locked. This is by design and is different from ControlAir, where the page numbers were written when the show was loaded. If a new graphic is created in the GIE, the new graphic will not show up until after the monitor server for the show is turned off and back on in iNEWS.
Configuring Command for Chyron Integration

Some additional configuration is required to enable Chyron integration with Command via the Graphic device servicepart of which is done at a Command Workstation, and part of which must be done on the Chyron device itself, using the Lyric software. Both are described in this section.
To configure System Settings in Command for Chyron Integration with GDS:
1. Start the Command Workstation application. 2. Select Tools > System Settings. The System Settings dialog box appears. 3. Expand Channel. 4. Select Device Channels.
192
5. Click Add. The Add Device Channel dialog box appears. a. Avid recommends using numbers for the name of the channel.
b. c. e. f.
The device name must match the device name set for the Graphic device service on the Device Settings tab in the Avid Service Configuration application. Set the device type to Other Graphics. Click OK. The Add Device Channel dialog box closes. Repeat these steps for each device channel as needed. For instance, if using two Chyron channels, add a second device channel and set the channel index to 1 for Chyron channel 2.
d. Set the channel index to zero (0) for Chyron channel 1.
6. Click Apply. 7. In The System Settings dialog box, select Groups.
193
8. Click Add. The Create New Channel Group dialog box appears. a. Set the name of the group to something eight characters or less with no spaces.
b. c.
Click Add for each channel in the group and select the appropriate device channel. If device type was set to Other Graphic (in a previous step), then an additional setting called the Graphic Page Range section is enabled in this dialog box. This lets you set the page range for the channel group. This needs to be a range of graphics that will be used solely for Command. Ensure that page ranges do not overlap between channel groups. A shows graphics will be loaded sequentially from the start of this page range when the channel group is locked. If graphics are added or updated, they will be loaded to the page at the end of the sequentially loaded pages.
194
Although the Minimum field permits zero (0), it should be set to a number greater than the largest page number used by your original graphics on the device; this is to ensure that your original graphics are not overwritten by the temporary graphics that contain fulfillment data for a show. The maximum value available is 99999998. After a show with graphics is loaded to Command, the page numbers assigned to graphics may be viewed in the playlist so long as the Graphic Page column is displayed. d. If device type was set to Other Graphic (in a previous step), then an additional setting is enabled in this dialog box. This lets you set the page range for the channel group.
To configure the Lyric software:
1. In the Lyric application, select Config > Intelligent Interface. 2. Select the Enable Telnet check box.
When switching from ControlAir to Command (from serial to telnet communications), be sure to change all macros on the Chyron so that the Intelligent Inteface configuration setting does not get altered inadvertently. Use the Clone Canvas feature to send preview output to a VGA monitor in the control room. See the Lyric Help system for further instructions.
Configuring the LUCI Plug-in for Chyron ActiveX Support

Avid iNEWS Command integration with Chyron supports both hand-entered items and newsroom playlist items added to an iNEWS rundown via the LUCI plug-in. For the plug-in to work, however, some minor configuration of the Graphic device service is necessary.
To configure the Graphic device service to support the LUCI plug-in:
1. Click the Start button, and then select All Programs > Avid > Service Framework > Avid Service Configuration. 2. On the Hosts tab, navigate to and select the Avid Graphic Device Service. 3. When prompted, enter the system administrator password and click OK. If you have not yet created one, leave the space blank and click OK. 4. On the Graphic Settings tab, at the bottom, select Add unplayable playlist to inventory.
195
Users need to select the Command profile in CAMIO so that Command correctly parses the plug-in data. The following limitations apply: Items can be numeric only, such as 10256. Items cannot be multi-triggered. This is set in the Graphic Inventory Editor application. Items cannot be persistent. This is set in the Graphic Inventory Editor application.
196
7 Integrating with Avid iNEWS

To ensure proper integration between Avid iNEWS Command and the iNEWS newsroom computer system, some configuration must be done at the iNEWS Workstation. Those configuring iNEWS must have system administrator access and a working knowledge of the newsroom computer systems administrative features. This chapter contains the following main sections: Editing the SYSTEM.MAP Story Editing the SYSTEM.MOS-MAP Story Setting up the Plug-ins in iNEWS Monitor Servers Queue Properties
Editing the SYSTEM.MAP Story

In Avid iNEWS the Map story, which is the first one in the SYSTEM.MAP queue, contains monitor server settings for each newsroom rundown. For more information on monitor servers, see Monitor Servers on page 207. Here is an example of settings for Command as they might appear in the Map story:
;NRCS.SHOWS.RUNDOWN USES MONITOR 292 nrcs.shows.rundown wnasvr cmdsvr1 CG video nrcs.shows cmdsvr2 Deko1 AB monitor D200
ca-composite 1 6pm;Deko Device Channels
A;AirSpeed Device Channels
The first line is a commentas indicated by the semicolonthat helps system administrators locate the appropriate settings within the Map story. The second line contains the following rundown information: Name of the rundown, such as nrcs.shows.rundown Directory that contains the rundown queue where event lists are created, such as
nrcs.shows.
Name of the Composite List queue. In none are configured, a hyphen is used, as shown. Name of the user group with access to monitor the rundown, such as monitors. Superusers are also permitted to start monitor servers. Monitor duration or quit time. A duration will automatically switch off the monitor server after the allotted time is achieved. For instance, D200 signifies the duration set to two hours, and no minutes. (This setting is not case sensitive.) A quit time, such as 2100, will automatically switch off the monitor server at the specified time, ensuring the integrity of the system. The quit time can be three to four digits, specifying an exact time on the 24-hour clock. When configured, this information appears in the iNEWS user interface at the bottom of the Monitor dialog box. See iNEWS Integration in the Avid iNEWS Command Users Guide.
Because monitor servers use large amounts of system resources, Avid recommends this setting be configured but, for best results, manually turn off monitor servers at the end of each show.
198
Editing the SYSTEM.MAP Story
The third line contains the following server information: Server type - wnasvr specifies a Command Server. Primary servers name, such as nrcs1, which is the computer running the Avid iNEWS Communication service. Backup servers name, such as nrcs2. Form name for the monitor server, such as ca-composite. A hyphen can be used as a placeholder.
Below the third line are device settings for channel groups in iNEWS Command. Each line associated with a device begins with: Type of device, such as CG or video. Name of devices channel group, such as Deko1 or AB. Channel group names are case sensitive. Alias for channel group. If none are used, hyphens can act as placeholders. For character generators, the next information in the line is the default channel, such as 1, which is assigned to an event when the user does not enter a channel in the story, followed by the style, such as 6pm. For Deko devices, this style must match the one configured on the Deko. For video devices, the next information in the line is the default channel, such as A, which is assigned to a clip when a user does not enter a channel in the story.
Any comments can be added to the end of the lines following a semicolon. The Map story can be edited like any other story in the newsroom computer system; however, access to it is typically limited to system administrators who already have access to SYSTEM.MAP directory in iNEWS.
To edit the Map story in iNEWS:
1. Log in to an iNEWS Workstation as a system administrator. 2. Navigate to the SYSTEM.MAP queue. 3. Double-click on the first story in the queue. 4. Modify the story as needed. 5. Click Save.
199
Editing the SYSTEM.MOS-MAP Story

The MOS-Map story, which is the first story in the SYSTEM.MOS-MAP queue, contains information vital to the integration of the plug-ins. Here is an example of settings for Command as they might appear in the Map story:
TABLE-START DeviceTable ;MOSID AMCPDeviceName ;============================== DEKO1 MOSIDTHDR_A CG1 Thunder
The first line is the header. The second and third lines are commentsas indicated by the semicolonsthat provides additional information or structure to the file to help system administrators. The fourth line contains the following device information, which is case sensitive: The MOS ID of a Deko character generator, such as DEKO1. The channel names in this channel group must match the Gateway ID configured on the DekoMOS Gateway. See Configuring the DekoMOS Gateway on page 104. The channel group for the Deko, such as CG1. This, too, must match the channels IDs assigned and configured on the DekoMOS Gateway.
You must enter a new line with MOS ID and channel group for each Deko channel group you configured in Avid iNEWS Command. The fifth line contains the following device information: The MOS ID of an Avid Thunder production server, such as MOSIDTHDR_A. This must match the MOS ID configured in the ThunderMOS.cfg file. See Creating the ThunderMOS.cfg File on page 140. The channel group for the Thunder, such as Thunder.
To ensure that the Avid Deko Select and Avid Thunder Select plug-ins use the correct device designation, you must set the MOS ID and channel groups in the MOS-Map story. The MOS-Map story can be edited like any other story in the newsroom computer system; however, access to it is typically limited to system administrators who already have access to SYSTEM.MOS-MAP directory in iNEWS.
200
Setting up the Plug-ins in iNEWS
To edit the SYSTEM.MOS-MAP story:
1. Log in to an iNEWS Workstation as a system administrator. 2. Navigate to the SYSTEM.MOS-MAP queue. 3. Double-click on the first story in the queue. 4. Modify the story as needed. 5. Click Save.

Using plug-ins, such as Deko Select or Thunder Select, with Avid iNEWS and iNEWS Command is optional. The plug-ins are installed on iNEWS Workstations and are accessed through the iNEWS client software. The appearance of the plug-in(s) in Avid iNEWS depends on whether one or more were installed. For instance, when both Deko Select and Thunder Select are installed, the title of the workspaceshown on the title baris Avid Graphics Select, and the plug-in workspace will appear in the iNEWS window with each plug-in on its own tab, as shown:
If only one plug-in is installed, the Tools menu option will be the name of that plug-in: Avid Deko Select or Avid Thunder Select. Also, only one tab will appear in the plug-in workspace.
If both Thunder and Deko plug-ins are being installed on an iNEWS Workstation, Avid recommends the Thunder service be installed first.
201
Installing and Configuring Avid Thunder Select

The Thunder Select plug-in allows iNEWS users to view thumbnails of video items on the Thunder and to drag-and-drop those items directly into an iNEWS story.
To install and configure Avid Thunder Select:
1. Ensure that the iNEWS client software is not running. 2. At the iNEWS Workstation, run the Avid Thunder Select installation program called ThunderSelectClient.exe. 3. Copy the ThunderMOS.ini file from the C:\Thunder directory on your Thunder device to your local C:\Thunder directory. If you do not have a ThunderMOS.ini file, create it in the C:\Thunder directory, open it, and enter the full UNC path to the the ThunderMOS.cfg file. For more information, see Creating the ThunderMOS.ini File on page 141. 4. Log in to iNEWS. 5. Select Tools > Plugins > Avid Thunder Select. If Avid Deko Select is also installed on the workstation, the menu option will be Tools > Plugins > Avid Graphics Select. The first time you open Avid Thunder Select, three errors will appear. 6. Click OK. The Setup Menu dialog box opens.
7. If it doesnt, click the Options button in the top right corner of the plug-in.
202
8. In the Setup Menu dialog box, select the interface, either iNEWS or ENPS, depending upon the newsroom computer system with which you are interfacing. If you are integrating with an iNEWS system, the fields will be grayed out and populated according to the information you supplied in the ThunderMOS.cfg file. If you are installing into an ENPS system, you must do the following: Type the Thunder name in the Avid Clip Server Computer Name (MosID) field, or browse to the Thunder by clicking on the ellipsis () button. Select File > Preferences > Protocol Setup, and browse to or enter the database that was set up on the Thunder. ThunderXL or LT system, use the dongle ID and password of the dongle on the Thunder server. ThunderMX, HD, or HY system, use the dongle ID and password that was printed on the options letter which shipped with your ThunderMX/HD/HY software CD.
9. Enter the Dongle ID and Dongle Password. If your Thunder system is a: -
The number of Thunder Select client licenses is controlled by the dongle on the server, and is determined by the number of client licenses that you purchased. 10. Click OK. The plug-in connects to the Thunder database, and you will see thumbnails of clips and stills. You can now drag and drop this media into an iNEWS or ENPS story or preview them by double-clicking.
Once this setup information has been entered, it should not need to be reconfigured. However, if the dongle is removed, or for any other reason the data has changed, a warning dialog appears and the setup information will need to be reconfigured. Enter the network path to the Thunder database and the Thunder license key.
203
11. Click the Options button again. The Options dialog box opens.
12. Set the options, including View Type, Event Properties, and Channel. The channel value selected here must match the channel name entered when the device channels were set up for the Thunder. For more information, see Setting up Device Channels on page 157. 13. Click Apply. For more information on Avid Thunder Select, see the Avid Thunder Select Installation and Configuration Guide.
Installing and Configuring Avid Deko Select

The Deko Select plug-in allows iNEWS users to create CG items directly at the iNEWS Workstation, including changing background graphics, editing replaceable text, and setting In and Out points.
To install and configure Avid Deko Select:
1. Ensure that the iNEWS client software is not running. 2. At the iNEWS Workstation, run the Deko Select installation program called DekoSelectClient.exe. 3. Log in to iNEWS.
204
4. Select Tools > Plugins > Avid Deko Select. If Thunder Select is also installed on the workstation, the menu option will be Tools > Plugins > Avid Graphics Select. The first time you open Avid Deko Select, an error message appears stating that Deko Select is not configured.
5. Click OK. The Configuration dialog box opens.
6. In the Configuration dialog box, on the Gateway Configuration tab, enter the host name or IP address for the computer that is running the DekoMOS Gateway software. 7. Click OK. The initial Configuration dialog box will close. 8. Click the Configure button on the toolbar of Deko Select. The Configuration dialog box opens with three tabs. 9. Click the User Preferences tab, if its not already selected.
205
10. Select options to indicate what you want Deko Select to display. 11. Select the Preview Style you want to use as your default, then click the Set As Default button. 12. Click OK. Configuring Gateway Settings from an ini File After you have configured the Gateway Settings on the first workstation, you can install them on additional workstations from an ini file. Gateway settings, as configured via the plug-ins Configuration dialog box, are stored in a file called DekoMOS.ini in C:\WinNT\System32 or C\WINDOWS\system32. After installing and configuring Gateway settings on one workstation, you can copy this DekoMos.ini file onto other computers rather than actually repeating the configuration procedure.
206
Monitor Servers
Monitor Servers
Monitor server is a utility programrunning on the iNEWS newsroom computer systemthat checks a shows event requests for errors, creates composite and event lists, and sends newsroom playlists to Avid iNEWS Command. A monitor server must be assigned device and mailbox numberstypically, these numbers are the same, which makes the configuration easier to remember. A device number is chosen for monitor server so iNEWS recognizes the server (utility) program as a valid device. The device number must be entered in the newsroom computer systems configuration file. The mailbox number must be assigned to both the shows monitor server and its rundown queue.
A mailbox is an activation mechanism for a server (utility) program, so if a queue has a mailbox number matching a server program, then that server is the one activated whenever something happens to the queue. The mailbox enables iNEWS to notify the monitor server of changes made to a rundown queuethe one sharing the same mailbox numberwhile that show is monitored.When on, monitor server checks its assigned rundown for machine control events, and builds playlists. The monitor server then sends updates to that rundowns newsroom playlist in Command, and will continue to do so as long as the monitor is running and the newsroom computer system retains the lock on the playlist. It also updates composite and event lists, if necessary.The monitor server is turned on when a user at an iNEWS Workstation turns it on. The monitor server loads data to the iNEWS Command system or the MOS Gateway system when a user instructs it to do so from an iNEWS Workstation.
Creating a Monitor Server for Each Show

The procedures in this section assumes the user has a working knowledge of administration tasks associated with an Avid iNEWS system and that rundown queues for the shows being monitored already exist in iNEWS. If not, create them before continuing. For more information on how to create queues or further details regarding steps in this section, see the administration documentation that accompanied your iNEWS system.
To create and configure a monitor server:
1. Check the configuration file (/site/config) and choose the next available device number for the monitor server, from the range of 3-digit numbers reserved for use by your systems server programs, such as 201 to 300. Valid standard mailbox numbers are 1 through 4096.
207
2. Choose an available mailbox number. For simplicity, this should be the same 3-digit device number. Do the following: a. Use the list console command to ensure no other device is using the mailbox number you have chosen. For instance, to check mailbox 266, type:
list mailbox=266 c
Information similar to the following appears:

DEV DEVICE_TYPE COMPUTER CCU PRINTER SPEED OPTIONS DEVNAME
For other list command options for determining mailbox assignments of queues and servers, see Using the list Command to View Assigned Mailboxes on page 211. b. If you see the device configuration header (as shown in step 2a) with no information below it, then no device has that mailbox and you can use that number. However, if configuration information for a device appears below the header, that device has the same mailbox as the one you chose. Therefore, choose another mailbox number and repeat step 2a.
If the mailbox number is already being used, and you must choose another, you may want to try another device number for the monitor server as well. Typically, mailbox numbers match server program device numbers, although this is not required. However, the mailbox number you select must be assigned to the queue monitored by the server program. Multiple queues can share the same mailbox number, but care must be take to avoid conflicts. For more information, see Using the list Command to View Assigned Mailboxes on page 211. 3. Changing the configuration file requires the use of ed, the line editor. Add the monitor server to the /site/config file on each iNEWS Serversuch as server A and server B in a dual server system by doing the following:
Always back up the /site/config file before making any changes. a. b. At the console, select all iNEWS Servers. Use the ed command to open and edit the configuration file, by typing:
ed /site/config 1259
After you press Enter, the editor responds by displaying a number, as shown, indicating the file size expressed as the number of characters, including spaces and returns. For more information on the line editor and Avid iNEWS configuration files, see the Avid iNEWS Setup and Configuration Manual.
208
Monitor Servers
c.
Add the monitor servers device number to the servers line in the host definition for the iNEWS Server that will run the monitor server program. For instance:
servers 261 263 265 267
The device number 267 is added to the servers line in this example.
Divide your server programs evenly among your iNEWS Servers to distribute the load they put on your system. For instance, put odd numbered programs on server A and even numbered ones on server B. Additionally, ensure that you also add the configuration line for the monitor server to alternate host definitions for your iNEWS Servers. This ensures it can run on the surviving computer should one of your iNEWS Servers stop functioning. Do not confuse the configuration line, which starts with server, and the servers line mentioned in 3c on page 208, which lists device numbers. d. Add a configuration line for the monitor server in the host definition belonging to the iNEWS Server that will run the server program. This line begins with the word server and contains the mailbox number assigned to the monitor server. The format for server programs configuration lines are:
server <device#> <type> <mailbox> <device name>
Parameter
device #
Description
The device number assigned to the server program. This 3-digit number must also be listed in the servers line in a host definition. The type of server program is monitor. The mailbox the server program uses. Valid standard mailbox numbers are 1 through 4096. This number typically matches the server programs device number. Monitor servers do not use a device name; enter a hyphen (-).
type mailbox
device name
Comments appearing after the semicolons (;) are optional. The following are sample configuration lines for monitor server programs:
server server server server 264 265 266 267 monitor monitor monitor monitor 264 265 266 267 - ;monitor server - ;monitor server - ;monitor server - ;monitor server
209
e.
When you finish making changes to the configuration file, save your changes by typing:
w
Do not use an uppercase (W) in step 3e. f. When you press enter, a number will appear, such as 1279, indicating the file size. You can then exit the line editor by typing:
q
4. (Optional) Test your configuration changes. After editing the configuration file (/site/config), it should be backed up. 5. Reconfigure the system. When adding monitor server programs, you do not need to stop anything to reconfigure the system.
Unlike other utility programs, it is not necessary to start a monitor server when you add it to the configuration file. It starts when someone uses the monitor on or monitor load command for the rundown queue to which you have assigned the monitor server. See the Command Users Guide for more information on using monitor servers. Mailboxes are assigned to queues in the same way other database traits areusing the Queue Properties dialog box. For more information, see Queue Properties on page 212. 6. After you choose the monitor servers mailbox number and verify that it is not used by another device, you must also assign it to the shows rundown queue, being monitored by the monitor server. For instance, if the monitor servers mailbox number is 267 and it will monitor the SHOWS.6PM.RUNDOWN queue, then that number must be assigned to that queue. For more information on assigning mailboxes to queues, see the Avid iNEWS Setup and Configuration Manual.
210
Monitor Servers
Using the list Command to View Assigned Mailboxes

Variations of the list command can be used at the console to determine mailbox assignments for specific devices, queues, and so forth. Since multiple queues can share the same mailbox, you can list all queues and directories in the database that are using a certain mailbox, such as 267, by typing: list mailbox=267 d
To find out which monitor server mailboxes are assigned:
Type: list c monitor The system displays configuration information for your systems monitor servers, similar to the following:
DEV DEVICE_TYPE COMPUTER CCU PRINTER SPEED OPTIONS DEVNAME S264 monitor S265 monitor S266 monitor S267 monitor A B A B N264 N265 N266 N267
NRCS-A$
The mailbox number assigned to each monitor server appears in the PRINTER column and begins with the letter, N.
To see if any servers are assigned a certain mailbox number:
t t
Use the following format: list mailbox=<mailbox number> c
To check whether mailbox 267 is assigned to a server program:
Type: list mailbox=267 c
Two rundowns queues can share the same mailbox, but they should never be monitored simultaneously.
If two rundowns share the same mailbox number, ensure that both their monitor servers do not run simultaneously; otherwise, results could be unpredictable.
211
Queue Properties
To ensure seamless interaction between Avid iNEWS and iNEWS Command, the queue properties for newsroom rundowns must be configured properly. This section provides a few things to verify in the Queue Properties dialog box of Avid iNEWS. For more information on the Queue Properties dialog box, see Chapter 5 in the Avid iNEWS Setup and Configuration Manual.
To view the Queue Properties dialog box:
1. Log in to an iNEWS Workstation. 2. Navigate to a rundown associated with iNEWS Command. 3. Right-click on that rundown in Directory panel. 4. Select Properties. The Queue Properties dialog box has multiple tabs; however, the ones of greater importance in regard to interaction with Command are: Forms, Maintain, and User Interface.
On the Forms tab, ensure that the appropriate story form is chosen. The selected form must contain fields for all necessary media events. The queue form determines the look of the queue. The story form chosen must contain an item-channel field. The story form determines how an event request is displayed when you double-click it. The forms will only appear in the drop-down lists if they exist in the database. For information about how to create your own
212
Queue Properties
forms or modify existing forms, and about database traits, see Chapters 5 and 8 of the Avid iNEWS Setup and Configuration Manual. Users should log off and sign back on to view the new queue/story form settings. On the Maintain tab, ensure the standard mailbox number is set correctly. Rundowns that load playlists to Command through monitor servers must be set to use a standard mailbox number.
The Mailbox section does not apply to the e-mail feature of the iNEWS newsroom computer system. These mailboxes are signal carriers by which utility programs, called servers, are notified to perform a pre-defined task. The mailbox number assigned to the queue must match the device number of the server monitoring it, as defined in the iNEWS Configuration file (/site/config). Valid mailbox numbers are one through 4096. For more information, see Using the list Command to View Assigned Mailboxes on page 211.
213
On the User Interface tab, ensure that the Refresh option is selected to enable automatic updates from Command.
214
8 Configuring Playout Control

Playout control through Avid iNEWS Command varies from site to site depending on workflow. Some television stations might want to control playout through the softwares graphical user interface, while others choose to use USB or GPI keypads. This chapter contains the following main sections: Controling Playout via the User Interface Disabling a Command Workstations Keyboard Checklist: Setting up an X-keys USB Keypad Installing an X-keys USB Keypad Mapping Indices to Channel Names Programming the X-keys Checklist: Setting up the GPI Panel Configuring the GPI Card Restarting the GPI Device Service Confirming Successful Setup of a GPI Panel Mapping Events to Actions for a GPI Panel Enabling the GPI Panel Checklist: Setting up the Maney Panel Configuring the PCI Card for a Maney Panel Restarting the Maney Panel Device Service Confirming Successful Setup of a Maney Panel Mapping Events to Actions for a Maney Panel
Controling Playout via the User Interface

Playout control from a Command Workstation is accomplished through the use of the tabbed workspace known as the Playlist Viewer. While some functionality is described in this section, additional information such as customization options is available in Chapter 4 of the Avid iNEWS Command Users Guide.
216
Controling Playout via the User Interface
Command uses various icons, as well as color, to indicate the status of machine control events (items) in the playlist. Some of which are shown in the following closeup graphic:
Playout of this event is done. This event is playing now. This event is cued. This event is unavailable.
Cursor location can appear solid or as an outline; varies by field. Icon representing a Follow-On Playout event.
There is no special installation or configuration needed to use the softwares graphic user interface to control playout of media from a Command Workstation with a standard keyboard and mouse. Users can cue, play, pause or stop the playout of media from a Command Workstation, using the mouse to click control buttons on the Playlist toolbar or by using keys on the numeric keypad.
To control playout, using the numeric keypad on a keyboard:
1. Select the event in the playlist. 2. Do one of the following: t t t t Press the Decimal key (.) to cue the media. Press Enter to play the media. Press the Plus key (+) to pause the media. Press zero (0) to stop playing the media.
Playout options are also available by right-clicking on the event and selecting the options from the Playout submenu. Users can also set playout of an item in a playlist to automatically occur immediately following the completion of the previous item. This functionality is called follow-on playout and is indicated by an icon in the playlist that looks like a bent blue arrow. For more information, see the Avid iNEWS Command Users Guide.
217
Disabling a Command Workstations Keyboard

Some sites use alternative devices to control playout from Command, such as a GPI device or an X-keys USB keypad, and therefore do not want the computer keyboard at the workstation enabled.
To enable or disable the keyboard:
1. Select Tools > Options.
2. In Category, select Keyboard. 3. Do one of the following: t t Select Enable keyboard. Deselect Enable keyboard.
4. Click Apply. 5. Click OK.
If the keyboard is disabled, the numeric keypad cannot be used to control playout from the Command Workstation. Disabling the keyboard does not affect the use of the keyboard for software on the workstation PC unrelated to the Command client software.
218
Checklist: Setting up an X-keys USB Keypad
Checklist: Setting up an X-keys USB Keypad

Avid iNEWS Command interfaces with the X-keys USB keypad for playout control. An X-keys USB keypad connects to the USB port the Command Workstation and offers up to twenty user-reprogrammable keys for one-button access to playout functionality.
X-keys is third-party hardware. Avid only supports Command on the twenty-button X-keys keypad, which is programmable via Command. However, other X-keys hardware can be used if programmed through the X-keys macro software. One risk of using macro software, though, is that it is dependent on the Command Workstation application having the focus. For more information on X-keys USB keypads, see that manufacturers documentation on www.xkeys.com. Setting up the keypad to control playout through Command requires the completion of the following tasks:
Tasks
Refer to...
(Optional) Disable the keyboard at the Command Disabling a Command Workstations Keyboard Workstation. on page 218 Install the keypad on the Command Workstation. Installing an X-keys USB Keypad on page 220 Map Indices to Channel Names. Program the keypad. Mapping Indices to Channel Names on page 220 Programming the X-keys on page 221
219
Installing an X-keys USB Keypad

To install an X-keys USB keypad:
Plug in the keypad to a USB port on your Command Workstation.
Mapping Indices to Channel Names

Channel indices are a configuration feature used to map an index integer (1-16) to a channel name, which can be alpha or numeric, to enable assignment of channel-specific actions to certain keys on a keypad. This pre-configuration should be done before assigning the channel-specific actions to any keys.
To map an index to a channel name:
1. Log in to a Command Workstation. 2. Select Tools > System Settings. The System Settings dialog box appears.
220
Programming the X-keys
3. Expand Channel. 4. Select Indices. 5. Enter the channels name in the Name column next to the appropriate index.
Avid recommends that if a channel name must be numeric, such as is the case whenever the ActiveX plug-in Avid Deko Select is used, assign it to the same Index number to avoid confusion. 6. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.

The following procedure should be conducted at the Command Workstation to which the X-keys USB keypad is installed.
To program the X-keys from the Command Workstation:
1. Select Tools > Options. 2. In Category, expand Actions and select X-keys.
221
3. Select Enable X-keys. 4. Set the de-bounce period. Designed to avoid inadvertent repetition, this is the span of time (in milliseconds) during which the system should ignore duplicated signals.
n n
If you find that you are having problems with double-hits when you press a key, increase the de-bounce period. 5. Click on a gray box that represents (or corresponds to) the key on the keypad. Some sites might use key caps that cover 2 or 4 buttons on the keypad, turning a set of buttons into a single key. If that is the case, select the left box to set the 2-button key. For 4-button keys, select the upper left box. 6. Assign an action to the key by selecting it from the list of those available in the Choose Action dialog box. The most commonly used actions will appear open for your selection already. The Playlist > Channel Group actions refer to channel group commands, such as lock, unlock, and assign channel. The Playlist > Selection actions refer to selected items on the playlist, such as play selection, cue selection, stop selection, and move up/down.
222
The Control actions refer to channel-specific actions that correspond to a particular index as configured when mapping indices to channel names. An example of this would be for a key to initiate a play command on a single channel. Assigning the channel-specific actions affects only the keypad attached to the workstation at which the assignments are programmed.
Channel 01 actually refers to Index value 01. 7. Click OK. 8. Repeat steps 5-7 as needed. 9. Click Apply. 10. Click OK. The following graphic shows a closeup of the first row of keys after they were assigned to the four playout control options of play, cue, pause, and stop.
223
Checklist: Setting up the GPI Panel

A GPI panel is alternative playback control device that can be used to control playout through Command. GPI panels connect to a GPI card installed in the Command Server. A GPI panel allows a user to select up to four channels, with each channel having its own set of Control buttons for play, cue, pause, and stop functionality. Configuring the system to work with a GPI panel requires defining certain parameters through the Avid Service Configuration application, the Avid Workgroup Properties application, and the system settings in Command itself. Before configuration can begin, you should verify installation of all necessary applications and components. To ensure a successful setup, complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily link to a topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Verify installation of Avid Service Framework, which includes the Avid Service Configuration and Workgroup Properties applications. Verify installation of the GPI device service on the Command Server.
Installing Avid Service Framework on page 145
Installing Avid iNEWS Command on the Server on page 40
Installation of the device service occurs during the installation of the Command Server software. Installing the GPI card on the Command Server. The installation instructions that came with your GPI card. See the latest Command ReadMe documentation for more information on which cards are supported. Configuring the GPI Card on page 225 Restarting the GPI Device Service on page 228 Confirming Successful Setup of a GPI Panel on page 229 Mapping Indices to Channel Names on page 220 Mapping Events to Actions for a GPI Panel on page 230 Enabling the GPI Panel on page 236

224
Configure the GPI card. Restart the GPI device service. Confirm proper setup of the GPI. Map Indices to Channel Names. Map GPI events to actions. Enable the GPI panel for playlist control.
Configuring the GPI Card

Configuring the GPI card is done using the Avid Service Configuration application. The procedure is covered in this section.
To define the GPI cards board settings:
1. Start Avid Service Configuration by clicking the Start button and selecting All Programs > Avid > Service Framework > Avid Service Configuration.
2. Navigate to and select the Avid GPI Device Service. 3. By default the Device Name is set to the host name of the computer on which the GPI Device service is installed plus a period and the numeral zero. So, for example, the default device name for the system in the previous graphic would be NRCS1.0. The default name can be changed, if necessary.
For redundant systems, the name of the device must match on all computers running the GPI Device service. For instance, if you have two servers with the GPI Device service installed, with one named NRCS1 and the second named NRCS2, by default, the device names would be NRCS1.0 and NRCS2.0. You would have to alter the device names to match to ensure redundancy.
225
4. Select the Board Typethe GPI card installed on the PC running the Avid GPI Device Service. 5. Set the Board Number to the number of GPI cards installed. Options include 0-4, with the zero (0) representing the first card and four (4) representing the fifth card, which is the maximum. Command supports only one board per server. 6. Click Apply. 7. Click Add Panel. The Add Panel dialog box appears.
8. Click OK. The new panel will appear as a tab. 9. (Optional) Rename the panel in the Panel Name textbox. 10. Accept the default Debounce Time. This input threshold setting in milliseconds is 200 by default, which means the system will ignore any signal shorter than 200 milliseconds. 11. Click Apply. 12. Set First Input Pin. Options include 0-15, with the zero (0) representing the first pin and fifteen (15) representing the sixteenth pin, which is the maximum. This numerical value is card dependent. 13. Click Add Event. The Add New Event dialog box appears.
226
14. Select the type of event. Options include:

Trigger GPI input. Used for normal, GPI button type; push the GPI button for it to trigger play, pause, cue, and so forth. The GPI signal occurs only while the button is held down, usually no more than a fraction of a second. GPI input. Extended on/off. While on, the voltage (usually around 5 volts) will remain high. This is useful for channel-specific actions like play (active) and stop (inactive), and can also be used for tally tally restriction/reflection. The signal will stay active as long as the switch allows the voltage signal to continue. GPI output. Quick on/off. Seldom used with Command, this is designed more for a toggle switch-type of workflow and not a button-type of workflow. It will trigger an action each time the switch changes positionup to down or down to up.
Level
Toggle
15. Enter a name for the event. 16. Click OK. 17. Repeat steps 14 through 17 to continue pin assignment.
For redundant systems, to ensure identical functionality, make certain that the device settingsall input pins and event names and typesare the same for every GPI Device service installed. 18. Click Apply.
227
19. After modifying the GPI Device service system settings, restart the service.
Restarting the GPI Device Service

After configuring the GPI card, you must restart the device service.
To restart the Avid GPI Device Service:
1. Click Start and select All Programs > Avid > Service Framework > Avid Workgroup Properties. 2. On the Services tab, click Advanced. 3. Select Avid GPI Device Service. 4. Click Restart.
Avid also recommends restarting the client software at the Command Workstation.
228
Confirming Successful Setup of a GPI Panel
Confirming Successful Setup of a GPI Panel

This section provides a way to verify that the installation and configuration of a GPI panel was successful.
To verify successful setup of a GPI panel:
1. At the Command Workstation to which a GPI panel is connected, click the Start button and select Programs > Avid > Service Framework > Avid Health Monitor. On the Hosts tab, services are listed by computer and device. The Processes tab lists by services. 2. Navigate to the Avid GPI Device Service and select it.
229
3. Expand the Information section. The Device Name shows the hostname.board number. If the Board Status is connected, the service is installed in the right location and the board number was set correctly. The Last Input Value will typically show zero (0) if theres no button pressed on the panel. The Last Event should be empty, and Event count should be zero (0). 4. Press any of the GPI panel buttons. Health Monitor will refresh after a short delay.
The time it takes Health Monitor to report a GPI event is slower than the response of Command to that GPI input. The Information section will appear similar to the following example:
5. Press a number of buttons to make sure they all work.
If the switcher is wired to the GPI panel, test that, too.
Mapping Events to Actions for a GPI Panel

Mapping events to playout actions is done at a Command Workstation in the System Settings dialog box. In most cases, GPI events are mapped directly to channel-specific actions because these actions are communicated directly to the Playlist Controller, bypassing the user interface; the procedure for this type of mapping is provided below.
For more information on mapping GPI events for selection-based playout, see page 233.
To map GPI events to channel-specific actions:
1. Log in to a Command Workstation. 2. Select Tools > System Settings.
230
The System Settings dialog box appears.
3. Select GPI. 4. Expand the panels to view each panels events. 5. Double-click on an event to map it to an action.
231
The Choose Action dialog box appears with the GPI > Control options expanded by default.
6. Expand the action, such as Play, and select the index value that corresponds to the appropriate channel.
n n n
Channel 01 actually refers to Index value 01. Here are some of the most commonly used commands for channel-specific playout: Play a specific channel - Choose GPI > Control > Play > index value Stop a specific channel - Choose GPI > Control > Stop > index value
If doing level-based playback, set the Level:Active to Play a specific channel and the Level:Inactive to stop that same channel. Cue a specific channel - Choose GPI > Control > Cue > index value
The Cue channel action only recues the item that is playing. Cueing a different item in the playlist must be done manuallyvia mouse, keyboard, or X-keysor a GPI button must be mapped and enabled for selection-based playout. 7. Click OK. 8. Repeat steps 5 through 7 as needed.
232
9. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
10. Enter the administrator password and click OK. If there is no administrator password, leave the field blank and click OK. 11. Confirm functionality by playing items in a playlist.
To map GPI events for selection-based playout:
1. Log in to a Command Workstation. 2. Select Tools > System Settings. 3. Select GPI. 4. Expand the panels to view each panels events. 5. Double-click on an event to map it to an action.
233
The Choose Action dialog box appears with the GPI > Control options expanded by default.
6. Navigate to the Playlist action and expand it.
234
Here are some of the most commonly used commands for selection-based playout: Play selection - Choose Playlist > Control > Play > Selection Stop selection - Choose Playlist > Control > Stop > Selection Cue selection - Choose Playlist > Control > Cue > Selection
If you program the GPI panel for these selection-based actions, you must enable the GPI panel at the workstation. 7. Click OK. 8. Repeat steps 5 through 7 as needed. 9. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
235
Enabling the GPI Panel

The GPI panel must be enabled to control a playlist if used for non-channel-specific, selection-based actions that go through the Command user interface.
This procedure does not apply to GPI panels (or Maney panels) with events mapped only to actions chosen in GPI > Controlsuch as Cue, Pause, Play, or Stopbecause those are sent directly to the Playlist Controller and do not go through the user interface. A user can enable a panel at any Command Workstation.
To enable a GPI panel to control a playlist:
1. At the Command Workstation, select Tools > Options. 2. In Category, expand Actions and select GPI.
3. Select a GPI panel from the list. 4. Click Apply. 5. Click OK.
236
Configuring GPI Out
System administrators must configure system settings to provide a list of GPI panels in the Options dialog box. You can confirm mapping by playing items from the GPI panel; test all of the commands.
Configuring GPI Out

Command supports GPI Out, meaning a GPI pulse can be sent from the system. This feature does require additional configuration, but after the GPI device service is configured, GPI events can be selected in a new GPI Out column of a playlist, or the user can enter them in the story title (slug) or an iNEWS or ENPS rundown.
To configure the GPI device service for GPI Out:
1. Click the Start button, and then select All Programs>Service Framework>Avid Service Configuration. 2. On the Hosts tab, navigate to and select GPI Device Service. 3. Click Add Panel. The Add Panel dialog box appears. 4. Select Output Panel and click OK. 5. In the Panel Name field, enter a name for the panel. 6. On the new panels tab, enter the Pulse Width and Output Early values. You will need to test this with your automation system to determine the Output Early value that will ensure a smooth transition. Lab testing revealed a maximum two-frame variation between when the pulse was sent and the Done status received from an AirSpeed (classic) device. 7. Set the first output pin. 8. Click Add Event. The Add Event dialog box appears. 9. Enter the events name and click OK. This is the name that will appear in the Command playlist (and needs to be entered by iNEWS or ENPS users), so it should be something that is easy to understand and type. 10. After you finish modifying the configuration, click Apply.
Configuring for Newswheel Workflow

Newswheel is the name for an automation workflow that, if used with Command, does require some new or altered configuration.
237
To configure a Command system for a Newswheel workflow:
1. In Command, configure the GPI Out event names so that each even name is something that implies its purpose, such as commercial, weather, live cut-in, and so forth. Also, configure the switcher so that each GPI Out pulse triggers its intended source. 2. Create a Command channel group with a single video device channel, known as the Newswheel playout channel. 3. In System Settings for Playlist, select New items are follow-on, so that when a playlist is loaded, its items are set to follow-on by default. 4. In System Settings for GPI, set a channel specific Play command for the Newswheel playout channel. 5. Configure the master control automation system to send a GPI Out signal, and configure the switcher to route this to the Command GPI channel specific Play command for the Newswheel playout channel. The following list contains some additional information related to the Newswheel workflow: Manage the Newswheel content via an iNEWS or ENPS rundown, and load the playlist to Command. Set the GPI Out to be triggered when a break is reached: For iNEWS, add the text GPIO:<event> to the story slug and then change it to a break. For ENPS, add the text GPIO:<event> to the story slug and do an object autocreate, so that it has a (bogus) video ID. When the story arrives in the Command playlist, Command coverts it to a break.
Set the automation system to send a GPI Out signal when the commercial segment has completed; this will trigger the first item after the break to play and the Newswheel to continue. To use GPI Out with a standalone playlist, add the GPIO column to the playlist viewvia the Tools > Options menu. In the Options dialog box, select the Playlist Viewer category and then Columns. Select the appropriate GPIO event from the dropdown list.
Checklist: Setting up the Maney Panel

A Maney panel is an alternative playback control device that can be used to control playout through Command. Maney panels, such as the 4-channel one shown below, is connected to a Measurement Computing PCI card via a very large, DB-37 connector.
238
Checklist: Setting up the Maney Panel
The Maney panel uses a 32-pin connector not supplied by Avid. See http://maney-logic.com for more information about this device and its wiring requirements. Configuring the system to work with a Maney panel requires defining certain parameters through the Avid Service Configuration application, the Avid Workgroup Properties application, and the system settings in Command itself. Before configuration can begin, you should verify installation of all necessary applications and components. To ensure a successful setup, complete the following tasks in the order that they are listed. If you are viewing this checklist online, you can easily link to a topic that provides procedural details for the task. Return to this main checklist after you have completed each task.
Tasks
Refer to...
Verify installation of Avid Service Framework, which includes the Avid Service Configuration and Workgroup Properties applications. Verify installation of the Maney Panel device service.
Installing Avid Service Framework on page 145
Installing Avid iNEWS Command on the Server on page 40
Installation of the device service occurs during the installation of the Command Server software. Instead of a GPI card, the Maney panel connects to a Measurement Computing PCI card, which should be installed on the same computer that is running the Maney Panel device service. Configure the PCI card. Configuring the PCI Card for a Maney Panel on page 241
239
Tasks
Refer to...
Restart the Maney panel device service. Confirm proper setup of the Maney panel. Map Indices to Channel Names. Map Maney panel events to actions.
Restarting the Maney Panel Device Service on page 244 Confirming Successful Setup of a Maney Panel on page 244 Mapping Indices to Channel Names on page 220 Mapping Events to Actions for a Maney Panel on page 247
240
Configuring the PCI Card for a Maney Panel

Configuring the Measurement Computing PCI card is done using a couple of applications, one of which is the Avid Service Configuration application. The procedure is covered in this section.
The PCI card is not the same as the GPI cards listed in the specifications for Avid iNEWS Command. They are not interchangeable.
To define the PCI cards board settings:
1. Determine the PCI cards board number by clicking the Start button and selecting All Programs > Measurement Computing > Instacal.
In this example, the board number is 1. You will need to know this for the next step in the configuration process. Click the X button to close the Instacal program. 2. Start Avid Service Configuration by clicking the Start button and selecting All Programs > Avid > Service Framework > Avid Service Configuration. 3. Navigate to and select the Avid Maney Panel Device Service. 4. Set the Board Number to the number obtained from Instacal. Command supports only one board per server. 5. Set Panel Type to either 2- or 4-channel. (The following example in step 7 shows a 4-channel configuration.)
With either type of Maney panel, you can add multiple panels on one Measurement Computing PCI card. A single card can handle 12 channels, either with six 2-channel panels or three 4-channel panels. You cannot mix panel types to equal the 12 channels, such as three 2-channel panels and one 4-channel panel.
241
6. Click Add Panel. The Add Panel dialog box appears.
Any active panels will appear and can be selected from the drop-down list. 7. Click OK. The new panel will appear as a tab.
8. (Optional) Rename the panel in the Panel Name textbox. 9. Set the Input, if needed. For a 2-channel Maney panel, options include A LOW, A HIGH, B LOW, B HIGH, C LOW, and C HIGH. For 4-channel Maney panels, always use the LOW settings.
242
10. The number of events that appear by default are determined by whether 2- or 4- channel was selected for in Panel Type. For 2-channel panels, there are eight events preconfigured to A and B. For 4-channel panels, there are sixteen events, preconfigured to A, B, C, and D (as shown in previous graphic). The panel buttons are numbered 1-8 for the 2-channel panels and 1-16 for the 4-channel panels; these numerical names cannot be altered. Also, the Event Type is always Trigger for Maney panels and cannot be altered. The Event Name may be changed. To edit an events name, double click on the event or select it and click the Edit Event button.
11. Enter a new name for the event. Being descriptive here will help when assigning events to actions later. 12. Click OK.
For redundant systems, to ensure identical functionality, make certain that the device settingsall input pins and event names and typesare the same for every device service installed. 13. Click Apply. 14. After modifying the Maney panels device service system settings, restart the service.
243
Restarting the Maney Panel Device Service

After configuring the PCI card, you must restart the device service.
To restart the Avid Maney Panel Device Service:
1. Click Start and select All Programs > Avid > Service Framework > Avid Workgroup Properties. 2. On the Services tab, click Advanced. 3. Select Avid Maney Panel Device Service. 4. Click Restart.
Avid also recommends restarting the client software at the Command Workstation.
Confirming Successful Setup of a Maney Panel

This section provides a way to verify that the installation and configuration of a Maney panel was successful.
To verify successful setup of a Maney panel:
1. At the Command Workstation to which a Maney panel is connected, click the Start button and select Programs > Avid > Service Framework > Avid Health Monitor. On the Hosts tab, services are listed by computer and device. The Processes tab lists by services. 2. Navigate to the Avid Maney Panel Device Service and select it.
244
Confirming Successful Setup of a Maney Panel
3. Expand the Information section. The Device Name shows the hostname.board number. If the Board Status is connected, the service is installed in the right location and the board number was set correctly. The Last Input Value will typically show ffffff if theres no button pressed on the panel. The Last Event should be empty, and Event count should be zero (0). 4. Press any of the Maney panel buttons. Health Monitor will refresh after a short delay.
The time it takes Health Monitor to report a Maney panel event is slower than the response of Command to that Maney panel input.
245
The Information section will appear similar to the following example:
5. Press a number of buttons to make sure they all work.
If the switcher is wired to the Maney panel, test that, too.
246
Mapping Events to Actions for a Maney Panel

After you configure the PCI card for a Maney panel and restart the device service, the events must be mapped to playout actions. This is done at a Command Workstation in the System Settings dialog box.
To map events to actions:
1. Log in to a Command Workstation. 2. Select Tools > System Settings. The System Settings dialog box appears.
3. Select GPI. This does apply to events for Maney panels, as shown in the above graphic; The C and D event has 8 events indicative of a 2-channel Maney panel. 4. Expand the panels to view each panels events. 5. Double-click on an event to map it to an action. The Choose Action dialog box appears with the GPI > Control options expanded by default.
247
Users can select any of the actions in the dialog box, such as selecting Playlist > Selection > Next Item, which would configure a button to advance the cursor in a playlist via the user interface. However, Avid recommends mapping Maney panel events to GPI > Control actions only because these actions are communicated directly to the Playlist Controller, bypassing the user interface. Similar actions, such as Cue, Pause, Play, and Stop, also appear under Control, but those are provided for USB keypads, such as X-keys.
6. Expand the GPI > Control action, such as Play, and select the index value that corresponds to the appropriate channel.
Channel 01 actually refers to Index value 01. 7. Click OK. 8. Repeat steps 5 through 7 as needed. 9. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK.
248
The system will prompt you for the administrator password.
249
250
9 Integrating with ENPS

To ensure proper integration between Avid iNEWS Command and the ENPS newsroom computer system, certain configuration must be completed within ENPS. Those configuring ENPS must have system administrator access and a working knowledge of the newsroom computer systems administrative features.
ENPS is third-party software. Refer to the manufacturers documentation for more detailed information regarding the newsroom computer system. This chapter contains the following main sections: Configuring ENPS Configuring MOS Settings in Command Configuring Command for Deko Select Configuring Command for MOS Redirection
Configuring ENPS
You must configure the ENPS MOS settings on an ENPS newsroom computer system to enable integration with Avid iNEWS Command.
To configure the ENPS MOS settings:
1. Open the ENPS client interface. 2. Click the green Rover button on the Corporate folder at the bottom of your screen. This folderfourth from the leftis typically labeled with your station call letters or corporate name. By default, it is labeled ENPS.
3. Select System Maintenance > Groups.
252
Configuring ENPS
A dialog box with a list of configured groups opens.
4. Click the New button. The ENPS dialog box opens.
5. Enter the name of the group and click OK. A new row appears in the list. 6. On that row, do the following: a. b. Enter a description. Select the server. This should be the primary ENPS server.
7. Click Save. 8. Click the green Rover button on the Corporate folder again.
253
9. Select System Maintenance > MOS Configuration. A dialog box with a list of configured MOS plug-ins opens.
10. Click the New button. The ENPS dialog box opens.
11. Enter the MOS ID. The information you enter here must match the iNEWS Command MOS ID in the Command system settings. For more information, see Configuring MOS Settings in Command on page 256. 12. Click OK. A new row appears in the list.
254
Configuring ENPS
13. On that row, fill in the fields as shown in the following table:
Text Box Name Description
Description IP ActiveX Program MOS Version
Enter the name that identifies this plug-in for users. Enter the IP address of the Command Server running the MOS Communication service. Enter the ActiveX Application ID. This is usually DekoMOS.Browser. (Dont forget the period between DekoMOS and Browser.) Select the group you created in step 5 on page 253. Enter the version used by your Avid iNEWS Command system. Although both versions 2.6 and 2.8 are supported, Avid strongly recommends using MOS 2.8. Enter the ActiveX Application ID. This is usually DekoMOS.Browser. (Dont forget the period between DekoMOS and Browser.) Ensure the auto create field is enabled. Set the object type to VIDEO.
Modal UI ActiveX Auto Create Object Type
You might need to scroll to the right to view all fields that require modification. 14. Click Save. 15. Restart all ENPS client applications so that the new MOS ID information will appear as an option. 16. Restart the ENPS News Object Manager (NOM) to allow the new MOS ID to take effect and appear throughout the ENPS newsroom computer system.
255
Configuring MOS Settings in Command

The MOS category in the System Settings dialog box allows system administrators to configure the Command system to integrate with a MOS-enabled newsroom computer system, such as ENPS. A MOS-enabled newsroom computer system can send playlists to Command. MOS (Media Object Server) is an industry-standard, XML-based protocol that is primarily used by a newsroom computer system (NRCS) to maintain running orders on a video server. MOS also enables servers to update the newsroom computer system with changes to the servers media inventory. Commands MOS support enables communication between the newsroom computer system and AirSpeed video servers, as shown in the following illustration.
MOS does not provide a means of controlling playout from a video server. Command supplies this function. Under the MOS category are three subcategories: General - used to configure MOS and graphics style settings. Channel Groups - used to identify channel groups for integration with MOS-based newsroom computer systems. Advanced - used for advanced MOS feature configuration.
Avid strongly recommends contacting Customer Support before altering any of the advanced settings.
To configure Commands system settings to work with a MOS-based newsroom computer system:
1. At a Command Workstation, select Tools > System Settings. 2. Expand the MOS category. 3. Select General.
256
4. Edit the MOS settings accordingly:

MOS Setting Description
iNEWS Command MOS The ID that enables enables bidirectional communications between a ID MOS-based newsroom computer system and Command. For instance: avid.command1.mos or avid.command2.mos Newsroom NCS ID Newsroom Host Name Usually, this is set to the host name of the newsroom computer systems server. Host name of the newsroom computer systems server. The name entered in this field must be resolvable via the Domain Name Service (DNS); otherwise, an IP address can be used instead. Usually, this is set to host name of the newsroom computer systems buddy or backup server. The name entered in this field must be resolvable via the Domain Name Service (DNS); otherwise, an IP address can be used instead.
Buddy NCS ID
257
MOS Setting
Description (Continued)
Buddy Host Name MOS version
Host name of the newsroom computer systems buddy or backup server. Determines which version of MOS protocol Command will use.
5. Set the default graphics style for playlists loaded from a MOS-based newsroom computer system, if necessary. Graphics styles are added at the Command Workstation via the Playlist category in the System Settings dialog box. If none are added, then the list in the MOS > General category will appear blank. 6. Select Channel Groups. 7. Click Add. The Channel Groups dialog box appears.
8. Select a channel group. 9. Click OK. The chosen channel group will appear in the list on the right side of the System Settings dialog box.
258
If entering multiple channel groups, the device channels in those groups must not conflict. When entering multiple channel groups of the same type, such as AirSpeed, Command will auto-assign MOS items to the first channel of the first channel group listed.
10. Click Apply (if you want the System Settings dialog box to remain open after settings are applied) or OK. The system will prompt you for the administrator password.
259
To view advanced MOS settings:
1. Select Tools > System Settings. 2. Expand the MOS category. 3. Select Advanced.
While a newsroom computer system can use non-standard ports for the incoming and outgoing sockets and the advanced settings can be customized, Avid recommends that the default settings be used.
Avid strongly recommends contacting Customer Support before altering any of the advanced settings. The first four settings specify the port numbers for the sockets used to communicate with the MOS-based newsroom computer system. The defaults, as defined in the MOS protocol specifications, are: 10541 (upper) and 10540 (lower).
260
Configuring Command for Deko Select
Configuring Command for Deko Select

When using the Avid Deko Select plug-in with Command and ENPS, some configuration is needed.
To configure integration for Deko Select with Command and ENPS:
1. In ENPS, configure the Deko Select plug-in, such as the example on the bottom row of the following graphic. The IP address is the DekoMOS Gateway.
For more information, see documentation provided by ENPS. 2. Configure the Deko channel group in Command. 3. In the DekoMOS Gateway, add the primary ENPS Servers MOS ID field, shown here with MOS ID per channel:
Configuring Command for MOS Redirection

Command sites that interface with the ENPS newsroom computer system can run two MOS Communication services and set the second one to have a different MOSID so that MOS redirection can be used to send playlists to the backup server. The purpose of MOS redirection to allow users to load the ENPS rundown to the backup Command Server in the event of a primary server failure. It is the equivalent of loading an iNEWS rundown to the backup server, but this workflow requires a little more configuration.
261
To configure Command for MOS redirection:
1. In ENPS, configure the primary and backup Command MOS IDs, such as the examples shown in the following graphic:
2. Click the Start button and select Programs > Avid > Service Framework > Avid Service Configuration. 3. On the Hosts tab, navigate to and select the Avid MOS Communication Service running on the backup server, such as barry.command2.mos. 4. Enter the MOSID for the backup server. 5. Open the ENPS rundown properties, toggle off the MOS Control Active (if necessary). 6. Click Apply. When you need to direct MOS traffic to the backup server, disconnect from the primary server and connect to the backup server via MOS redirection in ENPS. For instance, enter barry=barry.command2.mos in the MOS Redirection field, then click MOS Control Active, and click Go. The sample equation tells ENPS that any device in the rundown starting with barry should get redirected to the MOS backup system.
You can test MOS redirection at any time; it does not require the primary server to be down. For more information, see documentation that came with your third-party ENPS system.
262
10 Confirming Functionality
After software installation and system configuration is complete, you should verify proper functionality of components and ensure the success of the installation and integration. This chapter contains the following main sections: Monitoring System Status Viewing Status of Services Confirming Command Inventory Testing Workflow
Monitoring System Status

After installation and configuration of the Command system is complete, you can check the status by using the Avid Health Monitor
To check the current status of the system:
1. Click the Start button and select Programs > Avid > Service Framework > Avid Health Monitor.
On the Hosts tab, services are listed by computer and device. The Processes tab lists by services. 2. Confirm that no problems are reported. Any problems on the system will appear with a red X.
264
Viewing Status of Services
Viewing Status of Services

Avid Command uses Avid Service Framework as its structure for discovering and communicating with services.
To start Workgroup Properties:
Click the Start button and select > All Programs > Avid > Service Framework > Avid Workgroup Properties. The Avid Workgroup Properties window opens.
When you start the Workgroup Properties application, the Services tab appears by default displaying the name of the workgroup, to which this computer belongs, in the Workgroup text box. Also shown, in the Status text box, is the status of all Avid services running on the local computer.
265
The Workgroup Properties application uses colored iconsin combination with texton the Services tab to show the status (started and/or enabled) of all Avid services. A user can click the Advanced button to see more information about individual services. The icons displayed provide fast, easy identification of the current status of an Avid service.
Icon Description
When all of the enabled Avid components are running on the local machine a green circle with a check mark in the center is shown next to the Status text box and the sentenceAll enabled services are runningis displayed. When some of the enabled Avid components are running on the local machine a caution symbol (yellow triangle with an exclamation mark in the center) is shown next to the Status text box and the sentenceSome services are enabled but not runningis displayed. When none of the enabled Avid components are running on the local machine a red square is shown next to the Status text box and the sentenceNo services are runningis displayed.
For more information on viewing Avid services using the Workgroup Properties application, see the Avid Service Framework Users Guide.
Confirming Command Inventory

You should confirm that the inventory of media available to Command is appearing properly at a Command Workstation.
To confirm that the Avid iNEWS Command system is seeing inventory correctly:
1. Start the Command client application. 2. If the Inventory panel is not already open, select View > Inventory. 3. Click the down arrow (indicated in the graphic) and select a channel group from the list. The Inventory panel shows the inventory (media) for a selected channel group in a table or spreadsheet-style format. You can see the medias availability, clip ID, name (slug), duration, and the time when it was last modified. A user can select a different channel group using the drop-down arrow in the top right corner of the panel. When a user selects an item in the inventory, further details become available for viewing at the bottom of the panel. The size of the list and details area can be adjusted with the Resize bar that separates the two areas. For more information on the Inventory panel, see the Avid iNEWS Command Users Guide.
266
Confirming Command Inventory
If you are using VDCP and do not have an inventory port configured, you cannot confirm inventory via the Inventory panel in Command.
There can be a delay of approximately 2 minutes for the inventory to appear after creating a channel group. Also, ensure that you check both video and graphic (character generator) assets.
267
Testing Workflow
The person testing the systems workflow should have a basic working knowledge of the various systems that interact with Command, such as the newsroom computer system as well as the Command client application.
For basic user information on Avid iNEWS, iNEWS Command, or other integrated Avid products, see the Users Guides and help systems that accompany each product.
To test workflow:
1. Create an iNEWS rundown with stories that contain graphic and video events. a. b. If you use hand-entered machine control events, test that by entering some into new and existing stories. If you are using a plug-in, such as Avid Deko Select or Avid Thunder Select, open the plug-in and test it as well by using it to insert events into stories.
2. Load the rundown. (For Avid iNEWS, this means to turn on and load the monitor server.) 3. At a Command Workstation, start the Command client application. 4. Confirm that the newsroom playlist associated with that rundown appears in the Playlist Explorer.
5. Open the playlist. 6. Lock all channel groups. 7. Play video and graphic events. Ensure that they appear as expected on the video monitors, and check to make certain that available and unavailable items are correctly reported. 8. Rearrange stories in the newsroom rundown and ensure that the items in the newsroom playlist at the Command Workstation adjust accordingly.
268
ABCDEFGHIJKLMNOPQRSTUVWXYZ
Index
Index
Symbols
/site/config 207
A
Add Lookup Service dialog box 79 Add New Event dialog box 226 Add Panel dialog box 226, 242 Add Workgroup dialog box 135 AirSpeed channel designations 158 channel groups 160 configuring device services 49, 80 configuring services for thumbnails 60 default device service installation 45 AirSpeed Multi Stream channel designations 159 configuration checklist 78 configuring Command workgroup 82 configuring Interplay workgroup 79 configuring the device service 80 device integration checklist 72 install Service Framework 73 installing the device service 76 overview 71 play while record 85 Apply Studio Settings dialog box 164 Avid how to order documentation 14 online support 14 training services 15 Avid Deko channel designations 158 configure the device service 117 device integration checklist 90 installing device services 95 styles aka environments 119 Avid Deko Renderer service 46
Avid Diagnostics 29 Avid Graphics Select 201 Avid Health Monitor 29, 264 Avid iNEWS configuring 197 mailboxes 213 Map story 198 plug-ins 201 queue properties 212 Avid iNEWS Communication Service 44 Avid Interplay Agent Service 45 Avid MOS Communication Service 44 Avid Service Configuration application 24, 29 Avid Service Framework Diagnostic Log Viewer 29 Email Alerter 30 Lookup Service 24 Machine Monitor 29 Multicast Repeater 30 Service Configuration 29, 35, 117, 137 starting 225, 241 SNMP Gateway 30 System Configuration 24 Time Synchronization 30 Workgroup Properties 265 Avid Thunder channel designations 158 configure the device service 137 device integration checklist 124 installing device services 129 Avid Unity 71 Avid Video device service 45 Avid Workgroup Properties 49, 58, 117, 224, 228, 244 Avid_License_Setup.exe 30
B
Backup server 257
269
Index
installing software 149, 175 using X-keys 219 configuration lines, example of 209 Connections tab 106 Console commands iNEWS 208 list 207 variations of list 211
C
Channel groups creating 162 defined 160 deleting 167 editing 165 examples of 160 redundancy 161 Channel indices 220 Channel-specific actions assigning 223 mapping 220 Checklists Command client installation 144, 170 Command pre-installation 19 Command Server installation 20 Deko configuration 103 Deko installation 90 Multi Stream configuration 78 Multi Stream installation 72 setting up the GPI panel 224 setting up the Maney panel 238 setting up X-keys USB keypad 219 Thunder integration 124 Choose Action dialog box 232, 234, 248 Chyron configuring 192 configuring LUCI plug-in for ActiveX 195 configuring Lyric 195 installing the Graphic device service 175 installing the Graphic Inventory Editor 180 Command configuring second system 69 import graphic inventory from iNEWS 185 monitoring system status 264 pre-installation checklist 19 system architecture 18 viewing documentation 41 Command Server installation checklist 20 installing software 40 Command workgroup, configure for Multi Stream 82 Command Workstation alternative keypad device 224, 238 disabling keyboard 218 installation checklist 144, 170
270
D
Debounce Time 226 Deko 87 channel designations 158 configuration checklist 103 configuring device services 117 installation checklist 90 integration checklist 90 MOS ID 200 subfolders 110 system architecture 88 thumbnails 101 user settings 105 XML storage 105 Deko Renderer, configuring the service 118 Deko Select 201 configure for ENPS 261 installing 204 subfolders 110 DekoMOS Gateway configuring 104 installing 101 Net HASP dongle 101 DekoMOS Gateway Configuration dialog box 104 DekoMOS Macro Server configuring 111 configuring styles 113 installing 102 DekoMos.ini file 206 Destination Folder dialog box 151, 177 Device numbers 207 Device services Avid Video 45 configuring 49, 80, 117 configuring Deko Renderer service 118 configuring for Thunder 137 configuring Interplay Agent service 60
Diagnostic log viewer 29 Dialog boxes Add Lookup Service 79 Add New Event 226 Add Panel 226, 242 Add Workgroup 135 Apply Studio Settings 164 Choose Action 223, 232, 234, 234, 248 DekoMOS Gateway Configuration 104 Destination Folder 151, 177 Queue Properties 212 System Settings 162, 230, 247 Digital recorder 71 Documentation for Command 41 dongle 101 Duration 198 restart the device service 228 GPI events mapping for GPI panel 230 mapping for Maney panels 247 GPI Out 237 GPI panel checklist 224 enabling the panel 236 Graphic device service Chyron integration 192 configuring 181 configuring for LUCI plug-in 195 installing 175 Graphic Inventory Editor configuring 184 importing from iNEWS 185 installing 180 working with styles 190 working with templates 188 Graphic styles 190 Graphic templates 188 Graphics environments 119 setting default 258
Index
E
Email Alerter service 30 ENPS configure Deko Select 261 configure MOS redirection 261 integration 251 MOS settings 252 News Object Manager 255 play while record 85 Event types 227, 243
H
Harris Nexio 54 Health Monitor 29
F
First Input Pin 226, 242 Functionality, confirming 263
I
Icons DekoMOS Gateway 104 in Command playlists 217 Macro Server 111 NetHasp License Manager 102 transfer status 59 iNEWS /site/config 207 configuring 197 ed command line editor 208 list command 207 mailboxes 207 Map story 198 play while record 85 SYSTEM.MAP for styles 190 SYSTEM.MOS-MAP 200
271
G
Gateway settings 206 General tab 105 GIE configuring 184 importing from iNEWS 185 installing 180 working with styles 190 working with templates 188 GPI card 224 GPI device enabling the panel 236
Index
Mailboxes 213 assigning to rundown queue 210 defined 207 valid numbers 207 viewing assignments 211 Maney panel 239 checklist 238 configuring the PCI card 241 installing the device service 45 mapping events 247 restarting device service 244 Map story 198 Mapping GPI events to actions 230 Mapping Maney panel events to actions 247 Measurement Computing card 238, 239, 241 MiniMon column 139 Mirrored playout 164 channel groups 161 Monitor LOAD command 210 Monitor ON command 210 Monitor servers 207 configuration lines 209 form name 199 listing assigned mailboxes 211 MOS ID 200 MOS protocol defaults 260 described 256 version 258 MOS settings 260 editing 257 MOS, defined 256 MOS-based newsroom configuration 251 MOS-Map story 200 Multi Stream channel designations 159 installation checklist 72 play while record 85 Multicast Repeater service 30
SYSTEM.RESOURCE 185 iNEWS Command install on workstation 149 licensing 30 MOS ID 257 MOS support 256 iNEWS Servers configuration file 207 host definition 209 Installation Avid Deko Select 204 Avid Thunder Select 202 Command on a server 40 Command on a workstation 149, 175 determining disk space 99, 133 Service Framework software on Multi Stream 73 USB keypads 220 Interplay Agent service 60 Interplay workgroup, configuring for Multi Stream 79 Inventory panel 266 confirming media availability 266
K
Keyboard alternative keypad device 224, 238 disabling 218
L
Level 227 License manager 101 License service 30 configuring 35 Licenses activation file 36 permanent 38 temporary 35 list command, variations of 211 Lookup service 24 Lookup tab, configuring 66 LUCI plug-in 195
N
Net HASP Connection Settings 106 Net HASP dongle 101 Net HASP License Manager 101 Newsroom buddy host name 258 Newsroom buddyID 257
M
Machine Monitor service 29 Macro server 102
272
Newsroom host name 257 Newsroom NCS ID 257 Newswheel 237
Index
O
Omneon 53 configuring the video device service 50 Online support 14
P
Paths 105 PCI card 238, 239 mapping events 247 Play while record 85 Playlist icons 217 Playlist Viewer 216 Playout control 216 configuring 215 Plug-ins 201 Procedures add a style 191 add an environment 119 add the permanent license 38 add the temporary license 35 assign a style to standalone playlist 192 change system name 69 checking system status 264 configure a second Command system 69 configure Avid Video device service (Omneon) 50 configure Avid Video device service (VDCP) 57 configure Chyron integration 192 configure Command for MOS-based NRCS 256 configure Command workgroup properties 82 configure Deko Renderer service 118 configure Deko Select for ENPS 261 configure DekoMOS Macro Server 111 configure for GPI Out 237 configure for Newswheel 237 configure for VDCP redundancy 58 configure Interplay workgroup properties 79 configure Lookup tab 66 configure MOS redirection for ENPS 262 configure the Avid Thunder device service 137 configure the Deko device service 117
configure the DekoMOS Gateway 104 configure the ENPS MOS settings 252 configure the GPI cards board settings 225 configure the Graphic device service 181 configure the License service 35 configure the Maney panel 241 configure the Multi Stream device service 80 configure the PCI cards board settings 241 configure the Thunder 138 configure workgroup properties for Thunder 135 configuring LUCI plug-in 195 configuring Lyric 195 configuring the Graphic Inventory Editor 184 confirm GPI panel setup 229 confirm Maney panel setup 244 confirm running of NetHASP License Manager 102 confirming inventory 266 connect the New HASP Dongle 101 control playout with numeric keypad 217 copy a style 191 copy a template 189 copy install CD to local directory 22 create & configure monitor server 207 create a style 190 create a template 189 create channel groups 162 create the ThunderMOS.cfg file 140 create the ThunderMOS.ini file 141 delete a channel group 167 delete a style 191 delete a template 189 edit a channel group 165 edit the Map story in iNEWS 199 edit the SYSTEM.MOS-MAP story 201 enable a GPI panel to control a playlist 236 enable or disable the keyboard 218 generate an activation file 36 import graphic inventory from iNEWS 185 install an X-keys USB keypad 220 install Avid Deko Select 204 install Avid Service Framework on a workstation 125, 145, 171 install Avid Thunder Select 202 install Service Framework on a server 24 install Service Framework on a workstation 91 install Service Framework on Multi Stream 73
273
Index
Services Avid Deko Renderer 46 Service Framework 24, 29 viewing status 265 Site licenses 30 SNMP Gateway 30 Starting Workgroup Properties 265 Story forms, explained 212 system architecture 18 System settings GPI 230 indices 220 Maney panel 247 MOS 257 MOS advanced 260 MOS channel groups 258 Playlist 119 System Settings dialog box 162, 230, 247 System status, monitoring 264 SYSTEM.MAP 198 SYSTEM.MOS-MAP 200
install software on a Command Server 40 install software on a Command Workstation 149, 175 install the Deko device software 95 install the DekoMOS Gateway 101 install the DekoMOS Macro Server 102 install the Graphic device service 175 install the Graphic Inventory Editor 180 install the License service 30 install the Multi Stream device service 76 install the Thunder device software 129 map an index to a channel name 220 map GPI events to actions 230 map Maney panel events to actions 247 play while record on AMS 85 play while record with ENPS 86 play while record with iNEWS 85 play while record with standalone playlist 86 programming X-keys 221 restart the GPI device service 228 restart the Maney Panel device service 244 specify inventory path in GIE 184 start Workgroup Properties 265 test workflow 268 view advanced MOS settings 260 view the Queue Properties dialog box 212
T
Temporary Command license 35 Thumbnails, installing services for 45 Thunder channel designations 158 configuring device services 137 integration checklist 124 MOS ID 200 Thunder Select 201 ThunderMOS.cfg file 200 creating the file 140 ThunderMOS.ini file 141 Time Synchronization service 30 Toggle 227 Training services 15 Transfer status icon 59 Trigger 227 Troubleshooting 14
Q
Queue form, explained 212 Queue Properties dialog box 212 Quit time 198
R
Redundancy channel groups 161 configuring the Lookup tab 66 VDCP 45, 58 Rover button 252
S
Secondary Command systems 69 Serial connections 55 Server type 199 Service Configuration 35
274
U
USB keypad 219 Utility programs 207
Index
V
VDCP channel designations 158 configuring for mirrored playback 58 configuring the device service 57 installing the device service 45 wiring serial connections 55 Video server channel designations 158 channel groups 160
W
Wiring serial connections 55 Workflow, testing 268 Workgroup Properties 265 restarting GPI device service 228 restarting Maney panel device service 244
X
X-keys channel-specific actions 223 checklist 219 XML-based protocol 256
275
Index
276
Avid
75 Network Drive Burlington, MA 01803-2756 USA
Technical Support (USA)

Visit the Online Support Center at www.avid.com/support
Product Information
For company and product information, visit us on the web at www.avid.com

iNEWSCommandv27 ICG

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

iNEWSCommandv27 ICG

Încărcat de

Drepturi de autor:

Formate disponibile

Avid iNEWS Command

Installation and Configuration Guide

The following disclaimer is required by Apple Computer, Inc.:

The following disclaimer is required by the Independent JPEG Group:

The following disclaimer is required by Nexidia Inc.:

The following disclaimer is required by Paradigm Matrix:

The following disclaimer is required by Ray Sauers Associates, Inc.:

The following disclaimer is required by Videomedia, Inc.:

The following disclaimer is required by Ultimatte Corporation:

The following disclaimer is required by 3Prong.com Inc.:

The following disclaimer is required by Interplay Entertainment Corp.:

Attn. Government User(s). Restricted Rights Legend

Installing and Configuring the Command Server . . . . . . . . . . . . . . . . . . 17

Installing and Configuring the AirSpeed Multi Stream . . . . . . . . . . . . . . 71

Installing and Configuring the Deko. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Installing and Configuring the Thunder. . . . . . . . . . . . . . . . . . . . . . . . . 123

Installing the Command Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Installing GDS and GIE for Chyron. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Integrating with Avid iNEWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Configuring Playout Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Integrating with ENPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Confirming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Using This Guide

Symbols and Conventions

(Windows), (Windows only), (Macintosh), or (Macintosh only)

Symbol or Convention Meaning or Action

Bold font Italic font

Ctrl+key or mouse action

If You Need Help

How to Order Documentation

Avid Training Services

Avid Training Services

1 Installing and Configuring the Command Server

1 Installing and Configuring the Command Server

Checklist: Before you Begin

Checklist: Before you Begin

1 Installing and Configuring the Command Server

Checklist: Command Server Installation

Set the system administrator password. (Optional) Configure the Time

Checklist: Command Server Installation

(Optional) Configure the Lookup tab in

(Optional) Configure the Interplay Agent

Configuring Avid Interplay Agent Services on page 60 page 63

1 Installing and Configuring the Command Server

Copying Install CD to Local Directory

Copying Install CD to Local Directory

1 Installing and Configuring the Command Server

Installing Avid Service Framework

Installing Avid Service Framework

To install the Avid Service Framework software:

1 Installing and Configuring the Command Server

3. Click Next. The Workgroup Name dialog box opens.

Installing Avid Service Framework

5. Type a new or existing workgroup name in the field.

1 Installing and Configuring the Command Server

The Options dialog box opens.

Installing Avid Service Framework

1 Installing and Configuring the Command Server

Installing the License Service

Installing the License Service

1 Installing and Configuring the Command Server

3. Click Next. The Destination Folder dialog box appears.