avid inews commandresources.avid.com/supportfiles/attach/commandv2.0-icg... · 2009-06-20 · avid...

m a k e m a n a g e m ove | m e d i a ™ Avid ®

Avid® iNEWS® Command

Installation and Configuration Guide

2

Legal NoticesProduct 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,045,940; 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,452,378; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,583,496; 5,584,006; 5,627,765; 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; 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 licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for 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 © 2009 Avid Technology, Inc. and its licensors. All rights reserved.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:Copyright © 1988–1997 Sam Leffler Copyright © 1991–1997 Silicon Graphics, Inc.

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

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

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

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

Adobe and Photoshop are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Apple and Macintosh are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Windows is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. All other trademarks contained herein are the property of their respective owners.

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

http://www.avid.com

3

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

Trademarks888 I/O, Adrenaline, AirPlay, AirSPACE, AirSPACE HD, AirSpeed, ALEX, AniMatte, AudioSuite, AudioVision, AutoSync, Avid, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, AVIDdrive, AVIDdrive Towers, Avid DS Assist Station, Avid ISIS, Avid Learning Excellerator, Avid Liquid, Avid Mojo, AvidNet, AvidNetwork, Avid Remote Response, AVIDstripe, Avid Unity, Avid Unity ISIS, Avid Xpress, AVoption, AVX, CamCutter, ChromaCurve, ChromaWheel, DAE, Dazzle, Deko, DekoCast, D-Fi, D-fx, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Intelligent Noise Reduction, DigiDrive, Digital Nonlinear Accelerator, DigiTranslator, DINR, DNxchange, do more, D-Verb, Equinox, ExpertRender, FASTBREAK, Fast Track, FieldPak, Film Composer, FilmScribe, FluidMotion, FXDeko, HIIP, HyperSPACE, HyperSPACE HDCAM, IllusionFX, Image Independence, iNEWS, iNEWS ControlAir, Instinct, Interplay, Intraframe, iS9, iS18, iS23, iS36, IsoSync, LaunchPad, Lightning, Lo-Fi, Magic Mask, make manage move | media, Marquee, Maxim, MCXpress, Media Browse, Media Composer, MediaDock, MediaDock Shuttle, Media Fusion, Media Illusion, MediaLog, Media Reader, Media Recorder, MEDIArray, MediaShare, MediaStream, Meridien, MetaFuze, MetaSync, MicroTrack, MissionControl, NaturalMatch, Nearchive, NetReview, NewsCutter, Nitris, OMF, OMF Interchange, OMM, Open Media Framework, Open Media Management, PCTV, Pinnacle MediaSuite, Pinnacle Studio, Pinnacle Systems, ProEncode, Pro Tools, QuietDrive, Recti-Fi, RetroLoop, rS9, rS18, Sci-Fi, ScriptSync, SecureProductionEnvironment, Show Center, Sound Designer II, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Symphony, TARGA, Thunder, Thunder Station, TIMELINER, Trilligent, UnityRAID, Vari-Fi, Video RAID, Video Slave Driver, VideoSPACE, Xdeck, and X-Session are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

FootageArri — 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. It’s 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.

http://www.apache.org/

http://jcifs.samba.org/

http://www.wildlifeworlds.com

4

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 Avid’s mailing address, go to www.avid.com/footage.

*Note: Avid cannot guarantee the use of materials submitted.

Avid iNEWS Command Installation and Configuration Guide • 0130-30117-01B • Created 2/13/09 • Revised 04/29/09 This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printedform.

http://www.avid.com/footage

5

Contents

Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

How to Order Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1 Installing and Configuring the Command Server . . . . . . . . . . . . . . . . . . 13

System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Checklist: Before you Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Checklist: Command Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Copying Install CD to Local Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Disabling Windows Media Sense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Installing the License Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring the License Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Adding the Temporary Command License . . . . . . . . . . . . . . . . . . . . . . . . . 32

Generate an Activation File for a Full Command License . . . . . . . . . . . . . . 34

Add the Permanent Command License. . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing Avid iNEWS Command on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring the iNEWS Command Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Configuring the System Administration Password . . . . . . . . . . . . . . . . . . . . . . . 44

Configuring the Time Synchronization Service . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring AirSpeed Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Wiring Serial Connections for Avid Video Device Services (for VDCP) . . . . . . . 47

Configuring Avid Video Device Services (for VDCP) . . . . . . . . . . . . . . . . . . . . . 50

Configuring Avid Interplay Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Configuring the Lookup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring a Second Command System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 2 Installing and Configuring the AirSpeed Multi Stream . . . . . . . . . . . . . . 57

Checklist: Installing the AirSpeed Multi Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6


Installing AirSpeed Multi Stream Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Checklist: Configuring the AirSpeed Multi Stream . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring Properties for Interplay Workgroup. . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Configuring the AirSpeed Multi Stream Device Service . . . . . . . . . . . . . . . . . . . . . . 66

Configuring Properties for Command Workgroup . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Chapter 3 Installing and Configuring the Deko. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Command with Avid Deko Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Checklist: Installing the Deko . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74


Installing Avid Deko Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Installing the DekoMOS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Connecting the Net HASP Dongle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Installing the DekoMOS Gateway and Net HASP Software . . . . . . . . . . . . . . . 85

Confirming the NetHASP License Manager Configuration . . . . . . . . . . . . . . . . 86

Installing the DekoMOS Macro Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Checklist: Configuring the Deko. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring the DekoMOS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuring the DekoMOS Macro Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configuring Styles on the DekoMOS Macro Server . . . . . . . . . . . . . . . . . . . . . 96

Configuring Avid Workgroup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring the Deko Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Configuring the Avid Deko Renderer Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Creating Graphic Environments in Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 4 Installing and Configuring the Thunder . . . . . . . . . . . . . . . . . . . . . . . . . 105

Checklist: Installing and Configuring the Thunder . . . . . . . . . . . . . . . . . . . . . . . . . 106

Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Installing Avid Thunder Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring Avid Workgroup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Configuring the Thunder Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Configuring the Thunder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Creating the ThunderMOS.cfg File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

7

Creating the ThunderMOS.ini File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Chapter 5 Installing the Command Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Checklist: Installing the Command Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Installing Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Installing Avid iNEWS Command on the Workstation. . . . . . . . . . . . . . . . . . . . . . . 131

Configuring Avid Workgroup Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Setting up Device Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Setting up Channel Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Chapter 6 Integrating with Avid iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Editing the SYSTEM.MAP Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Editing the SYSTEM.MOS-MAP Story . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Setting up the Plug-ins in iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Installing and Configuring Avid Thunder Select . . . . . . . . . . . . . . . . . . . . . . . . 156

Installing and Configuring Avid Deko Select . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Configuring Gateway Settings from an ini File . . . . . . . . . . . . . . . . . . . . . 160

Monitor Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Creating a Monitor Server for Each Show . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Using the list Command to View Assigned Mailboxes . . . . . . . . . . . . . . . . . . . 165

Queue Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Chapter 7 Configuring Playout Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Controling Playout via the User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Disabling a Command Workstation’s Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Checklist: Setting up an X-keys USB Keypad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Installing an X-keys USB Keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Mapping Indices to Channel Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Programming the X-keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Checklist: Setting up the GPI Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Configuring the GPI Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Restarting the GPI Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Confirming Successful Setup of a GPI Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Mapping Events to Actions for a GPI Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Enabling the GPI Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Checklist: Setting up the Maney Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

8

Configuring the PCI Card for a Maney Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

Restarting the Maney Panel Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Confirming Successful Setup of a Maney Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Mapping Events to Actions for a Maney Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Chapter 8 Integrating with ENPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Configuring ENPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Configuring MOS Settings in Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Configuring Command for MOS Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 9 Confirming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Monitoring System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Viewing Status of Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Confirming Command Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Testing Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

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.

n 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 A note provides important related information, reminders, recommendations, and strong suggestions.

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

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

10

If You Need HelpIf 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 DocumentationTo 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.

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

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

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

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

Symbol or Convention Meaning or Action

http://www.avid.com/readme

http://www.avid.com/onlinesupport

Avid Training Services

11

Avid Training ServicesAvid 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).

http://learn.avid.com

http://www.avid.com/training

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

• Disabling Windows Media Sense

• 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


14

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

Checklist: Before you Begin

15

Checklist: Before you BeginBefore you start to install software and configure the Command Server(s), ensure the following tasks are completed.

Some Interplay products, such as Instinct, Assist, and Access use Avid Service Framework. Avid iNEWS Command also uses Service Framework; however, the two versions might not be compatible. Consult with Avid Customer Support to determine Avid Service Framework compatibility when Interplay products are installed in the same workgroup. It might be necessary to:

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 connection’s addresses in DNS checkbox is selected.

• (Optional) The Use this connection’s DNS suffix in DNS registration checkbox 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.

n Avid iNEWS Command only supports the Digi Accele Port card for VDCP playout control.

Tasks

Use a separate workgroup for the Command system.

Install Command on separate machines that run Service Framework compatible with Command.


16

Checklist: Command Server InstallationDetermine 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).

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

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

Disable Windows Media Sense. “Disabling Windows Media Sense” on page 20

Install Avid Service Framework. “Installing Avid Service Framework” on page 21

Install the License service. “Installing the License Service” on page 28

Install Avid iNEWS Command. For redundancy, repeat this procedure on the second server.

“Installing Avid iNEWS Command on the Server” on page 37

Configure the Command Server. “Configuring the iNEWS Command Server” on page 44

n All settings in Command and Interplay Framework are case sensitive. Ensure that case matches in all configuration settings.

Set the system administrator password. “Configuring the System Administration Password” on page 44

(Optional) Configure the Time Synchronization service.

“Configuring the Time Synchronization Service” on page 45

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

Configure the AirSpeed device services. “Configuring AirSpeed Device Services” on page 46

Configure the Avid Video device services. “Configuring Avid Video Device Services (for VDCP)” on page 50

Configure the Lookup tab in Workgroup Properties.

“Configuring the Lookup Tab” on page 53

Checklist: Command Server Installation

17

Configure the system name. “Configuring a Second Command System” on page 55

Configure the License service. “Configuring the License Service” on page 32

Add temporary license. “Adding the Temporary Command License” on page 32

Generate an activation file for a full license. “Generate an Activation File for a Full Command License” on page 34

Add the permanent license. “Add the Permanent Command License” on page 35

Tasks Refer to...


18

Copying Install CD to Local DirectoryThe 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.

Copying Install CD to Local Directory

19

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.

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


20

Disabling Windows Media SenseWindows Media Sense must be disabled for Service Framework to function correctly.

To disable Windows Media Sense:

1. On the Command Server, start Registry Editor.

2. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\ Parameters

3. Add the following registry enter to the Parameters subkey:

Name: DisableDHCPMediaSense

Data type: REG_DWORD (Boolean)

Value: 1

n This entry controls the behavior of Media Sensing. By default, Media Sensing events trigger a DHCP client to take an action. For example, when a connect event occurs, the client tries to obtain a lease. When a disconnect event occurs, the client might invalidate the interface and routes. If you set this value to 1, DHCP and non-DHCP clients ignore Media Sensing events.

4. Restart the computer.

Installing Avid Service Framework

21

Installing Avid Service FrameworkAvid 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.

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

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.

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

Major Services Description Server Workstation

Avid Lookup Service This service enables communication between all Command and Interplay 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.


22

To install the Avid Service Framework software:

1. Insert the Command installation CD (or access the install program from the network).

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

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

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


23

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.


24

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

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

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


25

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


26

The following table includes additional applications and services that Avid strongly recommends be installed on the server—since 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.

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


27

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.

8. Click Next and follow the installation instructions to complete the installation.

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.

SNMP Gateway This service provides an interface to send health monitoring information to industry standard SNMP manager applications. It is seldom installed on the Command Server.

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

c Serious problems can occur if more than one service for time synchronization is installed.

Multicast Repeater This service is required only when a workgroup must span subnets or domains. It is seldom installed on the Command Server.

n With the exception of the Multicast Repeater, most of these minor services are turned off by default in a typical server install. If your workgroup does not span subnets or domains, you must deselect the Multicast Repeater, as shown:


28

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



Installing the License Service

29


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 21 for more information.

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


30

Then the Welcome dialog box appears.

3. Click Next.

The Destination Folder dialog box appears.

4. Do one of the following:

t Accept the default location for the destination folder by clicking Next.


31

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


32

6. When the InstallShield Wizard Completed dialog box appears, click Finish.

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.


33

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.


34

6. Click Apply.

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

To generate an activation file:

1. Open the Service Configuration application.


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.


35

6. Review and edit the required information, as well as contact information, if necessary. You can also add comments.

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



5. On the Allow Unrestricted Security dialog, click Yes.

6. Click the Add License File button.


36

The Add Licenses dialog box appears.

7. Select the full Command license file, and click Add Licenses.

Your licensing configuration details will appear and replace the temporary license information .

Installing Avid iNEWS Command on the Server

37

8. Click Apply.

9. Restart the Avid License service.

n To verify that an installed service is running, you must use the Avid Workgroup Properties application.

Installing Avid iNEWS Command on the ServerThis 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.

n If you are upgrading, open Avid Workgroup Properties and stop all services first and then close the application when you’re done.

To install the software on a Command Server:





38

2. Click the Avid iNEWS Command button. If Avid Service Framework is not already installed, a warning dialog box will appear.


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


39

4. Read the License Agreement, accept the terms, and click Next.

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


t Click Change to designate an install directory, and then click Next.

t Accept the default location by clicking Next.


40


6. Select Server Installation and click Next.

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.


41

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


42

n 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 device—up to five possible per server—by clicking the plus [+] next to that service and selecting more. By default, this device service is not installed.

n 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. 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 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 service. This service will require some configuration after installation on each Command Server. For more information, see “Configuring Avid Interplay Agent Services” on page 51.

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

n The Deko Renderer service does not take up a HASP license seat.

8. Click Next.


43

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.


44

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 services—such 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.

n Click the Reset button to restore to password to the default “blank” password.


45

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:


2. On the Hosts tab, navigate to and select the Avid Time Synchronization Service.


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.

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


46

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 User’s Guide.

To configure the AirSpeed device services:


2. On the Hosts tab, navigate to and select the AirSpeed Device Service.


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.

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


47

2. Set Control Configurations to Local/Network Record or Play. It is the only configuration supported with Command.

n Avid recommends that you do not use VDCP to control AirSpeed video servers.Unrestricted VDCP is not supported for on-air broadcasting.

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 connector’s 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:

113

1425

Pins # Wire Color Signal

1 Not used —

2 Red TxD+

3 Yellow RxD+

4 - 13 Not used —

14 Green TxD-

15 Not used —

16 Black RxD-

17 - 25 Not used —


48

This table is for cabling with a Sony-standard, 9-pin, male-ended connector (shown) to the video server:

n Video pinouts are manufacturer specific, but in all tested devices, they used the Sony standard wiring provided in this section.

15

69

Pins # Wire Color Signal

1 Not used —

2 Black RxD-

3 Red TxD+

4 - 6 Not used —

7 Yellow RxD+

8 Green TxD-

9 Not used —


49

The following wiring diagram is for a serial connection between Command (DB25) and an Omneon Spectrum media port 4101 and 4102 (shown) using R-45 wires.

For serial connections not specifically covered in this section, the follow table applies:

DB-25 Video Server

Rx+ Tx+

Rx- Tx-

Tx+ Rx+

Tx- Rx-


50

Configuring Avid Video Device Services (for VDCP)

The Avid iNEWS Command user interface allows you to control some third-party video devices via Video Disk Control Protocol (VDCP). For the interface to work, however, it’s important to confirm that the device is set to VDCP control. Also, some configuration is required, using the Avid Service Configuration and Avid Workgroup Properties applications of Avid Service Framework. For more information about these applications, see the Avid Service Framework User’s Guide.

To configure the Avid Video device services:


2. On the Hosts tab, navigate to and select the Avid Video Device Service.


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.

5. Leave the Frame rate setting as is and the Drop Frame check box selected.

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


51

n If the Avid Video device service is configured with playback channels only (no inventory port), you will not see the device’s 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.

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





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

n If using the Avid Video device service to control an Omneon, and if you want to use Command’s system setting, Hold Last Frame—the default for which is five seconds—you 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.

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.

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 User’s Guide.


52

To configure Interplay Agent services:


2. On the Hosts tab, navigate to and select the Avid Interplay Agent Service.


4. If the Allow Unrestricted Security dialog box appears, click Yes.

5. On the Settings tab, enter the following information:

a. Server Name - This is the name of the asset manager server also known as the Interplay Server running the Interplay Administration application.

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

c. User Name - This should be the Avid Interplay administrator’s user name, not the Command administrator’s user name.

d. Password - This should be the Avid Interplay administrator’s password, not the Command administrator’s password.



53

n On systems with multiple Command Servers, you must configure the Avid Interplay Agent service on each of them.

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:


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:

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


54

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.

Configuring a Second Command System

55

Configuring a Second Command SystemA 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.

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


56

6. Select File > Save.

7. Close all workstation sessions and restart all Command and Avid Service Framework services on that computer.

n The commandsystemname.xml file must be changed on all computers that are part of the second Command system.

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 allows you to 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 Stream’s 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.


• Checklist: Installing the AirSpeed Multi Stream


• 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


58

Checklist: Installing the AirSpeed Multi StreamEnsuring 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.

After installation, some configuration is required. For more information, see “Checklist: Configuring the AirSpeed Multi Stream” on page 64.

n 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 workgroup—the same workgroup as the Command servers. The AirSpeed Multi Stream device service can be configured to be controlled by up to two Command systems.

Tasks Refer to...

Rack, cable, and connect the Multi Stream to the network.

The documentation that came with your Avid AirSpeed Multi Stream for more information.

Install the core components of Avid Service Framework on the Multi Stream.

“Installing Avid Service Framework” on page 59

Install the Multi Stream software. The documentation that came with your Avid AirSpeed Multi Stream for more information.

Install AirSpeed Multi Stream device service from the Avid iNEWS Command software installation CD.

“Installing AirSpeed Multi Stream Device Services” on page 62


59

Installing Avid Service FrameworkEach 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.

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



60

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


61

entered during other Avid Service Framework installations. Later, you’ll configure a secondary workgroup for the AirSpeed Multi Stream device service, which will be the Command workgroup.


7. Click Next.


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


62

Installing AirSpeed Multi Stream Device ServicesThe Command installation CD provides for installation of services associated with various production devices, such as the AirSpeed Multi Stream.

n Unlike other device services, the AirSpeed Multi Stream device service is not part of the Command installation program. It’s a separate install program, located on the CD.

To install the AirSpeed Multi Stream device service on the Multi Stream:


2. Navigate to and double-click on AvidAirSpeedMultiStreamDeviceService.exe.

3. After the Welcome dialog box appears, click Next. The License Agreement appears.


If you do not accept the terms, the installation program will not continue.

n You can print the terms if you want to read them later or keep a copy for your records.


Installing AirSpeed Multi Stream Device Services

63

A progress bar is provided to show the current status of the installation.


To verify that installed services are running, you must use the Avid Workgroup Properties application.


64

Checklist: Configuring the AirSpeed Multi StreamFor 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.

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

“Configuring Properties for Interplay Workgroup” on page 65

Configure the AirSpeed Multi Stream device service.

“Configuring the AirSpeed Multi Stream Device Service” on page 66

Configure the properties for the Command workgroup if Command will be used to control the AirSpeed Multi Stream for playback.

“Configuring Properties for Command Workgroup” on page 68

Add the AirSpeed Multi Stream to the list of devices and channels in Command. Also, add the channels to a channel group in Command.

The Avid iNEWS Command Administration Guide

Configuring Properties for Interplay Workgroup

65

Configuring Properties for Interplay WorkgroupAirSpeed 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 workgroup—the same workgroup as the Command Servers. See “Configuring Properties for Command Workgroup” on page 68 for more information.

To configure the properties for the Interplay Workgroup on the AirSpeed Multi Stream:


2. On the Lookup tab, select the Interplay workgroup listed in the Workgroup section.

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


66

4. Enter the fully qualified domain name of the server running the Lookup service for the workgroup.



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.



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:


2. On the Hosts tab, navigate to and select the AirSpeed Multi Stream Device Service.


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.

Configuring the AirSpeed Multi Stream Device Service

67

An example of these settings is shown in the following graphic.

7. Click Apply.

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


68

Configuring Properties for Command WorkgroupAirSpeed 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 workgroup—the 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.

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


2. On the Lookup tab, click the Add button under the Workgroup section—the far left button at the bottom.

Configuring Properties for Command Workgroup

69


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


70


6. Enter the fully qualified domain name of the server running the Lookup service for the Command workgroup.



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.



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.


• System Architecture

• Checklist: Installing the Deko


• 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 Environments in Command


72

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

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

System Architecture

73

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

Avid iNEWS • SYSTEM.MOS-MAP equates the MOS ID with the channel group in Command

• SYSTEM.MAP associates the newsroom rundown with the channel group and assigns a style

Avid Deko Select Used to choose the channel number and style for an item that is dragged into the newsroom rundown.

Avid iNEWS Command • Creates channel groups

• Creates graphic environments (also known as styles in Deko) for standalone playlists

• Sends playout control commands to the Avid Deko device

Avid Deko • Inventory is copied from this device to the DekoMOS Gateway.

• Deko software provides graphics for on-air playout.

DekoMOS Macro Server • 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


74

Checklist: Installing the DekoEnsuring 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.


After installation, some configuration is required. For more information, see “Checklist: Configuring the Deko” on page 87.

For more information on installation of the Avid Deko Select plug-in, see “Setting up the Plug-ins in iNEWS” on page 155.

Tasks Refer to...

Connect the Deko to the network. The documentation that came with your Avid Deko for more information..

Install the Deko software.

Install the core components of Avid Service Framework on the Deko.


Install Deko device service from the Avid iNEWS Command software installation CD.

“Installing Avid Deko Device Service” on page 79

Install the DekoMOS Gateway. This requires a dongle.

“Installing the DekoMOS Gateway” on page 85

Install DekoMOS Macro Server on the Deko. “Installing the DekoMOS Macro Server” on page 86


75

Installing Avid Service FrameworkEach 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:






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


76


3. Click Next.


n If space is a concern on the C drive, install in the D:\Avid\Service Framework\ directory. You will need to create these directories.


77



5. Type the name of the Command workgroup in the field.


6. Click Next.


78


7. Select the option: Avid Interplay Framework Client Install and click Next.


Installing Avid Deko Device Service

79

By default, the Interplay 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 21.




Installing Avid Deko Device ServiceThe 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:




80








81





n If space is a concern on the C drive, install in the D:\Avid\iNEWS Command\ directory. You will need to create these directories.





82

6. When the Options dialog box opens, select Avid Deko.

The Custom Setup dialog box will appear.


83

n 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 computer’s destination drive has enough disk space available to install the current selection of features.

7. Click Next.


84



To verify that installed services are running, you must use the Avid Service Framework Workgroup Properties application.

Installing the DekoMOS Gateway

85

Installing the DekoMOS GatewayThe 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

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

t 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 computer’s 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.


86

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

t 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 ServerThe 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 device’s 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.

Checklist: Configuring the Deko

87

Checklist: Configuring the DekoFor 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.


Tasks Refer to...

Configure the DekoMOS Gateway. “Configuring the DekoMOS Gateway” on page 88

Configure the DekoMOS Macro Server. “Configuring the DekoMOS Macro Server” on page 95

Configure the styles in the DekoMOS Macro Server.

“Configuring Styles on the DekoMOS Macro Server” on page 96

Configure Avid Workgroup Properties for the Deko.

“Configuring Avid Workgroup Properties” on page 98

Configure the Deko device service. “Configuring the Deko Device Service” on page 100

Add the MOS-IDs for Command channel group(s) to the SYSTEM.MOS-MAP story in Avid iNEWS.

“Editing the SYSTEM.MOS-MAP Story” on page 154

(Optional) If you intend to use standalone playlists in Command or use the Avid Deko Select plug-in with ENPS and Avid iNEWS Command, create the same styles—configured in the DekoMOS Macro Server—as graphic environments in Command.

“Creating Graphic Environments in Command” on page 102


88

Configuring the DekoMOS GatewayTemplates 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.

n 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 User’s 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 taskbar’s 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 Click the Configure button.

t Press Alt+C.

Configuring the DekoMOS Gateway

89

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

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

n In most cases, these are left at the default settings. The remaining settings on the General tab can also be left at the defaults.


90

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.

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

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


91

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.

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

13. Click OK to return to the DekoMOS Gateway Configuration dialog box.


92

14. Select the Reject items with unknown Gateway IDs check box unless you are using 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 Setting Graphic Browsers to <manual> enables the Deko Select plug-in for manual entry of replaceable graphic names or numbers.


93

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.

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

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.


94

All newsroom computer system workstations will locate the elements for display in these folders.

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

Configuring the DekoMOS Macro Server

95

Configuring the DekoMOS Macro ServerTo configure the DekoMOS Macro Server:


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.

t Double-click the desktop icon.

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

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.

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.


96

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.

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:


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.

t Double-click the desktop icon.

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

The DekoMOS Macro Server window appears.

Configuring the DekoMOS Macro Server

97

2. Click the Styles button.

The Deko Style Settings dialog box opens.

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:

t Click the Refresh Styles List button in the Deko Style Settings window.


98

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.





99

6. Enter the full domain name of the server running the Lookup service for the workgroup, such as: cmdsvr1.avidbroadcast.com.



9. Click OK.

10. Repeat steps 5 - 9 to add another server running the Lookup service for the workgroup.




100

Configuring the Deko Device ServiceAfter 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 User’s Guide.

To configure the device service:


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. Avid recommends single channel mode.

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





Configuring the Avid Deko Renderer Service

101

Configuring the Avid Deko Renderer ServiceThe 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.

n The Deko Renderer service does not take up a HASP license seat.

To configure Deko Renderer services:


2. On the Hosts tab, navigate to and select the Avid Deko Renderer Service.


4. If the Allow Unrestricted Security dialog box appears, click Yes.

On the Settings tab, you’ll see the service set to Automatically.


102

5. Select Manually.

6. Enter the host name or IP address for the DekoMOS Gateway computer.


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

Creating Graphic Environments in CommandGraphics environments are known as styles in Avid Deko software.

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 environments in Command that match the styles configured on the DekoMOS Macro Server.

To add an environment:

1. Select Tools > System Settings.

Creating Graphic Environments in Command

103

2. Select Playlist.

3. Click the Add button. An environment will appear in the Environments list as shown:

4. By default, the name of any added environment is Environment, but that can be changed. To do so, double-click on the name in the list and retype the new name.

5. After multiple environments are added, use the Default environment 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 environments, known as styles, see the Avid Deko Select User’s Guide.


104

n The set of graphics environments 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 environment list (shown in the previous graphic), the Default graphics environment 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 208), and in the Playlist Properties dialog box.

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.


• Checklist: Installing and Configuring the Thunder


• Installing Avid Thunder Device Service


• Configuring the Thunder Device Service

• Configuring the Thunder

• Creating the ThunderMOS.cfg File

• Creating the ThunderMOS.ini File


106

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.


Tasks Refer to...

Connect the Thunder to the network. The documentation that came with your Avid Thunder for more information.

Install the Thunder software.

n 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 User’s 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.

“Installing Avid Thunder Device Service” on page 111

Configure Avid Workgroup Properties for the Thunder.

“Configuring Avid Workgroup Properties” on page 117


Configure the Thunder device service. “Configuring the Thunder Device Service” on page 119

Configure the Thunder. “Configuring the Thunder” on page 120

Create the ThunderMOS configuration file. “Creating the ThunderMOS.cfg File” on page 122

Create the ThunderMOS.ini file. “Creating the ThunderMOS.ini File” on page 123


107










108


3. Click Next.




109





6. Click Next.


110




Installing Avid Thunder Device Service

111





Installing Avid Thunder Device ServiceThe 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:




112








113






114




6. When the Options dialog box opens, select Avid Thunder.

The Custom Setup dialog box will appear.


115



116

7. Click Next.



To verify that installed services are running, you must use the Avid Workgroup Properties application.


117

Configuring Avid Workgroup PropertiesIf 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.





118

6. Enter the full domain name of the server, such as: cmdsvr1.avidbroadcast.com.



9. Click OK.

10. Repeat steps 5 - 9 to add another Command Server if necessary.



Configuring the Thunder Device Service

119

Configuring the Thunder Device ServiceAfter 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 User’s Guide.

To configure the device service:


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


120




12. After the Avid Services dialog box opens, select the Avid Thunder device service, then stop and restart it.

Configuring the ThunderConfiguring 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.

Configuring the Thunder

121

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.


122

Creating the ThunderMOS.cfg FileIf 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 Thunder’s C drive create a folder called ThunderCFG, if one doesn’t already exist, and ensure it is shared across the network for read access.

Only one cfg file is necessary per iNEWS newsroom computer system.

n 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 Thunder’s arbitrary name and the full UNC path to the Thunder database as they might appear in the Thunder Select plug-in:

Creating the ThunderMOS.ini File

123

n 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 FileIf 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 Thunder’s 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>


124

Your finished ThunderMOS.ini file might look like this:

4. Save the ThunderMOS.ini file.

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.


• Checklist: Installing the Command Workstation


• Installing Avid iNEWS Command on the Workstation


• Setting up Device Channels

• Setting up Channel Groups


126

Checklist: Installing the Command WorkstationComplete 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. “Installing Avid iNEWS Command on the Workstation” on page 131

Configure Avid Workgroup Properties. “Configuring Avid Workgroup Properties” on page 137


Map the actual channels for the various production devices, such as Deko character generators or AirSpeed video servers, to names.

“Setting up Device Channels” on page 139

Create channel groups. “Setting up Channel Groups” on page 142


127










128


3. Click Next.




129





6. Click Next.


130




Installing Avid iNEWS Command on the Workstation

131






This section provides the standard procedure for installing the Command software on a Windows-based computer—Windows XP SP2, Windows Vista, or Windows Server 2003—designated as a Command Workstation.

To install the software on a Command Workstation:


The InstallShield Wizard starts and displays the Welcome screen.

2. Click Next.


132

The License Agreement appears.





133






134


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.


135



136

6. Click Next.



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


137


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.




138


6. Enter the full domain name of the server running the Lookup service, such as: cmdsvr1.avidbroadcast.com.



9. Click OK.

10. Repeat steps 5 - 9 to add another server running the Lookup service.



Setting up Device Channels

139


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 142. Also, see “Mapping Indices to Channel Names” on page 174 and “Programming the X-keys” on page 175 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.


140

5. Click Add.

6. Enter the channel’s name, which can be any alpha-numeric character(s), based on the following guidelines:

Device TypeChannel Index

Channel Name Description

n All channel names within a single device type must be unique.

Deko 0 1 Avid Deko devices begin channel designations at zero (0); however, the name of the first channel can be one.

Deko 1 2

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

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

AirSpeed 3 B

VDCP 1 A 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.

VDCP 2 B

Thunder 1 aPlay 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).Thunder 2 bPlay

n Avid recommends against using numeric names for the Thunder to avoid confusion with channel names for any Avid Deko device.


141

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.

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



13. Enter the administrator password and click OK.

Until this procedure is completed, device channels cannot be added to a channel group.

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

Multi Stream 1 A 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.

Multi Stream 2 B

Multi Stream 3 C

Multi Stream 4 D

Multi Stream 5 E

Multi Stream 6 F

Device TypeChannel Index

Channel Name Description


142

Setting up Channel GroupsA 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.

n 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.) Let’s call the first AirSpeed AS1 and the second AS2. With channel groups on Command, the station’s system administrator can set up numerous different channel groups and call them anything, such as:

Channel GroupChannel Names Actual Device Channels Channel Type

AS-Noon A

B

C

AS1 - channel 2

AS1 - channel 3

AS2 - channel 2

Playout

Playout

Browse

AS-5PM A

B

C

D

AS1 - channel 2

AS1 - channel 3

AS2 - channel 2

AS2 - channel 3

Playout

Playout

Playout

Playout

AS-10PM A

C

B

D

AS1 - channel 2

AS2 - channel 2

AS1 - channel 3

AS2 - channel 3

Playout

Mirrored

Playout

Mirrored

Setting up Channel Groups

143

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.


144

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

n The first eight (8) characters of a channel group’s 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:


2. Expand Channel.

3. Select Groups.


145

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 group’s name less than eight characters.

6. Click Add to add a channel to the group.

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


146

7. In the Channel Detail section, select the following:

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.




c Until the Apply or OK button is clicked and administrator password supplied, the channel group(s) are not created.

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 Select the channel designated as the primary playout channel for the device.

Mirrored (Optional) If mirrored playout is to be used, select the device’s channel designated for mirrored playout.

Preview (Optional) Select which device channel to use for displaying the headframe of the next media event in the playlist.


147

To edit a channel group:


2. Expand Channel.

3. Select Groups.

4. Select the channel group from the list on the right.

5. Click Edit.


148

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.




149


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


2. Expand Channel.

3. Select Groups.

4. Select the channel group from the list on the right.

5. Click Delete.



150



c Until the Apply or OK button is clicked and administrator password supplied, the channel group(s) are not deleted from the system settings.

6 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 system’s administrative features.


• Editing the SYSTEM.MAP Story

• Editing the SYSTEM.MOS-MAP Story

• Setting up the Plug-ins in iNEWS

• Monitor Servers

• Queue Properties


152

Editing the SYSTEM.MAP StoryIn 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 161.

Here is an example of settings for Command as they might appear in the Map story:

The first line is a comment—as indicated by the semicolon—that 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 User’s Guide.

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

;NRCS.SHOWS.RUNDOWN USES MONITOR 292

nrcs.shows.rundown nrcs.shows - monitor D200

wnasvr cmdsvr1 cmdsvr2 ca-composite

CG Deko1 - 1 6pm;Deko Device Channels

video AB - A;AirSpeed Device Channels

Editing the SYSTEM.MAP Story

153

The third line contains the following server information:

• Server type - wnasvr specifies a Command Server.

• Primary server’s name, such as nrcs1, which is the computer running the Avid iNEWS Communication service.

• Backup server’s 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 device’s 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.


154

Editing the SYSTEM.MOS-MAP StoryThe 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:

The first line is the header. The second and third lines are comments—as indicated by the semicolons—that 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 88.

• The channel group for the Deko, such as CG1. This, too, must match the channels IDs assigned and configured on the DekoMOS Gateway.

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

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

TABLE-START DeviceTable ;MOSID AMCPDeviceName ;==============================

DEKO1 CG1

MOSIDTHDR_A Thunder

Setting up the Plug-ins in iNEWS

155

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.

Setting up the Plug-ins in iNEWSUsing 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 workspace—shown on the title bar—is 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.

n If both Thunder and Deko plug-ins are being installed on an iNEWS Workstation, Avid recommends the Thunder service be installed first.


156

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

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 doesn’t, click the Options button in the top right corner of the plug-in.


157

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.

9. Enter the Dongle ID and Dongle Password. If your Thunder system is a:

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

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

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


158

11. Click the Options button again.


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

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.


159

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 it’s not already selected.


160

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-in’s 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.

Monitor Servers

161

Monitor ServersMonitor server is a utility program—running on the iNEWS newsroom computer system—that checks a show’s 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 numbers—typically, 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 system’s configuration file. The mailbox number must be assigned to both the show’s monitor server and its rundown queue.

n 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 queue—the one sharing the same mailbox number—while 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 rundown’s 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 system’s server programs, such as 201 to 300.

Valid standard mailbox numbers are 1 through 4096.


162

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:

n For other list command options for determining mailbox assignments of queues and servers, see “Using the list Command to View Assigned Mailboxes” on page 165.

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.

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

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 Server—such as server A and server B in a dual server system— by doing the following:

c Always back up the /site/config file before making any changes.

a. At the console, select all iNEWS Servers.

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

DEV DEVICE_TYPE COMPUTER CCU PRINTER SPEED OPTIONS DEVNAME

Monitor Servers

163

c. Add the monitor server’s 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.

n 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 step 3c, 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>

Comments appearing after the semicolons (;) are optional.

The following are sample configuration lines for monitor server programs:

Parameter Description

device # The device number assigned to the server program. This 3-digit number must also be listed in the servers line in a host definition.

type The type of server program is monitor.

mailbox The mailbox the server program uses. Valid standard mailbox numbers are 1 through 4096. This number typically matches the server program’s device number.

device name Monitor servers do not use a device name; enter a hyphen (-).

server 264 monitor 264 - ;monitor server





164

e. When you finish making changes to the configuration file, save your changes by typing:

w

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

n 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 User’s Guide for more information on using monitor servers.

Mailboxes are assigned to queues in the same way other database traits are—using the Queue Properties dialog box. For more information, see “Queue Properties” on page 166.

6. After you choose the monitor server’s mailbox number and verify that it is not used by another device, you must also assign it to the show’s rundown queue, being monitored by the monitor server.

For instance, if the monitor server’s 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.

Monitor Servers

165

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:

t Type: list c monitor

The system displays configuration information for your system’s monitor servers, similar to the following:

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 Use the following format: list mailbox=<mailbox number> c

To check whether mailbox 267 is assigned to a server program:

t Type: list mailbox=267 c

Two rundowns queues can share the same mailbox, but they should never be monitored simultaneously.

c If two rundowns share the same mailbox number, ensure that both their monitor servers do not run simultaneously; otherwise, results could be unpredictable.

DEV DEVICE_TYPE COMPUTER CCU PRINTER SPEED OPTIONS DEVNAME

S264 monitor A N264

S265 monitor B N265

S266 monitor A N266

S267 monitor B N267

NRCS-A$


166

Queue PropertiesTo 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

Queue Properties

167

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


168

On the User Interface tab, ensure that the Refresh option is selected to enable automatic updates from Command.

7 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 software’s graphical user interface, while others choose to use USB or GPI keypads.


• Controling Playout via the User Interface

• Disabling a Command Workstation’s 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


170

Controling Playout via the User InterfacePlayout 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 User’s Guide.

Controling Playout via the User Interface

171

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:

There is no special installation or configuration needed to use the software’s 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.


t Press the Decimal key (.) to cue the media.

t Press Enter to play the media.

t Press the Plus key (+) to pause the media.

t Press zero (0) to stop playing the media.

n 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 User’s Guide.

Icon representing a “Follow-On Playout” event.

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.


172

Disabling a Command Workstation’s KeyboardSome 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.


t Select Enable keyboard.

t Deselect Enable keyboard.

4. Click Apply.

5. Click OK.

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

Checklist: Setting up an X-keys USB Keypad

173

Checklist: Setting up an X-keys USB KeypadAvid 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.

n 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 manufacturer’s 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 Workstation.

“Disabling a Command Workstation’s Keyboard” on page 172

Install the keypad on the Command Workstation. “Installing an X-keys USB Keypad” on page 174

Map Indices to Channel Names. “Mapping Indices to Channel Names” on page 174

Program the keypad. “Programming the X-keys” on page 175


174

Installing an X-keys USB KeypadTo install an X-keys USB keypad:

t Plug in the keypad to a USB port on your Command Workstation.

Mapping Indices to Channel NamesChannel 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.


Programming the X-keys

175

3. Expand Channel.

4. Select Indices.

5. Enter the channel’s name in the Name column next to the appropriate index.

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


Programming the X-keysThe 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.


176

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

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

Programming the X-keys

177

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

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


178

Checklist: Setting up the GPI PanelA 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.


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

Configure the GPI card. “Configuring the GPI Card” on page 179

Restart the GPI device service. “Restarting the GPI Device Service” on page 182

Confirm proper setup of the GPI. “Confirming Successful Setup of a GPI Panel” on page 183


Map GPI events to actions. “Mapping Events to Actions for a GPI Panel” on page 184

Enable the GPI panel for playlist control. “Enabling the GPI Panel” on page 190

Configuring the GPI Card

179

Configuring the GPI CardConfiguring the GPI card is done using the Avid Service Configuration application. The procedure is covered in this section.

To define the GPI card’s 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.

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


180

4. Select the Board Type—the 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.

Configuring the GPI Card

181

14. Select the type of event. Options include:

15. Enter a name for the event.

16. Click OK.

17. Repeat steps 14 through 17 to continue pin assignment.

n For redundant systems, to ensure identical functionality, make certain that the device settings—all input pins and event names and types—are the same for every GPI Device service installed.

18. Click Apply.

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.

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

Toggle 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 position—up to down or down to up.


182

19. After modifying the GPI Device service system settings, restart the service.

Restarting the GPI Device ServiceAfter 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.

n Avid also recommends restarting the client software at the Command Workstation.

Confirming Successful Setup of a GPI Panel

183

Confirming Successful Setup of a GPI PanelThis 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.


184

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 there’s 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.

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

n If the switcher is wired to the GPI panel, test that, too.

Mapping Events to Actions for a GPI PanelMapping 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.

n For more information on mapping GPI events for selection-based playout, see page 187.

To map GPI events to channel-specific actions:



Mapping Events to Actions for a GPI Panel

185

The System Settings dialog box appears.

3. Select GPI.

4. Expand the panels to view each panel’s events.

5. Double-click on an event to map it to an action.


186

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.


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

n 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

n The Cue channel action only recues the item that is playing. Cueing a different item in the playlist must be done manually—via mouse, keyboard, or X-keys—or a GPI button must be mapped and enabled for selection-based playout.

7. Click OK.

8. Repeat steps 5 through 7 as needed.


187



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:



3. Select GPI.




188


6. Navigate to the Playlist action and expand it.


189

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

n If you program the GPI panel for these selection-based actions, you must enable the GPI panel at the workstation.

7. Click OK.







190

Enabling the GPI PanelThe 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.

n This procedure does not apply to GPI panels (or Maney panels) with events mapped only to actions chosen in GPI > Control—such as Cue, Pause, Play, or Stop—because 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.

Checklist: Setting up the Maney Panel

191

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.

Checklist: Setting up the Maney PanelA 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.

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


192

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.


n 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 193

Restart the Maney panel device service. “Restarting the Maney Panel Device Service” on page 196

Confirm proper setup of the Maney panel. “Confirming Successful Setup of a Maney Panel” on page 196


Map Maney panel events to actions. “Mapping Events to Actions for a Maney Panel” on page 199

Configuring the PCI Card for a Maney Panel

193

Configuring the PCI Card for a Maney PanelConfiguring 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.

n 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 card’s board settings:

1. Determine the PCI card’s 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.)

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


194

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.

Configuring the PCI Card for a Maney Panel

195

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 event’s 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.

n For redundant systems, to ensure identical functionality, make certain that the device settings—all input pins and event names and types—are the same for every device service installed.

13. Click Apply.

14. After modifying the Maney panel’s device service system settings, restart the service.


196

Restarting the Maney Panel Device ServiceAfter 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.

n Avid also recommends restarting the client software at the Command Workstation.

Confirming Successful Setup of a Maney PanelThis 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.


2. Navigate to the Avid Maney Panel Device Service and select it.

Confirming Successful Setup of a Maney Panel

197

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 there’s 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.

n The time it takes Health Monitor to report a Maney panel event is slower than the response of Command to that Maney panel input.


198

The Information section will appear similar to the following example:

5. Press a number of buttons to make sure they all work.

n If the switcher is wired to the Maney panel, test that, too.

Mapping Events to Actions for a Maney Panel

199

Mapping Events to Actions for a Maney PanelAfter 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:



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.





200

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


7. Click OK.



Mapping Events to Actions for a Maney Panel

201





202

8 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 system’s administrative features.

n ENPS is third-party software. Refer to the manufacturer’s documentation for more detailed information regarding the newsroom computer system.


• Configuring ENPS

• Configuring MOS Settings in Command

• Configuring Command for MOS Redirection


204

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 folder—fourth from the left—is typically labeled with your station call letters or corporate name. By default, it is labeled ENPS.

3. Select System Maintenance > Groups.

Configuring ENPS

205

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. Enter a description.

b. Select the server. This should be the primary ENPS server.

7. Click Save.

8. Click the green Rover button on the Corporate folder again.


206

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

12. Click OK. A new row appears in the list.

Configuring ENPS

207

13. On that row, fill in the fields as shown in the following table:

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

Text Box Name Description

Description Enter the name that identifies this plug-in for users.

IP Enter the IP address of the Command Server running the MOS Communication service.

ActiveX Enter the ActiveX Application ID. This is usually DekoMOS.Browser. (Don’t forget the period between DekoMOS and Browser.)

Program Select the group you created in step 5 on page 205.

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

Modal UI ActiveX Enter the ActiveX Application ID. This is usually DekoMOS.Browser. (Don’t forget the period between DekoMOS and Browser.)

Auto Create Ensure the auto create field is enabled.

Object Type Set the object type to VIDEO.


208

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 server’s media inventory. Command’s 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 environment settings.

• Channel Groups - used to identify channel groups for integration with MOS-based newsroom computer systems.

• Advanced - used for advanced MOS feature configuration.

n Avid strongly recommends contacting Customer Support before altering any of the advanced settings.

To configure Command’s 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.


209

4. Edit the MOS settings accordingly:

MOS Setting Description

iNEWS Command MOS ID

The ID that enables enables bidirectional communications between a MOS-based newsroom computer system and Command. For instance: avid.command1.mos or avid.command2.mos

Newsroom NCS ID Usually, this is set to the host name of the newsroom computer system’s server.

Newsroom Host Name Host name of the newsroom computer system’s 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 Usually, this is set to host name of the newsroom computer system’s “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.


210

5. Set the default graphics environment for playlists loaded from a MOS-based newsroom computer system, if necessary.

Graphics environments, known as styles in Avid Deko, 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.

Buddy Host Name Host name of the newsroom computer system’s “buddy” or backup server.

MOS version Determines which version of MOS protocol Command will use.

MOS Setting Description (Continued)


211

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



212

To view advanced MOS 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.

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

Configuring Command for MOS Redirection

213

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.

To configure Command for MOS redirection:

1. Click the Start button and select Programs > Avid > Service Framework > Avid Interplay Service Configuration.

2. On the Hosts tab, navigate to and select the Avid MOS Communication Service running on the backup server.

3. Enter the MOSID for the backup server.

4. 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 more information, see documentation that came with your third-party ENPS system.


214

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


• Monitoring System Status

• Viewing Status of Services

• Confirming Command Inventory

• Testing Workflow


216

Monitoring System StatusAfter 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.


2. Confirm that no problems are reported. Any problems on the system will appear with a red X.

Viewing Status of Services

217

Viewing Status of ServicesAvid Command uses Avid Service Framework as its structure for discovering and communicating with services.

To start Workgroup Properties:

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


218

The Workgroup Properties application uses colored icons—in combination with text—on 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.

For more information on viewing Avid services using the Workgroup Properties application, see the Avid Service Framework User’s Guide.

Confirming Command InventoryYou 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 media’s 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 User’s Guide.

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 sentence—All enabled services are running—is 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 sentence—Some services are enabled but not running—is 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 sentence—No services are running—is displayed.

Confirming Command Inventory

219

c If you are using VDCP and do not have an inventory port configured, you cannot confirm inventory via the Inventory panel in Command.

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


220

Testing WorkflowThe person testing the system’s 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.

n For basic user information on Avid iNEWS, iNEWS Command, or other integrated Avid products, see the User’s 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. If you use hand-entered machine control events, test that by entering some into new and existing stories.

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

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index

221

Symbols/site/config 161

AAdd Lookup Service dialog box 65Add New Event dialog box 180Add Panel dialog box 180, 194Add Workgroup dialog box 117AirSpeed

channel designations 140channel groups 142configuring device services 46, 66configuring services for thumbnails 51default device service installation 41

AirSpeed Multi Streamchannel designations 141configuration checklist 64configuring Command workgroup 68configuring Interplay workgroup 65configuring the device service 66device integration checklist 58install Service Framework 59installing the device service 62overview 57

Apply Studio Settings dialog box 146Avid

how to order documentation 10online support 10training services 11

Avid Dekochannel designations 140configure the device service 100device integration checklist 74installing device services 79styles aka environments 102

Avid Deko Renderer service 42Avid Diagnostics 26

Avid Graphics Select 155Avid Health Monitor 26, 216Avid iNEWS

configuring 151mailboxes 167Map story 152plug-ins 155queue properties 166

Avid iNEWS Communication Service 41Avid Interplay Agent Service 42Avid MOS Communication Service 41Avid Service Configuration application 21, 26Avid Service Framework

Diagnostic Log Viewer 26Email Alerter 27Lookup Service 21Machine Monitor 26Multicast Repeater 27Service Configuration 26, 32, 100, 119

starting 179, 193SNMP Gateway 27System Configuration 21Time Synchronization 27Workgroup Properties 217

Avid Thunderchannel designations 140configure the device service 119device integration checklist 106installing device services 111

Avid Unity 57Avid Video device service 42Avid Workgroup Properties 46, 51, 100, 178, 182,

196Avid_License_Setup.exe 28

BBackup server 209

Index

Index A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

222

CChannel groups

creating 144defined 142deleting 149editing 147examples of 142redundancy 143

Channel indices 174Channel-specific actions

assigning 177mapping 174

ChecklistsCommand client installation 126Command pre-installation 15Command Server installation 16Deko configuration 87Deko installation 74Multi Stream configuration 64Multi Stream installation 58setting up the GPI panel 178setting up the Maney panel 191setting up X-keys USB keypad 173Thunder integration 106

Choose Action dialog box 186, 188, 200Command

configuring second system 55monitoring system status 216pre-installation checklist 15system architecture 14viewing documentation 37

Command Serverinstallation checklist 16installing software 37

Command workgroup, configure for Multi Stream 68Command Workstation

alternative keypad device 178, 191disabling keyboard 172installation checklist 126installing software 131using X-keys 173

configuration lines, example of 163Connections tab 90Console commands

iNEWS 162list 161

variations of list 165

DDebounce Time 180Deko 71

channel designations 140configuration checklist 87configuring device services 100installation checklist 74integration checklist 74MOS ID 154system architecture 72thumbnails 85user settings 89XML storage 89

Deko Renderer, configuring the service 101Deko Select 155

installing 158DekoMOS Gateway

configuring 88installing 85Net HASP dongle 85

DekoMOS Gateway Configuration dialog box 88DekoMOS Macro Server

configuring 95configuring styles 96installing 86

DekoMos.ini file 160Destination Folder dialog box 133Device numbers 161Device services

Avid Video 42configuring 46, 66, 100configuring Deko Renderer service 101configuring for Thunder 119configuring Interplay Agent service 51

Diagnostic log viewer 26Dialog boxes

Add Lookup Service 65Add New Event 180Add Panel 180, 194Add Workgroup 117Apply Studio Settings 146Choose Action 177, 186, 188, 188, 200DekoMOS Gateway Configuration 88Destination Folder 133


223

Queue Properties 166System Settings 144, 184, 199

Digital recorder 57Documentation for Command 37dongle 85Duration 152

EEmail Alerter service 27ENPS

integration 203MOS settings 204News Object Manager 207

Event types 181, 195

FFirst Input Pin 180, 194Functionality, confirming 215

GGateway settings 160General tab 89GPI card 178GPI device

enabling the panel 190restart the device service 182

GPI eventsmapping for GPI panel 184mapping for Maney panels 199

GPI panelchecklist 178enabling the panel 190

Graphics environments 102setting default 210

HHealth Monitor 26

IIcons

DekoMOS Gateway 88

in Command playlists 171Macro Server 95NetHasp License Manager 86

iNEWS/site/config 161configuring 151ed command line editor 162list command 161mailboxes 161Map story 152SYSTEM.MOS-MAP 154

iNEWS Commandinstall on workstation 131licensing 28MOS ID 209MOS support 208

iNEWS Serversconfiguration file 161host definition 163

InstallationAvid Deko Select 158Avid Thunder Select 156Command on a server 37Command on a workstation 131determining disk space 83, 115Service Framework software on Multi Stream 59USB keypads 174

Interplay Agent service 51Interplay workgroup, configuring for Multi Stream 65Inventory panel 218

confirming media availability 218

KKeyboard

alternative keypad device 178, 191disabling 172

LLevel 181License manager 85License service 28

configuring 32Licenses

activation file 34permanent 35


224

temporary 32list command, variations of 165Lookup service 21Lookup tab, configuring 53

MMachine Monitor service 26Macro server 86Mailboxes 167

assigning to rundown queue 164defined 161valid numbers 161viewing assignments 165

Maney panel 192checklist 191configuring the PCI card 193installing the device service 42mapping events 199restarting device service 196

Map story 152Mapping GPI events to actions 184Mapping Maney panel events to actions 199Measurement Computing card 191, 192, 193MiniMon column 121Mirrored playout 146

channel groups 143Monitor LOAD command 164Monitor ON command 164Monitor servers 161

configuration lines 163form name 153listing assigned mailboxes 165

MOS ID 154MOS protocol

defaults 212described 208version 210

MOS settings 212editing 209

MOS, defined 208MOS-based newsroom configuration 203MOS-Map story 154Multi Stream

channel designations 141installation checklist 58

Multicast Repeater service 27

NNet HASP Connection Settings 90Net HASP dongle 85Net HASP License Manager 85Newsroom buddy host name 210Newsroom buddyID 209Newsroom host name 209Newsroom NCS ID 209

OOmneon 51Online support 10

PPaths 89PCI card 191, 192

mapping events 199Playlist icons 171Playlist Viewer 170Playout control 170

configuring 169Plug-ins 155Procedures

add an environment 102add the permanent license 35add the temporary license 32change system name 55checking system status 216configure a second Command system 55configure Avid Video device service (VDCP) 50configure Command for MOS-based NRCS 208configure Command workgroup properties 68configure Deko Renderer service 101configure DekoMOS Macro Server 95configure Interplay workgroup properties 65configure Lookup tab 53configure the Avid Thunder device service 119configure the Deko device service 100configure the DekoMOS Gateway 88configure the ENPS MOS settings 204configure the GPI card’s board settings 179configure the License service 32configure the Maney panel 193configure the Multi Stream device service 66


225

configure the PCI card’s board settings 193configure the Thunder 120configure workgroup properties for Thunder 117confirm GPI panel setup 183confirm Maney panel setup 196confirm running of NetHASP License Manager

86confirming inventory 218connect the New HASP Dongle 85control playout with numeric keypad 171copy install CD to local directory 18create & configure monitor server 161create channel groups 144create the ThunderMOS.cfg file 122create the ThunderMOS.ini file 123delete a channel group 149disabling Windows Media Sense 20edit a channel group 147edit the Map story in iNEWS 153edit the SYSTEM.MOS-MAP story 155enable a GPI panel to control a playlist 190enable or disable the keyboard 172generate an activation file 34install an X-keys USB keypad 174install Avid Deko Select 158install Avid Service Framework on a workstation

107, 127install Avid Thunder Select 156install Service Framework on a server 21install Service Framework on a workstation 75install Service Framework on Multi Stream 59install software on a Command Server 37install software on a Command Workstation 131install the Deko device software 79install the DekoMOS Gateway 85install the DekoMOS Macro Server 86install the License service 28install the Multi Stream device service 62install the Thunder device software 111map an index to a channel name 174map GPI events to actions 184map Maney panel events to actions 199programming X-keys 175restart the GPI device service 182restart the Maney Panel device service 196start Workgroup Properties 217test workflow 220

view advanced MOS settings 212view the Queue Properties dialog box 166

QQueue form, explained 166Queue Properties dialog box 166Quit time 152

RRedundancy

channel groups 143configuring the Lookup tab 53VDCP 42

Rover button 204

SSecondary Command systems 55Serial connections 47Server type 153Service Configuration 32Services

Avid Deko Renderer 42Service Framework 21, 26viewing status 217

Site licenses 28SNMP Gateway 27Starting

Workgroup Properties 217Story forms, explained 166system architecture 14System settings

GPI 184indices 174Maney panel 199MOS 209MOS advanced 212MOS channel groups 210Playlist 102

System Settings dialog box 144, 184, 199System status, monitoring 216SYSTEM.MAP 152SYSTEM.MOS-MAP 154


226

TTemporary Command license 32Thumbnails, installing services for 42Thunder

channel designations 140configuring device services 119integration checklist 106MOS ID 154

Thunder Select 155ThunderMOS.cfg file 154

creating the file 122ThunderMOS.ini file 123Time Synchronization service 27Toggle 181Training services 11Trigger 181Troubleshooting 10

UUSB keypad 173Utility programs 161

VVDCP

channel designations 140configuring the device service 50installing the device service 42wiring serial connections 47

Video serverchannel designations 140channel groups 142

WWindows Media Sense 20Wiring serial connections 47Workflow, testing 220Workgroup Properties 217

restarting GPI device service 182restarting Maney panel device service 196

XX-keys

channel-specific actions 177checklist 173

XML-based protocol 208