Professional Documents
Culture Documents
Capture IA
Capture IA
This product is subject to the terms and conditions of a software license agreement provided with the software. The product
may only be used in accordance with the license agreement.
Avid products or portions thereof are protected by one or more of the following United States Patents: 5,267,351; 5,309,528;
5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364;
5,654,737; 5,724,605; 5,726,717; 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,986,584; 5,999,406; 6,038,573; 6,061,758; 6,069,668; 6,141,007; 6,211,869; 6,532,043; 6,546,190; 6,596,031; 6,636,869;
6,747,705; 6,763,523; 6,766,357; 6,813,622; 6,847,373; 7,081,900; RE40,107; 7,403,561; 7,433,519; 7,671,871; D352,278;
D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912. Other patents are pending.
Avid products or portions thereof are protected by one or more of the following European Patents: 0506870; 0635188;
0674414; 0694243; 0752174; 0895623; 1111910; 1629675. Other patents are pending.
This document is protected under copyright law. An authorized licensee of [product name] 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 [product name]. Reasonable care has been taken in preparing the information it
contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology,
Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications
are subject to change without notice.
Copyright © 2010 Avid Technology, Inc. and its licensors. All rights reserved.
The following disclaimer is required by 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.
This Software may contain components licensed under the following conditions:
Copyright (c) 1989 The Regents of the University of California. All rights reserved.
2
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph
are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived from this software without specific prior written
permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission
notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission
notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.
Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the
suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Modifications Copyright 1999 Matt Koss, under the same license as above.
Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this
entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all
copies of the supporting documentation for such software.
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR,
NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
This product includes software developed by the University of California, Berkeley and its contributors.
Manufactured under license from the Georgia Tech Research Corporation, U.S.A. Patent Pending.
“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.”
3
The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample
Source Code:
©1993–1998 Altura Software, Inc.
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.
Trademarks
003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II,
Assistant Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA,
Avid DNxcel, Avid DNxHD, Avid DS Assist Station, Avid Liquid, Avid Media Engine, Avid Media Processor, Avid MEDIArray,
Avid Mojo, Avid Remote Response, Avid Unity, Avid Unity ISIS, Avid VideoRAID, AvidRAID, AvidShare, AVIDstripe, AVX,
Axiom, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Boom, Bruno, C|24,
CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor,
Command|24, Command|8, Conectiv, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, Dazzle,
Dazzle Digital Video Creator, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 003, DigiBase, DigiDelivery,
Digidesign, Digidesign Audio Engine, Digidesign Development Partners, Digidesign Intelligent Noise Reduction,
Digidesign TDM Bus, DigiLink, DigiMeter, DigiPanner, DigiProNet, DigiRack, DigiSerial, DigiSnake, DigiSystem,
Digital Choreography, Digital Nonlinear Accelerator, DigiTest, DigiTranslator, DigiWear, DINR, DNxchange, DPP-1, D-Show,
DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, Euphonix, EUCON, EveryPhase, Expander,
ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase,
FXDeko, HD Core, HD Process, HDPack, Home-to-Hollywood, HYBRID, HyperControl, HyperSPACE, HyperSPACE HDCAM,
iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, Instantwrite, Instinct,
Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat,
Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, ISIS, IsoSync, iS9, iS18,
iS23, iS36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi,
Luna, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack,
Massive Pack Pro, M-Audio, M-Audio Micro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMatch, MediaMix,
Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MicroTrack, MIDI I/O, Midiman,
Mix Rack, MixLab, Moviebox, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, Nitris, NL3D, NLP, Nova,
NRV-10 interFX, NSDOS, NSWIN, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework,
Open Media Management, Ozone, Ozonic, Painterly Effects, Palladium, Personal Q, PET, Pinnacle, Pinnacle DistanTV,
Pinnacle GenieBox, Pinnacle HomeMusic, Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle Scorefitter, Pinnacle Studio,
Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle VideoSpin, Podcast Factory, PowerSwap, PRE, ProControl,
ProEncode, Profiler, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, Pro Tools, QuickPunch, QuietDrive,
Realtime Motion Synthesis, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, Reprise, Res Rocket Surfer,
Reso, RetroLoop, Reverb One, ReVibe, Revolution, rS9, rS18, RTAS, Salesview, Sci-Fi, Scorch, Scorefitter, ScriptSync,
SecureProductionEnvironment, Serv|LT, Serv|GT, Session, Shape-to-Shape, ShuttleCase, Sibelius, SIDON, SimulPlay,
4
SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, Solaris, SoundReplacer, SPACE,
SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, Strike, Structure,
Studiophile, SubCap, Sundance Digital, Sundance, SurroundScope, Symphony, SYNC HD, Synchronic, SynchroScope,
SYNC I/O, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, Titansync, Titan, TL Aggro, TL AutoPan, TL Drum Rehab,
TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, tools for storytellers, Torq,
Torq Xponent, Transfuser, Transit, TransJammer, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet,
Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, VTEM, Work-N-Play, Xdeck, X-Form, Xmon, XPAND!, Xponent,
X-Session, and X-Session Pro are either registered trademarks or trademarks of Avid Technology, Inc. in the United States
and/or other countries.
Footage
Arri — Courtesy of Arri/Fauer — John Fauer, Inc.
Bell South “Anticipation” — Courtesy of Two Headed Monster — Tucker/Wayne Atlanta/GMS.
Canyonlands — Courtesy of the National Park Service/Department of the Interior.
Eco Challenge British Columbia — Courtesy of Eco Challenge Lifestyles, Inc., All Rights Reserved.
Eco Challenge Morocco — Courtesy of Discovery Communications, Inc.
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.
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!*
Avid Interplay Capture Installation and Administration Guide • 0130-30666-01 Rev A• Created 4/20/11 • This
document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed
form.
5
6
Contents
7
Checklist: Interplay Capture Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Avid Service Framework Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Installing Avid License Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Installing Capture Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Plug-in Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Capture Client Installation on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Router Control Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Capture Database in Interplay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Chapter 3 Capture Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Checklist: Capture Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuring the Capture Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configuring the Avid Interplay Shared Storage Service . . . . . . . . . . . . . . . . . . 64
Interplay Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring the Avid Route Engine Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Route Confidence Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Manual Routing of a Source to an External Monitor . . . . . . . . . . . . . . . . . . 71
Assign an External Monitor to a Recording . . . . . . . . . . . . . . . . . . . . . . . . 73
Route the First Source to Default Source Monitor . . . . . . . . . . . . . . . . . . . 74
Configuring the Avid Time Synchronization Service . . . . . . . . . . . . . . . . . . . . . 75
Configuring the Interplay Capture License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding the Temporary Capture License . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Generate an Activation File for a Full Capture License . . . . . . . . . . . . . . . 79
Add the Permanent Capture License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuring Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
AirSpeed Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Low-Resolution Encoder Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . 83
AirSpeed Multi Stream Device Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Low-Resolution Encoder VMOPTIONS Settings . . . . . . . . . . . . . . . . . . . . 89
VTR Device Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Interplay Administrator Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Capture Settings Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
General Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Channels Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8
Channel Pools Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Ancillary Data for Channel Pools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Ingest Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Ingest Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Aspect Ratio Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Chapter 4 Capture Workstation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Installing Applications and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Installing Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Interplay Administrator Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Chapter 5 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Main Interplay Capture Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Avid Interplay Capture Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Avid Interplay Capture Clip Manager Service . . . . . . . . . . . . . . . . . . . . . . . . . 110
Avid Interplay Shared Storage Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Avid Route Engine Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Avid Capture Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Avid Service Framework Applications & Services. . . . . . . . . . . . . . . . . . . . . . . . . . 112
Avid Monitoring Gateway Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Redundancy/Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Service Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Viewing the Status of Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Starting and Stopping Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Chapter 6 Shared Storage Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 121
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configuring the Shared Storage Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Viewing Shared Storage Service Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Discovery Status Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Shared Storage Service Overview Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
<Server Hostname> Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Chapter 7 System Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Status Bar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9
Record Controller Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Data Store Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Monitoring Service Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Avid Health Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Viewing Capture Service Health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Database Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Channels Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
System Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Ingest System Information Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Record Controllers Information Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Schedule Information Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Channel Pool Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Device Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Workspace Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Channel Allocation Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Field Validation Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Viewing Shared Storage Service Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Shared Storage Service Overview Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
<Shared Storage Server Hostname> Section . . . . . . . . . . . . . . . . . . . . . . . . . 148
Shared Storage Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Viewing Route Engine Service Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Plug-in Information Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Viewing Device Services Health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Chapter 8 Capture Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Installing Capture Web Service (Remote API) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Changing the Web Service Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Chapter 9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Master Clips and Device Clips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Master Clip Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Device Clip Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Failed Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
10
Using the Support Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Standard Information to Include Regardless of Issue . . . . . . . . . . . . . . . . . . . 166
VTR Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
VTR Timecode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Source VTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Clips From Source VTR Recordings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Avid Interplay Capture Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Opening the Monitoring application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Customizing the Interplay Capture Monitor Application . . . . . . . . . . . . . . . . . . 171
Router Crosspoints Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Route Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Channels Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Viewing Details and Clearing Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Channel Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Channel Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Starting the Route Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
System Diagnostics Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11
12
Using This Guide
This guide contains all the task-oriented instructions, conceptual information, and reference
material you need to install and administer your Avid Interplay Capture software.
This guide is intended for those personnel charged with setting up and maintaining the Avid
Interplay Capture system.
Unless noted otherwise, the material in this document applies to the Windows XP operating
system.The screen shots in this document were captured on a Windows XP system.
n The documentation describes the features and hardware of all models. Therefore, your
system might not contain certain features and hardware that are covered in the
documentation.
c A caution means that a specific action you take could cause harm to
your computer or cause you to lose data.
(Windows), (Windows This text indicates that the information applies only to the specified
only) operating system.
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.
14
Avid Training Services
To learn about Avid's new online learning environment, Avid Learning Excellerator™
(ALEX), visit http://learn.avid.com.
15
16
1 Introduction to Avid Interplay Capture
The following provides an overview of the Avid Interplay Capture system, its workflow, and
user interface.
Overview
Interplay Capture is a newsroom ingest tool that enables automated recordings. It contains
individual applications, which allow you to schedule and monitor recordings. Capture stores
its schedule and other metadata in the Interplay database, which allows for easy access to the
captured material within the Interplay work environment.
The Capture system works with Avid Service Framework applications and services to ensure
you always have the best system performance. These applications and services provide
health monitoring, diagnostics, and discovery so users and system administrators can
monitor the system and sub-system health, as well as the health of connected devices and
channels.
As an option, Capture can use Avid Router Control to dynamically route media from sources
to destinations. Sources are routed to particular destinations, which may be devices
configured to be controlled by Capture, such as Avid AirSpeed, Avid AirSpeed Multi
Stream, Avid Interplay Low-res encoders or VTR tape decks.
Capture interfaces with a wide range of industry standard components, allowing for easy,
simultaneous control of routers, VTRs and video servers. The Schedule application provides
users a way to schedule recordings in advance, on a single day or on recurring days. Users
can also perform instant recordings by ensuring the synchronous start of multiple ingest
devices—for late-breaking news events.
18
Overview
Features
The Avid Interplay Capture system provides the features described in the following table:
Feature Description
Shared Interplay Database Capture stores a complete copy of its database, settings, and user
permissions in the Interplay database.
19
1 Introduction to Avid Interplay Capture
Interplay Authentication All Interplay users can log into Capture because Capture uses Interplay
authentication methods. Capture user permissions, such as whether or not a
user can modify the recording schedule, are set in Interplay.
Interplay Clip Capture creates its own Interplay clip that groups all resolutions, mirrors,
and recovered clips into one master clip that represents a recording as a
whole.
Interplay Master Clip Metadata Capture can update the metadata in the Interplay master clip. If a change is
Updates made to a recording’s name in Capture, the updated name is reflected in the
master clip.
Transfer Status Capture reports the transfer status of clips from the ingest device to the
shared storage. Capture reports the transfer status per clip, and as a summary
status for all clips, in a recording on the timeline.
Interplay Check-in Status Capture reports the Interplay check-in status of clips from the ingest device
to Interplay. It reports the check-in status per clip and as a summary status
for all clips in a recording on the timeline.
Clip Retransfers A user can initiate a retransfer of clips back to Shared Storage (ISIS) and
Interplay from the ingest device.
Automated Clip Deletion Capture can delete clips and media off Interplay and Shared storage (ISIS)
after a set amount of time. Reserved media does not get deleted.
Multi-resolution Recordings Multi-resolution recordings can be enabled, per recording, for proxy editing
workflows. This results in two clips of different resolutions associated with
the same master clip in Interplay.
Mirrored Recordings Mirroring can be enabled, per recording, for hot channel redundancy. This
results in two clips of the same resolution associated with the same master
clip in Interplay.
Recurring Recordings Recordings can be set to recur on a scheduled interval of daily, weekly or
monthly.
Segmented Recordings Recordings can be set to segment at a user defined interval. For instance, a
24 hour recording could be segmented into 1 hour master clips.
20
Overview
Recording Templates Templates can be created from recordings that contain some, or all, required
metadata. These templates can be used when making future recordings to
populate the saved set of recording metadata.
Recording Favorites Favorites are a per user preference that can be saved and reused.
Instant Recordings Favorites can be setup as instant recordings. Instant recordings begin
recording immediately if there is an available channel for the recording.
Dual Monitor support User preferences set for Capture can remember multiple monitor screen
layouts.
Time Boundaries The Schedule panel in Capture allows scheduling and viewing recordings
over midnight and other common time boundaries.
Quick Recording Turnaround Capture recordings can be scheduled as near in the future as the user
requests. No artificial two minute block for schedule recordings.
Workspace Steering Users can specify, per recording and per channel, the workspace to which
media is transferred. This is dynamically set from Capture and does not
require pre setting destination templates on the ingest device.
Cloned Recordings Recordings can be cloned, or copied. When cloning a recording, all metadata
for the recording is duplicated to another recording. This enables a user to
quickly setup a recording, when one already exists, which contains all
metadata they need.
Interplay Capture Monitor Interplay Capture Monitor is an administrative application for monitoring all
channels and crosspoints configured in the Capture and Router Control
environment.
Recording Health Capture reports problems to users by recording health. Recording health is
indicated to the user by displaying a warning or critical icon. Examples of
recording health include invalid metadata or over allocation of channels.
Channel Pool Health Capture reports problems with channels through channel pool health.
Channel pool health is indicated to the user by displaying a warning or
critical icon. Examples of channel pool health include channel offline, ingest
device disk space low, or missing router destination.
Shared Storage Health Capture reports problems with shared storage workspaces through shared
storage health. Health is indicated by a warning or critical icon. Shared
storage health indicates when disk space on workspaces is low.
System Health Capture reports problems with the overall system through system health.
System health is indicated by a warning or critical icon. System health
includes a summary of all other health as well as additional system functions
like data store and record controller connectivity.
21
1 Introduction to Avid Interplay Capture
System Diagnostics Capture uses the Avid Service Framework Diagnostic application to store all
logs.These granular logs are extremely useful when troubleshooting any
issues.
Recording Clip History Each Capture recording keeps a history of all of the clips it checked into
Interplay.
Channel Pools Capture groups channels together in channel pools. When it starts, a
recording automatically selects a healthy channel from the pool.
Channel Pool Conflict Resolution If a channel failure were to occur during a recording, an available healthy
channel from the pool is started and continues the recording.
VTR Destination Capture can be configured to have a VTR as a destination. This is designed
to be a backup ingest option.
Capture Service Redundancy The Capture service,which contains the data store and record controller, uses
the Avid Service Framework redundancy. Avid supports up to two Capture
services in the Interplay workgroup.
Shared Storage Service The Shared Storage service uses the Avid Service Framework redundancy.
Redundancy framework. Avid supports up to two Shared Storage services in the Interplay
workgroup.
Route Engine Service The Route Engine service uses the Avid Service Framework redundancy.
Redundancy Avid supports up to two Route Engine services in the Interplay workgroup.
Capture Web Service The Remote API allows third party applications to create, modify, and delete
recordings. As well receive notifications of updates to recordings.
22
The User Interface
The following shows an example of the Avid Capture Monitor application user interface.
23
1 Introduction to Avid Interplay Capture
Panels
Panels are components that appear in the application and provide information in various
ways as well as tools and controls, which help you use the panels effectively. The Capture
window contains panels that you can dock, undock, move, resize, or even hide from view.
You can autohide the panels on a side of the window, where they can appear if you move the
mouse pointer that area. Each panel is easily identified by the name appearing in its title bar
as shown in the following Alerts panel example.
24
The User Interface
Another panel available in the Avid Capture Schedule application is the Interplay directory
panel, shown in the following illustration.
For more information about the panels, including the Interplay directory panel, see the Avid
Interplay Capture User’s Guide.
Menu Bar
Each Capture application has a menu bar that contains some or all of the following menus:
• File
• View
25
1 Introduction to Avid Interplay Capture
• Tools
• Help
The following table describes the menus, options and shortcut keys for the Avid Interplay
Capture Schedule application.
Schedule Application
Menu Submenu Shortcut Keys Description
New Default Ctrl+Shift+N Opens the Schedule Item Detail panel but
skips the template chooser dialog box
(Same as selecting File > New and pressing
the Skip button on the template chooser
dialog box.) The Schedule Item Detail
panel opens with default values in some of
the fields.
26
The User Interface
The following table describes the menus and options for the Avid Interplay Capture Monitor
application.
Monitor Application
Menu Submenu Description
Status Bar
The Status bar shows connectivity and health of the Capture system and subsystems,
including, in the following graphic from left to right, workspace health, record controller
connectivity, data store connectivity, and overall system health.
27
1 Introduction to Avid Interplay Capture
The following table describes the possible icons that appear on the Status bar.
Health Status
Icon Description
Unknown
Whether or not the Status bar appears in the user interface is customizable.
28
Support Dialog Box
3. Click the Save button. The Save support zip dialog box opens.
4. Select the name and location where you want the zipped file to be saved.
5. Click the Save button.
29
1 Introduction to Avid Interplay Capture
The system saves your comments inside a zipped file that also contains other vital
information, such as system settings and software versions, which enable support
personnel to troubleshoot the issue. This file can then be e-mailed to Avid.
6. E-mail the aforementioned zipped file to Avid.
30
2 Capture Server Installation
The Avid Interplay Capture Server stores its schedule and other metadata in the Interplay
database, which allows for easy access to the captured material within the Interplay work
environment.
System Architecture
Your Avid Interplay Capture system might include some or all of the following:
• Capture Server — This can be an SR2500 or an AS3000 from Avid.
• AirSpeed Device Service Expansion Server — From Avid.
• Capture Workstation — This computer is supplied by the customer.
• Capture Client — This software is installed on Interplay Assist.
For the most current Capture system hardware and software specifications, see the system
requirements listed online for Avid Interplay Capture.
Prepare Interplay Capture “Checklist: Prepare the Interplay Capture Server Operating
Server Operating System System” on page 34
32
Checklist: Pre-Installation Preparations
Avid also recommends you have a list of the site’s ingest channels. This listshould include
the following information about each ingest channel:
• Channel Index
• Router Crosspoints
• Timecode Source
• Channel Pool Type
33
2 Capture Server Installation
The following are optional applications that you can use with Avid Interplay Capture:
• Interplay Adapter (required for AirSpeed Classic only).
• A separate adapter can be installed on each server for load balancing. The adaptor
installer suggests one adapter per 10 AirSpeed Servers. Each Capture Server can run 10
AirSpeed Device services so Avid recommends a separate adapter on each Capture
Server. There is no redundancy in the Interplay Adapter.
• NTP Server from http://www.ntp.org. Some sites choose to use NTP as their time
synchronization protocol. Bundled with the Capture installers is the NTP server and
Avid recommended installation instructions.
Task
Set up Time Synchronization (Internet Update, Domain Time, NTP, or the Avid Service
Framework, Time Synchronization service).
n When using the Avid Service Framework, Time Synchronization service as the method of
synchronizing time, disable Windows Time service and also disable "Internet Time" update
from clock settings.
Disable the User Account Control (UAC) setting for the Windows user account.
Disable real time scanning of virus scanners. (Schedule full scans for a time when systems
are at minimal use.)
Match the Windows user account to ISIS and the Interplay Administrator user account.
This is recommended to make a unique account on ISIS and Interplay for use with
Capture.
34
Checklist: Pre-Installation Preparations
Interplay Capture does not support connecting the Capture Servers to more than one VLAN.
ISIS networks have two VLANs, and many of the Interplay Production Servers are dual
connected to VLAN10 and VLAN20. Interplay Capture does not support this type of
configuration.
n To help alleviate network failure scenarios, Interplay Capture supports network teaming.
This lets a site connect both network adapters on a server to one or two separate switches.
The two adapters share the same IP address.
When using network teaming, Avid recommends setting the receive and transmit buffers of
the network adapters used to 1024.
n When configuring teaming, ensure the receive and transmit buffers are set on both adapters.
35
2 Capture Server Installation
36
Checklist: Pre-Installation Preparations
37
2 Capture Server Installation
If an AirSpeed Multi Stream controlled by Capture were to have a network failure on the
primary network connection, the AirSpeed Multi Stream device service does not
automatically begin communicating on the other NIC. If this happens, re-starting the
AirSpeed Multi Stream resolves the issue.
To prevent this situation from happening, your site can set up fault-tolerance network
teaming for both VLAN connections at your site. This results in four connected network
adapters, two for each VLAN.
7. Select the adapters to include in the team. These are adapter port numbers, not to be
confused with the “Local Area Connection 1” names.
8. Click the Next button.
9. Select the Adapter Fault Tolerance team type.
10. Repeat steps 6 through 9 for the second VLAN team.
38
Checklist: Pre-Installation Preparations
The Avid Time Synchronization service has the capability to get the timecode off this
card and apply the time to the local clock. For more information, see “Configuring the
Avid Time Synchronization Service” on page 75.
n For specific instructions pertaining to the physical installation of a timecode card into the
AS3000 server, see the chapter called, Installing and Removing a PCIe Add-in Card in the
Avid AS3000 Setup Guide.
39
2 Capture Server Installation
mmp
40
Checklist: Pre-Installation Preparations
11. Select the option, Let me pick from a list of device drivers on my computer.
41
2 Capture Server Installation
42
Checklist: Pre-Installation Preparations
43
2 Capture Server Installation
18. Click the Next button. The Update Driver Warning dialog box opens.
44
Checklist: Pre-Installation Preparations
Verify the driver version number and date of the version. These steps have installed the
card in the chosen slot. If the card is moved to another slot, the steps must be done again
to re-install the card. If you remove the card, and later put it back in the slot into which it
was originally installed, the card will reappear in the device manager as the timecode
card.
45
2 Capture Server Installation
Configure the Digi serial Card “Configuring the Digi Serial Card” on page 46
Install the Digi Port Server “Digi Port Server Installation” on page 47.
Set up the VTR Device Service “VTR Device Service” on page 90.
n When setting up the VTR devices, make a note of what port numbers are used by the serial
card.
The Digi serial card is installed in any slot in the Interplay Capture Server. This is true
whether the server is an SR2500 or an AS3000.
46
Checklist: Pre-Installation Preparations
Optionally, a Digi Port Server can be used instead of or in addition to the Digi PCI serial
card. Follow the instructions in the installation guide, which came with Digi Port Server, to
configure the device with an IP address on the network. Avid recommends installing the
Digi Port Server in the same IP subnet as the Interplay Capture Server so that discovery can
automatically find the Port Server.
After installing the Digi Port Server, the serial ports can be configured.
47
2 Capture Server Installation
After configuring the serial ports and adding the new devices, you can access your serial
devices over the network. Add the new devices using Digi RealPort
48
Checklist: Pre-Installation Preparations
49
2 Capture Server Installation
50
Checklist: Pre-Installation Preparations
The port server and serial ports are verified using the device manager. Make note of where
the COM ports are located. In the following example, the port server has COM ports 21-36.
The previous illustration shows the start of a long mapping process to get a serial port from
the port server, to Capture for communication. In the illustration, the first physical port on
the port server is mapped to COM21 on the Capture Server.
In the Interplay Administration application, the Capture Settings plug-in is used to configure
VTR channels for Interplay Capture. For more information, see “Plug-in Installation” on
page 58.
51
2 Capture Server Installation
3. After adding the channel, you can define the channel as a Source VTR or a Destination
VTR. The configurations are slightly different.
For a source VTR, you can add a note, the Router source, and default timecode output
method, as shown in the following example.
For a destination VTR, you can add a note, the Router destination, Timecode source (for
recording), and Channel pool, as shown in the following example.
52
Checklist: Interplay Capture Server Installation
After it is configured, the source VTR shows up in the Source VTR panel in the Capture
UI and as a VTR Source Channel. It also appears in the Avid Health Monitor for the
Capture service.
Destination VTR channels show up in the Channel Pool in which they are configured.
Prior to installing Capture Server software on a server, ensure that all of the pre-installation
preparations have been completed. For more information, see “Gather Site Information” on
page 33.
53
2 Capture Server Installation
On the Capture Server, complete the following installation tasks in the order that they are
listed. You can print this checklist to use as a reference or if you are viewing this checklist
online, you can link to a topic that provides procedural details for the task. Return to this
main checklist after you have completed each task.
Install the Avid “Capture Client Installation on the Server” on page 59.
Interplay Capture
Client on the Server
Install Avid Router “Router Control Installation” on page 59 and the documentation
Control (if not included with your Avid Router Control software.
already installed)
After completing the installation tasks on the Capture Server, the installed applications can
be configured. Always perform the installation and configuration tasks on the primary server
first and the complete the installation and configuration of the backup server. For more
information, see “Checklist: Capture Server Configuration” on page 62.
54
Checklist: Interplay Capture Server Installation
The Avid Service Framework applications are used to configure and maintain the following
services for the Avid Interplay Capture system.
• Avid Interplay Capture Service — For more information, see “Configuring the Capture
Service” on page 62
• Avid Shared Storage Service — For more information, see “Configuring the Avid
Interplay Shared Storage Service” on page 64.
• Avid Route Engine Service — For more information, see “Configuring the Avid Route
Engine Service” on page 68.
• Avid Time Synchronization Service — For more information, see “Configuring the
Avid Time Synchronization Service” on page 75.
• Avid Interplay Capture License — For more information, see “Configuring the Interplay
Capture License” on page 77.
• Device Services
- AirSpeed Device Service — For more information, see “AirSpeed Device Service”
on page 83.
- Low-Resolution Encoder Device Service — For more information, see
“Low-Resolution Encoder Device Service” on page 83.
- AirSpeed Multi Stream Device Service — For more information, see “AirSpeed
Multi Stream Device Service” on page 86.
- VTR Device Service — For more information, see “VTR Device Service” on page
90.
55
2 Capture Server Installation
n If you opt not to use the Avid Service Framework Time Synchronization service as its time
synchronization system, it is highly recommended you use the Avid Service Framework Time
Synchronization service to set the workgroup time to the same timecode as that coming over
LTC.
4. Click the Next button and complete the Service Framework installation.
56
Checklist: Interplay Capture Server Installation
- Avid Interplay Capture Service—This service is the main Capture service and is
required on the Capture Server.
- Avid Interplay Capture Clip Manager Service—This is the service that provides
communication between Capture and Interplay to create master clips and is required
on the Capture Server.
- Avid Interplay Shared Storage Service—This is the service that provides
communication between Capture and the shared storage and is required on the
Capture Server.
57
2 Capture Server Installation
- Avid Interplay Capture Web Service—This is the API service for Avid Interplay
Capture. This service this is not required but can be installed on the Capture Server,
or on a separate server. It requires an additional license.
- Avid AirSpeed Device Service—This is the service that provides communication
between Capture and AirSpeed devices. This is only required if the site has
AirSpeed devices.
n The reference in this section referring to AirSpeed does not include AirSpeed Multi Stream.
Up to ten AirSpeed device services can run on each Capture Server. If your site has
more than ten AirSpeed device services, an additional server is required to run more
device services. For the main Capture Server, select only the number of AirSpeed
device services that are required on the Capture Server.
n If more AirSpeed device services are required for a site, the same installer program can be
run, but do not select any of the other services; only select the AirSpeed device services.
Uncheck all of the main Capture services so they do not start up in a redundant mode.
- Avid VTR Service—This is the service that provides for communication between
Capture and VTR devices.
3. Click the Next button and complete the Capture service installation.
Plug-in Installation
After installing the Avid Service Framework applications, Avid License service, and the
other Capture services required by the site on the Capture server, the Capture Administrator
plug-in can also be installed on that server or any other server in the Capture workgroup.
n When upgrading Interplay from v1.6 to 2.0 or later and the Capture Administrator plug-in is
already installed, the Capture Administrator plug-in must be uninstalled and then
reinstalled to ensure a clean installation.
This plug-in is used to manage the settings for the Capture system. For more
information, see “Interplay Administrator Configuration” on page 91.
58
Checklist: Interplay Capture Server Installation
n The client software may be installed on the Capture Server but it is only used for
troubleshooting and must not be left open for long periods of time.
n For more information about installing the Capture client software on a workstation
computer in a workgroup, see “Installing Client Software” on page 102.
Later, a folder for Device clips is created, which is also only accessible to Interplay
administrators. Avid recommends putting both of these in the same folder. Since the Device
clips must be located in the Projects folder, this is also an ideal location in which to put the
Database folder.
59
2 Capture Server Installation
2. Create a folder under the Projects folder called, _Capture, or use your own custom
folder name.
3. Create a folder under the new_Capture folder called, database.
4. (Optional) Create a folder under the _Capture folder called, device clips.
5. Open the Interplay Administrator application and set user permissions on the Capture
database to allow only Interplay administrators to read or write to the Capture database.
60
3 Capture Server Configuration
Prior to configuring the services on the Interplay Capture Server ensure all of the installation
tasks were successfully completed, and that you have the information available needed to
configure the services on the Interplay Capture Server. For more information, see
“Checklist: Interplay Capture Server Installation” on page 53.
On the Capture Server, complete the following configuration tasks in the order that they are
listed. Complete these tasks on the primary Capture Server first before configuring the
backup server. 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.
Configure the Avid “Configuring the Avid Interplay Shared Storage Service” on page 64.
Interplay Shared
Storage Service
Configure the Avid “Configuring the Avid Route Engine Service” on page 68.
Route Engine service
Configure Avid Time “Configuring the Avid Time Synchronization Service” on page 75.
Synchronization
Configure the Avid “Configuring the Interplay Capture License” on page 77.
Interplay Capture
Product License
62
Checklist: Capture Server Configuration
3. In the Configuration pane, on the Ingest Settings tab, enter the following information:
a. Enter a Capture system name. This is an alias name that can be used to identify this
Capture system. The system name is displayed on the client login screen.
b. Enter the hostname of the Interplay Server.
c. Enter the name of the Interplay database. The name is always AvidWG.
d. Enter the Interplay database folder path beginning with the forward slash
(/)character. This is the path to the folder in interplay in which Capture stores its
database.
e. The Interplay version is optional and not needed by Capture.
f. Enter the Capture system user. This is the Interplay user account Capture uses to log
into Interplay and create master clips.
n Avid recommends this user account is unique to Capture. Don’t use the same account as
AirSpeed Multi Stream, AirSpeed, or any other administrator name. If a unique user account
is used, for example Capture searches can be created to find assets created by the Capture
system.
g. Enter a Capture password. This is the Interplay password used with the Capture
system user account, which is used to log into Interplay and create master clips.
63
3 Capture Server Configuration
When the Avid Interplay Capture Server is in the same network subnet as the ISIS system,
the Avid Interplay Shared Storage service automatically detects the shared storage server
(such as, the ISIS System Director) and adds it to the list of workspaces. If the shared storage
server is not automatically discovered, it can be manually added to the list.
If you want to restricted the workspaces which can be used for ingest, those restrictions must
be applied to the user account.
64
Checklist: Capture Server Configuration
3. In the Details pane on the Shared Storage Settings tab do the following:
a. If the Capture Server is in the same network subnet as the ISIS system, the Avid
Interplay Shared Storage service automatically detects the Avid Interplay Shared
Storage Server and adds it to the list. If the Avid Interplay Shared Storage Server is
not automatically discovered, you can manually add it to the list by clicking the Add
button. When you click the Add button, the Input dialog box opens. Enter the name
of the new shared storage workspace and click the Ok button. The new name is
added to the list of workspaces and you can now configure the username and
password settings for this shared storage workspace.
65
3 Capture Server Configuration
b. Select that server from the list and provide a username and password with which to
log in. This user account provides Capture with a list of workspaces to which a user
can send recordings. If the site needs to restrict the workstations that can be used for
ingest, this user account can have those restrictions applied to it.
Interplay Notifications
In addition to the Clip Manager service polling, the Clip Manager service receives
notifications from the Avid Interplay Engine. These notifications enable Capture to
recognize when a new device clip is created in Interplay so that Capture can create the
master clip for that device clip faster. For more information about the Clip Manager service,
see “Main Interplay Capture Services” on page 110.
Enabling Interplay notifications is a two step process. First, notifications must be enabled on
the Avid Interplay Engine (on both when the Interplay engine is clustered). This is done by
installing the InterplayEngineSESActivation.exe executable, which comes with the
Interplay Capture installers, on the Avid Interplay Engine. If installing in a clustered
environment, the installer is run on the ONLINE node only, and the backup receives the
update automatically.
After enabling notifications on the Avid Interplay Engine, you must enable notifications on
the Capture service.
66
Checklist: Capture Server Configuration
67
3 Capture Server Configuration
68
Checklist: Capture Server Configuration
3. On the Router Group Name tab enter the Router Group Name.
Capture contains a feature that allows users to route video sources to dedicated monitors
through the Interplay Capture user interface. The monitors are configured in the Avid Route
Engine service using the Avid Service Configuration application.This feature is only
available in Interplay Capture systems that use automated routing. The route confidence
monitoring feature is enabled by default but routing options can be configured or disabled in
the Capture Settings section of Avid Interplay Administrator.
69
3 Capture Server Configuration
In the following example, three router destinations are designated as route confidence
monitors. They are called A Mon, B Mon, and C Mon.
The monitors shown in the previous example are configured and available for use in
Capture.
70
Checklist: Capture Server Configuration
When this feature is enabled, all of the routing options are also selected, as shown in the
following illustration.
The route confidence monitoring options can be changed in the Routing section of the
General tab by clicking the corresponding check boxes, to enable or disable each option.
Manually routing a source to an external monitor is done from within the Capture Schedule
Sources panel. When enabled, users can select a source and right click to open a context
menu, as shown in the following:
71
3 Capture Server Configuration
Selecting “Route To Monitor” option from the context menu displays a list of the
pre-configured monitors for this system. When the user selects one of the monitors, the
selected source is routed to that monitor.
If the Allow users to manually route a source to an external monitor option is not enabled in
the Capture Settings in Interplay Administrator, the Route to Monitor menu option does not
appear in the context menu.
Selecting the Allow users to manually route a source to an external monitor option in the
Capture Settings in Interplay Administrator enables a context menu for recordings in the
timeline. As shown in the following:
72
Checklist: Capture Server Configuration
This option allows a user to route sources assigned to that recording from the timeline
directly to a monitor.
If this option is not enabled in the Capture Settings in Interplay Administrator, routing
options do not appear in the context menu.
Assigning an external monitor to a recording enables a Monitor Field in the Schedule Item
Detail panel, which is used to create new recordings.
73
3 Capture Server Configuration
When the Monitor option in the Schedule Item Detail panel is enabled, a drop-down list of
source monitors allows the user to select a source monitor for the recording. In a
multi-source recording, the first source in the source list is routed to the monitor. When the
recording starts, the source is routed to the designated monitor. This route does not clear at
the end of the first recording. It stays in place until another source, from the multi-source
recording, is routed to that monitor.
The third option in the routing menu of the Capture Settings in the Interplay Administrator
allows the user to automatically route the first source to the default monitor when the user
clicks on a recording in the timeline.
When this option is enabled, recordings clicked in the timeline are automatically routed to a
default monitor. The default monitor is set in Capture, under Tools>Options>Workstation
Options, as shown in the following:
74
Checklist: Capture Server Configuration
The default monitor is saved on the Capture Schedule local workstation and is not saved to
the logged in Capture user’s account.
When this option is enabled and a user clicks a recording in the timeline, the source listed in
the recording is automatically routed to the specified default monitor. In a multi-source
recording, the first source listed in the recording is the one that is routed.
75
3 Capture Server Configuration
4. Select the Get Time Sync reference from internal Time Code Reader option,. This
ensures the workgroup time is equal to the timecode used by the ingest devices,
5. (Option) If the site does not want to use the Avid Time Synchronization service as their
time synchronization tool they can select the Set the Local PC clock to match the
Workgroup time and Stop setting if the clock is updated by a different mechanism
settings. These optional settings only work with computers in the same Capture
Workgroup.
76
Checklist: Capture Server Configuration
The Avid Service Configuration application should already be installed on a PC on the same
network, but might not necessarily be installed on the same computer as the Capture
software or the Avid License service.
n A temporary or permanent Capture product license must be applied at this point before
continuing with the installation and setup of the Capture system.
To get you started with Avid Interplay Capture, Avid provides you with a Capture temporary
(TEMP) license to use until your get your full Capture license.
77
3 Capture Server Configuration
78
Checklist: Capture Server Configuration
n The temporary license Avid provides gives full Capture functionality for thirty (30) days.
On systems with redundant configurations, the activation file for a full license must be
generated on the primary server.
2. On the Hosts tab, navigate to and select the Avid License Service.
3. When prompted, enter the system administrator password and click the OK button. 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 Activate button.
The Activate dialog box opens.
79
3 Capture Server Configuration
6. Select the I don’t have a Serial Number and would like to activate manually option and
click the Next button.
The Create an Activation File dialog box opens.
7. Review and edit the required information, as well as contact information, if necessary.
You can also add comments.
8. Click the Generate Activation File button to create the .act file and select where you
want to save it on your PC.
9. 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 Capture Activation
File.
80
Checklist: Capture Server Configuration
7. Select the full Capture license file, and click the Add Licenses button.
Your licensing configuration details will appear and replace the temporary license
information.
81
3 Capture Server Configuration
n To verify that an installed service is running, you must use the Avid Workgroup Properties
application.
82
Checklist: Capture Server Configuration
The AirSpeed device service may not be installed on an AirSpeed so it must be configured
on the Capture Server or on an AirSpeed Device Service Expansion Server. The AirSpeed
Device Service Expansion Server is an optional server that is only required if the site
requires more than 10 AirSpeed ingest channels.
3. On the Device Settings tab, enter the Host name of the AirSpeed.
The low-resolution encoder device service package runs on the low-resolution encoder. The
low-resolution device service qualified with Capture is separated from the bootset and is
included in the installers.
83
3 Capture Server Configuration
3. On the Encoder Settings tab, enter the asset manager, asset manager project (database),
username, password for that username, and the Shared Storage Server configured for
your site as shown in the following example.
84
Checklist: Capture Server Configuration
n The Enable Avid Interplay CaptureManager setting is only for Avid CaptureManager. Do
not enable this setting. You are installing Avid Interplay Capture.
On the lower portion of the Encoder Settings tab there are tabs representing each
channel. On the Recording tab for each channel are some important settings to
configure.
85
3 Capture Server Configuration
4. Mark the check box Always assume dual-ingest mode to enabled dual-ingest.
This allows you to specify a lead time and delay for the end time.
5. Avid recommends setting the lead and delay values to 5 seconds.
6. The check in time should be set to 30 seconds.
The AirSpeed Multi Stream Device Service runs on the AirSpeed Multi Stream Server,
which must be installed in the Interplay workgroup. The installer required for Avid Interplay
Capture is bundled with the Capture installers.
n If the site needs to configure an AirSpeed Multi Stream to communicate with both iNEWS
Command and Interplay Capture at the same time, use a version of iNEWS Command and
Interplay Capture that can use the same version of the AirSpeed Multi Stream Device
service.
2. After the Welcome dialog box appears. Click the Next button. The License Agreement
appears.
3. Read the License Agreement, accept the terms, and click the Next button.
4. When the Ready to Install the Program dialog box appears, click the Install button.
5. When the installation is complete, click the Finish button.
86
Checklist: Capture Server Configuration
If the Capture servers are in an isolated workgroup, the AirSpeed Multi Stream Device
Service must be configured to join another workgroup. There are two parts to complete
for this type of configuration; the first part is done using the Avid Service Configuration
application and the second part is done using the Avid Workgroup Properties
application.
n If you are configuring this Device service for use with both iNEWS Command and Interplay
Capture it does not matter in which order they are configured.
In the following example, Command is the name of the second workgroup. The default
is the Capture workgroup.
4. (Option) if a third workgroup is required, enter the information for that workgroup as
well.
5. Click the Apply button and close the Avid Service Configuration application.
Next, the lookup locators for the workgroup must be added to the workgroup's
properties on the AirSpeed Multi Stream Server. This is done using the Avid Workgroup
Properties application.
6. Open the Avid Workgroup Properties application.
87
3 Capture Server Configuration
7. On the Lookup tab, click the Add button under the Workgroup section—the far left
button at the bottom.
The Add Workgroup dialog box opens on top of the Avid Workgroup Properties widow.
8. Enter the name of the Capture workgroup, it is case sensitive, and click the OK button.
The name you entered appears in the Workgroup section of the Avid Workgroup
Properties window. It is important that each workgroup is listed and their lookup
locators be added in Workgroup properties.
9. Click the Add button under the Lookup services section (located above the Apply
button, not the button on the far left).
The add Lookup Service dialog box opens.
10. Enter the fully qualified domain name of the server running the Lookup service for the
Capture workgroup. Leave the port setting and select the Expected check box. then,
click the OK button.
11. Click the OK button on the Workgroup Properties window and close the Workgroup
Properties application.
88
Checklist: Capture Server Configuration
The low-resolution encoder needs extra time to setup its video signal before starting to
record. If a site is using a low-resolution encoder, Avid recommends setting some
VMOPTIONS to insert delays between the route>cue, and cue>record states. These
VMOPTIONS are applied to all recordings, manual and scheduled, without regard to the
type of channel used for them.
n If there are multiple Capture servers, then these VMOPTIONS must be set on each server.
c:\ProgramFiles(x86)\Avid\Interplaycapture\Service\scheduler\state\conf
ig\workgroup.properties
89
3 Capture Server Configuration
2. In this file, copy the following three lines (and be sure to include a blank line at the end
of the file)
com.avid.automation.ingest.cue.delayafterroute=3000
com.avid.automation.ingest.record.delayaftercue=3000
com.avid.automation.ingest.recordcontrol.controller.time.TimeConstan
ts.VTR_PREROLL=2500
n The VTRPreroll parameter adjusts how long Capture pre-rolls a VTR prior to batch or quick
recordings. This value is the amount of time the VTR rewinds, not the amount of time on the
tape that is pre-rolled. The 2500 setting puts the VTR into rewind for 2.5 seconds and results
in the tape backing up 5-6 seconds (depending on the VTR deck). Low-resolution encoders
take longer than AirSpeed Multi Stream or AirSpeed to lock to the video signal, so
pre-rolling and playing back stable video for a longer period is necessary only for sites that
use low-resolution encoder's.
These lines insert a 3 second delay between route and cue and another 3 second delay
between cue and record. These additional seconds implement a 6 second delay for manual
recordings but additional time might be required for the devices to setup. Due to the
additional delays, the configuration for the manual start time offset (in the Interplay
Administrator), may be adjusted. The recommended value for sites with these delays would
be 10 seconds (sites without the delays are recommended to use 5 seconds). If the site needs
to adjust this value for any reason, it is configurable.
The VTR Device Service is installed on one of the Capture servers and is not redundant. The
service communicates over RS422 so the server on which it is setup must have the a Digi
Serial PCI Card installed. For more information, see “Configuring the Digi Serial Card” on
page 46.
90
Interplay Administrator Configuration
3. On the Channel & Communication Settings tab, select the COM port next to the channel
index. Set the Bitrate, Stopbits, Databits, and parity to the settings shown in the previous
example.
4. Click the Apply button.
5. Open Avid Health Monitor application to confirm there is a “live” connection.
n Restarting the device service after new serial port installation is required.
n The Capture Settings plug-in is used for Capture Settings, Ingest Users, and Ingest
Monitoring.
This section contains information about the following Interplay Administrator configuration
tasks for Interplay Capture:
• Capture Settings Section
• Ingest Users
• Aspect Ratio Fields
91
3 Capture Server Configuration
The Capture Setting plug-in is comprised of three tabs; General, Channels, and Channel
Pools with which to administer various settings.
The Capture Settings plug-in allows you to administer the general settings for the Avid
Interplay Capture system on the General tab.
92
Interplay Administrator Configuration
93
3 Capture Server Configuration
t Delete device clips after — This setting is how long the device clips stay in the
device clips folder. Capture automatically deletes clips from this folder after this
period of time. The media is not deleted though; the media stays associated with the
master clip, which is created in the Interplay folder requested by the user in the
recording.
t Manual Recording start time offset — This setting affects manual recordings
only. This setting changes the start time that is written to the master clip in
Interplay. By default, the offset is 5 seconds.
t Delete schedule meta data —This setting is the amount of time recordings stay in
the Capture schedule database after they finish.
t Delete video clips with schedule meta-data — This setting, when enabled, deletes
clips and all associated media out of Interplay when the recording is purged from
the Capture schedule database.
t Automated routing using router group — This setting is used if you have Router
Control v2.0 or later. Enter the router group name for the route system used with
this Capture system.
Channels Tab
The Capture Settings plug-in allows you to administer the channel settings for the Avid
Interplay Capture system on the Channels tab.
n The Interplay Capture product license must be configured prior to configuring channels for
use with Capture. For more information, see “Configuring the Interplay Capture License”
on page 77.
2. Click the Search button located at the bottom of the tab to Search the workgroup for all
available channels which Capture can use. If the search doesn’t find any channels it
means that something is not correctly configured on the ingest device or that the ingest
device is not running.
n Do not attempt to add channels manually. Do use the Add button for adding channels.
3. After the channel is added, most fields to the right of the Channels table populate with
data about that channel. You may optionally add notes or change the timecode source.
94
Interplay Administrator Configuration
The Capture Settings plug-in allows you to administer the channel pool settings for the Avid
Interplay Capture system on the Channel Pools tab. This tab also allows you to enable an
ancillary data track for a channel pool, which can be used to embed data, such as timecode
or closed captioning, in video signals. The following environment is required when using the
ancillary data workflow:
• Interplay Capture v1.0.5 or later (ingest ancillary data)
• Interplay v2.2 or later (manage clips with ancillary data track)
• AirSpeed Multi Stream v 1.5 or later (ingest ancillary data)
• NewsCutterv 9.0 or Media Composer v5.0 or later (edit clips with ancillary data)
For more information about ancillary data, see “Ancillary Data for Channel Pools” on page
97.
95
3 Capture Server Configuration
2. To create a new channel pool, click the Add button located at the bottom of the tab.
3. Enter the following information:
t In the Name text box, enter the name for this new channel pool. This is the name
users see displayed in the Capture UI.
t In the Notes text box, enter any notes about this channel pool that you want to
display in the Capture UI.
t In the Shared Storage text box, enter the name of the Avid Shared Storage Server to
which the channels in this channel pool will send media.
t In the Default Mirror Workspace text box, enter the workspace assigned to a
recording when this channel pool is selected. This is the default workspace but this
workspace can be changed on a per recording basis. The default mirror workspace
is used for mirrored channels.
n Avid Interplay Capture can tell devices to which workspace to send media but the device is
required to have write permission to that workspace. If the device does not have write
permission to the workspace, the transfer will fail.
96
Interplay Administrator Configuration
t In the Default Mirror Workspace text box, enter the workspace assigned to a
recording when this channel pool is selected. This is the default workspace but this
workspace can be changed on a per recording basis. The default mirror workspace
is used for mirrored channels.
4. Click the Add button located on the right side of the Channel Pool tab.
The Add Channels To Pool dialog box appears containing all the channels configured
for the Capture system. This includes the channels listed on the Channels tab.
5. Select the channels to include in the channel pool, and click the OK button.
n Channel pools are limited by device type (AirSpeed, AirSpeed Multi Stream, low-resolution
encoder). There can be only one device type per channel pool.
6. Set the Allocation Warning.This warning alerts the user when the specified number of
channels (or fewer) in the channel pool are available. You can set this warning so the
user is warned earlier, when fewer channels are available in the pool.
7. Set the Audio Tracks. This is a setting for administrators to specify how many audio
tracks there are in the channels inside this channel pool. Ideally, all channels in the
system have the same number of audio tracks. If there is a difference in channels that are
a part of the same recording, when Capture creates its master clip, Capture uses the
highest number of audio tracks to ensure tracks do not get hidden in the master clip.
Using Interplay Administrator you can also enable an ancillary data track for a channel pool,
which can be used to embed data, such as timecode or closed captioning, in video signals.
97
3 Capture Server Configuration
n The AirSpeed Multi Stream must also be setup to Capture ancillary data (outside of the
Interplay Capture configuration). If ancillary data is enabled in Interplay Capture, but the
AirSpeed Multi Stream does not Capture any ancillary data, then the data track will be
empty when opened in the editor.
4. In the Timecode Source text box, use the dropdown to select Ancillary Time Code
(ATC).
5. Click the Apply button.
98
Interplay Administrator Configuration
n The AirSpeed Multi Stream must also be receiving ancillary timecode. If the AirSpeed Multi
Stream is not receiving ancillary timecode, recordings may fail to record properly.
Ingest Users
Interplay Capture shares its user database with Interplay. All Interplay users can log into
Capture, but they must have permission assigned to them before they can change scheduled
recordings or create new recordings. They must be assigned ingest users permissions.
2. Select a user from the directory tree located on the left side of the window
3. Configure the ingest user permissions for the user.
n The managing recordings (ingest) permission may not be assigned to a user group.
Ingest Monitoring
The Ingest Monitoring icon in the Interplay Administrator is a shortcut which opens the
Capture Monitoring application.
Capture does not automatically add the custom meta data fields for Aspect Ratio to
Interplay. Capture does not add Aspect Ratio meta data to Interplay clips if these fields are
not created. If the site does not use Aspect Ratio, they do not need to create these fields in
Interplay.
99
3 Capture Server Configuration
3. Click the Custom Meta Data tab and enter the names of the two Aspect Ratio fields.
100
4 Capture Workstation Installation
The Avid Interplay Capture client software can be installed on workstation computers in the
Interplay workgroup, the Capture workgroup, or the iNEWS Command workgroup. The
Avid Interplay Capture client software may also be installed on the Capture Server. For more
information about installing the Avid Interplay Capture client software on the Capture
Server, see “Capture Client Installation on the Server” on page 59.
n If you are installing the Interplay Capture client software on an Interplay Capture Server,
see “Capture Client Installation on the Server” on page 59. On the Capture Server, the
Client software is used only for troubleshooting and must not be left open for long periods of
time
102
Installing Client Software
3. Read the License Agreement, accept the terms, and click Next.
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.
103
4 Capture Workstation Installation
104
Installing Client Software
105
4 Capture Workstation Installation
6. Click Next.
The Installing Progress Bar displays while the workstation software is installing.
106
Interplay Administrator Plug-in
n The Capture Workstation allows you to specify the workgroup name during login. When the
Interplay Capture Workstation is started, if the Capture workgroup does not auto-populate
in the list of workgroups to join, it means the Lookup service for the Capture workgroup is
not within broadcast range (usually because the client and server are in different subnets).
In this situation, you are required to add the Lookup service Fully Qualified Domain Name
(FQDN) to the workstation computer. This is accomplished using the Avid Service
Framework application, Workgroup Properties.
For more information about installing the Interplay Administrator plug-in for Capture, see
“Plug-in Installation” on page 58.
107
4 Capture Workstation Installation
108
5 Services
The services for Avid Interplay Capture allow you to schedule and perform recordings,
control routing and video devices. Some of the services can be defined as Main
services—those services that make up the core of the Capture system. Other services are
known as Device services—those responsible for controlling devices, such as video servers
or VTRs.
n Some of the Device services used for Capture can be shared with other Avid systems, such as
iNEWS Command.
The Avid Service Configuration application is used to configure the Clip Manager service
catch-up polling.
c This setting must not be changed except under direct supervision of Avid support.
These settings are only to be used in an emergency if master clips, for a period of time
in the recent past, were not created.
110
Device Services
The Clip Manager Catch-up Polling Period Seconds setting is the wait time between each
search so that Interplay is not polled too often. The default wait time is 30 seconds. This
setting can be used to speed up or slow down the polling during catch-up polling.
The Clip Manager Number Hours To Rescan setting is the number of hours to rescan. This
tells the Clip Manager service how far back into the past to scan. The most time allowed is
24 hours.
n New recordings do not get clips or updates until after the catch-up period is finished.
The results of the catch-up polling and rescans may be viewed using the Avid Service
Framework, Health Monitor application, in the Clip Monitor Search Data section.
Device Services
Device services are those services responsible for controlling the ingest and playback
channels on video devices, such as video servers, and VTRs.
111
5 Services
Avid AirSpeed Device service Provides control of a single AirSpeed video server controlling the
ingest and playback channels on the device. One is required for
each AirSpeed and there can be redundant AirSpeed Device
services. It runs on a server, such as a Capture or a dedicated
AirSpeed Device Service Server.
Avid AirSpeed Multi Stream Provides control of a single AirSpeed Multi Stream video server
Device service controlling the ingest and playback channels on the device. One is
required for each AirSpeed Multi Stream, and it runs directly on
the AirSpeed Multi Stream server.
Avid Interplay Low-Res Encode Provides control of a single Low-Res Encoder device controlling
service ingest and playback channels on the device. One is required for
each Low-resolution Encoder device and it runs directly on the
Low-resolution encoder.
VTR Device service This service can control up to 8 VTRs but there is only one VTR
device service for each Capture system. It is used for controlling
the ingest and playback channels on the device. This service is not
redundant.
For more information on Avid Service Framework applications and services, see the
Avid Service Framework User’s Guide.
Avid Interplay Capture requires the installation of some Avid Service Framework Support
services. These Support services, installed on any Capture computer that is a member of an
Avid workgroup, are the Service Starter service, Machine Monitor, and the Time
Synchronization services. Although recommended, if the Avid Time Synchronization
service is not used for the time synchronization system, the Interplay workgroup must have
at least one server with this service running on it, and set to Master. This way the workgroup
time is synchronized with whichever system is used by Capture at this site.
n For Capture workstations, you may install the Avid Workstation service, which provides the
functionality of the Machine Monitor, Service Starter and Time Synchronization services.
The Avid Workstation service is not installed on Capture servers.
112
Avid Service Framework Applications & Services
Services Description
Avid Service Starter The Avid Service Starter service is responsible for starting all the other
Service Avid Service Framework services on the machine when the machine is
started. It can also be configured to restart any services that stop
unexpectedly.
Avid Machine Monitor This service reports machine information to the Health Monitor, including
disk, memory, network status, and time synchronization. You can also
monitor specific services on that local machine.
Avid Time This service is required to be installed on the Capture servers. If you use
Synchronization NTP or some other method for time synchronization, do not configure this
service to set the clock on the local computer. For more information see,
“Time Synchronization” on page 115.
c Serious problems can occur if more than one service for time
synchronization is installed.
Avid Workstation This service combines the workstation relevant functions of the Avid
Service Service Starter service, Avid Time Synchronization service, and Avid
Machine Monitor service into a single service installed on a computer. The
Workstation Service is mutually exclusive of these other Framework
services. By installing the Avid Workstation Service instead of those
services, the number of service registrations, which the Lookup service
keeps track of within the system, is reduced. It also reduces the amount of
memory used by the Avid Service Framework component.
Services Description
Lookup Service This service supports other important Avid services used throughout
your Avid environment. It acts as a broker or locator between
services and clients and it is an important communication link
between the Avid Service Framework applications and the other
support services.
License Service This service manages site licenses and can be installed on the
Capture servers if an instance of the service is not already installed
elsewhere in the workgroup.
113
5 Services
System Configuration Service This service is installed within the workgroup and is used to
configure services such as, ASF support services, Avid Route
Engine, and so forth.
The following Avid Interplay Framework applications are required for configuring and
managing and monitoring various aspects of Avid Interplay Capture as well as providing
vital help in troubleshooting integration issues. Avid recommends installing the Avid Health
Monitor, Avid Diagnostics, Avid Service Configuration, and Avid Workgroup Properties
applications on all Capture computers.
Application Description
Avid Health Monitor This application allows you to see the status of Capture and
other Avid services health statistics throughout the workgroup.
Avid recommends installing this application on the same server
on which the Capture service is installed.
Avid Diagnostics This application is used to view Avid log files (.alf) when
troubleshooting. Avid recommends installing this application on
the same computer on which Capture is installed.
Avid Service Configuration This application is used to configure settings and host names for
Avid services in the workgroup. For instance, configuring the
Capture service requires defining certain parameters through the
Avid Service Configuration application. Avid recommends
installing this application on the same computers on which Avid
Interplay Capture is installed.
Avid Workgroup Properties This application provides host specific configuration and control
of services. It allows you to set the workgroup of which the host
and it’s services are members. This application allows you to
enable or disable and start or stop workgroup services. You can
also specify the physical location of the computer, which is
reported to remote software. Avid requires this application to be
installed on all computers in an Avid workgroup.
114
Time Synchronization
Time Synchronization
Avid Interplay Capture is a scheduling application and time synchronization is of critical
importance to the overall health of the Capture system. Capture does not require the use of
any certain type of time synchronization method, such as NTP, Domain, or the Avid Service
Framework (ASF) Time Synchronization service, but it does require that the time
synchronization source be synchronized with the house time being served over LTC or
VITC. It is the responsibility of the site to ensure this requirement is met.
For Capture, there must be one Avid Service Framework (ASF) Time Synchronization
service running as a master in the workgroup that retrieves its time from the time
synchronization source. This is required to set the workgroup time. There are two key
benefits from using this method. This method allows the ASF Machine Monitor and the
Workstation services to report time offsets from this workgroup time and the time
synchronization Master’s workgroup time. It also enables log files to be synchronized to this
workgroup time.
Setting a Time Synchronization Master does not mean clients and other servers are
synchronizing to that server. The Workstation service and the ASF Time Synchronization
service have a local option to disable updating the local clock. For instance, If the site
chooses to use the Domain as their time source for all servers and clients, Interplay Capture
may run the ASF Time Synchronization service as Master, retrieving time from the local
clock, and not updating its own local clock, As shown in the following illustration.
115
5 Services
Redundancy/Failover
Avid Interplay Capture operates on a primary/backup basis. There can be only one primary
service. Avid recommends dedicating a computer as a Capture Server. Avid does not support
running the Capture services on a Capture workstation.
If the primary Capture service becomes unavailable, Capture conducts an election, and
promotes the backup Capture service to be a primary Capture service. This new primary
service will remain the primary service. If the previously primary Capture service should
become available again, it becomes the backup service.
Each Capture service runs on a Capture Server. If the Capture Server were to become
unavailable, each backup service within the system would conduct an election and all of the
services on the backup server would then become the primary services. For more
information see, “Monitoring Service Health” on page 132.
If network connectivity to a Capture server is lost, the primary services on that server still
continue to run. However, the backup services on another server become the new primary
services. When the network connection is restored, both the original and new primary
services conduct an election to determine which services have been running the longest.
Service Redundancy
The following table lists services and their redundancy capabilities.
AirSpeed Multi Stream Device This device service is not redundant because it runs on the
Service AirSpeed Multi Stream Server.
Low-resolution Encoder Device This device service is not redundant because it runs on the
Service Low-resolution encoder.
AirSpeed Device services This service is redundant because it does not run on the AirSpeed
Server but on the Capture Server.
Service Starter service, Machine These Avid Service Framework services are computer specific, so
Monitor service, Time no redundancy is required. The Time Synchronization service is
Synchronization service redundant in Master mode only. When the Time Synchronization
service is run in Slave mode it is not a redundant service.
116
Viewing the Status of Services
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.
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
on the local computer. A user can click the Advanced button to see more information
about the individual services. The icons displayed provide fast, easy identification of the
current status of an Avid service.
117
5 Services
When all of the enabled Avid components are running on the local computer 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 but not all of the enabled Avid services are running on the local
computer 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 computer a red
square is shown next to the Status text box and the sentence—No services are
running—is displayed.
For more information on viewing Avid services using the Workgroup Properties
application, see the Avid Service Framework User’s Guide.
118
Starting and Stopping Services
2. Select a row on which to perform the stop, start, enable, or disable action.
Multiple rows can be selected. The Action buttons are enabled with the Start button
changing to Restart if all of the services are running.
For more information on viewing Avid services using the Workgroup Properties
application, see the Avid Service Framework User’s Guide.
119
5 Services
120
6 Shared Storage Service Configuration
The Avid Interplay Capture service uses the Avid Interplay Shared Storage service to obtain
a list of the workspaces from the supported shared storage system.
Overview
The Capture service uses the Avid Interplay Shared Storage service to obtain a list of the
workspaces (and their individual health status) from the supported shared storage system.
From this list, the user can see what workspaces are available and choose a workspace to
which recordings may be sent.
When the Capture Server is in the same network subnet as the ISIS system, the Avid
Interplay Shared Storage service automatically detects the Avid Interplay Shared Storage
Server (such as, the ISIS System Director) and adds it to the list of workspaces. If the shared
storage server is not automatically discovered, it can be manually added to the list. If a site
wants to restricted the workspaces which can be used for ingest, those restrictions must be
applied to the user account.
122
Viewing Shared Storage Service Health
123
6 Shared Storage Service Configuration
Each of the Information sections for this service displays a colored status icon so you
can tell at a glance if it is in good health or if it is experiencing any issues that might
negatively affect the performance of the service.
3. Click the button corresponding to the information section you want to view. Some
examples are shown in the following.
Some of the information sections, such as the Current Process Information, JVM
Information, and Redundancy Information are commom to all services and always
appear in the details pane
124
Viewing Shared Storage Service Health
Colored icons are used so you can tell at a glance if the Lookup locator status is configured.
125
6 Shared Storage Service Configuration
Colored icons are used so you can tell at a glance if the server numbers are within a
normal range.
In the previous illustration, the server host name is MADISISON. The names Sports,
Satellite4 , and Satellite5 are the names of separate drives to which recorded media can
be sent. The numbers displayed for each drive are the percentages of free space.
The yellow and red colored zones are configurable warning thresholds. If any drive’s
percentage of free space reaches the yellow zone, it causes the whole Shared Storage
service to go into a warning. Likewise, if any drive’s percent free goes into red, the
whole service goes into a critical state. These warning thresholds are configurable.
126
Viewing Shared Storage Service Health
127
6 Shared Storage Service Configuration
128
7 System Health
Avid Interplay Capture system health can be viewed through the health status icons in the
Capture user interface as well as through the Avid Service Framework Health Monitoring
application.
n Modifying system settings for Avid Interplay Capture requires an Interplay administrator
password.
Health Status
Icon Description
Unknown
The following is an example of the Status bar displaying critical system status.
130
Status Bar Icons
If the record controller does not start properly, fails for any reason, or an open client looses
connectivity with the record controller, the Status bar record controller icon displays a red
square with a white X over it.
For instance, if the Capture service has stopped running it will cause the record controller
health to go into a bad health state. However, when the Capture service is restarted the
record controller health returns to a normal healthy state.
n The Capture database is stored in Interplay, but a local copy is also stored and managed in
RAM for quick access by the Capture system.
In the Status bar, the data store icon is gray in color when the record controller is running
and the client is connected.
If the data store does not start properly, fails for any reason, or an open client looses
connectivity with the data store, the Status bar data store icon displays a red square with a
white X over it. This can happen for instance, when the Capture service has stopped running.
131
7 System Health
The details pane displays various information sections for the service.
Some of the information sections, such as the Current Process Information, JVM
Information, Discovery Status, and Redundancy Information are common to all services
and always appear in the details pane. The following table describes these sections.
132
Monitoring Service Health
Current Process Information This section displays, the process ID number, % CPU usage,
handle count, thread count, memory usage, page file usage,
and running time. Status icons are used so you can tell at a
glance if the % CPU usage, handle, and thread counts, are
within normal ranges. “Icon Quick Reference” on page
101For more information about Status icons, see “Icon Quick
Reference” on page 101.
133
7 System Health
134
Viewing Capture Service Health
Each of the Information sections for this service displays a status icon so you can tell at
a glance if it is in good health or if it is experiencing any issues that might negatively
affect the performance of the service. For more information about Status icons, see
“Icon Quick Reference” on page 101.
3. Click the button corresponding to the information you want to view. Some examples are
shown in the following.
Some of the information sections, such as the Current Process Information, JVM
Information, and Redundancy Information are common to all services and always
appear in the details pane. For more information, see “Avid Health Monitor” on page
132.
Database Section
Capture stores its database of user preferences and permissions, channels and channel pools,
recordings, and general Capture system settings in a folder in Interplay. The folder is created
by the administrator in Interplay prior to configuring Capture.The Database information
section contains important process information about the Capture database connection with
Interplay.
135
7 System Health
• Server: This is the name of the Interplay server to which Capture writes it’s database and
master clips.
• Database: This is the Interplay database name to which Capture writes it’s database and
master clips.
• Path: This is the Interplay database folder path to where Capture stores it’s database on
Interplay.
• User: This is the Capture system user account with which Capture logs in to Interplay to
write it’s database and master clips.
• Connection: This lets you know if the Capture database is connected to the Interplay
database. If this is a primary Capture service the state must always be Connected. If this
is a backup Capture service the state should be Standby. If the Capture database is not
connected to the Interplay database, the state will be Disconnected. There is a brief
status that reads Connecting when the Capture database is connecting to the Interplay
database after being in a Disconnected state.
• Last Save: This date and time indicates when the Capture database was last successfully
saved to the Interplay database. The Capture database is stored in the local memory
while the Capture service is running. By default, the database is written to the Capture
server’s hard drive every thirty seconds, and every 8 minutes written to Interplay.
• Missed Heartbeat: By default, every thirty seconds the Capture server pings the
Interplay server establishing a heartbeat that lets Capture know the Interplay database is
still running. Missed heartbeats are the concurrent number of pings that are not
acknowledged by the Interplay database. For instance if the Interplay database was
down for 2 minutes, the missed heartbeats would read 4.
136
Viewing Capture Service Health
Channels Section
The Channels section shows the unusable channels, which are the number of channels that
are found to be unusable by Capture for ingest. It also shows the allocated channels, which
are the number of channels that are in use by the Capture system.
137
7 System Health
This section also displays the number of recordings in the next twenty four hours, the total
number of channels, channel pools, and devices.
138
Viewing Capture Service Health
The Record Controllers information section displays number of record controllers. When
there are active recordings, the details of each record controller are listed. Information
includes recording's Video ID, start and end times, allocated channels, and status of the
allocated channels.
139
7 System Health
n When a recording results in system health going into either a warning or critical status, the
recording is not listed in the Avid Service Framework, Health Monitor application. To find
the cause or reason for the poor health, the system administrator must first find the
recording in the Capture application, schedule panel.
The Channel Pools panel displays information about the channel pools, such as the names of
channel pools, administrative notes about each pool in the panel, and the health of each
channel pool.
140
Channel Pool Health
The health of a channel pool is also displayed in the table of channel pools in the recording's
detail pane.
The health of individual channels can be viewed using thw Interplay Capture Monitor
application in the Channel Monitor panel, as shown in the following illustration/
141
7 System Health
Device Health
Device health refers to the health of a hardware device, such as the health of an ingest
channel or the health of a workspace on a shared storage server.
Ingest channel health is visable in the Capture Monitor application. You can also see the
channel health using the Avid Health Monitor application. When using this application, in
the Directory pane, you select the Avid Interplay Capture service and in the Information
pane, click the Channels section.
n If you select the Ingest System Information section in the Information pane, some health is
displayed but in this section, Capture does not factor all of the health information for the
device service into the health of the channel.
You can view the health of a workspace using the Avid Health Monitor application. When
using this application, in the Directory pane, you select the Avid Interplay Shared Storage
Service.
142
Workspace Health
For more information see, “Viewing Shared Storage Service Health” on page 146. You can
also see the health of a worspace displayed in the workspace column of the Capture
recording table in the Schedule Item details panel.
Workspace Health
Workspace health refers to the communication between the Interplay Capture system and the
shared storage server. Good health means the workspace exists and the disk allocation is
within healthy limits.
The health of a workspace is viewed using the Avid Health Monitor application. The
workspace health also displays in the Schedule Item Detail panel for a recording, as shown
in the following illustration, when the “show device health in recordings” system setting is
enabled using the Capture Settings plug-in. For more information see “General Settings
Tab” on page 92.
143
7 System Health
The Clock panel also reports when the client’s local time is different than the server’s time.
In the following example, the amount of time difference between the client and the server is
5 or more seconds and the Critical health icon is displayed next to the time on the Clock
panel.
144
Channel Allocation Health
During a recording, the allocation is healthy for the channel pool used in the recording when
all of the channels requested for the recording are currently allocated to the recording. If a
channel is not available for the recording, a critical or warning health is applied to the
recording.
License Information
Information about the licensing for the Interplay Capture system is viewed using the Avid
Health Monitor application. Open an instance of the Avid Health Monitor application and
select the Avid Licensing service. The information about Capture licensing is displayed in
the Avid Capture section, as shown in the following:
145
7 System Health
Colored icons are used so you can tell at a glance if the licensing is configured. For more
information about Status icons, see “Icon Quick Reference” on page 101.
146
Viewing Shared Storage Service Health
Each of the Information sections for this service displays a colored status icon so you
can tell at a glance if it is in good health or if it is experiencing any issues that might
negatively affect the performance of the service.
3. Click the button corresponding to the information section you want to view. Some
examples are shown in the following.
Some of the information sections, such as the Current Process Information, JVM
Information, and Redundancy Information are common to all services and always
appear in the details pane
147
7 System Health
For each connected server, a unique section for that server is provided for health.
148
Viewing Shared Storage Service Health
Colored icons are used so you can tell at a glance if the server numbers are within a
normal range. For more information about Status icons, see “Icon Quick Reference” on
page 101.
In the previous illustration, the Avid Interplay Shared Storage Server hostname is
MADISISON. The names Sports, News, and Feeds are the names of separate
workspaces to which recorded media can be sent. The numbers displayed for each
workspace are the percentages of free space.
The yellow and red colored zones are configurable warning and critical thresholds. If
any drive’s percentage of free space reaches the yellow zone, it causes the workspace
and the whole Shared Storage service to go into a warning health status. Likewise, if any
drive’s percent free goes into red, the workspaces and the whole service goes into a
critical state. These warning thresholds can be configured
To configure thresholds:
1. Click on the name of the service.
The Range Configuration dialog box opens.
2. Enter the Warning limit percentage.
3. Enter the Critical limit percentage.
4. Chick the OK button.
149
7 System Health
150
Viewing Shared Storage Service Health
n When the shared storage service and shared storage server (ISIS System Director) are in the
same subnet, the shared storage server automatically appears in this list.
n All of the workspaces in this list can be used for recordings. However, the system
administrator can restrict ingest to a certain workspace. This is done by ensuring that the
user account, with which the shared storage service logs in, has access to only that
workspace.
n Capture does not give write permissions to an AirSpeed, Avid Multi Stream, or
Low-resolution encoder. The account used to log into the shared storage service, should
share the same permissions as that of the shared storage user accounts for the AirSpeed,
Avid Multi Stream, or Low-resolution encoder. Permission conflicts can result in failed
transfers.
151
7 System Health
The Avid Health Monitor application is used to view the health of the Route Engine service.
Each of the Information sections for this service displays a status icon so you can tell at
a glance if it is in good health or if it is experiencing any issues that might negatively
affect the performance of the service. For more information about Status icons, see
“Icon Quick Reference” on page 101.
3. Click the button corresponding to the information you want to view.
Some of the information sections, such as the Current Process Information, JVM
Information, Redundancy Information, and Discovery Status are common to all services
and always appear in the details pane. For more information, see “Avid Health Monitor”
on page 132.
152
Viewing Device Services Health
The Avid Health Monitor application is used to view the health of the each of the device
services.
153
7 System Health
Each of the Information sections for this service displays a status icon so you can tell at
a glance if it is in good health or if it is experiencing any issues that might negatively
affect the performance of the service. For more information about Status icons, see
“Icon Quick Reference” on page 101.
3. Click the button corresponding to the information you want to view.
Some of the information sections are common to all services and always appear in the
details pane. For more information, see “Avid Health Monitor” on page 132.
n Other Information sections that may appear will vary depending on which device service is
selected. For instance, different data sets are displayed for AirSpeed, Avid Multi Stream, and
Low-resolution encoders.Refer to the particular device’s administration guide for more
information.
154
8 Capture Web Service
The Capture Web service allows access to the Capture API so that a site can integrate their
custom applications with Interplay Capture.
n Installing the Web service without a valid license results in the service going into an endless
boot loop process. If this happens, Power off the computer during the power on self test
(POST) phase of the boot process.
When installing the Capture Web service on a server, which is not a Capture Server, that
server must first have Avid Service Framework installed on it with the same services the
Interplay Capture Server has installed on it. This server must then join the same Interplay
workgroup to which Interplay Capture belongs.
n You can print the terms if you want to read them later or keep a copy for your records.
156
Installing Capture Web Service (Remote API)
4. Select the Avid Interplay Capture Web Service (and deselect any other services), as
shown in the following illustration.
5. Click Next.
The Avid Interplay Capture Web service installs and no other configuration is required.
157
8 Capture Web Service
Redundancy
The Capture Web service is not a redundant service. It behaves the same as an Avid Interplay
Capture client workstation to Capture. Multiple instances of the Capture Web service can
run within the workgroup, but they all operate independently of each other and require their
own license.
158
Changing the Web Service Port
com.avid.ingest.sdk.webservice.Port=8080
3. In the line you just added, change the “8080” port to the number of the port this site
wants to use instead
4. The C# sample client requires a configuration change to adjust the sample client's Web
reference. In the same folder as the test client .exe is the following file:
TestCaptureWebClient.exe.config
159
8 Capture Web Service
160
9 Troubleshooting
The Avid Interplay Capture system offers redundancy in case of failover and a method for
system administrators or users to keep track of issues for the purpose of troubleshooting.
When attempting to troubleshoot any problem, it is best to have the most current version of
the Capture ReadMe available, which is available as a free download on the Avid
Knowledge Base at:
http://www.avid.com/onlineSupport
The Interplay Capture master clip automatically associates itself with each device clip for
the recording. For instance, a mirrored multi-resolution recording could have four associated
device clips in the Capture master clip. Capture writes all of the recording’s metadata (such
as, recording name, tape name, video, comments, aspect ratio) to the master clip.
n Editors must always use the Capture master clip for editing or storing metadata and only
use the device clips in the event of a missing master clip.
Using Interplay Access or an editor, when searching for a recently created master clip in
Interplay both the device clip and master clip are visible. Distinguishing between the two
can be difficult because the clip names are the same. Two added criteria to the recent media
search can help distinguish between the two.
• Narrow your search to folders where recordings are saved.
• Search for clips created by the Capture user (The Capture service logs in to Interplay as
a single user – all of the Capture master clips are created by this user. If the user account
is unique to only Capture, the search for recent media created by that user would return
only Capture master clips).
Capture has a global setting to direct where, under the projects folder, device clips are
created. This device clip folder is searched periodically by Capture. When a new or updated
device clip is detected, Capture creates or updates the master clip. For optimal performance,
it is important that no other users or devices are writing clips to this folder or it’s subfolders.
Only ingest devices, under the control of Capture, should be writing their clips to this device
clip folder.
162
Using the Support Dialog Box
Interplay in the device clips folder, defined in Interplay for new clips about every 30
seconds. When the first clip is found, the master clip is created in the Interplay folder
specified for the recording.
• For mirrored and multi-resolution recordings, where there are multiple ingest device
clips that are added to the same master clip, the additional device clips are associated
with the same master clip.
• Channel failure and channel failover can result in multiple device clips that are added to
the same master clip.
• Retransfered clips are appended to the original master clip, if that clip still exists in
Interplay. If the original master clip does not exist, a new one is created and the
retransfered clip is associated with the new master clip.
• Multi-cam (multi-source) recordings result in separate master clips for each source
specified in Interplay Capture.
• Segmented recordings (for example: 24 hour recording with 1 hour segments) result in
separate master clips for each segment.
n If the master clip is deleted from Interplay and Capture needs to update something in the
clip, Interplay Capture creates a new master clip in the original folder requested by the
recording’s specified details. In this case, previous data, such as associated clips, are not
restored to the master clip.
Failed Transfers
Permission conflicts can result in failed transfers. Capture does not give write permissions to
an AirSpeed, Avid Multi Stream, or Low-resolution encoder. The account used to log into
the shared storage service, should share the same permissions as that of the shared storage
user accounts for the AirSpeed, Avid Multi Stream, or Low-resolution encoder.
163
9 Troubleshooting
3. Click Save.
The Save support zip dialog box appears.
164
Using the Support Dialog Box
4. Select the location where you want the zipped file to be saved.
5. Click OK.
The system saves your comments inside a zipped file that also contains other information,
such as system settings and event logs, which enable support personnel to troubleshoot the
issue. This file can then be sent to Avid Customer Support. For more information, see “If
You Need Help” on page 14.
165
9 Troubleshooting
VTR Media
Batch recording has many variables that can effect the success of the recordings. The result
in some scenarios can be media loss. The following are some examples of things that can
cause media loss in Batch recordings.
• The mark-in point of a VTR clip is not found on the tape—In this case, the VTR clip
and all following VTR clips are not created, and the recording ends.
• The mark-out point of a VTR clip is not found on the tape—In this case, the current
VTR clip records to the end of the tape.
• An ingest channel goes offline—The feed recording workflow requests a new channel
and starts it recording as soon as possible. It does not stop the VTR playout and back up
to start again.
• The VTR clip exceeds the max clip duration—Some media may be lost as
segmentation is forced.
• The tape timecode jumps backward during recording more than 5 seconds—The
VTR clip is stopped and the next VTR clip is started.
• The tape timecode jumps forward further than 5 seconds—The VTR clip is stopped
and the next VTR clip started.
166
VTR Timecode
VTR Timecode
Where timecode is concerned, there are two aspects to consider for VTR Recording, one is
the timecode on the source VTR and the other is the timecode recorded to the destination
clip.
Source VTR
Batch and Quick recordings are the two different workflow types used for source VTR
recordings During either a Batch or Quick VTR recording, the timecode from the source
VTR is monitored. Capture requires continuous and monotonic (forward advancing)
timecode for VTR recordings. This means while Capture is monitoring timecode on the
source VTR, if a large jump in timecode is detected (either forward or backwards), the clip
currently being recorded is aborted.
n Timecode monitoring is not frame accurate due to this there is a small tolerance of 5 seconds
for timecode jumps.
If the clip was part of a Batch recording Capture attempts to cue the next clip and continue
recording. If the clip was a Quick recording, the recording is aborted. In the event of an
aborted recording, an event log can be reviewed to see what caused the recording to abort.
n For source VTR timecode, discontinuities and/or jumps in timecode can cause a recording to
fail or can cause a failure to locate a clip in a Batch recording, which results in a recording
failure.
For Batch VTR recordings, when Capture is required to Cue a VTR deck to a specific
timecode, as long as the deck continues advancing in the same direction, the cue does not
timeout. After the tape starts cueing in the opposite direction (due to end of tape or timecode
jump), a 30 second timeout period begins, and Capture stops the cue and aborts the
recording, if the 30 second timeout is reached. The event log for the recording indicates a
failure to locate a VTR clip.
For either Batch or Quick VTR recordings, before the tape begins playing, destination
channels must be cued. this cue action has a timeout of 60 seconds. At the 60 second mark, if
no destination channels are available for the recording, the recording is aborted.
n NOTE: During the recording process, if destination channels fail for any reason, normal
Capture channel failover procedures attempt to find another channel in the pool to continue
the recording. Capture does not stop the source VTR and reattempt to record. The user can
decide to do this manually, but it is not an automated decision.
167
9 Troubleshooting
n Avid recommends using your site’s previously defined workflow strategy for timecode as
labels of LTC and VITC can not be relabeled with their use or function.
There are two main workflows for destination timecode. The workflow used is determined
by the way in which the timecode is delivered; over LTC or both VITC and LTC.
Tape Timecode over VITC and Time of Day (TOD) Timecode over LTC
When tape timecode is delivered over VITC and time of day (TOD) timecode is delivered
over LTC, there is some flexibility as to whether or not to keep timecode that was originally
recorded with the tape's contents, or overwrite the timecode with a new track that is TOD
when the clips are recorded.
n This is the primary workflow when using AirSpeed Multi Stream because it only has one
LTC input, which is shared with all 4 ingest channels.
In this workflow, the administrator could designate VITC as the primary (default) timecode
source for VTR channels. When a user creates a VTR recording, VITC is selected by default
as the timecode source. If this selection is not changed, tape timecode is recorded into the
destination clip. If the user decided they do not want to preserve tape timecode, they could
change from VITC to LTC and record TOD timecode.
When the tape timecode is delivered over both VITC and LTC the timecodes may or may not
match one and other. This workflow assumes LTC is routed as another level on the router
and that the destination channels can use either VITC or LTC from the source VTR deck.
n Be aware that when using an AirSpeed Multi Stream in this workflow all 4 ingest channels
share only one LTC input.
In this workflow, the administrator can specify the default timecode to be used by the
channel. Usually, the site has a default location for timecode on which it can relay. When
using this workflow, it is far less likely for the user to want to change the timecode source. If
the timecode is broken or wrong on a particular tape, this option allows the user to change
the timecode source to the other timecode source.
168
Avid Interplay Capture Monitor
n The Interplay Server and Interplay Database names are set up in the Avid Inerplay
Administrator application.
169
9 Troubleshooting
Menu bar
The Interplay Capture Monitor application contains a straight forward menu bar to help you
make the most of it’s features.
Status Bar
The Status bar shows connectivity and health of the Capture system and subsystems,
including the Capture service, record controller, and shared storage. For more information,
see “Status Bar” on page 26.
170
Avid Interplay Capture Monitor
If the router supports protection and it is enabled, a system administrator can protect (lock)
or unprotect (unlock) routes using the Router Crosspoints panel. For instance, a user may
have protected (locked) a route during a recording so that other users may not access it. If
something goes wrong while recording, the system administrator can unprotect (unlock) the
source video.
Route Protection
The system administrator can protect or unprotect routes with the Router Crosspoints panel.
For more information see, “Starting the Route Monitor” on page 174.
171
9 Troubleshooting
Channels Panel
The Channels panel is available in the Interplay Capture Monitor application and displays
information and messages about Channels. The cells in the table display the channels, their
health, transport status, recording information (start time, duration, sources), and the channel
pools to which the channels belong.
172
Viewing Details and Clearing Alerts
Critical
Warning
Succeeded
n The succeeded alert with its check mark icon will only appear as a follow-up to previously
reported warnings and critical alerts.
Each alert appears along with a timestamp for when the alert was issued.
If the summary shown in the alert’s title column extends beyond the size of the panel, resize
the panel or mouse over the alert to view the entire title in a tooltip. A user can also select
any alert and view additional details as well as clear alerts from the list.
To clear alerts:
t Right-click and select Clear Alerts.
173
9 Troubleshooting
Channel Failure
There are three channel failure scenarios.
• Ingest channel fails to start on time – When this happens, the master clip shows a
MEDIA OFFLINE state in the editor, from the expected start of the recording up to the
time an ingest channel started recording. Interplay Access reports the master clip as
PARTIALLY ONLINE.
• Ingest channel fails in the middle of a recording and recovered before the end of the
recording – When this happens, the master clip shows a MEDIA OFFLINE state in the
editor, between the time the ingest channel failed, and when the channel recovered to
continue the recording. Interplay Access reports the master clip as PARTIALLY
ONLINE.
• Ingest channel fails before the recording ended and never recovered – When this
happens, the master clip shows a MEDIA OFFLINE state at the point of the failure
through the end of the recording. Interplay Access reports the master clip as
PARTIALLY ONLINE.
Channel Failover
Channel pools and automated routing make channel failover possible, if needed, during a
recording. If a channel fails part way through a recording, with the help of automated
routing, Capture can switch to another channel in the pool and continue the recording,
(generally in less than 2 seconds) with minimum loss of media. When this happens, the
ingested device clip is associated with the same master clip and the master clip shows a
MEDIA OFFLINE state in the editor between the time the ingest channel failed, and when
the new channel started and continued the recording. Interplay Access reports the master clip
as PARTIALLY ONLINE.
n See the Avid Router Control Installation and Configuration Guide for information about
Avid Router Control.
174
Starting the Route Monitor
n The first time that the Route Monitor is started, the Router Group must be selected in the
Avid Route Engine Crosspoints Monitor window from the Edit menu. Doing this enables the
Route Monitor automatically select this Router Group on subsequent startups.
The Route Monitor window displays information in two panels. The upper Information
panel shows information about the crosspoints and the lower Message panel shows
messages about the actions of the Avid Route Engine service. The information and
messages are continually refreshed while the session is open.
175
9 Troubleshooting
If the router supports protection and it is enabled, a system administrator can protect
(lock) and unprotect (unlock) routes using the Avid Route Monitor. For instance, a user
may have protected (locked) a route during a recording so that other users may not
access it. If something goes wrong while recording, the system administrator can
unprotect (unlock) the source video using the Avid Route Monitor so that the route is
available for others to use.
176
ABCDEFGHIJKLMNOPQRSTUVWXYZ Index
Index
177
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ
Device I
clip updating 163
health 142 Ingest system information 138
viewing service health 153 Ingest users
Device service 111 configure 99
AirSpeed device service configuration 83 Installation
AirSpeed Multi Stream 86 Capture admin plug-in 58
Avid AirSpeed Device service 112 Capture Client on the server 59
Avid AirSpeed Multi Stream Device service 112 Router Control 59
Avid Low-Res Encoder 112 Installing
configuration 82 Avid License Service 56
description 116 Avid Service Framework 54
health 153 Capture services 57
low-resolution encoder 83 Interplay Administrator
VTR 90 Capture settings 92
VTR device service 112 Capture settings plugin 91
Dialog box Interplay Capture Monitor
Avid services 118 application 169
Digi serial PCI card 46 channels panel 172
Interplay Engine
notifications 66
F Interplay notifications
Failover 116 clip manager service 66
Failure transfer 163
Field valadation L
health 145
Framework applications License
Avid Health Monitor 112 activation file 79
Avid Service Configuration 112 configuration 77
Avid Workgroup Properties 112 information 145
permanent 81
temporary 77
H Logging support information 28
Hardware requirements 32 Low-resolution encoder
Health VMOPTION settings 89
capture service 134
channel allocation 145 M
channel pool 140
device 142 Media loss
device service 153 vtr 166
field validation 145 Monitor
route engine service 152 assign an external monitor to a recording 73
shared storage service 146 Interplay Capture Monitor 169
workspace 143
N
Network
178
ABCDEFGHIJKLMNOPQRSTUVWXYZ Index
179
Index ABCDEFGHIJKLMNOPQRSTUVWXYZ
U
Updating
device clip 163
User
interface 22
shared storage account permissions 163
V
VTR
Channel configuration 51
COM port verification 51
destination timecode 168
media loss 166
PCI and Port Server setup 45
Port Server installation 47
Port Serverconfiguration 47
Serial device access 48
setup 45
180
Avid Technical Support (USA) Product Information
75 Network Drive Visit the Online Support Center at For company and product information,
Burlington, MA 01803-2756 USA www.avid.com/support visit us on the web at www.avid.com