Lightspeed Live User Guide

October 2019 283449

Live Capture 3.1 for Vantage 8.0 + ComponentPac 8.0.0

Copyrights and Trademark Notices2

Lightspeed Live Capture User Guide

Copyrights and Trademark NoticesCopyright © 2019 Telestream, LLC. All rights reserved worldwide. No part of this publication may be reproduced, transmitted, transcribed, altered, or translated into any languages without the written permission of Telestream. Information and specifications in this document are subject to change without notice and do not represent a commitment on the part of Telestream.

Telestream. Telestream, CaptionMaker, Episode, Flip4Mac, FlipFactory, Flip Player, Gameshow, GraphicsFactory, Lightspeed, MetaFlip, Post Producer, ScreenFlow, Split-and-Stitch, Switch, Tempo, TrafficManager, Vantage, VOD Producer and Wirecast, are registered trademarks and Cricket, e-Captioning, iQ, iVMS, iVMS ASM, Inspector, MacCaption, Pipeline, Vantage Cloud Port, Vidchecker, and Surveyor are trademarks of Telestream, LLC. All other trademarks are the property of their respective owners.

Adobe. Adobe® HTTP Dynamic Streaming Copyright © 2014 Adobe Systems. All rights reserved.

Apple. QuickTime, MacOS X, and Safari are trademarks of Apple, Inc. Bonjour, the Bonjour logo, and the Bonjour symbol are trademarks of Apple, Inc.

Avid. Portions of this product Copyright 2012 Avid Technology, Inc.

CoreOS. Developers of ETCD.

Dolby. Dolby and the double-D symbol are registered trademarks of Dolby Laboratories.

Fraunhofer IIS and Thomson Multimedia. MPEG Layer-3 audio coding technology licensed from Fraunhofer IIS and Thomson Multimedia.

Google. VP6 and VP8 Copyright Google Inc. 2014 All rights reserved.

MainConcept. MainConcept is a registered trademark of MainConcept LLC and MainConcept AG. Copyright 2004 MainConcept Multimedia Technologies.

Manzanita. Manzanita is a registered trademark of Manzanita Systems, Inc.

MCW. HEVC Decoding software licensed from MCW.

MediaInfo. Copyright © 2002-2013 MediaArea.net SARL. All rights reserved.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.



Microsoft. Microsoft, Windows NT|2000|XP|XP Professional|Server 2003|Server 2008 |Server 2012, Windows 7, Windows 8, Windows 10, Media Player, Media Encoder, .Net, Internet Explorer, SQL Server 2005|2008|Server 2012, and Windows Media Technologies are trademarks of Microsoft Corporation.

NLOG, MIT, Apache, Google. NLog open source code used in this product under MIT License and Apache License is copyright © 2014-2016 by Google, Inc., © 2016 by Stabzs, © 2015 by Hiro, Sjoerd Tieleman, © 2016 by Denis Pushkarev, © 2015 by Dash Industry Forum. All rights reserved.

SharpSSH2. SharpSSH2 Copyright (c) 2008, Ryan Faircloth. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of Diversified Sales and Service, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Swagger. Licensed from SmartBear.

Telerik. RadControls for ASP.NET AJAX copyright Telerik All rights reserved.

VoiceAge. This product is manufactured by Telestream under license from VoiceAge Corporation.

x264 LLC. The product is manufactured by Telestream under license from x264 LLC.

Xceed. The Software is Copyright ©1994-2012 Xceed Software Inc., all rights reserved.



ZLIB. Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler.

Other brands, product names, and company names are trademarks of their respective holders, and are used for identification purpose only.

MPEG Disclaimers

MPEGLA MPEG2 PatentANY USE OF THIS PRODUCT IN ANY MANNER OTHER THAN PERSONAL USE THAT COMPLIES WITH THE MPEG-2 STANDARD FOR ENCODING VIDEO INFORMATION FOR PACKAGED MEDIA IS EXPRESSLY PROHIBITED WITHOUT A LICENSE UNDER APPLICABLE PATENTS IN THE MPEG-2 PATENT PORTFOLIO, WHICH LICENSE IS AVAILABLE FROM MPEG LA, LLC, 4600 S. Ulster Street, Suite 400, Denver, Colorado 80237 U.S.A.

MPEGLA MPEG4 VISUALTHIS PRODUCT IS LICENSED UNDER THE MPEG-4 VISUAL PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND NON-COMMERCIAL USE OF A CONSUMER FOR (i) ENCODING VIDEO IN COMPLIANCE WITH THE MPEG-4 VISUAL STANDARD (“MPEG-4 VIDEO”) AND/OR (ii) DECODING MPEG-4 VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION INCLUDING THAT RELATING TO PROMOTIONAL, INTERNAL AND COMMERCIAL USES AND LICENSING MAY BE OBTAINED FROM MPEG LA, LLC. SEE HTTP://WWW.MPEGLA.COM.

MPEGLA AVCTHIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM.



MPEG4 SYSTEMSTHIS PRODUCT IS LICENSED UNDER THE MPEG-4 SYSTEMS PATENT PORTFOLIO LICENSE FOR ENCODING IN COMPLIANCE WITH THE MPEG-4 SYSTEMS STANDARD, EXCEPT THAT AN ADDITIONAL LICENSE AND PAYMENT OF ROYALTIES ARE NECESSARY FOR ENCODING IN CONNECTION WITH (i) DATA STORED OR REPLICATED IN PHYSICAL MEDIA WHICH IS PAID FOR ON A TITLE BY TITLE BASIS AND/OR (ii) DATA WHICH IS PAID FOR ON A TITLE BY TITLE BASIS AND IS TRANSMITTED TO AN END USER FOR PERMANENT STORAGE AND/OR USE. SUCH ADDITIONAL LICENSE MAY BE OBTAINED FROM MPEG LA, LLC. SEE HTTP://WWW.MPEGLA.COM FOR ADDITIONAL DETAILS.

Limited Warranty and DisclaimersTelestream, LLC (the Company) warrants to the original registered end user that the product will perform as stated below for a period of one (1) year from the date of shipment from factory:

Hardware and Media—The Product hardware components, if any, including equipment supplied but not manufactured by the Company but NOT including any third party equipment that has been substituted by the Distributor for such equipment (the “Hardware”), will be free from defects in materials and workmanship under normal operating conditions and use.

Warranty RemediesYour sole remedies under this limited warranty are as follows:

Hardware and Media—The Company will either repair or replace (at its option) any defective Hardware component or part, or Software Media, with new or like new Hardware components or Software Media. Components may not be necessarily the same, but will be of equivalent operation and quality.

Software UpdatesExcept as may be provided in a separate agreement between Telestream and You, if any, Telestream is under no obligation to maintain or support the Software and Telestream has no obligation to furnish you with any further assistance, technical support, documentation, software, update, upgrades, or information of any nature or kind.

Restrictions and Conditions of Limited WarrantyThis Limited Warranty will be void and of no force and effect if (i) Product Hardware or Software Media, or any part thereof, is damaged due to abuse, misuse, alteration, neglect, or shipping, or as a result of service or modification by a party other than the Company, or (ii) Software is modified without the written consent of the Company.



Limitations of WarrantiesTHE EXPRESS WARRANTIES SET FORTH IN THIS AGREEMENT ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. No oral or written information or advice given by the Company, its distributors, dealers or agents, shall increase the scope of this Limited Warranty or create any new warranties.

Geographical Limitation of Warranty—This limited warranty is valid only within the country in which the Product is purchased/licensed.

Limitations on Remedies—YOUR EXCLUSIVE REMEDIES, AND THE ENTIRE LIABILITY OF TELESTREAM, LLC WITH RESPECT TO THE PRODUCT, SHALL BE AS STATED IN THIS LIMITED WARRANTY. Your sole and exclusive remedy for any and all breaches of any Limited Warranty by the Company shall be the recovery of reasonable damages which, in the aggregate, shall not exceed the total amount of the combined license fee and purchase price paid by you for the Product.

DamagesTELESTREAM, LLC SHALL NOT BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF YOUR USE OR INABILITY TO USE THE PRODUCT, OR THE BREACH OF ANY EXPRESS OR IMPLIED WARRANTY, EVEN IF THE COMPANY HAS BEEN ADVISED OF THE POSSIBILITY OF THOSE DAMAGES, OR ANY REMEDY PROVIDED FAILS OF ITS ESSENTIAL PURPOSE.

Further information regarding this limited warranty may be obtained by writing:Telestream, LLC848 Gold Flat RoadNevada City, CA 95959 USA

You can call Telestream during U. S. business hours via telephone at (530) 470-1300.

Regulatory ComplianceElectromagnetic Emissions: FCC Class A, EN 55022 Class A, EN 61000-3-2/-3-3, CISPR 22 Class A

Electromagnetic Immunity: EN 55024/CISPR 24, (EN 61000-4-2, EN 61000-4-3, EN 61000-4-4, EN 61000-4-5, EN 61000-4-6, EN 61000-4-8, EN 61000-4-11)

Safety: CSA/EN/IEC/UL 60950-1 Compliant, UL or CSA Listed (USA and Canada), CE Marking (Europe)

California Best Management Practices Regulations for Perchlorate Materials:This Perchlorate warning applies only to products containing CR (Manganese Dioxide) Lithium coin cells. Perchlorate Material-special handling may apply. See www.dtsc.ca.gov/hazardouswaste/perchlorate.

7


8


9

Contents

Introducing Lightspeed Live Stream and Capture 25Overview 26Lightspeed Live Server Platform 26Lightspeed Live Stream 27Lightspeed Live Capture 27Using Live Stream and Live Capture Concurrently 28

Shared Resource Allocation 28Lightspeed Live Application Program Interfaces 29

Lightspeed Live Stream Web API 29Lightspeed Live Capture Web API 29Lightspeed Live Source Web API 29

Lightspeed Live Server Hardware Specifications and Components 30System Power 31Drives 31Front Control Panel 31Cooling System 31SDI Input Cards 32SDI Card Input Formats 32

SDI Input Video 32SDI Input Audio 32

GPU 33Expansion Input Card Slots 33RS-422 VTR Interface Kit Option for Capture 33Front Panel 34

Front Panel Features 34Rear Panel 35

Video Input Connections 36

Installing and Maintaining a Lightspeed Live Server 39Installing the Server 40

Unpacking the Server 40Rack Installation 40

Assembling the Rails 40

Contents10

Installing Outer Rails into a Rack 41Installing the Server in the Rack 42

Making Connections 44Data and Signal Connections 44Power Requirements and Connections 45

Power and General Cautions and Warnings 45Managing the Operating System 47

Microsoft Activation Key 47Microsoft Updates 47Windows User ID and Password 47Windows Firewall 47

Maintaining the Lightspeed Server 49Performance Tuning a Lightspeed Live Server 49Backing up the Lightspeed Live Server 52Managing the Lightspeed Live Server 53Installing New or Replacement Hard Drives 54Rebuilding the Lightspeed Live Storage RAID 55Replacing Power Supplies 55

Replacing the Power Supply 55Monitoring Lightspeed Live via SNMP 56

Enabling SNMP Monitoring 56

Configuring the Lightspeed Live Capture Server and Apps 57Changing a Source Name 58Managing and Configuring Sources 59

Sources Overview 60Source and Channel Indicator Icons 62

Configuring an SDI Source 63Switching Between HD and 4K/UHD Configurations 67

Configuring SDI Loop Through 69Using both Loop Through and Normal Modes 69Creating a Loop Through Output 69Port Pairing Assignments for Loop Through 70

Configuring a File Loop Source 72Configuring a Slate Source 73Configuring a Transport Stream Source 74Configuring an RTMP Source 77Managing and Configuring Audio Tracks (AC-3 Only) 79

Adding an Audio Track 80Previewing the Audio Tracks 80Configuring an Audio Track 80

Configuring Capture Resources 82Configuring Settings for Your Facility 83Using Inputs for Both Live Stream and Capture 88Configuring Ingest Sources 89

Configuring a Channel Group Nexus 89Using Capture Inventory to Preview and Find Workflows Used by an Input 91

Contents 11

Previewing Sources 92Finding Workflows 92

Installing the Live Capture & Tape Capture Web Apps 93Installation on Standard Servers 93Clear Browsing Data after Updating 93

Renaming or Reconfiguring Servers 94Stopping and Restarting Telestream Live Services 96Firewalls and Blocked Ports Limit Functionality 97Create a UNC Path for the Resource Location 97Array Licensing for Multiple Server Live Capture Systems 98

Vantage and Live Capture Solutions 98New Vantage Systems Containing Live Capture 98Adding Live Capture to an Existing Vantage Domain Array 98

Important Notes on Configuring Non-Capture Workflow Actions on Multiple Server Systems 99

Joining Multiple Capture Servers 100Best Practice When Joining Two or More Live Capture Servers Into a Single Do-

main 100Joining Capture-Only Systems 101Existing Vantage Array - Adding Live Capture Server(s) 102

Uniquely Named Multiple Capture Servers 103Best Practice for Multiple Live Capture Server System Design 104Connecting the Applications for Multiple Servers 106

Configuring Vantage Client Applications for Multiple Servers 106Using the Live Capture Web App with Multiple Servers 107

Using NetBIOS Hostnames Instead of External Name Server 108Correcting Thumbnail Appearance on Non-Local Systems 110

MacOS Procedure to Correct Thumbnail Appearance 110Windows Procedure to Correct Thumbnail Appearance 110

Updating Capture using Secured Version Control and ComponentPacs 111Clear Browsing Data after Updating Vantage or Live Capture 112

Creating Capture & Tape Action Workflows 113Additional Resources 114Creating, Configuring, and Activating Capture Workflows 115

Capture Action Overview 116Configuring Program Settings 117Restricting Input Frame Type and Rate 120

Operation When Restrict Input is Enabled 121Automatic Triggers Record When Restrict Input is Enabled 121

Expected Labels 121Configuring Trigger Settings 123

DAI Triggers 123Manual Triggers 125Recurring Segment Triggers 125Schedule Triggers 126Web Service Triggers 127

Contents12

Using the Schedule Trigger 128What Happens When a Queued Event is Deleted 128Creating Repeating Events in Google Calendar 128Adjusting your Google Account Settings for Live Capture Access 129Creating a Schedule Trigger 130

Configuring Primary and Secondary Outputs 133Time Code Burn-in Filter 135

Creating a Capture Action Workflow 136Creating and Activating a Tape Action Workflow 139

Tape Action Overview 140Inputs 140Expected Labels 141Primary and Secondary Outputs 141Settings Panel 142

Time Code Burn-in Filter 146Creating the Tape Action Workflow 147

Binding Variables to Configuration Parameters 149Enabling Open Workflows in Vantage 150

Using Live Capture with Avid Workflows 151Licensing Live Capture Systems for Avid Workflows 152

Live Capture-only Vantage Domains 152For Live Capture System as Part of a Separate Vantage Domain 152

Required Avid Components Installed by User/Avid 152Using the Interplay Advanced Encoder 153Prototype Single Resolution Avid Workflow 155Prototype Multiple Resolution Avid Workflow 156Updating Avid User Properties in Capture Jobs 158

Setting Default Metadata Values for Capture Operation 160Updating Metadata Values During an In-Progress Capture 162

Creating an Avid User Properties Metadata Label 164Creating a Capture-to-Interplay-with-Metadata Workflow 165Creating a Dynamic-Metadata-Update Workflow 167

Using the Live Capture Web Application 169Prerequisites to Using Live Capture 170Accessing the Lightspeed Live Capture Web App 171

Creating and Using External Links 171Create a Separate Account for Each User 172Multiple User Access to the Capture or Tape Web Apps 172

Close Instances of the Web Application when Not in Use 172Changing the Domain 172

Lightspeed Live Capture Web App Overview 173What is a Channel? 173

Live Capture Controls and Operation Status 174Title Panel 174

Contents 13

Selection Panel 174Channel Previews Panel 175

Channel Previews Controls 176Configuring the Custom Ganged Recording Defaults 178

Channel Controls 180Trigger Type 181Channel Options 182Channel Recording Information 184Display and Information Panel 185

Loss of Signal Behavior 187Limited Bandwidth Behavior 188

Channel Status Panel 188Filtering Job Status 189

Triggers Determine the Method of Channel Control 190DAI Trigger 190Manual Trigger 192Recurring Segment Trigger 193Schedule Trigger 194Web Service Trigger 194

Recorded File Location and Format 195Selecting Output Encoders and Format 195Deleting Captured Files 195

Using the Vantage Job Status Views 196Opening Vantage Job Status Views 196The Vantage Job Status Views Web Application 197Configuring Job Status Views Information 198

Using the Tape Capture Web Application 199Prerequisites to Using Tape Capture 200Configuring the VTR Connection 201

Checking the VTR Connection Status 202Troubleshooting the VTR Connection 202

Accessing the Lightspeed Tape Capture Web App 204Changing the Domain 204

Tape Capture Overview 206Tape Capture Controls and Operation Status 207

Selection Panel 207Workflow/Status Panel 207Log Panel 208

Clip Panel 209Log 211EDL File Import and Export 211Capturing an Entire Tape 212Timecode Break Recording 212Tapes 215Clip Log 215Capturing Clips 216

Preview Player Panel 218

Contents14

VTR Controls and Keyboard Shortcuts 219Using the Tape Capture Web App 220

Setting up for Logging 220Creating Tape Names 220Creating a Clip 220Configuring Clip Stitching 221Capturing Clips 222Configuring Tape Parameters that are Bound to Variables 223Setting Drop/Non-Drop Frame Characteristics 224Creating a Stitched Clip 225Recording a Complete Tape—Even if It Has Errors 227

Using the Job Status View in Tape Capture 228

Calculating Live Capture Resources 229Lightspeed Live Capture Resource Calculator 230

Browser Operation is Not Included in Usage Calculations 231Determining the Time-Shift Buffer Duration 231

Standard Definition (SD) Codecs 231High Definition (HD) Codecs 231UHD/4K Codecs 231

Calculating your Resource Usage Capacity 232Resource Use Factor (RUF) Charts 233Primary Outputs—RUF Values 233Secondary Outputs - RUF Values 234Example 1—Uses a Total of 1.00 RUF 235Example 2—Uses a Total of 0.90 RUF 236

Capacity for Capturing Uncompressed Media Via 3G-SDI Inputs 237Example 3—Uncompressed 10-bit - Uses a Total of 1 RUF 238Example 4—Uncompressed 10-bit - Uses a Total of 1 RUF 239

Appendix A: Support 241Obtaining Support | Information | Assistance 242Return Material Authorization (RMA) Procedure 243Using Log Files and Other Support Information 244

Log Files for Live Capture 244Accessing the Log Files 244Changing Log Content Settings 244Downloading Log Files for Support 245

Resolving Capture Error Messages 247

Appendix B: Containers, Codecs, and Vantage Actions 249Capture Action Output Containers 250MXF OP1a Output 251

Generic MXF Format Summary 251Video 251Audio 251

Contents 15

Timecode 251MXF Applicable Standards 251Container Settings 252

General 252Aspect Ratio Mode 253

Video Stream Details 253Codec 253AVC 253Avid DNxHD 253Avid DNxHR 253DV 253DVCPRO HD 253IMX 253JPEG2000 Lossless (Comprimato) 253JPEG2000 Lossy (Comprimato) 254Panasonic AVC-Intra 255Panasonic AVC-Ultra 256Sony XAVC 256Sony XDCAM 256Uncompressed 256x264 256Time Code Burn-in Filter 256

Audio Stream Details 257Codec (PCM) 257General 257

MPEG2-TS Output 258MPEG-2 TS Format Summary 258

Video 258Audio 258

Container Settings 258Video Stream Details 259

Codec 259HEVC H/W 259MPEG-2 259x264 260Time Code Burn-in Filter 261

Audio Stream Details 261Codec 261AAC Codec 261General 261PCM Codec 262General 262Channel Map 262

QuickTime Output 263QuickTime Format Summary 263

Video 263Audio 263

Container Settings 263

Contents16

General 263Aspect Ratio Mode 264Clean Aperture 264

Video Stream Details 265Codec 265Apple ProRes 265AVC 265Avid DNxHD 265Avid DNxHR 265DV 265DVCPRO HD 265HEVC 265HEVC (H/W) 265IMX 266Panasonic AVC-Intra 266Uncompressed 266x264 266x265 266Time Code Burn-in Filter 267

Audio Stream Details 268Codec (PCM) 268Channel Configuration 268

QuickTime Open Output 269Format Summary 269

Video 269Audio 269

Container Settings 269General 269Important Information about Default Duration 270Aspect Ratio Mode 271Clean Aperture 272

Video Stream Details 272Codec 272Apple ProRes 272Avid DNxHD 272Avid DNxHR 272Time Code Burn-in Filter 272

Audio Stream Details 273Codec (PCM) 273Channel Configuration 273

TIFO Output 275TIFO Format Summary 275

Video 275Audio 275

Container Settings 275General 275Aspect Ratio Mode 275

Video Stream Details 276

Contents 17

Codec 276Apple ProRes 276Avid DNxHD 276Avid DNxHR 276AVC 276DV 277DVCPRO HD 277HEVC 277HEVC H/W 277IMX 277JPEG2000 Lossless (Comprimato) 277JPEG2000 Lossy (Comprimato) 278MPEG-2 279Panasonic AVC-Intra 280Panasonic AVC-Ultra 280Sony XAVC 280Sony XDCAM 280Uncompressed 281x264 281x265 282Time Code Burn-in Filter 282

Audio Stream Details 283Codec (PCM) 283

Proxy TIFO Output 284TIFO Format Summary 284

Video 284Audio 284


Video Stream Details 284Codec 285AVC 285DNxHD 285Apple ProRes 285Time Code Burn-in Filter 285


Proxy MP4 Output 287Container Settings 287Video Stream Details 287

Codec (AVC) 287AVC 287

Audio Stream Details 287Codec (AAC) 287

Proxy MXF RDD 25 Output 288Container Settings 288Video Stream Details 288

Contents18


Audio Stream Details 288Codec (AAC) 288AAC 289

Proxy HLS Output 290Container Settings 290Video Stream Details 290


Audio Stream Details 290Codec (AAC) 291

Tape Action Output Containers 292MXF OP1a Output 293

Generic MXF Format Summary 293Video 293Audio 293Timecode 293

MXF Applicable Standards 293Output Settings 294Container Settings 295

General 295Aspect Ratio Mode 295

Video Stream Details 295Codec 295AVC 295Avid DNxHD 295DV 295DVCPRO HD 296IMX 296JPEG2000 Lossless (Comprimato) 296JPEG2000 Lossy (Comprimato) 297Panasonic AVC-Intra 298Panasonic AVC-Ultra 298Sony XAVC 298Sony XDCAM 298Uncompressed 298x264 298Time Code Burn-in Filter 298


MPEG2-TS Output 300Format Summary 300

Video 300Audio 300

Container 300Container Settings 300Video Stream Details 301

Contents 19

Codec 301MPEG-2 Codec 302x264 Codec 302Time Code Burn-in Filter 302

Audio Stream Details 303Codec 303General 303Channel Map 303

QuickTime Output 304QuickTime Format Summary 304

Video 304Audio 304

Container Settings 304General Panel 304Aspect Ratio Mode 305Clean Aperture 305

Video Stream Details 306Codec 306Apple ProRes 306AVC 306Avid DNxHD 306Avid DNxHR 307DV 307DVCPRO HD 307HEVC 307HEVC (H/W) 307IMX 307Panasonic AVC-Intra 308Sony XDCAM 308Uncompressed (10-bit) 308x264 308x265 309Time Code Burn-in Filter 309


TIFO Output 312TIFO Format Summary 312

Video 312Audio 312

Container Settings 312General Panel 312Aspect Ratio Mode 312

Video Stream Details 313Codec 313Apple ProRes 313AVC 313

Contents20

Avid DNxHD 313Avid DNxHR 314DV 314DVCPRO HD 314HEVC 314HEVC H/W 314IMX 314JPEG2000 Lossless (Comprimato) 315JPEG2000 Lossy (Comprimato) 316MPEG-2 317Panasonic AVC-Intra 318Panasonic AVC-Ultra 318Sony XAVC 318Sony XDCAM 318Uncompressed 318x264 319x265 319HEVC (H/W) 320Time Code Burn-in Filter 320


Proxy TIFO Output 322TIFO Format Summary 322

Video 322Audio 322


Video Stream Details 322Codec 323AVC 323Avid DNxHD 323Apple ProRes 323Time Code Burn-in Filter 323


Proxy MP4 Output 325Format Summary 325

Video 325Audio 325

Container 325Container Settings 325

Aspect Ratio Mode 325Video Stream Details 326

Codec (AVC) 326Time Code Burn-in Filter 326

Contents 21


Proxy MXF RDD 25 Output 328Container Settings 328Video Stream Details 328


Audio Stream Details 328Codec (AAC) 328AAC 329

Poster Frame 329Container Settings 329

Primary Output - Video Codecs 330Apple ProRes 330AVC 331Avid DNxHD 331Avid DNxHR 331DV/DVCPro 332DVCPRO HD 332HEVC 332HEVC (H/W) 332IMX 333JPEG2000 LossLess (Comprimato) 333JPEG2000 Lossy (Comprimato) 334MPEG-2 336Panasonic AVC-Intra 337Panasonic AVC-Ultra 337Sony XDCAM 338Uncompressed (10-bit) 338x264 338x265/HEVC 339XAVC 340

Primary Output - Audio Codec 341PCM 341

Secondary Output - Video Codecs 343AVC 343ProRes Proxy 343DNxHD LB 343

Secondary Output - Audio Codecs 344AAC 344PCM 344

Vantage Actions 346Live Actions 346

Capture Action 346Tape Action 346SubClip Action (Technology Preview) 347

Cloud Actions 347Cloud Flip Action 347Cloud QC Action 347Cloud Speech Action 347

Contents22

Metadata Actions 348Extract Action 348Populate Action 348Transform Action 348

Transcode Actions 348Flip Action 349Flip64 349Split 350Stitch 350

Transport Actions 350Copy Action 351Delete Action 351Deploy Action 351Move Action 351

Common Actions 352Compute Action 352Construct Action 352Decide Action 352Forward Action 353Receive Action 353Synchronize Action 353

Communicate Actions 354Automate Action 354Message Action 354Notify Action 354

VidChecker Action 354

Appendix C: RS-422 VTR Interface 355RS-422 Interface Kit Assembly and Installation 356

What the RS-422 VTR Interface Kit Includes 356User-Supplied Cable 357

Installing the USB Cable Retainer on the Lightspeed Live Server 358Assembling & Installing the RS-422 Interface Box and Rack Mount Tray 359Connecting a VTR to the Lightspeed Live Server 362Creating the Tape Capture Workflow 363RS-422 Connector Pin Assignments 363Configuring an RS-422 COM Port's Latency Time 364

Video Disk Communications Protocol (VDCP) 365Making Connections 365Communications Signal 365Configuring VDCP Control 366VDCP Commands 368

Sense Requests 368Variable ID Length Sense Requests 368Immediate Commands 368Preset / Select Commands 368Variable ID Preset / Select Commands 369Frame Accurate Recording 369

23

Introducing Lightspeed Live Stream and Capture

This chapter presents an overview of Telestream’s Lightspeed Live Stream and Lightspeed Live Capture and the Lightspeed Live server platform.

■ Overview

■ Lightspeed Live Server Platform

■ Lightspeed Live Stream

■ Lightspeed Live Capture

■ Using Live Stream and Live Capture Concurrently

■ Lightspeed Live Application Program Interfaces

■ Lightspeed Live Server Hardware Specifications and Components

Introducing Lightspeed Live Stream and CaptureOverview

24


OverviewLightspeed Live Stream and Lightspeed Live Capture are two separate applications that run on a Lightspeed Live server to deliver real-time, enterprise-class live streaming for media and entertainment companies, corporations, government agencies, and educational facilities. Lightspeed Live Stream solves the problem of preparing real time content for adaptive bitrate live streaming, while Lightspeed Live Capture can independently record multiple channels of SD, HD, or a single channel of UHD.

Lightspeed Live Server PlatformThe Lightspeed Live server is a high-speed, high-capacity, real-time media processing server with these main components installed or included:

• Windows Server 2012 R2 Operating System for Live Capture and Live Stream

• (Optional, by request) Windows Server 2016 Operating System for Live Stream

• High speed multi-core processors

• GPU

• SDI input card

• Lightspeed Live Stream web application (when configured as Live Stream server)

• Vantage media processing software (when configured as Live Capture server)

• Lightspeed Live Capture web application (when configured as Live Capture server)

Documentation is available directly in applications and on flash drive (optional DVD by request). The most up-to-date versions are available on the Telestream web site.

For additional details and specifications, see Lightspeed Live Server Hardware Specifications and Components.

Control via WebControl via:Web, API, or Calendar.

HLS, DASH, and more

Web Service

API

Web Service

API

VantageOpen

Workflows

Storage/SANs

DELIVER

LiveSources

Lightspeed LiveCapture

SD/HD/UHD SDI

Lightspeed LiveStream

Lightspeed Live 1RUcan host Stream and/or Capture

CDNOrigin

Introducing Lightspeed Live Stream and CaptureLightspeed Live Stream

25


Lightspeed Live StreamLightspeed Live Stream encodes a live program at highest quality and simultaneously streams the output over the Internet or intranet via Transport Stream or RTMP, to origin servers for distribution to Content Delivery Networks (CDN). Lightspeed Live Stream can be deployed as a stand-alone solution for live multi-screen services or installed on the same server as Lightspeed Live Capture, where they share the SDI and network-based sources.

Lightspeed Live Stream ingests live content via 3G baseband (SDI) as well as IP sources via 10Gb Ethernet. Output is encoded and delivered as Adaptive Bit Rate (ABR) packages, including HTTP Live Streaming (HLS), CMAF, ATS, and MPEG DASH (in AVC and HEVC) at SD, HD, and UHD resolutions. Lightspeed Live Stream can also record an MP4 version of any variant for use as an archive or proxy of a stream or package.

Note: Lightspeed Live Stream is a standalone appliance that runs exclusively on a Lightspeed Live Server. Individual Lightspeed Live Stream appliances can be joined together to create a multi-server streaming group.All Live Stream software and background processes are completely independent of Vantage services, components or licensing. You can obtain a Lightspeed Live Stream license by contacting Telestream Licensing, and it applies to the Lightspeed Live Stream software only.

Lightspeed Live CaptureLightspeed Live Capture is a highly-scalable and flexible multiple channel capture solution for ingesting high-resolution and proxy files for use in production, post-production or broadcast workflows.

Until now, file-based and siloed systems required a serial workflow. By closely integrating parallel file-based open workflows with the combined CPU/GPU power of the Lightspeed Live server and applications, the fastest possible delivery of all assets is realized.

Note: Live Capture is built on the Vantage Media Processing Platform. The Lightspeed Live Capture server ships with the following Vantage services pre-installed: Live, Transport, Transcode, Metrics, SDK, Cloud, Metadata, and Communicate. No other Vantage services can be installed or executed on a Lightspeed Live server.Individual Lightspeed Live Capture servers can be joined together to create a multi-server capture farm or joined to an another Vantage domain allowing Live Capture server(s) to be seamlessly integrated into its workflows. Live Capture servers use Vantage Media Processing Platform licensing.

Introducing Lightspeed Live Stream and CaptureUsing Live Stream and Live Capture Concurrently

26


Using Live Stream and Live Capture ConcurrentlyA Lightspeed Live Server can host Lightspeed Live Capture or Lightspeed Live Stream independently or host both applications simultaneously, sharing SDI and network-based sources.

Note: Release notes and Support Services are the best sources of compatibility information regarding the use of Live Stream and Live Capture on the same server.

Although both applications can operate stand-alone, the greatest benefits are realized when Lightspeed Live Stream is installed on a Lightspeed Live Server with Live Capture coupled to Telestream’s Vantage platform for complete workflow orchestration. In this configuration, you can concurrently stream, capture, and process live content for consumption on a wide variety of platforms.

Lightspeed Live Capture, in addition to operating as a standalone capture system, can extend live encoding capability by providing live capture in a number of high-quality mezzanine formats in the Vantage Media Processing Platform. Through this integration, you can simultaneously make use of both the real-time streaming capability and the full range of video manipulation that Vantage offers.

Shared Resource AllocationSince Live Capture and Live Stream use shared operating resources, care is needed to avoid over subscription of CPU, GPU, memory, and other resources. Source content coming through the Lightspeed Live server inputs can be used by both Live Capture and Live Stream. See Live Stream Server CPU/GPU Usage Guidelines for information about creating efficient Live Stream channels.

Introducing Lightspeed Live Stream and CaptureLightspeed Live Application Program Interfaces

27


Lightspeed Live Application Program InterfacesThe three Lightspeed Live web APIs—Capture, Stream, and Source —enable you to monitor and control your Lightspeed Live system within a broader, web services-based system or create your own customized monitoring system.

You can also create a web services-based system to control streaming and capture beyond the functionality or capability of the general-purpose Vantage Capture and Stream web applications, to meet your organization’s requirements.

Lightspeed Live Stream Web APIThe Lightspeed Live Stream Web API enables custom programs to remotely control the operation of the Live Stream services by implementing it in a custom program.

To access the Live Stream Web API Reference directly in Lightspeed Live, click the General menu in the upper right of the Live Stream web application and select About > Web API Reference.

Lightspeed Live Capture Web APIThe Lightspeed Live Capture Web API enables recording of live streaming media in a Vantage workflow to be controlled manually via the HTTP web service. The Capture web API is implemented in the Lightspeed Live Capture web service.

The Live Capture Web API is described in the Lightspeed Live Capture Web API Reference at the bottom of the Live Support page on the Telestream web site.

Lightspeed Live Source Web APIThe Lightspeed Live Source Web API supports the insertion of SCTE-35 and ID3 tags. Use of the Source API to insert tags can be performed during capture or stream sessions. The Source API is implemented in the Lightspeed Live Source web service.

The Lightspeed Source web API is also described in the Lightspeed Live Capture Web API Reference.

http://www.telestream.net/telestream-support/lightspeed-live/support.htm


Introducing Lightspeed Live Stream and CaptureLightspeed Live Server Hardware Specifications and Components

28


Lightspeed Live Server Hardware Specifications and Components

The Lightspeed Live server is a high-speed, high-end Windows server configured specially for streaming and capturing live video using a pre-installed SDI input card and hosting Telestream Vantage with the Lightspeed Live Stream and Lightspeed Live Capture web applications or independently for high-performance media processing.

The following table summarizes the Lightspeed Live server hardware details, followed by more detailed descriptions of the components.

Lightspeed Live server Hardware Details (subject to change without notice):

Components Description

RAM 64 GB or 96 GB (model-dependent)

CPU Dual Multi-Core CPUs

GPU 1 GPU

OS Drives 1 SATA SSD drive for Windows OS (top right-most slot)

1 optional OS SSD drive configured in RAID 1 (bottom, right-most slot)

Storage Drives 4 RAID 5 SAS hard drives, 1.2TB per drive, 10k RPM

4 additional SAS drive bays

SAS Controller Supports up to 8 SAS3 media drives

PCIe Option Slot 1 half-height PCIe 3.0 x8 slot or 1 full-height PCIe 3.0 x16 slot (model-dependent)

Capture and Stream Hardware

1 standard 4-input or 8-input SD/HD/3G-SDI input card

Video Input Standard: 4 or 8 video plus 1 LTC mini-BNC inputs (model-dependent)

Optional: 4 video inputs plus 1 LTC standard BNC input (Stream only)

USB 3.0 2 front, 2 back

Ethernet Four 10-Gb ports

VGA Monitor 1 VGA monitor port

AC Inputs 2 redundant AC inputs, 100-240 Volts, 4.5-9.5 Amps, 50-60 Hz.


29


System PowerThe chassis features redundant hot-swappable dual digital power supplies that automatically sense the input voltage between 100v to 240v, and operate at that voltage. Power cords plug directly into the power supply units at the back of the chassis, and the Power On/Off (0/1) button on the front energizes the unit. A green light indicates that the power supply is operating. When a power supply fails or is disconnected, an amber light on the power supply illuminates and an alarm sounds.

DrivesThe chassis supports up to eight SAS hot-swappable 2.5" media hard disk drives. The eight drive bays on the left (viewed from the front) support SAS3 media drives, four of which are included as standard. These eight storage drives can be configured for RAID 0, 1, 5 or 10 (RAID 5 set at the factory). The two additional bays on the right support only SSD/SATA drives. The top right bay is reserved for the Windows OS drive, and the bay below it is available.

When replacing or adding hard drives, replace with matching drives:

• HGST Ultrastar C10K1800 or Seagate Enterprise Performance ST1200MM0129 drive

• 1.2 TB capacity, 10K RPM

• 128MB cache buffer, 12Gb/s data rate

Front Control PanelThe chassis front control panel provides system monitoring lights and control buttons which are described later (see Front Panel).

Cooling SystemThe system cooling design features eight 4-cm counter-rotating fans located in the middle section of the chassis. Fan speed is controlled by the IPMI system management software to respond to fluctuations in system temperature.

Dual air shrouds direct air flow to the dual CPUs and components that require cooling. The power supply module also includes a cooling fan.

RS-422 for VTR(optional)

4-Port RS-422 VTR Interface (Capture only).

Operating Environment

10 degrees C to 35 degrees C, 8-90 percent humidity (non-condensing)

Lightspeed Live server Hardware Details (subject to change without notice):

Components Description


30


SDI Input CardsThe standard (or optional HEVC; supported by Live Stream only) SDI input cards are installed in one of the Lightspeed Live server's PCI card slots and provides up to 8 SD/HD/3G-SDI serial digital (SDI) inputs allowing for up to 8 independent SD/HD/3G SDI signals or 2 UHD/4K signals. Additionally, one input is provided for an analog Longitudinal Timecode (LTC) for use across all SDI input signals (see Data and Signal Connections).

For standard cards each input consists of a mini-BNC connector and can be converted to standard BNC with the included mini-standard BNC converter cables. For 4K and Ultra HD, SDI-1 through SDI-4 or SDI-5 through SDI-8 (model-dependent) BNC connectors can be used to provide a 4K or Ultra HD input. The 4K/UHD signal should be connected to all four BNC inputs (SDI-1 through SDI-4). All other resolutions use one BNC per input.

SDI Card Input FormatsLightspeed Live Capture supports the following SDI input types:

SDI Input Video– SD-SDI NTSC 525i29.97/PAL 625i25

– HD-SDI 720p50/59.94/60

– HD-SDI 1080i25/29.97/30

– HD-SDI 1080p23.98/24/25/29.97/30

– HD-SDI 1080psF23.98/24/29.97/30

– 3G-SDI 1080p50/59.94/60 (Level A only)

– Quad Link UHD 3840 x 2160p23.98/24/25/29.97/30 (

– Square Division Level A only)

– Quad Link UHD 3840 x 2160p50/59.94/60 (2SI/Square Division Level A/B)

– Quad Link 4K 4096 x 2160p23.98/24/25/29.97/30 (Square Division Level A only)

– Quad Link 4K 4096 x 2160p50/59.94/60 (2SI/Square Division Level A only)

SDI Input Audio– S16-channel 24-bit Little Endian SDI embedded, 48 kHz synchronous

Input Reference• SD/HD—Reference is derived from an internal free-run clock on each 3G-SDI input.

• UHD/4K—Reference is derived from an internal free-run clock on each 3G-SDI input.

Notes: All 16 channels of audio for UHD/4K are provided on SDI Input #1 and SDI Input #5 (model-dependent).

Sources in the YCbCr 444 or RGB 444 color space are not supported. Only the YUV 422 color space is supported.


31


GPUThe GPU in the Lightspeed Live server accelerates video processing and H.264/H.265 media creation. Using the GPU in combination with Lightspeed Live’s powerful dual CPU processors enables the creation of streaming and captured media from multiple live input sources.

Expansion Input Card SlotsThe system supports one optional full- or half-height PCIe card, installed by Telestream.

In order to ensure optimal product performance and warranty coverage, insure that Telestream products are used in accordance with the following product policy. It is critical that our product policy be adhered to when using add-in cards:

• Add-in card(s) are to be installed by Telestream, or an authorized agent, at or before commissioning.

• Only Telestream-qualified add-in cards can be used. For the most up-to-date list refer to the Lightspeed Live Server product sheet on the Telestream.net web site. Using untested and unknown add-in cards voids the product warranty.

Note: Except for externally removable power supplies and disk drives, the Lightspeed Live server has no user-serviceable parts. To maintain your warranty, any repair or additional PCI card installation and any service inside the sealed top cover must be performed by Telestream or an authorized Telestream service technician.

RS-422 VTR Interface Kit Option for CaptureThe optional 4-Port RS-422 VTR Interface Kit provides the ability to connect up to four VTR units to the Lightspeed Live server, and allows a VTR to be remotely controlled by the Lightspeed Tape Capture application to facilitate conversion of tape-based media into digital video files.

http://www.telestream.net/lightspeed-live/techspecs.htm

http://www.telestream.net


32


Front PanelThe Lightspeed Live server has a removable front bezel. By removing the bezel, you can access the system interface buttons and LEDs, drives, and front USB ports.

Front Panel FeaturesThe front bezel provides visibility of the system monitoring LED indicators and allows pinhole access to the recessed UID and power buttons. This graphic illustrates the front bezel and below, the bays exposed when the bezel is removed:

LEDs (left to right)• System Overheat | FAN Fail | UID

• Network Activity (NIC1)

• Network Activity (NIC2)

• Hard Drive Activity

• Power

UID Button (left)The UID button alternately turns on and off the blue front and rear panel UID LEDs used to locate a particular unit among many units in a rack or server room.

Power On/Off Button (right)Press the Power On/Off button to perform a normal power up/power down cycle or a hardware reboot (hold the button down for 4 seconds). A reboot abnormally terminates connected clients and systems and should be done only in the event of an unrecoverable system error. Under normal conditions, you should properly close client programs and shut down the domain and OS before cycling power.

USB PortsTwo USB 3.0 ports for general use are located below the LEDs and buttons.

LEDs On/Off Button

2 USB 3.0

SSD/SATA OS Drive

4 included RAID 5 SAS drives

4 RAID 5 SASoptional drive bays

Optional SSD or SATA drive bay

UID Button


33


DrivesThe top right-most drive bay houses the SSD/SATA Windows OS drive, and the drive beneath it is an available SATA drive bay. These drives have their own controller, separate from the storage drives.

To the left of the OS drive are 8 SAS media storage drive slots containing the 4 standard and 4 optional media drives. These drives are configured for RAID 5 and have their own controller separate from the OS drive.

Rear PanelThese are the rear panel ports and connectors:

• 2 redundant AC power connectors—connect to a 10-amp or greater AC source

• 4 10GbT Ethernet LAN ports—connect as required to Ethernet LAN

• 2 USB 3.0 ports—connect as required to keyboard, mouse, or other serial device

• 1 IPMI Ethernet dedicated port that should not used for any other purpose

• 1 VGA monitor port

• 1 COM control port (not used)

• 4-input or 8-input card with 3G-SDI inputs

• 1 analog LTC input

Lightspeed Live Server rear panel, showing the 4-input card and 8-input card:

Additional PCIe cards can be optionally installed by Telestream in the PCIe expansion slots.

AC Power Connectors

1 PCIe half-height 3.0x8 expansion slot for Telestream-approved cards

4 Onboard 10Gb Ethernet LAN ports

IPMI port(dedicated)

2 USB VGACOM4 mini-BNCSDI Inputs

UnusedLTC

SDI 4-input CardGPU

SDI 8-input Card

LTC


34


Video Input ConnectionsThe Lightspeed Live server includes an installed standard SDI input card (included) or an optional HEVC SDI input card in the lower right PCI slot. For a complete list of video formats, see the SDI Input Cards.

Standard 4 SDI Input CardThe standard 4 SDI input card contains 5 miniature BNC video input connectors with 5 adapter cables to convert to full-size BNC connectors:

• SDI Inputs 1-4: SD/HD/3G x 1080/4K video formats; audio 16-Channel, 24-bit SDI embedded, 48 kHz synchronous

• Input R: LTC timecode input

Standard 8 SDI Input CardThe standard 8 SDI input card contains 9 miniature BNC video input connectors with 9 adapter cables to convert to full-size BNC connectors:

• SDI Inputs 1-8: SD/HD/3G x 1080/4K video formats; audio 16-Channel, 24-bit SDI embedded, 48 kHz synchronous

• Input R: LTC timecode input.


35


Optional HEVC SDI Input Card (Supported by Live Stream only)The HEVC card replaces the standard SDI input card and contains 5 full-sized BNC video input connectors:

• SDI Inputs: SD/HD/3G x 1080/4K video formats; audio 16-Channel, 24-bit SDI embedded, 48 kHz synchronous

• LTC Timecode Input: The BNC connector on the bottom of the board, on the far right in the picture below:

Introducing Lightspeed Live Stream and Capture36


37

Installing and Maintaining a Lightspeed Live Server

This chapter explains how to install the Lightspeed Live server into an equipment rack and configure it for operation.

■ Installing the Server

■ Making Connections

■ Managing the Operating System

■ Maintaining the Lightspeed Server

■ Monitoring Lightspeed Live via SNMP

Installing and Maintaining a Lightspeed Live ServerInstalling the Server

38


Installing the Server■ Unpacking the Server

■ Rack Installation

WARNING: Only trained and qualified personnel should be allowed to install, replace, or service this equipment.

CAUTION: Except for replaceable power supplies and hard drives which may be accessed from the outside, the Lightspeed Live server is a sealed device, with no user-serviceable parts or user-accessible expansion slots. You should never open the top cover or attempt to upgrade or alter the server. Doing so exposes you to electrical hazard, may damage the unit, and may invalidate your warranty. If you have hardware or software problems with your Lightspeed Live server, follow the steps in Appendix A: Support of this guide to obtain service.

Note: Before proceeding, work with your network administrator to determine computer and network setting requirements.

Unpacking the ServerThe Lightspeed Live server arrives packed in a heavy duty cardboard box with foam padding surrounding the device to protect it. During unpacking, inspect the container and the contents for damage. In the event of damage, report it immediately to the freight carrier and to Telestream Support.

The server is heavy. Unpack the server on a strong, well-balanced table that can support the full weight of the server and shipping container without tipping.

Inside the box are the server, optional components such as rack rails, five mini BNC to standard BNC cables, and documentation on paper and flash drive (a DVD is available by request).

Rack InstallationThe Lightspeed Live server is designed to fit into a standard 19-inch (483 mm) equipment rack with support front and rear, using supplied rack rails and rear support extensions.

Assembling the RailsThe inner rail extensions install on each side of the chassis as shown. Align the extension’s holes with the hooks on the side rail and slide the extension forward to engage the hooks until the quick release bracket snaps into place. For added stability, you can secure the extension with a screw.

http://www.telestream.net/telestream-support/overview.htm


39


The outer rails assemble by sliding the front and rear sections together as shown.

Installing Outer Rails into a RackNext, install the outer rails into the rack as shown in the next figure. Align the square pegs on the front of the rail with the square holes in the front of the rack (C).

Push the rail into the rack until the quick release bracket snaps into place, securing the rail to the rack.

Extend the rear of the rail to align its square pegs with the square holes on the rear of the rack (D). Push the rail into the rack until the quick release bracket snaps into place, securing the rail to the rack.


40


CAUTION: To prevent the server chassis from falling and becoming damaged, be sure the rails are solidly in position and ready to support the full weight of the chassis.

F

Installing the Server in the RackWhen selecting a position in a rack to place the server, be sure to allow a minimum of 30 inches of clearance at the back of the server for sufficient cooling airflow and servicing.

To install the server, follow this procedure:

Slide the inner rail extensions forward into the front of the outer rails.

Support the chassis and align the back of the chassis with the front of the rails.

Push the chassis backward, sliding it into the rack rails, until the chassis clicks into the locked position.


41


CAUTION: To prevent the server from falling and becoming damaged, be sure to insert it securely in the rack before you remove support.

To remove the server from the rack, press the outer rail latch shown in the figure to release the chassis.

Slide the chassis forward off the outer rails and out of the chassis.

Installing and Maintaining a Lightspeed Live ServerMaking Connections

42


Making ConnectionsThis topic describes the server’s connectors and how to connect to them. Follow the order of connections given here:

■ Data and Signal Connections

■ Power Requirements and Connections

Data and Signal ConnectionsMake the following data and signal connections at the back of the server unit:

• Make Ethernet LAN connections to provide network connectivity.

Note: The Lightspeed Live Stream server can generate large amounts of network traffic when actively streaming. To prevent possible network issues, consult with your IT administrator to determine the best network configuration for your environment.

• Connect devices, such as a keyboard and mouse, to the USB connectors (optional).

• Connect a dedicated IPMI LAN to the IPMI port (optional).

• Connect a monitor to the VGA connector (optional).

• Connect SDI video sources to the connectors on the SDI input card using the sup-plied mini-to-BNC SDI cables.

Lightspeed Live Server Rear Panel, showing the 4-input card and location of the 8-input card:

AC Power Connectors

1 PCIe half-height 3.0x8 expansion slot for Telestream approved cards only

4 Onboard 10Gb Ethernet LAN ports

IPMI port(dedicated)

2 USB VGACOM4 mini-BNCSDI Inputs

UnusedLTC

SDI 4-Input Card

GPU

SDI 8-Input Card


43


Power Requirements and ConnectionsAfter the server chassis has been physically installed and all other connections made, connect the two redundant AC power cords to the back of the chassis and to an AC power source. Be certain to observe the following AC power and connection requirements and all applicable electrical codes.

The Lightspeed Live server is rated at 100-240 VAC, 50-60 Hz, up to 10 amps. Take the following precautions to ensure a safe power connection:

• Make certain that the power source circuit can supply voltage within the specified range and current of at least 10 amps without becoming overloaded.

• Counted together, the server and other devices connected to the same power source must not exceed the total capacity of the power source circuit.

• To protect against circuit overload and overheating, ensure that the power source circuit includes a circuit breaker no greater than 250 Volts, 20 Amps.

When power is connected, press the Power On/Off (0/1) button on the front of the chassis to turn the server on. To turn power off at any time, press the Power On/Off button again.

Power and General Cautions and WarningsObserve the following precautions when connecting power and operating the server.

WARNING: Only trained and qualified personnel should be allowed to install, replace, or service this equipment.

WARNING: Hazardous voltage or energy is present on the backplane when the system is operating. To prevent possible injury or death, use caution when servicing.

WARNING: This product relies on the building's installation for short-circuit (over-current) protection. Ensure that the protective device is rated not greater than 250 Volts, 20 Amps.

WARNING: Ensure a proper earth ground connection to the ground conductor in the AC power plug. Failure to do so could present a severe electric shock hazard that could result in injury or death.

CAUTION: Telestream recommends connecting computer equipment to AC power through an uninterruptible power supply (UPS) with surge protection. Fluctuations in commercial supply voltage can damage unprotected electronic equipment. A high quality surge suppressor may be substituted if a UPS is not available, but it may not provide adequate electrical spike protection.


44


WARNING: When installing the product, use the provided or designated connection power cables. Using any other cables could cause a malfunction or a fire.

WARNING: The fans might still be turning when you remove the replaceable power supply from the chassis. Keep fingers, screwdrivers, and other objects away from the openings in the replaceable power supply’s housing.

WARNING: Power supplies and other components can get very hot. Use caution when touching possibly hot components during operation and directly after unplugging.

WARNING: This unit has two power supply connections. Both connections must be removed to completely de-energize the unit.

Installing and Maintaining a Lightspeed Live ServerManaging the Operating System

45


Managing the Operating System Windows Server 2012 R2 (Standard 64-bit) is pre-installed on the Lightspeed Live server on an SSD drive. See microsoft.com for OS specifications.

Microsoft Activation KeyA sticker on the top surface of the Lightspeed Live server lists license numbers. The Physical Key number is the OEM license number for the Microsoft Windows operating system. If you reinstall the OS, use this key to activate Windows again. The key typically contains five groups of five digits, for example: YFG8H-TDD97-6BR4G-F88PF-XXXXX.

Microsoft UpdatesThe Lightspeed Live server ships with the Windows operating system set to check for updates, but it does not automatically download or install them. Downloading and installation of critical operating system updates is the responsibility of each customer (see your system administrator).

Windows User ID and PasswordWhen a Lightspeed Live server starts, log into with this Windows user account::

Windows FirewallThe Lightspeed Live Capture web applications use port 8083 and/or 8084, and by default, select any available TCP/IP port between 1024 and 65534 for the web app’s Live Preview display. To customize the available Live Preview ports, refer to Managing and Configuring Sources. The Live Source Manager web app uses port 8090 and the Live Stream web app uses port 8089. If you use Windows Firewall, be sure those ports are open on the Lightspeed Live server and across your network.

To open the Windows firewall on the Lightspeed Live server or other Windows computer, go to Start > Control Panel > Windows Firewall > Allow a program or feature through Windows Firewall > Allow another program.

Scroll through the list of programs, and click Add for each of these: Lightspeed Live Capture, Lightspeed Live Stream, Vantage Management Console, and Vantage Workflow Portal.

Click OK to close the programs list. The added programs appear in the firewall list, and you can check which networks they can use. Then close the Control Panel.

Lightspeed Server Windows User Account

User Administrator

Password telestream!1

http://www.microsoft.com

Installing and Maintaining a Lightspeed Live ServerMaintaining the Lightspeed Server

46


Maintaining the Lightspeed ServerThe following section describes common server maintenance tasks that you may need to perform from time to time:

■ Performance Tuning a Lightspeed Live Server

■ Backing up the Lightspeed Live Server

■ Managing the Lightspeed Live Server

■ Installing New or Replacement Hard Drives

■ Rebuilding the Lightspeed Live Storage RAID

■ Replacing Power Supplies

■ Monitoring Lightspeed Live via SNMP

Performance Tuning a Lightspeed Live ServerThe following settings are made at the factory to ensure best performance of your Lightspeed Live server. The settings are supplied here in the event they have been changed and you want to restore them to factory original settings. (For details, consult your System Administrator or a Telestream Field Sales Engineer).

1. In Performance Options, set Windows Performance options:

a. Navigate to Start > Control Panel > System > Advanced system settings > Settings button > Visual Effects tab.

b. Select Adjust for best performance.


47


c. Select the Advanced tab.d. Select Background services for Vantage transcoding nodes and SQL nodes. Select

Programs for editorial systems and Vantage client applications that are not running other Vantage services.


48


e. Select the Data Execution Prevention tab:f. Select Turn on DEP (Data Execution Prevention) for essential Windows programs and

services only.

g. Click OK in both dialogs to save your changes.

2. Set User Account Control (UAC):

a. Navigate to Start > Control Panel > User Accounts > Change User Account Control Settings. Set as low as safely possible, considering your exposure to Internet viruses and malware. Click OK to save your changes.

3. Set Power Options to High Performance with Sleep disabled:

a. Navigate to Start > Control Panel > Power Options.b. Select the High Performance plan. c. Select Change plan settings, and set Turn off the display to Never. d. Select Change advanced power settings, and set all critical functions so that they

are always ON (this usually means setting them to Never turn OFF). Click OK to save your changes and close the dialog.

e. Click the Save Changes button on the Edit Plan Settings window.


49


4. Disable (turn OFF) any real-time software applications and processes, such as the following, that could adversely affect disk I/O performance or use excessive CPU:

– Real-time virus scanning of media files as they are being captured.

– Automatic software updates that can preempt real-time services.

– Real-time file indexing.

5. Disable all unnecessary Windows services in Start > Control Panel > Administrative Tools > Services (consult your System Administrator).

6. Turn OFF all firewalls (including third party firewalls) and packet filtering, which may cause unpredictable performance:

a. Navigate to Start > Control Panel > Windows Firewall > Turn Windows Firewall on or off, select Turn off Windows Firewall.

If you choose to use firewalls, open them for the applications installed on the Light-speed Live server.

7. You may increase network throughput by increasing buffer size in your network adapter. Set your Network Adapter’s transmit and receive buffers to 1024:

a. Navigate to Start > Control Panel > Network and Sharing Center > Change Adapter Settings > Local Area Connection > Right-click and select Properties.

8. Disable any screen savers:

a. Navigate to Start > Control Panel > Personalization > Screen Saver and select (None).

9. Disable disk indexing:

a. Right click on Start and select Disk Management from the pop-up menu. b. Right-click each disk and select Properties. c. In the General tab uncheck Allow files on this drive to have contents indexed in

addition to file properties, unless you want some drives to be indexed.

Backing up the Lightspeed Live ServerIn order to protect your Lightspeed Live server from data loss, Telestream highly recommends that you create an image of the Operating System drive (C:\) drive immediately upon taking delivery of your server and that you perform periodic back-ups of all critical data on the server.

Several disk image software solutions are available for creating a restoration image that you can use to restore the Lightspeed Live server's operating system drive (C:\) to its original state. Using software solutions such as these, along with regular backups, you can restore your server back to its original shipping state with all of your critical data:

• Norton Ghost

• Clonezilla

Consult your IT/Systems administrator for details on creating restoration images and performing a periodic backup of your Lightspeed’s critical data.


50


Managing the Lightspeed Live ServerIPMI View management software provides remote network management of one or more Lightspeed or Lightspeed Live servers using IPMI messages over Ethernet LAN or a dedicated IPMI LAN. If your Lightspeed Ethernet connectors are used to connect to storage, you can use the IPMI LAN connector to create an IPMI network among your Lightspeed servers.

To download IPMI View, paste this expression into your browser and press Enter: ftp://ftp.supermicro.com/utility/IPMIView/.

You’ll find the IPMI View User’s Guide at this browser location: ftp://ftp.supermicro.com/utility/IPMIView/IPMIView20.pdf

Among the tasks you can perform using IPMI View are these (see the IPMI View User’s Guide for details):

• Discover Lightspeed Servers on the IPMI network (requires dedicated IPMI LAN)

• View system event logs

• Check current sensors and monitor history of fans, voltages, temperature, and power supplies

• View firmware revision levels

• Perform various kinds of shutdowns and resets

• Blink the UID LED to locate a particular unit in the rack or server room

• Set fan speed

• Manage LAN configuration, SNMP configuration, and RS232 modem

• Manage users, passwords, and privileges

• Set up paging of users in the event of malfunctions

• Establish Text Console Redirection or KVM Console Video Redirection for remote system control via text display or full graphic display

• Access virtual media

• Set up server management groups

• Update firmware

For detailed instructions about using any of these system management features, consult the IPMI View User’s Guide.


51


Installing New or Replacement Hard DrivesFollow these steps to replace a failing hard drive or install a new one. Drives may be removed or replaced with power on. See Drives for new or replacement drive specifications.

1. Remove the front bezel from the chassis.

2. Press the release button on the right front of the drive carrier.

3. Use the drive carrier handle to pull the carrier out of the chassis.

4. Remove the drive or dummy drive from the carrier by removing the four M3 screws from the underside of the carrier. Retain the screws.

5. Insert the new drive into the carrier with the PCB side down and the connector facing the back of the carrier.

6. Secure the drive to the carrier with the four M3 screws retained from removal. Gently tighten but do not over tighten the screws, which could cause damage.

7. Slide the drive carrier into its bay with the drive facing up until the drive seats firmly in the rear connector.

8. Push the carrier handle closed flat against the front of the carrier to secure the carrier and drive in place.

9. Replace the front bezel on the chassis, and go to the next topic to rebuild the RAID.


52


Rebuilding the Lightspeed Live Storage RAIDThe MegaRAID Storage Manager software on the Lightspeed Live server enables you to rebuild the storage RAID if necessary, such as when you add a new drive, or want to change drive configurations. The MegaRAID Storage Manager is located at:

C:\Program Files (x86)\MegaRAID Storage Manager

In the MegaRAID Storage Manager folder, locate the startupui.bat file and double-click it to start the application. In the initial application panel, click on the server you want to work with, then enter your credentials to log in. The MegaRAID Storage Manager application opens.

Replacing Power SuppliesThe Lightspeed Live server includes two redundant, hot-pluggable power supply modules. They automatically sense the input voltage between 100v to 240v, and operate at that voltage. Power cords plug directly into the power supply units at the back of the chassis. A green light indicates that the power supply is operating. When a power supply fails or loses power, an amber light on the power supply illuminates and an alarm sounds.

If either of the power supply modules fail, the other module supports the full load and allows the system to continue operation without interruption. The PWR Fail LED illuminates and remains on until the failed unit has been replaced. Replace with the same model. Replacement units can be ordered from Telestream. See Appendix A: Support in this guide for information about contacting Telestream Support to order parts.

Replacing the Power Supply1. Unplug the AC power cord from the failed power supply module.

2. Push in the locking tab at the back of the module to release it.

3. Pull the unit straight out of the chassis.

CAUTION: The power supply may be very hot when first unplugged and could cause burns. Handle carefully by the edges and do not touch hot components.

4. Insert the new unit into the chassis, pushing it in until it clicks firmly in place.

5. Reconnect the power cord.

Installing and Maintaining a Lightspeed Live ServerMonitoring Lightspeed Live via SNMP

53


Monitoring Lightspeed Live via SNMPManagement Information Base (MIB) files are provided for those organizations wanting to manage their Lightspeed Live servers via SNMP.

MIB files can be found on the Lightspeed Live server in this location:

C:\Program Files\Telestream\Live Stream Server

MIB files can also be found on the Lightspeed Live DVD or USB thumb-drive in the SNMP folder.

Enabling SNMP MonitoringYou should add three lines (add, target, and logger) to the SourceService.exe.config and LiveService.exe.config files in order to enable SNMP traps and configure ports. For more information about log files see Using Log Files and Other Support Information.

Note: The ports must be different in each file and port 62 should not be used.

The following example shows a typical configuration file, with the added lines in red:<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><extensions><add assembly="NLog.Targets.Snmp" />

</extensions><targets><target name="logconsole" xsi:type="Console" layout="[${level}] ${message}" /><target name="logfile" xsi:type="File" archiveAboveSize="10000000" maxArchiveFiles="1000" fileName="${specialfolder:folder=ApplicationData}/Live/SNMPLogs/LiveService-${date:format=yyyy-MM-dd}-log.txt"layout="${longdate} [${level}] ${message}" /><target name="snmp" xsi:type="Snmp" port="163" />

</targets><rules><logger name="*" minlevel="Info" writeTo="logconsole" /><logger name="*" minlevel="Warn" writeTo="logfile" /><logger name="*" minlevel="Info" writeTo="snmp" />

</rules></nlog>

Installing and Maintaining a Lightspeed Live ServerMonitoring Lightspeed Live via SNMP

54


55

Configuring the Lightspeed Live Capture Server and Apps

This chapter explains how to configure and maintain the Lightspeed Live Capture software, including implementing updates.

These topics help you configure and maintain the server:

■ Changing a Source Name

■ Managing and Configuring Sources

■ Configuring Capture Resources

■ Configuring Settings for Your Facility

■ Using Inputs for Both Live Stream and Capture

■ Configuring Ingest Sources

■ Installing the Live Capture & Tape Capture Web Apps

■ Renaming or Reconfiguring Servers

■ Updating Capture using Secured Version Control and ComponentPacs

■ Clear Browsing Data after Updating Vantage or Live Capture

Configuring the Lightspeed Live Capture Server and AppsChanging a Source Name

56


Changing a Source NameThe default names for SDI ports has this form: “SDI Input [1 through n]”, where ‘n’ is 4 or 8 depending on which Lightspeed Live server you have. To rename a source, follow the procedures below and observe these renaming rules:

• Use the Source Manager to change the input source name. After changing a source name you must re-configure affected Capture actions to select the renamed source.

• Each source must be named uniquely.

• These characters are prohibited in the source name: ` * | \ : ; " ' < > ? /

Configuring the Lightspeed Live Capture Server and AppsManaging and Configuring Sources

57


Managing and Configuring SourcesBefore capture video sources can be used, they must be configured using the Source Manager web app located at http://localhost:8090/ or http://[hostname]:8090/.

Up to four or eight (depending on the server version) SDI streaming video sources, such as those from live cameras, can be connected through the SDI Input connectors on the back panel of the Lightspeed Live Server. You can also add IP-based RTMP and Transport Streams from your Ethernet connection.

Sources display the current input or the LOS Video Test Pattern that is selected in the Configure Source dialog if no input is present. SDI inputs can be combined to make a single 4K input. You can edit SDI sources but not delete them. They update when you change the SDI input source. For supported formats see SDI Card Input Formats.

In the case of multiple Lightspeed Live servers, the list of Sources is separated into a panel for each server, and each panel can be expanded and collapsed.

Note: Only when running both Live Stream and Live Capture, if you need to change the Source Web Socket Server Port of the web application, use the Settings menu of the Live Stream web app, Network Configuration tab. Note that after making this change, the Source Manager won’t function and you can only use the Sources panel in the Live Stream web app to change source configurations.

■ Sources Overview

■ Configuring an SDI Source

■ Configuring a File Loop Source

■ Configuring a Transport Stream Source

■ Configuring an RTMP Source

■ Managing and Configuring Audio Tracks (AC-3 Only)

■ Sources Overview

■ Configuring an SDI Source

■ Configuring a File Loop Source

■ Configuring a Slate Source

■ Configuring a Transport Stream Source

■ Configuring an RTMP Source

■ Managing and Configuring Audio Tracks (AC-3 Only)

Note: Sources cannot be edited when they are being used by an active Channel.


58


Sources OverviewThe Sources panel displays when you access the Source Manager web app by entering http://localhost:8090/ or http://[hostname]:8090/ as the URL in your browser. If requested, enter your user name and password. The default user name is admin and the default password is live!.

The Sources panel is organized into two panels: The left panel is the Sources list, which displays the four built-in SDI sources, plus sources you’ve created. The right panel displays a live preview feed of the selected source, along with track information.

Source Information and Statistics

Audio Levels

Sources Panel Source Menu

Audio and Text Track Panels

Source Preview Panel System Settings


59


• Sources Panel—Displays all source thumbnails, and allows you to select a source to view or edit. See Source and Channel Indicator Icons.

• Add Source—Click the + icon in the Sources panel to add a new File Loop, Slate, Transport Stream or RTMP source. The SDI input sources are automatically included and you can’t delete them.

• Source Menu Toolbar—Top-right, above the Sources Preview Panel.

– Editor Icon—Click the pencil icon to view or update the settings of the selected Source. Source configuration panels vary by type.

– Audio Track—Selects which audio track to configure and play. The Source Preview panel shows the selected track.

– Text Track—(Live Stream only) Specifies which caption track to use, 608 or 708. The Source Preview panel shows the selected track.

– Delete Icon—Click the trash icon to delete the selected Source.

• Admin—Log out or log in for the current user.

• System Settings—Top-right, three-dot icon.

– Settings—Provides these options:

- Advanced Mode—Turn Advanced mode off or on.

- RTMP Listener Port—Set the RTMP Listener Port. The default port is 1953.

- Restrict Preview Ports Range—Enable to set a range for restricting the pre-view ports. The lower and upper range is from 1024 to 65534.

Port Range Start—Specifies the lower threshold of ports to use for previews.

Port Range End—Specifies the upper threshold of ports to use for previews.

Note: At least two open ports must be available in the configured range. The first is used for Live Capture, even when not installed. The second is for Live Stream. The Port Range Start must be a lower value than the Port Range End, otherwise random ports are used.

– Download System Logs—Gathers the system logs, then opens a Save dialog to choose the location to save the file.

– About—Provides the version number of the application, some document links, and Telestream contact information.

• Source Preview Panel—Displays the currently selected Source and audio meters.

• Source Information Panel—Displays details about the selected source video.

• Audio and Text Track Panels—Add, delete, and configure audio and captioning text tracks. Text Track is for Live Stream only.

• Audio Level Meters and Mute Controls—Audio level meters for each channel that adjust automatically, based on the track (stereo, 5.1 Surround Sound, etc.), with channel-by-channel mute control. If you have multiple audio tracks, you can switch among them, using the Audio Track menu.


60


Source and Channel Indicator IconsThumbnail preview icons for each source in the Sources panel indicate the type of source, whether that source is being used in a live stream or there is a loss of signal.

SDI source

File Loop source

Slate source

Transport Stream source

RTMP source

This source is currently being used in a stream and cannot be edited or removed

This source has experienced a loss of signal


61


Configuring an SDI SourceYou configure SDI Input source options in the Live Source Manager panel. All SDI sources present on Lightspeed Live systems are automatically added to the inventory list of sources. For systems with more than one Live Capture server in a domain you should name each server’s SDI ports with unique names.

The SDI Configure Source dialog opens when you click the pencil icon to edit the selected SDI source.

Note: Some Configure Source selections display only when you access the Settings menu

and enable Advanced Mode.


62


The Configure Source dialog provides these options for the SDI input sources:

• Name—Specifies the name of the source.

• Force 10-Bit Video—When enabled, activates full 10-bit sampling of the video on the SDI input. Using 10-bit sampling requires additional processing and should not be enabled for Standard Definition (SD) sources.

CAUTION: When using an 8-bit leader, filler, or trailer along with the video, do not enable the 10-bit sampling mode. Corrupted output can result.

• PsF—Enable PsF when your incoming SDI source signal is formatted as PsF (Pro-gressive segmented Frame).

Note: The Live Capture system always treats 23.98 | 24 fps SDI sources as progressive.

• Freeze on LOS—When enabled, a loss of signal (LOS) causes the incoming video signal to freeze on the last frame. When disabled, LOS causes the LOS Video Test Pattern to be displayed. For LOS details, see Loss of Signal Behavior in the Lightspeed Live Capture User Guide.

• Assign Processor (SD/HD sources only)—When enabled, all processing associ-ated with individual Capture or Tape workflows is assigned to a single multi-core CPU socket. If four (4) workflows are capturing concurrently, each workflow process runs exclusively on a single CPU socket, with two (2) workflows on socket 1 and two (2) workflows on socket 2. This prevents inefficient mapping of processes across CPU sockets during heavy loads, such as when all four inputs are being processed. Not enabling this option when capturing multiple workflow channels can result in excessive CPU usage.

Note: This option defaults to ON (enabled) when capturing new non-4K SDI sources. It should be disabled when capturing UHD/4K.

Note: On new Lightspeed Live server models, and on systems that utilize multiple processor groups, the Assign Processor option is not shown, and processor balancing is internally managed.

• LOS Video Test Pattern—Select the test pattern to display during LOS.

• LOS Audio Test Signal—Select the audio signal to use during LOS.

• Max Time-Shift—This value represents the maximum size of the Time-Shift frame buffer (in seconds) for workflows using this SDI source. The recommended value is 30 seconds, or less, and is limited to no more than 60 seconds.

Note: Time-Shift—Live Capture’s Time-Shift allows you to hold incoming source media frames in an internal FIFO buffer. You can choose to buffer up to 60 seconds of media for each input on your Lightspeed Live server (some limitations may exist for higher bit rates and frame rates). Caution should be taken when setting Time-Shift to a


63


value greater than 30 seconds on more than one input source. See Determining the Time-Shift Buffer Duration for recommendations on settings for various frame sizes and frame rates. When a capture workflow is activated with Time-Shift enabled, the input’s source media is stored in a FIFO buffer which allows Lightspeed Live to reach back in time and access media processed in the past, based on the value of the Time-Shift field. Since Live Capture’s Time-Shift is always processing an input source’s media, when a record is initiated any media stored in the Time-Shift buffer is available to be added to the captured file.

• TimeCode Source—Click the drop-down menu to choose one of the following timecode source signals for the selected SDI input:

– Source—Uses the timecode provided in VBI or VANC (SMPTE 12M-2/RP188) of the selected Lightspeed Live Capture's video input signal. If a valid timecode is not available or goes away, see the Free Run TimeCode option below.

– Computer Clock—Uses the time-of-day clock provided by the Lightspeed Live Capture Server.

– Free Run—This timecode starts at 00:00:00:00 and free-runs, after the associated Capture workflow is activated. The recorded timecode captured reflects the free run timecode at the time capture begins.

– Analog LTC—Uses the timecode provided on the SDI card's LTC input (marked with an R on the SDI card). If a valid timecode is not available or goes away, see the Free Run TimeCode option below.

– RS-422—Uses the timecode provided by a VTR connected via RS-422. (Requires the optional RS-422 control kit.) If an input is connected to a VTR under RS-422 control, RS-422 must be selected for TimeCode Source.

Note: When using the Schedule Trigger you should set your TimeCode Source to either Computer Clock or Source. When using Source, you must have time-of-day timecode in your source that matches the time set in your Lightspeed Live server. See Configuring Trigger Settings.

• Free Run TimeCode—When enabled, and the desired timecode is not detected or goes away, the timecode seamlessly free-runs from the last good timecode received. When Free Run TimeCode is not enabled, and the desired timecode is not detected or goes away, then the timecode reverts to zero (00:00:00:00) and stays at zero.

• Raw Ancillary Dump—Only available when Advanced mode is enabled. WARNING: Do not enable this option unless directed to by Telestream Support.

• Use Inverse Telecine (Live Stream only)—When enabled, sets the source to be de-interlaced using Inverse Telecine settings.

Note: The Inverse Telecine setting only applies to Live Stream. This feature is not yet enabled in Live Capture and has no affect on Capture operations.


64


• Line Offset—Shift the video by the specified line offset. The default is 0, the mini-mum is -4, and the maximum is +4. The range is -4 to 4 lines. Available only in Advanced Mode (System Settings).

• Cisco ID3—Enable to allow the SCTE-104 information to be converted to ID3 on output. This option can also be turned off or on from Live Capture when configur-ing SDI sources. See Cisco ID3 in the Configuring SDI Source Options topic in the Lightspeed Live Capture User Guide. This setting is available only in Advanced Mode.

• Extended RS-422 Status—When enabled, the RS-422 port is polled for extended error status information and the data is added to the log files. Available only in Advanced Mode (System Settings).

• VDCP—When enabled, activates the RS-422 port in VDCP (Video Disk Control Pro-tocol) mode (RS-422 timecode is not available). This setting is available only in Advanced Mode (System Settings).

• Video Mode—Select the video mode:

– SD/HD Video Input—Sets the source to SD/HD video input.

– SD/HD Video Input with Loop Through—Sets the source to SD/HD video input with loop through. See Configuring SDI Loop Through for details.

– 4K/UHD Video Input—Sets the source to 4K/UHD video input. When activated, all four SDI inputs are merged into one 4K/UHD input.

– 4K/UHD Video Input with Loop Through—Sets the source to 4K/UHD video input with loop through. See Configuring SDI Loop Through for details.

Note: Loop through is not supported for the HEVC (H/W) card.

• Ignore Format Match Check—When 4K/UHD is chosen as the video mode, enabling this option adds a 4K/UHD source via SDI inputs even if all four quadrants do not have a matching signal. When there is no valid 4K/UHD signal from all quad-rants, the entire output displays the 4K/UHD signal as the LOS Video Test Pattern. When disabled, all four quadrants of a 4K/UHD source must match for the 4K/UHD mode to be activated. Unmatched quadrants can occur when some 4K/UHD sources are not currently playing video.

• Quad-Split Scheme—When 4K/UHD is chosen as the video mode, select from one of the following Quad-Split Schemes:

– Square Division Level A—The image is divided into four quadrants, level type A.

– Square Division Level B—The image is divided into four quadrants, level type B.

– 2SI-A—Two Sample Interleave, type A.

– 2SI-B—Two Sample Interleave, type B.

Note: To successfully switch between the 2SI-A or the 2SI-B setting, you must first select Square Division, save the change, then reopen the dialog and select the A or B setting you want to switch to.


65


Note: The SDI inputs on the Lightspeed server cannot differentiate between 4K/UHD and HD/SD signals. When the server inputs are receiving a 4K/UHD signal, but the 4K/UHD Video Input option is not selected, the four corners of the source are divided into the four SDI inputs. To get one source that uses the full 4K/UHD signal you must enable the 4K/UHD Video Input option for one of the SDI inputs.

When the SDI inputs are receiving HD/SD signals and the 4K/UHD Video Input option is selected, there is a single SDI 4K/UHD input source that has four segments of duplicate video in it. All four inputs must be synchronous, and have the same frame rate and resolution in order to be combined into a single source view.

Switching Between HD and 4K/UHD ConfigurationsThe key to enabling or disabling 4K/UHD mode is making sure that a valid and active 4K/UHD signal is connected to the Lightspeed Live server during the switching process. To successfully switch from an HD configuration to a 4K/UHD input and then back again, follow these procedures:

To switch from HD to 4K/UHD input mode:

1. Deactivate all Capture workflows actively running on any of the server inputs.

2. From a valid 4K/UHD source connect the four (4) UHD input cables to the appropriate SDI input BNC connectors.

3. Start your 4K/UHD source to actively provide a signal to the Lightspeed Live server.

4. Open the Source Manager panel (see Managing and Configuring Sources), select SDI Input 1 and/or SDI Input 5 (model-dependent), then open the Configure Source panel.

5. Disable the Assign Processor option. (This option should be disabled for 4K/UHD.)

6. From the Video Mode option select 4K/UHD Video Input, then click the Save button to enable your changes.

7. The four inputs are now consolidated into one input and renamed to include 4K/UHD in the name.

8. In Vantage Workflow Designer, for any workflow that you want to use the 4K source, open the Capture action and select the new 4K/UHD input as the Source.

9. Make any other desired changes action and save it.

10. Click Activate below the workflow to initiate workflow operation.

To switch from 4K/UHD to HD input mode:

1. The 4K/UHD source must be actively providing a signal to the server.

2. Deactivate all Capture action workflows that are using the 4K/UHD input source.

3. Open the Source Manager panel (see Managing and Configuring Sources), select the 4K/UHD input, and open the Configure Source panel.

4. From the Video Mode option select SD/HD Video Input, then click the Save button to enable your changes.


66


5. The 4K/UHD input is now converted back to four individual SDI inputs.

6. Turn off your 4K/UHD signal source and disconnect the cables from the 4K/UHD device.

7. Connect HD source cables to one or more of the SDI input BNC connectors.

8. On the Source Manager panel, select each source to configure the options uniquely for each input. See Configuring an SDI Source above.

9. In Vantage Workflow Designer, configure each Capture action to use any one of the SDI inputs that you want for that workflow, and make any other desired adjustments and save your changes. See Creating, Configuring, and Activating Capture Workflows.

10. Click Activate for each workflow that you want to place into operation.


67


Configuring SDI Loop ThroughLoop through capabilities in the Source Manager web app allow one or more SDI input connections to the Lightspeed Live system to be set as a loop through output. This can be used, for example, as confidence monitoring of the SDI signal into the system.

Important Note: The SDI-1 input is used as the master sync when loop through is enabled. All source inputs MUST be of the same baseband video type (framerate, frame size) and they MUST share a common video reference that is frame synced and gen-locked together. Failure to meet this requirement results in a vertical offset being introduced in the sources.

Important Note: If the source video type (such as framerate or frame size) changes on SDI1 when operating in loop through, the other inputs fail and go to LOS (loss of signal). After SDI1 is set back to match the other inputs, changing a setting on an input source and saving it resets the input source back into operation.

When a source is set to be a loop through connection, a new input source instance is created. For example, [host] - SDI Input 1 to SDI input 3 to replace the previous input source instance of [host] - SDI Input 1. The previous non loop through input source is unavailable to any Tape or Capture action or Stream channel that was set to use that input source. See Port Pairing Assignments for Loop Through for more information.

Note: Loop through is not supported for the HEVC (H/W) card.

Using both Loop Through and Normal ModesIf a system is used in both loop through and straight through modes, workflows should be managed using the following criteria:

• Use Vantage Workflow Designer to deactivate all workflows and stream channels that use the sources you are reconfiguring.

• Change the source configuration in the Source Manager web app using the Config-ure Source dialog. See Creating a Loop Through Output below.

• Use Vantage Workflow Designer to create or activate the workflows that use the new configuration.

Note: Actions in Workflow Designer do not signal an invalid connection after changing them unless the inspector is opened for reconfiguration.

Creating a Loop Through OutputBefore setting an SDI connection to be a loop through output, there should be no signal going to that connection. Follow these steps to create a loop through output:


68


1. Disconnect or turn off the SDI source going to the inputs that are going to be changed to loop through mode.

2. In the Source Manager web app, select the input you want to use for loop through, then click the pencil icon to open the Configure Source dialog

3. Change the Video Mode selection in the Configure Source dialog to the loop through option. Click Save to close the dialog.

4. Reconnect or turn on the SDI source going to the inputs that are set to loop through mode.

5. Open the Live Capture web app for further configuration and activation of the loop through outputs.

Port Pairing Assignments for Loop ThroughThe following input port pairings apply when creating loop through outputs.

For Servers with 4 SDI Ports• SD/HD:

– SDI-1 is always paired with SDI-3



69


• 4K/UHD:

– No loop through

For Servers with 8 SDI Ports• SD/HD:





• 4K/UHD:

– 4K/UHD Input 1 Quad Linked using SDI-1, SDI-2, SDI-3, and SDI-4 is paired with SDI-5, SDI-6, SDI-7, and SDI-8


70


Configuring a File Loop SourceThe File Loop Configure Source dialog opens when you create or edit a File Loop source.

Note: File Loops are intended for test purposes only.

The File Loop Configure Source dialog provides these options:

• Name—Specifies the name of the File Loop.

• Path—Specifies the path for the looping file source.

• Max Time-Shift—Sets the size of the internal Time-Shift buffer that may be used to delay the source.

• Simulate Deck—Simulates a VTR tape deck. Only available when Advanced mode is enabled in System Settings.

• Force 8-Bit Video—Forces the source to be 8 bit instead of 10 bit regardless of original source.

• Assign Processor—Assign this source and its dependents to a single processor. When on, all processing is assigned to a single multi-core CPU socket. This prevents inefficient mapping of processes across CPU sockets during heavy loads, such as when all four inputs are being processed. Works for SD/HD sources only, not 4K.


• Use Inverse Telecine—Sets the source to be de-interlaced using Inverse Telecine settings.

• Cisco ID3—Enable to allow the SCTE-104 information to be converted to ID3 on output. This option can also be turned off or on from Live Capture when configur-


71


ing SDI sources, see Cisco ID3 in the Configuring SDI Source Options topic in the Lightspeed Live Capture User Guide. Available only in Advanced Mode.

Configuring a Slate SourceThe Slate Configure Source dialog displays when you create or edit a Slate source. A Slate (test pattern) displays when no signal is present. This is only available in Lightspeed Live Stream.

The Slate Configure Source dialog provides these options:

• Name—Specifies the name of the Slate.

• Video Test Pattern—Specifies the video test pattern to display.

• Audio Test Signal—Specifies the audio test signal to use.

• Video Frame Rate—Specifies the video frame rate to use for the Slate.

• Video Resolution—Specifies the video resolution to use for the Slate.

• Force 10-Bit Video—Sets the Slate at 10-bit video rather than 8-bit.

• Assign Processor—Assign this source and its dependents to a single processor. When on, all processing is assigned to a single multi-core CPU socket. This prevents inefficient mapping of processes across CPU sockets during heavy loads, such as when all four inputs are being processed. Works for SD/HD sources only, not 4K.



72


Configuring a Transport Stream SourceThe Transport Stream Configure Source dialog displays when you create or edit a Transport Stream source.

Note: The settings for Multicast Group IP Address, Local NIC/IP Address, Port Number, and Program Number can only be changed when you are first adding a new Transport Stream source. After the source has been added, only the other settings for the Transport Stream source can be edited.

The Transport Stream Configure Source dialog provides these options:

• Name—Specifies the name of the stream.

• Multicast Group IP Address—The optional Multicast Group IP address to use.

• Local NIC/IP Address—The local NIC (Network Interface Card)/IP address. Select other ones from the menu, if they are available.

Note: When a new network adapter is added, or changed from disabled to enabled state, Live services must be restarted for the service to be available in the Local NIC/IP Address menu. See Stopping and Restarting Telestream Live Services.


73


• Enable SSM—When Source Specific Multicast (SSM) is enabled, you can enter a list of accepted source IP addresses for multicast, under Source Filter.

– Source Filter—When you enable SSM, Source Filter appears. Enter a list of accepted IP addresses for the multicast sources. To add IP addresses to the list, press the Enter key after entering an IP address to add a new entry line.

• Port Number—Specifies the port number.

• Program Number—Set the slide button to the on position to enable, then enter or select the program number. When disabled, the first available program is used.

• Max Time-Shift—Sets the size of the internal Time-Shift buffer that may be used to delay the source.

• Force 8 Bit Video—Forces the source to be 8 bit instead of 10 bit regardless of orig-inal source.

• Assign Processor—Assign this source and its dependents to a single processor. When on, all processing is assigned to a single multi-core CPU socket. This prevents inefficient mapping of processes across CPU sockets during heavy loads, such as when all four inputs are being processed. Assign processor should be applied only to SD/HD sources, not 4K.


• TimeCode Source—Sets the default timecode source. Choose one of the following timecode source signals for the selected Transport Stream Input:

– Source—For H.264 or H.265 the source’s SEI user data is used, and for MPEG2 the source’s GOP header timecode is used. If no valid Source timecode is available see the Free Run TimeCode option below.


There are two additional settings when Computer Clock is selected as the Time-Code Source that determines how the system processes the time code value:

When Compensate for Computer Clock Drift is enabled (see below) Computer Clock Time is monitored and compared to the time code being added to the captured file. Since the Computer Clock is not gen-locked with a true time source associated with the incoming frames it can drift over time and get out of sync with the incoming stream. When a drift of one second is reached the timecode being added to the file is re-synced to the system's Computer Clock time. This means there may be a discontinuity in the file’s timecode at the point where the re-sync occurred. Enabling ‘Free Run Time-


74


code’ when Compensate for Computer Clock Drift is enabled has no effect on the process described here.

When Compensate for Computer Clock Drift is Disabled and Free Run Time-code is EnabledThe source process uses the Computer Clock time without compensating for drift. Over time the timecode may drift several seconds compared to the ‘real’ time. For example—if a recording is 6 hours long the Computer Clock drift might be many seconds by the end of the 6 hour recording. If no frames were dropped the timecode in the output file is contiguous from start to finish.

Regardless of how Compensate for Computer Clock Drift is set, if packets are lost and frames are dropped the Live Source process adds frames using the last good timecode in order to compensate for the lost frames. This may cause timecode values to be repeated where a frame was lost. If your Transport Stream signal is strong, this problem should not occur.

– Free Run—This timecode starts at 00:00:00:00 and free-runs after the associated Capture workflow is activated. The recorded timecode captured reflects the free run timecode at the time capture begins.

• Free Run TimeCode—When enabled, and the desired timecode is not detected or goes away, the timecode seamlessly free-runs from the last good timecode received. When Free Run TimeCode is not enabled and the desired timecode isn’t detected or goes away, the timecode reverts to zero (00:00:00:00) and stay at zero.

• Compensate for Computer Clock Drift—When enabled, compensates for Com-puter Time Code drift when Computer Clock is the chosen TimeCode Source.

• Freeze on LOS—Causes the source to hold the last good frame the signal is lost.


Note: The LOS Audio Test Signal is not available for Transport Stream sources.

• Use Inverse Telecine—Sets the source to be de-interlaced using Inverse Telecine settings.

• TS Over RTP (Live Stream only)—When enabled, wraps the Transport Stream in an RTP packet.

• Cisco ID3—Enable to allow the SCTE-104 information to be converted to ID3 on output. This option can also be turned off or on from Live Capture when configur-ing SDI sources, see Cisco ID3 in the Configuring SDI Source Options topic in the Lightspeed Live Capture User Guide. Available only in Advanced Mode.

• Stream dump—Available when Advanced mode is enabled. When enabled, cap-tures the Transport Stream source to the location and file you specify, until you turn the Stream dump option off. Type the path, folder, and file name into the Stream dump field. Specify the file extension as ts (for example, MyStreamDump.ts.) If the folder you specify does not exist, the new folder and file are automatically created.

• Log Timecode—When enabled, the timecode is added to the log. Available only in Advanced Mode. (To be used only as directed by Telestream Customer Service for debugging purposes.)


75


SCTE-35 Information and ID3 Tag Pass Through or InsertionWhen a Transport Stream source contains SCTE-35 information or ID3 tags, this data is passed through to the output. SCTE-35 and ID3 data can also be inserted via the Sources API.

Note: Lightspeed Live Capture requires that an IP input source is formated using standard frame sizes and frame rates. See the Technical Specifications in the Lightspeed Live Capture product sheet on the Telestream web site for the supported formats.

Configuring an RTMP SourceThe RTMP Configure Source dialog opens when you create or edit an RTMP source. Telestream recommends limiting RTMP/Transport Stream sources to eight, unless testing in your environment indicates you can enable more.

Note: The options for an RTMP source can only be changed when you are adding it. After the source has been added, only the name can be changed. When an RTMP source is connected, the name can’t be changed either. When you require an RTMP source with different settings, add a new RTMP source and configure it accordingly.

Note: You must first add an RTMP Source to Live Stream before you can start ingesting the RTMP source.

The RTMP Configure Source dialog provides these options:

http://www.telestream.net/pdfs/datasheets/dat-Lightspeed-Live-Capture.pdf


76


• Name—Specifies the name to use in Live Stream.

• Stream Name—Specifies the name of this RTMP stream source. The Stream Name can be changed multiple times until an RTMP stream source is connected. After an RTMP stream has connected, the Stream Name can’t be changed.

• Max Time-Shift—In Live Capture, specifies the size of the internal Time-Shift buf-fer that is used to delay the source. In Live Stream, applies to the Retroactive Chan-nel Start feature.

• Assign Processor—When enabled, assigns this source and its dependents to a sin-gle, multi-core CPU socket. This prevents inefficient mapping of processes across CPU sockets during heavy loads, such as when all four inputs are being processed. Applies to SD/HD sources only, not 4K.


• TimeCode Source—Sets the default timecode source. Choose one of the following timecode source signals for the selected RTMP Input:

– Source—For H.264 or H.265 the source’s SEI user data is used, and for MPEG2 the source’s GOP header timecode is used. If no valid Source timecode is available see the Free Run TimeCode option below.


There are two additional settings when Computer Clock is selected as the Time-Code Source that determines how the system processes the time code value:

When ‘Compensate for Computer Clock Drift’ is enabled (see below) the Computer Clock Time is monitored and compared to the time code being added to the captured file. Since the Computer Clock is not gen-locked with a true time source associated with the incoming frames it can drift over time and get “out of sync” with the incoming stream. When a drift of one second is reached the timecode being added to the file is re-synced to the system's Computer Clock time. This means there may be a discontinuity in the file's timecode at the point where the re-sync occurred. Enabling ‘Free Run Time-code’ when ‘Compensate for Computer Clock Drift’ is enabled has no effect on the process described here.

When ‘Compensate for Computer Clock Drift’ is disabled and ‘Free Run Timecode’ is enabled, the source process uses the Computer Clock time with-out compensating for drift. Over time the timecode may drift several seconds compared to the ‘real’ time. For example—if a recording is 6 hours long the Computer Clock drift might be many seconds by the end of the 6 hour record-ing. If no frames were dropped the timecode in the output file is contiguous from start to finish.

Regardless of how ‘Compensate for Computer Clock Drift’ is set, if packets are lost and frames are dropped the Live Source process adds frames using the


77


last good timecode in order to compensate for the lost frames. This may cause timecode values to be repeated where a frame was lost. If your RTMP signal is strong you should never see this happen.

– Free Run—This timecode starts at 00:00:00:00 and free-runs, after the associated Capture workflow is activated. The recorded timecode captured reflects the free run timecode at the time capture begins.

• Free Run TimeCode—When enabled, and the desired timecode is not detected or goes away, the timecode seamlessly free-runs from the last good timecode received. When Free Run TimeCode is not enabled and the desired timecode is not detected or goes away, the timecode reverts to zero (00:00:00:00) and stays at zero.

• Compensate for Computer Clock Drift—When enabled, compensates for Com-puter Time Code drift when Computer Clock is the chosen TimeCode Source.

• Freeze on LOS—When enabled, causes the source to hold the last good frame if the signal is lost.


Note: The LOS Audio Test Signal is not available for RTMP sources.

• Log Timecode—When enabled, the timecode is added to the log. Available only in Advanced Mode.

Note: Lightspeed Live Capture requires that an IP input source is formated using standard frame sizes and frame rates. See the Technical Specifications in the Lightspeed Live Capture product sheet on the Telestream web site for the supported formats.

Managing and Configuring Audio Tracks (AC-3 Only)Audio Tracks are managed in the Preview panel of the Source Manager. The selected track is displayed when you click Audio Tracks below the video display and includes configuration tools.

Note: The only audio track setting that applies to Live Capture is the AC3 Decompressor. All other settings are for Live Stream only.

An Audio Track is added, by default, when you create a source and it usually is automatically configured to match the source.

http://www.telestream.net/pdfs/datasheets/dat-Lightspeed-Live-Capture.pdf


78


Adding an Audio TrackClick the musical note + icon in the toolbar to add a new audio track. Select Mono | Stereo | 5.1 Surround. You can add multiple tracks to provide for different languages, various services, or other variations. The channel assignments can be changed if you want specific different configurations.

Click the Trash icon in the toolbar to delete the selected track.

Previewing the Audio TracksWhen more than one Audio Track is present, you can select the track that you want to hear in the Source Preview panel by selecting it from the audio track list. Audio tracks display in the list only after you add them as explained above. The track configured as Default track is the one that you hear if you do not manually select a track.

Configuring an Audio TrackTo open the audio track configuration dialog, click the Edit This Track pencil icon for the track you want to configure. You can change configuration dialog settings to configure the track as described below.

• Name—Specifies the name of the audio track.

• Language—Specifies the language to use for this track. (Does not affect final output).


79


• Audio Service—Specifies the audio service label to use for this track: Primary | Sec-ondary | Commentary | Music. (Does not affect final output).

• Description—Select a description to use for the Audio Track. The descriptions are created and edited in the Settings dialog > Audio Descriptions tab of Live Stream. See Audio Descriptions.

• Default—Enable to set the audio track as the default. When enabled, this track is the one used first when you select the input source to preview. You can select a dif-ferent Audio Track to use for the preview from the menu in the upper right of the Sources panel. Setting a track to Default also marks it as the settings to use for the Channel Assignment of the output. However, the audio encoder setting determines the actual channel type of Mono, Stereo, or 5.1 to use for the output. See the AAC Audio Streams, AAC Channel Layout setting.

• Channel Assignment—Specifies which source channel is assigned to the output channel. The default for Mono is Center=1; for Stereo is Left=1, Right=2; for Sur-round (5.1) is Left=1, Right=2, Center=3, LFE=4, Left Surround=5, and Right Sur-round=6.

• AC3 Decompressor—When enabled, AC3 audio embedded in PCM is decoded at the source level and passed on as PCM, for use directly in the primary or secondary outputs and the Preview panel of a Live system. The AC3 Decompressor setting appears in the audio Edit Track panel, where you can enable it. After the AC3 Decom-pressor is enabled, the affected source’s Live Source process restarts automatically.

Configuring the Lightspeed Live Capture Server and AppsConfiguring Capture Resources

80


Configuring Capture ResourcesLightspeed Live Capture employs a browser-based web application together with Vantage workflow-based transcoding software to ingest and encode live, live linear, or tape-based source video into output media files. Lightspeed Live Capture is designed to run on a single-server Vantage domain, or operate as a node in a multi-server Vantage array.

Configuring Lightspeed Live Capture consists primarily of setting up Vantage and customizing Vantage workflows to automate the capture process. The workflows are made up of individual tasks called actions, which specify what tasks to perform, such as discovering and capturing video sources, transcoding them into media files, and delivering the files to specified destinations. In the case of Lightspeed Live Capture, the primary actions are the Capture action and the Tape action.

Before a Lightspeed Live Capture workflow can be activated to capture media, you must first configure Lightspeed Live Capture and Vantage as follows:

■ Configuring Settings for Your Facility

■ Using Inputs for Both Live Stream and Capture

■ Configuring Ingest Sources

The program used to perform these tasks is the Vantage Management Console, which has an icon on your desktop. Later in this chapter you’ll learn how to use the console to perform the tasks.

Workflows are designed using a program called Vantage Workflow Designer, which is also launched from a desktop icon. We will guide you step by step in creating and activating a simple Capture workflow that detects your sources, encodes them, and places your captured files into a storage location.

Once your Capture workflow is activated you're ready to start capturing. Capture control is performed in the Lightspeed Live Capture web application. The Lightspeed Live Capture Web API can also be used to control operations.

WARNING: Do not uninstall the Lightspeed Live Stream application. Components of the Live Stream application are needed in order for Capture to operate properly.

Configuring the Lightspeed Live Capture Server and AppsConfiguring Settings for Your Facility

81


Configuring Settings for Your FacilityA few settings are required on your Lightspeed Live server before you launch the Lightspeed Live Capture or Tape Capture web application. Some of these settings are configured at the factory, but you should verify them and make additional custom settings as follows:

1: Open the Vantage Management Console.Launch the Vantage Management Console by double-clicking the desktop icon.

(To learn more about any of the following steps, click the question mark (?) button in the upper right corner of the Console to open the Vantage Domain Management Guide.)

2: Apply Your License.Apply your Lightspeed Live Capture license by clicking Licenses in the left panel and verifying that you have a Live Capture license.

If not, contact Telestream for a license, and click the Add/Update a License button in the Licenses panel to add the new license.

3: Activate User Administration.Activate User Administration (or verify that it was activated at the factory.) Select Settings & Options in the left panel. On the General tab, verify that Enable user administration is selected, and if not, select it. This must be enabled in order to use the Lightspeed Live Capture web application.

You may also want to check Use Windows Active Directory for Users to use your Windows logins for Vantage. Alternatively, you can create Vantage-only users if you leave the Windows option unchecked. If you made any changes, click the Save icon .


82


4: Create User Accounts.

Create user accounts for Lightspeed Live Capture. Select Users near the bottom of the left panel to create new user accounts. To add a new account, click the New User button in the Users panel and fill in the form. Each Capture user should have a login.

Note: User accounts can be used to control access to the Management Console, Workflow Designer, Workflow Categories, and Channel Groups; or can prevent Lightspeed Tape Capture users from competing for the same resources.

5: Add a Live Store for capture files.

Add a Live Store for Capture (or verify that it has been added at the factory). Select Storage > Vantage Stores in the left panel and verify that a Live Store exists in the


83


D:\Live Store\ location. If not, click the New Vantage Store icon, fill out the form, and be sure to select Type: Live in the form. Also, if a default Vantage Local Store (file type) does not exist, you must create one using this same Vantage Management Console panel.

When to Specify a UNC Path for Live StoresTo ensure Live Stores are properly configured so that captured files can be automatically deleted when jobs expire, you may need to specify the storage location as a UNC path. This is especially true if you have multiple servers connected together in an array. A UNC path is also important when you have multiple users accessing the Tape Capture application from remote browsers.

A UNC path looks like this: \\hostname\d\live\store.

Follow these steps to configure Live Stores as UNC paths to allow automatic deletion of deleted and expired capture files:

a. Create a local Live Store for each Lightspeed Live Capture server in the domain. For example, for Capture servers LSL-01, LSL-02, and LSL-03, create these stores:

b. Share the Live Stores in Windows as UNC paths on all servers.c. In the Live Store Alias field, add the UNC path for each source. For example:

Live Store Name Location Store Type

LSL-01 Local Live Store D:\live\store Live




84


d. Create authorization entries in the Vantage Management Console > Settings and Options > Authorization tab for each Live Store UNC path alias. Then put all services into Maintenance Mode and exit them again to apply the change.

e. When creating workflows, be sure to assign Capture actions to the Live Store corresponding to the server where the action resides. For example, assign Capture actions on LSL-01 to the LSL-01 Live Store (\\LSL-01\d\live\store).

When to Run Copy and Move Actions on Local or on Any ServerIf the Live Store is a local path, then the Vantage service supporting the Copy or Move action following a Capture action in a workflow should always run on the same server as the Capture action.

If the Live Store is a UNC path, then Copy or Move actions downstream from a Capture action can run on any server in the Vantage domain, assuming an array license is present.

Live Store Name LocationStore Type Alias

LSL-01 Local Live Store D:\Live\Store Live \\LSL-01\d\live\store




85


6: Create Address Book Delivery Locations.

Add delivery locations to the Vantage Folder Address Book where captured files can be written. Click Vantage Folder Address Book and create new address book entries. Folder locations must be Windows file system locations with a letter drive or network UNC path.

7: Create Labels and Variables for the Tape and Capture Actions.

Labels and variables you create can be added to the Tape and Capture actions and can be viewed, included, and modified in the Tape Capture and Live Capture web applications. For example, you might want to create labels for social media accounts to post directly to Facebook and YouTube using account and file description metadata stored in the labels. Similarly, you may want to use or create variables for tape or media file parameters.

In the Vantage Management Console, add labels using Workflow Design Items > Metadata Labels. in Workflow Designer, add Variables using Items > Variables.

Note: An additional Vantage license may be required for social media posting.

Configuring the Lightspeed Live Capture Server and AppsUsing Inputs for Both Live Stream and Capture

86


Using Inputs for Both Live Stream and CaptureThis Note and Warning apply only when Live Stream and Live Capture are used on the same Lightspeed Live server:

Note: Changing sources in any way on the Source Manager panel affects which sources are available to the Live Capture and Live Stream web applications. Conversely, changing source configurations in the Live Stream web application changes what is shown on the Source Manager panel.

WARNING: When Live Stream and Live Capture are used on a server concurrently, any File Loop or Slate sources that appear on the Source Manager panel are NOT supported for Capture workflows. Do not make any changes to the options for these sources; they are created by and used by the Stream application. Configuration changes for these sources are made in the Lightspeed Live Stream web application. The actual name of the sources created in Live Stream can be any name they have been given, and may not be called File Loop, RTMP, and so on.

Configuring the Lightspeed Live Capture Server and AppsConfiguring Ingest Sources

87


Configuring Ingest SourcesBefore the channel groups and sources can be accessed by the Lightspeed Live Capture or Tape Capture web app, they must be defined. This allows the system to work with the sources according to your workflow and Lightspeed Live Capture or Tape Capture web app configurations. The workflows and web apps work together, and the beginning of the inter-operation is to define nexus channel groups and source inputs.

Note: If you have already configured input sources using the Source Manager app (http://localhost:8090), you still need to create a Nexus, but you can skip configuring SDI, IP, and other sources in Vantage as explained by topics below.

Configuring a Channel Group NexusLightspeed Live Capture uses the concept of a nexus to group related video source channels together. For example, one group of sources might be camera video feeds coming from the same studio, and another group might come from another studio. A single source can be referenced in multiple workflows and, hence, in more than one nexus. The Nexus Definitions created here are called Channel Groups in the Lightspeed Live Capture web application. There are two types of definitions; one when capturing from a live source and another when controlling a VTR when capturing from tape. See Lightspeed Live Capture Web App Overview.

Follow these steps to configure a nexus and an inventory of video sources:

1. Launch the Vantage Management Console.

2. Select Workflow Design Items > Nexus Definitions in the left panel.


88


3. Use the Create a new Nexus definition button in the Nexus Definitions panel to create at least one Channel Group Nexus definition, setting the type to Capture or Tape Capture. Workflows built using a Tape Capture origin action are assigned to Tape Capture Channel Groups, while workflows built with a Capture origin action are assigned to Capture Channel Groups.

4. Select Capture or Tape Capture in the dialog that opens, and click OK to add a new nexus.

5. In the Name field, type the name you want, and add optional information in the Description field.

6. In the Permitted Users section (visible only if User Administration is enabled in the Settings & Options > General tab) you can assign Permitted Users by clicking on a user in the left list, and clicking Add to move them to the right list. You can check Everyone (Public Access) (this is the default) to allow all users access to that nexus. Use Remove to move a selected user on the right to the non-permitted list on the left. This disables that user’s access. Each nexus can have its own Permitted Users.

The list of available users is created by adding user accounts in the Users panel. See Configuring Settings for Your Facility for instructions.

Note: Users with administrator privileges have access whether they are included or not, in the Permitted Users list.

7. Click Save to save the changes and create a new channel group nexus.


89


Using Capture Inventory to Preview and Find Workflows Used by an Input

Note: Source management and configuration should be performed using the Source Manager web app at http://localhost: 8090, described in Managing and Configuring Sources. The Capture Inventory panel in the Vantage Management Console should only be used for discovering workflows and previewing inputs.

The Capture Inventory panel in the Vantage Management Console (VMC) enables you to discover which workflows are configured to use a particular input and can display a Preview of the input configuration. All SDI sources present on a Lightspeed Live system are automatically added to the inventory list of sources.

Select Capture Inventory in the left panel to display the Capture Inventory panel:

Note: If sources are not displayed after installing Live Capture, restart the server, then check again for the list of sources. The list of sources should be refreshed after the server restarts.


90


Previewing SourcesYou can preview source video and view details in a small window (below) by using the Preview button in the Capture Inventory toolbar. The preview image is updated once per second.

Finding WorkflowsYou can determine which workflows are configured to use a specific input source by clicking the Find Workflows button in the Capture Inventory toolbar. A list of associated workflows display.

Configuring the Lightspeed Live Capture Server and AppsInstalling the Live Capture & Tape Capture Web Apps

91


Installing the Live Capture & Tape Capture Web Apps

Lightspeed Live Capture and Tape Capture are web applications that come pre-installed on Lightspeed Live Capture servers. The applications are facilitated by IIS (Windows Internet Information Services) which ships properly configured in the Lightspeed Live Capture server.

Note: If sources are not displayed in Capture Inventory after installing Live Capture, restart the server, then check again for the list of sources. The list of sources should be populated after the server is restarted. See Using Capture Inventory to Preview and Find Workflows Used by an Input.

Installation on Standard ServersTo install Live Capture and Tape Capture on standard servers (other than Lightspeed Live Capture), you must set up IIS first. If IIS is already installed, you must create the configuration that supports Vantage Web Applications.

For full details about setup for standard servers, see “Installing and Configuring Vantage Web Applications” in the Vantage Installation Guide or the Domain Management Guide. An easy way to access the Domain Management Guide is to open the Vantage Management Console and click the ? in the upper right corner.

See Configuring Settings for Your Facility for information about the Vantage Management Console.

The following helpful topics are in the Vantage Installation Guide and the Domain Management Guide:

• Server Hardware Requirements

• Vantage Web Applications OS

Clear Browsing Data after UpdatingAfter a Vantage or Live Capture ComponentPac update is installed, you must clear the browsing data in your Chrome browser in order for the Lightspeed Live Capture or Tape Capture web applications to operate properly. See Clear Browsing Data after Updating Vantage or Live Capture for detailed information.

Configuring the Lightspeed Live Capture Server and AppsRenaming or Reconfiguring Servers

92


Renaming or Reconfiguring ServersThe following topics explain how to make common configuration changes.

■ Array Licensing for Multiple Server Live Capture Systems

■ Important Notes on Configuring Non-Capture Workflow Actions on Multiple Server Systems

■ Joining Multiple Capture Servers

■ Uniquely Named Multiple Capture Servers

■ Best Practice for Multiple Live Capture Server System Design

■ Connecting the Applications for Multiple Servers

■ Correcting Thumbnail Appearance on Non-Local Systems

Lightspeed Live Stream servers do not include Vantage as part of the product. However, Lightspeed Live Capture includes Vantage pre-installed as part of the product, and the Capture Vantage domain uses the name assigned to the Windows server that hosts the Vantage domain database as its domain name. Consequently, renaming the Capture server includes steps to rename the Vantage domain that do not apply to renaming a Live server.

Renaming a Capture or Stream/Capture Server—Follow all of these steps for a Capture server, but for a Stream server, skip any steps pertaining to Vantage.

Renaming a Stream Only Server—Follow steps 6 through 12 only (ignore all Vantage steps). An easier method to change the Stream server name is via the Systems options in the Group Portal web app. See Changing a Server Name.

Note: If the server name is changed and Live Stream doesn’t auto-update, you can change the server name via the Systems options in the Group Portal web app.

If you want to rename your Lightspeed Live server and keep the pre-installed Vantage database, you’ll complete the following tasks to ensure that your database is updated with the new machine name (detailed steps following):

• Remove all Vantage services from the Vantage domain.

• Rename the Windows server that hosts the Vantage domain database.

• Restart the renamed server and add all Vantage services to the renamed domain.

CAUTION: The server name must be limited to 15 characters or less.

Note: To complete this procedure, your Windows user must have permission to rename the computer, or you must get assistance from your Windows domain administrator. Be sure to schedule the rename during a maintenance window, as renaming the Vantage domain interrupts all Vantage services in the domain and all Windows services on the server are renamed.

Use the following steps to rename a Vantage server and domain.


93


1. Start the Vantage Management Console, select the domain to manage, and log on as described in Starting the Vantage Management Console in the Vantage Domain Management Guide.

2. Select Services in the component panel.

3. Take note of Storage, Variables, and/or Qualification Rules settings for each service that you have configured. Write down any Storage, Variable, and/or Qualification Rule settings that you want to reconfigure after the Vantage domain is renamed.

Note: When you remove Vantage services from the domain, the Storage, Variable, and Qualification rule configuration for each service is lost. The rest of the Vantage domain configuration is retained. If you are changing the machine name during initial server installation, no custom rules have been configured, so this does not apply.

4. Click a service in the Services details panel, then press Ctrl-A to select all services.

5. Click the Remove Service button in the toolbar.

6. Open the Windows Server Manager—click the Windows Start Menu > Administrative Tools > Server Manager.

7. Click Local Server in the left pane then click the Computer Name link.

8. Select the Computer Name tab and click Change.

9. Enter the new computer name in the Computer Name text field and click OK. This new computer name becomes your new Vantage domain name.

10. If prompted to do so, enter a Windows user name and password for an account that has permission to rename this computer in the Windows domain.

11. Restart the server.

12. Start the Vantage Management Console, select the new domain, and log on.

– If you are not prompted to select the new domain, click on File > Change Vantage Domain, click Search, select the new domain and click OK.

13. Select Services in the Component panel.

14. Click the Add Service button in the toolbar.

Note: If you are not able to log in with the local Administrator account, check the hostname listed by Windows as it may not have been updated. For example, if the original hostname was lsl-telestream and the new one is lsl-customer, the User Name may still be listed as: lsl-telestream\Administrator. If so, change the hostname to: lsl-customer\Administrator, and re-enter your password.

15. When the Select Service dialog displays, click Machine to sort the services by machine name.

16. To add Vantage services for a specific server, select the services you want and click OK.

17. If any Storage, Variables, and/or Qualification Rules settings were configured for services, add them now.


94


18. Send the new Vantage domain name to all Vantage users and administrators so they can reconnect to the Vantage domain.

Stopping and Restarting Telestream Live ServicesIf you have changed server settings to join a group, or changed port numbers, some services must be stopped and restarted on the server(s).

Note: There are also other changes that require stopping and restarting the live services, such as changing the materials Resource Location in the Stream Edit Settings dialog or changing port numbers. In these cases, if you have just one Lightspeed Live server you only need to perform the portion of this procedure that affects that server.

Follow these steps to stop and restart the Live services:

1. Open the Services control panel by typing services.msc in the search field of the Start menu, then press Enter. The Services window opens.

2. On each new server, stop the following services, in this order:

a. Telestream Live Stream Serviceb. Telestream Live Source Service

Note: Insure that the services stop process has completed before continuing.

3. On each new server, restart the following services, in this order:

a. Telestream Live Source Serviceb. Telestream Live Stream Service

4. Close the Services window.

5. On the Primary server, stop the following services, in this order:

a. Telestream Live Stream Serviceb. Telestream Live Source Service


95


Note: Insure that the services stop process has completed before continuing.

6. On the Primary server, restart the following services, in this order:

a. Telestream Live Source Serviceb. Telestream Live Stream Service

7. Close the Services window.

The sources from all Lightspeed Live servers should now display in the Lightspeed Live Stream web application Sources section and Source Manager.

Firewalls and Blocked Ports Limit FunctionalityIf you have firewalls and/or blocked ports you may not be able to fully access joined Lightspeed Live servers. The servers display, but you may not be able to configure settings for Channels or see the Sources.

Telestream recommends that you disable the Windows Firewall on all computers that must communicate with or support Vantage services. The default Windows Firewall configuration blocks access to a Vantage server from other Vantage components, such as other Vantage servers or workstations running Vantage client software.

For more information, see Firewall Guidelines in the Telestream Vantage Domain Management Guide.

When Lightspeed Live servers are joined together in a group, you manage all of the joined machines from a single Lightspeed Live Stream web application, but all machines are working independently.

The list of Sources in the Live Stream and Source Manager web apps are separated into a section for each server.

Create a UNC Path for the Resource LocationWhen multiple Lightspeed Live servers are joined together, you should specify the Resource Location for Materials assets as a Universal Naming Convention (UNC) path. This allows different servers to access the image or video assets used for Segment Materials. See Managing General Settings to set the Resource Location path.

A typical UNC path looks like this: \\hostname\Stream\Materials.

A UNC path uses two backslashes to precede the name of the host server, followed by the set of folders to the file, and optionally, the file itself. In this case, only supply the folder path.


96


Array Licensing for Multiple Server Live Capture SystemsThe need for array licenses varies, depending on whether the Vantage domain is operating on a single server or on multiple servers, which is called a Vantage array.

Vantage and Live Capture SolutionsArray licenses are required on each Vantage and Live Capture server when they are connected together in a single Vantage Domain.

• Live Capture server licenses automatically include an array license instance as part of your purchase of the Live Capture server. No additional purchase is required for these servers.

• All Vantage servers joined together with Live Capture servers in a single domain require an array license to be purchased for each Vantage server.

The following examples illustrate the requirements for purchasing and licensing Vantage domains containing Live Capture servers.

New Vantage Systems Containing Live Capture• Example 1: A brand new system consisting of two Lightspeed Live Capture servers

and two Vantage servers that are joined into a single domain requires a total of four array licenses. For this system you order two array licenses for the Vantage servers and receive a domain license file containing array license instances for all four serv-ers; two purchased for the Vantage servers and two included with your Lightspeed Live Capture servers.

• Example 2: A brand new system consisting of five Lightspeed Live Capture servers and three Vantage servers that are joined into a single domain requires a total of eight array licenses. For this system you order three array licenses for the Vantage servers and receive a domain license file containing array license instances for all eight servers; three purchased for the Vantage servers and five included with your Lightspeed Live Capture servers.

Adding Live Capture to an Existing Vantage Domain Array• Example: If you are adding one or more Lightspeed Live Capture servers to an

existing Vantage domain that already has array licensing for the Vantage servers, no additional array licenses need to be ordered. For these types of systems you must have the existing Vantage domain license updated to include Live Capture and an associated array license for each Live Capture server added to it.


97


Important Notes on Configuring Non-Capture Workflow Actions on Multiple Server Systems

Live Capture server licenses automatically include an array license instance as part of your purchase. When Live Capture workflows are created and executed, all Capture origin action processes run on their respective Live Capture servers automatically. However, other services such as the Transport or Deploy service, can run on any server with available resources for the desired service's action. The following describes the best practices for configuring storage settings when using non-Capture actions.

Best Practice When Capturing to a Live Capture Local Media Drive:When you are capturing directly to a Local Live Store that is set to a local drive letter's folder, any workflow action immediately following the Capture Action are processed locally. For actions that do not immediately follow the Capture Action, best practice is to set Run On Rules that instruct the non-Capture action processes to run on the Live Capture server where the media resides. This insures that the non-Capture action process runs directly on the server where the media resides. See the Configuring an Action's Run On Rules section of the Vantage User Guide for more information.

Best Practice When Capturing to Shared External Storage: When you are capturing to a shared external storage location, such as a NAS or SAN, you can allow other non-Capture action processes to run on any server with available resources. In this case “Run On Rules” are not required. Your system automatically chooses an available resource on any server that can run the required action's process.

Note: Running Lightspeed Live Capture and Vantage together without array licenses is not recommended and may result in reduced functionality.

See Joining Multiple Capture Servers below for information about setting up an array.


98


Joining Multiple Capture ServersYour Lightspeed Live Capture server is factory-configured as a standalone live Capture system. This configuration includes a Vantage database running on each standalone Live Capture server. If you plan to manage multiple Live Capture servers from a common interface, or add Live Capture servers to an existing Vantage Array, you can do this in two ways:

• For Capture-only systems, join all Live Capture servers together by creating a sys-tem that utilizes a single domain database.

• For Capture systems that need to utilize other Vantage services and actions, such as Transcoding and Analysis, you can add your Live Capture servers to an existing Van-tage Array.

Best Practice When Joining Two or More Live Capture Servers Into a Single Domain The system Database and the Live Capture web application traffic can affect the performance of a Live Capture server when run in a domain containing more than one Live Capture server. Therefore, when joining two or more Live Capture servers together into a single domain, either as a Capture-only solution or into an existing Vantage server domain, Telestream recommends that the Live Capture/Vantage Database and IIS software hosting the Live Capture/Vantage web applications run on an independent, non-Live Capture/Vantage server. See images below and Best Practice for Multiple Live Capture Server System Design.

Further information regarding running the Database and IIS on non-Live Capture/Vantage servers can be found in the Vantage Domain Management Guide on the Telestream web site.

It is also highly recommended that the process of creating multiple server domains containing Live Capture servers be done as part of the installation and commissioning phase.

Important Note: When standalone Lightspeed Live Capture servers are combined together using a single database, only those ComponentPacs properly installed on the master domain database are utilized. When joining Lightspeed Live Capture servers together into a Live Capture-only system, or into an existing Vantage Array, always verify that all of the required ComponentPacs are properly installed on the combined system's master domain database. For details on how to install ComponentPacs see Updating Capture using Secured Version Control and ComponentPacs below.

https://www.telestream.net/pdfs/user-guides/Vantage-UserGuides/VantageDomainManagement.pdf


99


Joining Capture-Only SystemsTwo or more Lightspeed Live Capture servers can be joined together to form a multiple server Live Capture-only system. This allows for common configuration, management, and capture control.

To join Lightspeed Live Capture servers together, follow these steps:

1. Select one of your Lightspeed Live Capture servers to act as the master domain. The master domain server system contains the common database and has all the services running on other Lightspeed Live Capture servers added to it via the Vantage Management Console.

2. Add all services running on your Lightspeed Live Capture servers to the Lightspeed Live Capture master domain server. See the Vantage Domain Management Guide for details on adding services.

3. Apply the appropriate multiple-server Vantage license onto the system running the master domain database. See the Vantage Domain Management Guide for details on licensing.

To configure, manage, and control your Lightspeed Live Capture system, run the Vantage Management Console, Vantage Workflow Designer, and Lightspeed Live Capture web applications pointing to the domain contained on the Lightspeed Live Capture master domain server selected in Step 1, above.

Also see, Important Notes on Configuring Non-Capture Workflow Actions on Multiple Server Systems.


100


Existing Vantage Array - Adding Live Capture Server(s)Joining Lightspeed Live Capture systems to an existing Vantage Array allows Vantage workflows to begin with a Capture origin action that is connected to other Vantage actions and services, such as general transcoding, IPTV/VOD transcoding, analysis, third party application control, delivery options, or other service/action types.

Adding ServicesThe Lightspeed Live Capture server includes Vantage services, so adding these services to an existing Vantage Array is no different than adding any other Vantage service running on a separate server to a Vantage Array.

Important Note: Joining Live Capture services to an existing Vantage Array requires the appropriate Vantage Array licensing. See the Vantage Domain Management Guide for details.

To add Lightspeed Live Capture services to a Vantage Array, follow these steps:

1. Verify that the Lightspeed Live Capture services are running, all Vantage Services are running on the server, and no jobs are being processed in the local, factory-installed All-In-One domain.


101


2. Verify that you have configured the other (non-Lightspeed) Vantage domain server with Array, and is running. Refer to the Vantage Domain Management Guide > Installing a Vantage Distributed Domain, for more details.

3. Verify that the Lightspeed Live Capture server is on the same network as the existing Vantage Array domain, with sufficient network permissions and access. Refer to the Vantage Domain Management Guide > Network Requirements, to configure your network.

4. Start the Vantage Management Console, and select the new Vantage Array domain.

5. Add the services on the Lightspeed Live Capture server to the new Vantage Array domain, just as you would do with any Vantage Services running on any Vantage server.

6. Apply the appropriate multiple-server Vantage license onto the system running the master domain database. See the Vantage Domain Management Guide for details on licensing.

Also see Important Notes on Configuring Non-Capture Workflow Actions on Multiple Server Systems.

Uniquely Named Multiple Capture ServersTo ensure each capture source has a unique name when multiple Live Capture servers are part of a multi-server, Capture-only system, or part of an existing Vantage array, you must change the default source names to make them unique and identifiable.

Source names default to SDI Input [1 through n], where n is 4 or 8 depending on which Lightspeed Live server you have.

For example, by default, Source names for a 4 channel Live Capture server are:

SDI Input 1 | SDI Input 2 | SDI Input 3 | SDI Input 4

If you change source names by using the Source Manager, keep in mind that all sources in an array must be uniquely named so you can easily distinguish sources on one server from another.


102


Best Practice for Multiple Live Capture Server System Design

The best practice for using multiple Live Capture server systems is to install and run the Vantage master domain database and IIS Web Server on a server(s) that is separate from the Live Capture servers. See the Vantage Domain Management Guide for details on how to install a Vantage Database and Microsoft's IIS Web Server.

When clustering two or more Live Capture and Vantage servers together, best practice is to use a separate server designated as the IIS Web Server to host the Live Capture Web application. Ideally, the web host should be separate from the Vantage master domain database system since both IIS and SQL can consume a considerable amount of system resources.

The following are two example systems utilizing a separate Database and IIS Web Server.

Capture-only System

For this Capture-only system example, the Vantage master domain database and IIS Web server are installed together on a separate server. This prevents database or Web server resources consumption from affecting the Live Capture servers.


103


Live Capture/Vantage Array—with Separate Vantage Domain Database and IIS Web Host Servers

For this example the Vantage master domain database and IIS Web server are installed on two completely separate servers. Since this is a large system array containing six (6) Vantage system and three (3) Live Capture servers, separating the database and Web Server is recommended to prevent the database and IIS Web server resource consumption from affecting the Live Capture and Vantage servers.

For additional information on best practices for Vantage and Vantage Databases, refer to the Vantage Domain Management Guide and the publication Planning and Setting Up a Vantage Database on the Telestream.net web site.


104


Connecting the Applications for Multiple ServersWhen you have multiple Capture server systems where the database and web server reside on specific server(s) in the multiple server configuration, the Vantage client applications and/or the Live Capture web application must be configured to connect to the appropriate server.

Configuring Vantage Client Applications for Multiple Servers Since the database in a multiple server system is located on a separate server, the Vantage client applications must point to that database. Do this by selecting the database server in the Select Vantage Domain dialog in each Vantage client application.

Using the Vantage Desktop Client Applications First, install the Vantage Management Console and Vantage Workflow Designer client applications on any Windows system on your network. To use these client applications, you must change the Vantage Domain so they connect to the server that is running the Vantage master domain database.

Select Change Vantage Domains from the File menu of each client application to open the Select Vantage Domain dialog.

Note: To learn more about the Vantage Management Console or Vantage Workflow Designer, click the ? icon to display the topic for the feature that you are using. Or, use the Help menu to open the searchable Vantage User Guide for general help.


105


Using the Live Capture Web App with Multiple Servers To use the Lightspeed Live Capture web application with multiple servers, first install the Vantage web applications on the server running the IIS Web service. To open the Lightspeed Live Capture web application, use the following URL:

http://[Name or IP Address of server running IIS Web service]/Vantage/CapturePortal/Default.aspx

When prompted to select a Vantage Domain, choose the server hosting the Vantage master domain database.


106


Using NetBIOS Hostnames Instead of External Name ServerA multi-node Live Capture system can be used without an external name server, when NetBIOS is enabled in the database server and all nodes.

Configure the following settings in all servers to enable NetBIOS:

1. Open the Control Panel and select Network and Sharing Center

2. Select the Change Adapter Settings option to open Network Connections.

3. Right-click on the network connection to be changed and select Properties. The Properties dialog opens:

4. Select TCP/IPv4 and click the Properties button. The TCP/IPv4 dialog opens:


107


5. Configure the IP Address, unique for each server.

6. Configure the Subnet Mask, Default Gateway, and the DNS server addresses. Use the same addresses for each server.

7. Click the Advanced button. The Advanced dialog opens:

8. In the Advanced dialog select the WINS tab, then select Enable NetBIOS over TCP/IP.

9. Click OK in all dialogs to save the configuration.

10. Reboot the server you just configured, then configure all other servers.


108


Correcting Thumbnail Appearance on Non-Local SystemsWhen using the Live Capture Web Application from a non-local server, you may see a No Event message instead of the video thumbnails. If so, update the hosts file on the computer you are using to access the Web Applications. The following procedures describe how to correct this for Mac OS and Windows workstations.

MacOS Procedure to Correct Thumbnail AppearanceOn a Mac OS computer, you add the server IP address and hostname to the /etc/hosts file and save it. Perform the following procedure:

1. Open the Terminal application by going to Application > Utilities and double-clicking Terminal.app.

2. Type the following command and press Return: sudo nano/etc/hosts

3. Enter the administrator password for the computer and press Return.

4. Move the cursor using the arrow keys and position it after all of the text in the window. Then type the IP address of your Lightspeed Live Capture server.

For example: 102.54.94.97

5. Press the Tab key, then type the hostname of the Lightspeed Live Capture server.

For example: CaptureServer1

6. Hold down the Control and 0 keys and press Return.

7. Press Control-X to exit.

8. Flush your DNS by executing the following command in the Terminal:

sudo killall -HUP mDNSResponder

9. Quit the Terminal application.

Windows Procedure to Correct Thumbnail AppearanceOn a Windows computer, you add the IP address and hostname to your hosts file and save it. Perform the following procedure:

1. Open File Explorer and navigate to: C:\Windows\System32\drivers\etc.

2. Right-click the hosts file and open it in Notepad.

3. On a new line, enter the IP address of your Lightspeed Live Capture server.

For example: 102.54.94.97

4. Press the Tab key.

5. Enter the hostname of your Lightspeed Live Capture server.

For example: CaptureServer1

6. Save the file and close Notepad.

Configuring the Lightspeed Live Capture Server and AppsUpdating Capture using Secured Version Control and ComponentPacs

109


Updating Capture using Secured Version Control and ComponentPacs

ComponentPacs are software libraries that execute the actions, such as Capture. ComponentPacs are part of Telestream's Secure Version Control feature. ComponentPacs are designed in such a way as to facilitate the inclusion of multiple component versions. For details, see the Secured Version Control application note on the Telestream web site.

Secured Version Control provides the ability to install the latest software—and begin building workflows that utilize new ComponentPac libraries, while keeping the existing workflows untouched and operating from previous versions of a ComponentPac. When you want to upgrade a workflow or action in a workflow, it can be done at a convenient time. Secured Version Control has been implemented as part of Lightspeed Live Capture and Vantage V7.0.

With Secured Version Control, you can manage the ComponentPac versions in workflows. When you hover over the Inspector icon on an action, information is displayed which includes the version of the ComponentPac library. In the following image, the Capture action's ComponentPac is shown as Capture 7.0.0.197022.

For more information see the Secured Version Control application note on the Telestream web site.

http://www.telestream.net/pdfs/app-notes/app-Secured-Version-Control.pdf

http://www.telestream.net/pdfs/app-notes/app-Secured-Version-Control.pdf

Configuring the Lightspeed Live Capture Server and AppsClear Browsing Data after Updating Vantage or Live Capture

110


Clear Browsing Data after Updating Vantage or Live Capture

After a Vantage or ComponentPac update is installed, you must clear the browsing data in your Chrome browser in order for the Lightspeed Live Capture or Tape Capture web applications to operate properly.

Follow these steps to clear the browsing data:

1. In Google Chrome click the “Customize and Control” icon, select the “More Tools” menu and choose “Clear browsing data...”. The Clear browsing data options appear.

2. In the Clear browsing data options select “The beginning of time” from the drop-down menu, then place a check-mark in “Cookies and other site and plugin data”, and “Cached images and files”.

3. Click the “Clear browsing data” button.

Your browser should now be ready to operate properly with the new update.

111

Creating Capture & Tape Action Workflows

This chapter describes how to create, configure, and activate the Lightspeed Live Capture and Tape action workflows.

For additional details, open the application help (M) or the Vantage Help menu (?) from the upper right corner of the action inspector.

■ Additional Resources

■ Creating, Configuring, and Activating Capture Workflows

■ Creating and Activating a Tape Action Workflow

■ Binding Variables to Configuration Parameters

■ Enabling Open Workflows in Vantage

Additional ResourcesThe following additional resources provide information about topics related to creating and using Capture and Tape action workflows. You may want to refer to these resources as you use this chapter:

• Using the Live Capture Web Application

• Appendix B: Containers, Codecs, and Vantage Actions

• Lightspeed Live Stream User Guide

• Vantage User Guide

• Lightspeed Live Capture Web API Reference


http://www.telestream.net/telestream-support/vantage/support.htm

http://www.telestream.net/pdfs/user-guides/Lightspeed-UserGuides/Live-Capture-API-Reference.pdf

Creating Capture & Tape Action WorkflowsCreating, Configuring, and Activating Capture Workflows

112


Creating, Configuring, and Activating Capture Workflows

Before you can use the Capture web application or API to produce recordings, you must create and activate a capture workflow (you may have several, designed to meet different requirements), which uses the Capture action to serialize a live video source controlled from the Capture web app or Capture API-based program into a media file.

This topic focuses on configuring the Capture action and activating a Capture workflow:

■ Capture Action Overview

■ Configuring Program Settings

■ Restricting Input Frame Type and Rate

■ Expected Labels

■ Configuring Trigger Settings

■ Using the Schedule Trigger

■ Configuring Primary and Secondary Outputs

■ Creating a Capture Action Workflow


113


Capture Action OverviewThe Telestream Live Service and the Capture action are Vantage features in a Vantage domain running on a Lightspeed Live server. The Capture action is used in workflows created for ingesting live and live linear media directly into production, post production, and broadcast workflows and serializing it into a file for further file-based video processing.

You use the Lightspeed Live Capture web application to start and stop recording the select sources and to pause recording. You can also use Lightspeed Live Capture Web API to create custom programs to control Vantage capture workflows. For details on the Web API see the Lightspeed Live Capture Web API Reference at the bottom of the Live Support page on the Telestream website.

Capture supports SDI, RTMP, and Transport Stream inputs only.

You can also use the action to insert leader, filler, and trailer media from files into the live stream as the file is being written.

CAUTION: Workflows containing more than one Capture action are not supported in the Live Capture web application.

The container and codec selected in the Capture action specify the encoding and format of the output file. The encoded media is captured to a primary file stored locally or copied to external SAN/NAS storage, also based on the Capture action configuration. At the same time, a secondary proxy file may also be configured and produced.

Note: Most MXF files containing IMX, XDCAM or AVC Intra, and QuickTime Open files (Capture action only), are created in such a way that they can be opened for editing/playing (in Adobe Premiere Pro CC, Telestream Switch and other media applications) while they are still growing during capture. Check with your edit/player application software documentation for details about supported formats.

As an origin action, the Capture action can only be used to begin a workflow. It may optionally be the only action in the workflow. A capture workflow can also include additional actions to meet processing requirements, such as a Populate action or other transcoding (using a Flip action, for example). Or, it may contain Move or Copy actions, to replicate the output the captured file to other locations.

The Capture action can operate in normal mode or open workflow mode. You can create workflows where the capture action operates normally: it serializes the input stream and, when recording stops, passes it to the next action (if any) in the workflow.

By default, the Vantage domain on the Lightspeed Live server has an Open Workflows license. Thus, you can execute the Capture action (and any other Open Workflow actions) in open workflow mode, significantly speeding media processing. To enable Open Workflow mode on an action, right-click the action and select Workflow Mode > Open. (Open Workflows must also be enabled in the workflow and in the Vantage Management Console). See help in Workflow Designer and the Domain Console.





114


The Capture action inspector enables you to select and configure live streams for specific processing, filtering, transcoding, and output.

Configuring Program SettingsUse the Program panel to configure the Capture action to meet your requirements.

The Program panel displays the input selection and controls.

Source. Select the input source to use. Capture sources are defined in the Vantage Management Console > Capture Inventory.

When Live Stream and Capture are Used on the Same Server

Note: If your server is configured with both Capture and Lightspeed Live Stream, the File Loop and Slate sources may display in the Source menu. These are NOT supported for use by Capture workflows and are reserved for Lightspeed Live Stream. The actual name of the sources created in Live Stream may be altered by the user, and may not be called File Loop or Slate. Consult the Lightspeed Live Stream User Guide for details.

Channel Group. Select the Channel Group in which you want this workflow to reside.

Generate Variables. Open this panel to select which variables to generate.

Avid Master Mob ID | Avid Source Mob ID. Check to generate variables to provide the Avid Master Mob ID and/or the Avid Source Mob ID for use in downstream actions. Then select the text variable you want to generate.


115


Leader, Filler, and Trailer Requirements

All Leader, Filler, and Trailer files must meet these requirements:

- QuickTime- wrapped MOV ProRes format

- One stereo audio track containing two channels of PCM audio

- The frame size and frame rate must match the input source it is used with

- The files must be located on the Lightspeed Live server where Capture is installed.

Leader. Check to write the Leader file to the front of your capture file. The file must be under 30 seconds long.

Note: When Create Output file(s) at Job Start is enabled (see below) and a Leader is to be written, Time-Shift should be set to be 5 seconds longer than the Leader's duration.

Filler. Check to write the selected filler file to your capture file when the EditOUT command is executed via the Web API. Typically, this is a looping video used during breaks in live action. This feature is not provided in the Capture Web application.

Note: For details on the Web API see the Lightspeed Live Capture Web API Reference at the bottom of the Live Support page on the Telestream website.

Trailer. Check to write specified Trailer file at the end of your captured file. The selected file must be under 30 seconds long.

Time-Shift. When a Capture workflow is activated with Time-Shift enabled, the source input media frames are stored in a FIFO RAM buffer. This allows Lightspeed Live Capture to reach back in time and access media processed in the past based on the value of the Time-Shift field. Since Live Capture's Time-Shift is always processing a source input's media frames, when recording is initiated, any media frame stored in the Time-Shift buffer is available to be added to the captured file.

The number of seconds set for Time-Shift in Capture actions associated with this source should be less than or equal to the Max Time-Shift set in the Source Manager. See Managing and Configuring Sources in the Lightspeed Live User Guide for more information on setting Max Time-Shift.

Timecode Override Enable. Check to enable override of the Input Source timecode with the one you enter in the Timecode Override control. When enabled, Timecode Override will override the Input Source timecode during a capture with the one specified and put this timecode at the beginning of the output file.

Timecode Override. A timecode value. Enter the timecode to put at the beginning of the output file when Timecode Override Enable is checked.

Ignore Lost Frames. When enabled, allows a capture to continue recording if a loss of signal or lost frame is encountered. If disabled, the capture will stop when it encounters the loss of signal or lost frame. For LOS details, see Loss of Signal Behavior.




116


Create Output File(s) at Job Start. (Enabled by default.) When enabled, the Capture action associated with a workflow creates output files at the time a capture job is started. If a Leader is to be written, Time-Shift should be enabled and set to 5 seconds longer than the Leader's duration.

In the disabled state the file name and output location cannot be changed after workflow activation.

Note: When Create Output File(s) at Job Start is disabled, output file(s) are created immediately upon the activation of the workflow. In addition, when recording begins an additional file(s) is preemptively created in anticipation of the next capture event. If Create Output File(s) at Job Start is disabled and the Output Location is set to a Path URI, Collision Resolution should never be set to Overwrite.

Delete files on failure. When enabled, the output files are deleted when a job fails or the workflow is deactivated while capturing. When not enabled, output files from failed jobs are retained. Depending on the cause of the failure and type of file being captured, the output files from failed jobs may be usable to the point where capture stopped.

Switch Primary and Secondary Encoding Acceleration. Advanced Users only: By default, the primary output is compressed by the CPU and formatted by the GPU, and the secondary output video formatting is performed by the CPU. When enabled, both the compression and the formatting is performed by the CPU. The exception is that the AVC compressor for the secondary output always executes on the GPU. Use this setting only when advised by Telestream Technical Support or an authorized Telestream Support representative.

Update Workflow. Check Update Workflow to pass a metadata label to the target metadata update workflow, which communicates with Interplay to update Properties.


117


Restricting Input Frame Type and RateWhen enabled, the Capture workflow is restricted to a specific combination of frame type and frame rate. This setting applies only to the Manual trigger or any trigger that has Allow Manual Control enabled.

Select Frame Type. Specifies the frame type/size to use for the restriction.

Frame Rate. Specifies the frame rate to use with the selected frame type.

The following are the available combinations of frame type and frame rate:

- 2160p-4K: 23.98, 24, 25, 29.97, 30, 50, 59.94, 60

- 2160p-UHD: 23.98, 24, 25, 29.97, 30, 50, 59.94, 60

- 1080i: 25, 29.97, 30

- 1080p: 23.98, 24, 25, 29.97, 30, 50, 59.94, 60

- 720p: 50, 59.94, 60

- 625i-PAL: 25

- 525i-NTSC: 29.97

Warning Only. When enabled, you can start and stop manual recordings in the Capture Web app with settings that do not match the selected restrictions. The warning message "Format Mismatch" is displayed on the channel thumbnail card in the web UI, but recording will continue.


118


Operation When Restrict Input is EnabledWhen Restrict Input is enabled AND Warning Only is NOT enabled, the Record button and Gang Record icon are disabled when settings do not match. No recording can be started via the Capture web UI controls. This restriction applies to the Manual trigger and any trigger that has the "Allow Manual Control" option enabled.

When Restrict Input is enabled AND Warning Only is IS enabled, manual recordings can be started and completed with settings that do not match the selected restrictions. The warning message "Format Mismatch" is displayed on the channel thumbnail card in the Capture web UI, but recording will continue.

Automatic Triggers Record When Restrict Input is EnabledAutomatic triggers, such as Web Service, DAI Trigger, CalDAV Calendar, and Schedule Trigger will record even when Restrict Input is enabled and settings do not match UNLESS they have the Allow Manual Control option enabled. See Operation When Restrict Input is Enabled above for behavior when the Allow Manual Control option is enabled.

Expected LabelsEnable Labels to be able to update label values in the Live Capture web application. Labels that are enabled can be configured in the Live Capture web app Channel Options > Configure Labels dialog. The design of a label is accomplished in the Vantage


119


Management Console. Labels can be used in downstream Vantage actions, typically to update or add properties in Interplay, or transformed into text or XML for out-of-band delivery.

For more information on creating labels, search the Lightspeed Live Capture User Guide for Create Labels and Variables for the Tape and Capture Actions. To update Labels in the Live Capture web application, search for Channel Options.

Note: If a label’s parameters are changed or modified in the Vantage Management Console, the changes need to be applied to the workflow’s Capture action before they will display in the Live Capture web app. To apply the updates to a Label you must: 1. Put the workflow into edit mode and open the Capture action configuration panel 2. In the Expected Labels control, disable the target label(s); then re-enable them. 3. Save the action and reactivate the workflow. The updated label(s) will now display the correct information in the Live Capture app.


120


Configuring Trigger SettingsThe Trigger panel enables you to select the method you want to use to start and stop live video input, and provides setting options for the trigger operation.

Select. Choose DAI, Manual, Recurring Segment, Schedule, or Web Service.

DAI TriggersThe DAI (Dynamic Ad Insertion) Trigger enables automatic recording to start and stop based on incoming SCTE-104 markers contained in the VANC data stream of the workflow’s SDI input. Recording begins when a Start Program marker is detected and stops when an associated Stop Program marker with an Event ID that matches the Start Program’s ID is detected. See more details below.

Single unique files are created for each Capture event.

Note: A Time-Shift buffer of 15 seconds or greater is required when using the DAI Trigger.

Start Preroll. Enable to set the number of frames to preroll the start trigger.

Stop Preroll. Enable to set the number of frames to preroll the stop trigger.

Default Start Behaviors for DAI Trigger

A recording is started by the Capture action when one of the following is seen attached to a sample on the source:

- SCTE splice insert data with Splice Insert_Type = 3.

- SCTE time signal data with a segmentation type ID of 0x10 indicating Program Start.


121


Default Stop Behaviors for DAI Trigger

A recording is stopped by the Capture action when one of the following is seen attached to a sample on the source with the corresponding Event ID:

- SCTE splice insert data with Splice_Insert_Type = 1.

- SCTE time signal data with a segmentation type ID of 0x11 indicating Program End.

Allow Manual Stop. When enabled, DAI jobs can be manually stopped via the Lightspeed Live Capture web application.

Select Rules File. Browse to select the XML rules file used to enable automatic recording to start and stop based on SCTE-104 markers.

Note: SCTE-104 rules files can be complex. It is best to contact a Telestream Sales Engineer for details on configuring them correctly.

Issuing a Stop Command Using the Web API

If a DAI SCTE-104 triggered recording should be stopped immediately and Allow Manual Stop has not been enabled, you can issue the following Lightspeed Live Web API Source command:

http://[IP of system hosting the SOURCE Input]:[15000]/InsertScte35Message?source=[SOURCE GUID]&scte35Message=ProgramEnd&eventID=0

The SOURCE GUID can be obtained by using the GetSource command. See the Lightspeed Live Capture Web API Reference at the bottom of the Live Support page on the Telestream website for details on this command.




122


Manual TriggersSelect Manual to trigger capture of live video manually, using the Record button in the Lightspeed Live Capture web application.

Note: If you are using the Lightspeed Live Capture web application to control capturing, you must set the Trigger option to Manual so the web app can control the recording of input channels.

Enable VDCP Control. When checked, Manual capture can be initiated using a VDCP start command. The source must have VDCP enabled in the source configuration.

VDCP Port. Select the port to use for the VDCP commands.

Set Base Name with VDCP Cue Command. When checked, the BaseName token is filled with the text included in the VDCP cue command.

Recurring Segment TriggersThe Recurring Segment trigger enables you to capture files of the duration specified. The Recurring Segment trigger record start is controlled in the Live Capture web app, unless Begin recording on workflow activation is selected, in which case, the recording starts as soon as you activate the workflow.

Segments are created on logical time boundaries based on the duration selected. For example, if a 15 minute segment is selected, the segments will start and stop at 00:00, 00:15, 00:30, and 00:45. Only the first and last segment will start or stop on a non-logic boundary.

The first and last segments captured could be a shorter time than the specified duration, depending on when the recording start and stop commands are initiated. The captured files are frame accurate, so the files can be played continuously from one to the next with no dropped or added frames.

When capturing a recurring segment, Capture tries to start new segments at the exact start of a minute, and the job name reflects this in the naming convention: record-HH:MM:SS:00. If the start time is only an estimate, the name reflects the estimated start time of the segment, and the delineation for seconds is omitted from the name: [base name]-~HH:MM. If the service fails to retrieve a time code but the source is not in a LOS state, the name is [base name]-initial.

Segment Duration. Select the duration of the segment. The options are 5, 10, 15, 20, 30 minutes, and 1 hour. The default is 5 minutes.

Note: When you set the Primary Output of your workflow to use the QuickTime Open container, you should also set the Default Duration in the QuickTime Open general configuration to the same duration as the segment duration.


123


Schedule TriggersThe Schedule Trigger enables you to record based on events on a CalDAV-compatible calendar, such as Google. For detailed instructions, see Using the Schedule Trigger below.

Note: When using the Schedule Trigger you must set your TimeCode Source in the Vantage Management Console to either Computer Clock or Source. When using Source, you must have time-of-day timecode in your source that matches the time set in your Lightspeed Live server.

Calendar. Enter the URL to the CalDAV calendar you want to use.

Username. Enter the email address you use for your CalDAV calendar.

Password. Enter the password you use to sign in to your CalDAV calendar.

Send Calendar Status Notification Emails. Check this option if you want to have an email sent when Capture is able to successfully connect to the CalDAV calendar upon workflow activation, or when connection to the URL goes online, and when the calendar goes offline. The email goes to the address configured in the Vantage Management Console for the Administrator Email Address. If you have not received a notification email, check your spam folder, and then check your Vantage configuration.

Note: The email address for notifications must be properly configured in the Vantage Management Console > Settings & Options > Email tab. See the Vantage Domain Management Guide for detailed instructions.

Allow Manual Control. (Use caution when enabling the Schedule Manual Trigger manual control.) When enabled, manual control via the Lightspeed Live Capture web application is allowed. Jobs can be immediately started using the manual controls in the same way as with the Manual Trigger.

In addition, scheduled jobs that have been added to the Schedule record queue can be stopped and removed from the job queue. When a manual stop is issued, all scheduled jobs that are currently queued or are in the process of being recorded will be removed from the schedule queue. Jobs currently recording will be stopped and removed from the queue. New events added to the calendar will be added to the queue if they are within the 1-hour queue window.

If a Schedule Trigger workflow is deactivated then reactivated, any scheduled events on the calendar that are within the 1-hour schedule queue window will be added to the scheduled capture queue regardless of any previous manual control.


124


Web Service TriggersSelect Web Service to trigger live video capture in a custom program, using commands from the Lightspeed Live Capture Web API. You can queue up a maximum of 16 Web Service trigger jobs per Live Capture host server at any one time.

For details on the Web API see the Lightspeed Live Capture Web API Reference at the bottom of the Live Support page on the Telestream website.

Port. Specify a port number for the web service input that will trigger Live Capture or leave the default, which is 17000. When running multiple Capture workflows simultaneously, you must use unique ports. The program interacting with each workflow must be configured to use the same port number for execution of Capture operations.

Note: Do not use port numbers 8083, 8084, 8089, 8090, 15000, or 18000 for the Web Service input port. An error message does not appear when activating a workflow set to these ports, but the Web Service Trigger will not function.

Create Metadata Log. When enabled, metadata log files are created that include frame numbers, the timecode value of each frame, and RS422 status (when RS422 is enabled). The log file is written to the output location along with the primary output.

Allow Manual Control. (Use caution when enabling the Web Service manual control.) When enabled, manual control via the Lightspeed Live Capture web application is allowed (in addition to capture via the Web API). Jobs can be immediately started using the manual controls in the same way as with the Manual Trigger.

In addition, web service jobs that have been added to the web service record queue can be stopped and removed from the job queue. When a manual stop is issued all web service jobs that are currently queued or are in the process of being recorded will be stopped and removed from the web service queue.




125


Using the Schedule TriggerThe Schedule Trigger enables you to record based on events a Google CalDAV calendar. Only Google calendars are supported at this time. Lightspeed Live Capture software checks the calendar every ten seconds for changes in existing events, and for new events, then loads them and queues them up for capture using a one-hour look-ahead window of time.

When using Schedule Trigger:

- Each event must be at least 15 minutes in duration, or greater.

- Event durations are restricted to a maximum of 9 hours. Events that are longer will stop recording automatically at 9 hours duration.

- Event names cannot contain an accent grave character or any of the following characters: * | \ : ; " ' < > ? /

Note: You must use a calendar that is dedicated to only contain events that are used for Lightspeed Live Capture. All events in the calendar are used for Live Capture, no matter what name they are given or other purpose they are intended for.

What Happens When a Queued Event is DeletedIf an event on the calendar has been added to the Capture queue (events are queued up when they are within 1 hour of their start time) and is subsequently deleted from the CalDAV calendar, its job status is reported as Complete in the Workflow Designer and the Job Status Views application.

- In the case where the deleted event had not yet started capturing, a 0K (zero K) sized file associated with the job will remain in the workflow's output folder location.

- In the case where the deleted event was in a capturing state when it was deleted, a playable file associated with the job will remain in the file's output folder location.

See Using the Job Status Views in the Lightspeed Live User Guide for more information on using this application.

Creating Repeating Events in Google CalendarRepeating Events can be created in a Google calendar, but certain restrictions apply in order to operate properly with Live Capture. When you create a new event in Google calendar and enable the Repeat option, the following restrictions apply.

For Weekly Events only these settings are supported:

- Repeats must be set to Weekly (no other options, besides Daily, are supported).

- Repeat Every must be set to 1 to repeat every week.


126


- Repeat On must only have one day of the week selected (having more than one day enabled is not supported). If you want to capture weekly events on additional days, create a new repeating weekly event for each day.

- Starts On can be any day in the future.

- Ends Never, After, and On are all supported.

For Daily Events only these settings are supported:

- Repeats must be Daily (no other options besides Weekly, are supported).

- Repeat Every must be set to 1 to repeat every day.

- Starts On can be any day in the future.

- Ends Never, After, and On are all supported.

Any other options, except those mentioned above, are not supported and unexpected results may occur. Remember to create specific events for new Repeat schedules, which also keeps your events easier to manage and understand.

Adjusting your Google Account Settings for Live Capture AccessFor Live Capture to be able to read events from your Google calendar you must enable the Allow Less Secure Apps setting in your Google account. Follow these steps to enable this setting:

1. Log in to your Google account.

2. Click on your Google Account icon in the upper right corner and select My Account.

3. Click on Sign-in & Security.

4. Scroll almost all the way down the page to Allow Less Secure Apps.

5. Change the slider from Off to On.

This setting should now read Allow Less Secure Apps: ON.

Note: This setting is not available if the account has 2-Step Verification, or if your Google account administrator has locked less secure app account access. In these situations you should use a different account or change the account settings in order to access the Allow Less Secure Apps option.


127


Creating a Schedule TriggerTo create a Schedule Trigger, follow these steps:

1. In Vantage Workflow Designer, select File > Create New Workflow and name the workflow.

2. In the Live group, drag a Capture action into the workspace. Then double-click to open the action inspector for configuration.

3. Select the Source and the Channel Group to use with the schedule, and make any additional Program selections.

4. Select Schedule from the Trigger menu.

5. The Schedule fields display in the right panel.

6. Calendar - In the Calendar field enter the URL to the CalDAV calendar you want to use. The URL pattern is:


128


https://www.google.com/calendar/dav/<your Google Calendar ID>/events/

Here are some Google Calendar examples:

https://www.google.com/calendar/dav/<calendarid>@group.calendar.google.com/events/

https://www.google.com/calendar/dav/[email protected]/events/

Note: The Google Calendar URL must end with exactly this string: /events/

Note: Your Google Calendar ID for your primary calendar is your email address, but for all other calendars the Calendar ID is in the form of: <long string of characters> @group.calendar.google.com. You can get the Calendar ID by clicking the down arrow next to your calendar at calendar.google.com and selecting Calendar Settings. The Calendar ID is contained in the Calendar Settings > Calendar Address panel. Be sure to use https in your URL - http does not work.

Example Calendar Addresses: Primary using your Google email address: https://www.google.com/calendar/dav/<your Google Email Address>/events/

Additional Calendars using Calendar ID: https://www.google.com/calendar/dav/<Calendar ID>@group.calendar.google.com/events/

Note: Events can be scheduled directly on the CalDAV calendar or by accepting event requests sent by external systems. If an event is requested and tentatively accepted with Maybe, the event will be captured as fully accepted.

Note: CalDAV calendar server applications may implement security restrictions to prevent unauthorized access. Set your calendar's security settings appropriately to allow Lightspeed Live Capture access to calendar events.

7. Username - In the Username field enter the email address you use for your CalDAV calendar. This is the complete email address you use with a CalDAV Calendar. If you are using Google Apps, be sure to enter your Google Apps email address.

8. Password - In the Password field enter the password you use to sign in to your CalDAV calendar.

9. Configure the Primary Output, and optionally the Secondary Output.

10. Save the action and Activate the workflow.


129


When a workflow using a Schedule Trigger is activated it will immediately attempt to log into the calendar service using the credentials supplied. The status of the calendar connection can be found in the workflow's Monitor Status panel within the Vantage Workflow Designer. If it fails to log in the workflow activation will fail. If this occurs, re-enter the correct credentials within the Schedule Trigger and reactivate the Workflow.

Note: Do not edit a previously captured calendar event, and do not try to reuse a previously captured calendar event by giving it a new time; if you do, errors may occur. It is permissible to edit an event that has not yet been captured.

Note: Calendar event time windows should not overlap. For example, if one event is set from 3:00 to 4:00 and another event on the same day is set from 3:15 to 4:15, they will overlap and may cause errors to occur.

Note: When a Leader is included in the Capture action workflow, enough time must be provided between activating the workflow and capturing the first clip to allow the Leader to be written. The capture will fail when adequate time is not available between activating the workflow and capturing the first clip.


130


Configuring Primary and Secondary OutputsThe Primary output panel allows you to select the container format and the video and audio codecs to use for the main captured output. You can also select the output storage location where the file will be written, edit the file name using tokens, and specify a workflow nickname.

The Secondary output panel is optional, and allows you to select the container format and video/audio codecs to use for a proxy output. To configure the video and audio codecs, select the component in the container to display the settings panel to the right.

Primary Output > Select. Choose the output's container format: MPEG2-TS | MXF OP1a | QuickTime | QuickTime Open | TIFO.

Secondary Output > Select. Choose the output's container format: Proxy HLS | Proxy MP4 | Proxy MXF RDD-25.

Delete. To delete this component, click the X icon in the upper right corner.

Output Location. Click Output Location and select from these choices:

- Vantage Store: Write the output to a Live Store. Select any available Live Store from the drop down list.

- Path: Write the output to a specific Windows file system server and directory. Manually enter a Windows share (UNC path) or drive letter (not recommended on Vantage arrays) or click Browse to navigate and select the location. Or, click the green Browse button and select a variable which supplies the fully-qualified path.

WARNING: In rare instances two capture processes writing to the same Path location folder could result in one file overwriting the other. To prevent this it is best to use a unique folder location for each workflow, or append a Time token set to 'mmm' to the file name in one workflow by using Edit Filename, which will return seconds down to a thousandth of a second and add this onto the file name.


131


Edit Filename. Displays the Filename Pattern Editor and specifies the pattern for the file you are creating. Default: Workflow Name - Source Name. Use the menu on the right to select one or more tokens to insert to create the exact filename pattern you require.

Available tokens:

- Base Name: Add a Base Name token so you can customize the output file name with a name you enter in the Live Capture web application, or when passing a name token from the Web API or Schedule trigger.

Note: Base Name tokens can only be used to customize file names when "Create output file(s) at job start" is enabled.

- Workflow Name: Select to add the name of the workflow as part of the file name.

- Source Name: Select to add the name of the live source as part of the file name.

- Variable: Select to choose and add a variable to the file name.

- Date: Select to add the date as part of the file name.

- Time: Select to add the time as part of the file name.

Note: The time applied to the Time token represents the time that the output file is created. Files are initialize at different times based on the Trigger type being used

The Variable token is replaced by the value it holds when the action executes. The variable should be set prior to execution of this action. For example, if a Variable token named ISCI is given the value 12H4JA678, wherever the ISCI variable token appears in the filename pattern it is replaced with that value.

Select Media Nickname. Click the menu to select the nickname (or enter it manually) for this new package file.

Delete. Click the X icon on the right to delete the output from this action.


132


Time Code Burn-in FilterSelect to have the media timecode burned into the output video.

You can set the following options:

X Position—The X position of the top-left of the timecode in the output video frame. The range is from 0 to 4096 pixels.

Y Position—The Y position of the top-left of the timecode in the output video frame. The range is from 0 to 2160 pixels.

Font Size—Sets the font size of the timecode. The range is from 6 to 120 pixels.

Text Color—Set the text color of the timecode. The default is black. You can enter simple color names, such as red, green, or white. Or enter a color hexadecimal code such as #0000DDFF, which is dark blue. The “FF” characters in this example specify the opacity, and are optional. When these characters are not included the text is completely opaque (no transparency). The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the black default is used.

Background Color—Set the color of the area behind the timecode. The default is white. You can enter simple color names, such as red, green, or blue, or enter a color hexadecimal code such as #0000DD, which is dark blue. The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the white default is used.

Timecode Transparency—The opacity of the timecode. 1.00 is fully opaque, or 100% opacity, 0 is transparent.

Note: The burned-in Timecode always represents the actual input timecode being used by the Input Source.


133


Creating a Capture Action WorkflowFollow these steps to create and activate a Capture action workflow:

1. Launch Vantage Workflow Designer (double-click the desktop icon).

2. Select File > Create New Workflow and name the workflow. You may also need to create a Category (File > Create New Category), which is a folder where the workflow is stored. The default workflow naming pattern is [Workflow Name]_[Source Name].

Note: To avoid workflow failures, do not use these characters in workflow names: ` * | \ : ; " ' < > ? /

3. In the Workflow Design panel, open the Live category and drag a Capture action into the workflow workspace below.

Note: If you use multiple Capture actions in a single workflow and each action is actively recording, inaccurate state information is displayed reported for the workflow Status in the thumbnail card and Status Panel. For best practices, use only one Capture action per workflow.

4. Click the Inspector (circled i) icon on the upper left corner of the action to open the Inspector and configure the action or double-click the action to open the Inspector.


134


5. For information on the settings and options see Configuring Program Settings and Configuring Primary and Secondary Outputs.

6. Click Save when finished with your configuration settings.

7. Click Activate below the workflow to initiate workflow operation.

Note: Workflow expiration is set for 24 hours and is enabled by default. For details, click the ? in the upper right to open the Vantage User Guide. See the Viewing and Specifying Workflow Details topic for information on adjusting the expiration time.


135


8. The Monitor Status tab opens to show the progress of your workflow as it operates and gives you information about it. You can double-click the line item representing your workflow and get details about how it is functioning.

When you activate a workflow, it begins to operate and work with the Lightspeed Live Capture or Tape Capture web application to accept the input you select, encode and package it into the format you specified in the workflow, and output the captured media package to the Live Store location you specified.

There are many more ways to monitor your workflow. To learn more, click the ? icon or use the Help menu to open the Vantage User Guide.

This completes configuration and a simple workflow as prerequisites for running the Live Capture web app. You are now ready to log into the Live Capture web app and begin using it as explained in Using the Live Capture Web Application chapter.

Creating Capture & Tape Action WorkflowsCreating and Activating a Tape Action Workflow

136


Creating and Activating a Tape Action WorkflowBefore you can use the Tape Capture web application or API to produce recordings, you should create and activate one or more tape capture workflows as needed, each of which uses the Tape action to make a video source available for Capture web app or API control.

The following topics explain this workflow and how to create it:

■ Tape Action Overview

■ Expected Labels

■ Primary and Secondary Outputs

■ Settings Panel

■ Creating the Tape Action Workflow


137


Tape Action OverviewThe Live Service and Tape action are software management features built into a Lightspeed Live server, which accepts VTR SDI video feeds and captures them to media files.

The Tape action is used to start SDI tape capture workflows created in any Vantage domain installed on the Lightspeed Live server. The Tape action inspector allows you to select and configure VTR sources for processing, filtering, transcoding, and output. You can also use the action to add metadata labels.

The container and codec selected in the Tape action allow configuration of the encoding and format of the capture operation. The encoded media is captured to a primary file stored locally or copied to external storage.

Note: Most Lightspeed Live Capture MXF files containing IMX, XDCAM or AVC Intra, and QuickTime Open files (Capture action only), are created in such a way that they can be opened for editing/playing (in Adobe Premiere Pro CC, Telestream Switch and other media applications) while they are still growing during capture. Check with your edit/player application software documentation for further details on supported formats.

As a Vantage origin action, the Tape action can be used in Vantage to begin a workflow, and can be the only action in the workflow. A tape capture workflow can include additional actions, such as a Copy or Move action, which can be optionally used to output the captured file to an additional location.

Use the Lightspeed Tape Capture web application to control VTR sources from the VTR Preview Player panel, log clips from tapes, and capture logged clips from tape to files. For information about the Live Capture web application, please see the Lightspeed Live Capture User Guide. The Lightspeed Live Tape Capture Web API can also be used to create custom programs to control tape capture workflows.

This action is open workflow capable if the Open Workflows license is installed; right-click the action and select Workflow Mode > Open. Open Workflows must also be enabled for the current workflow and in the Vantage Management Console Settings.

Note: Controls with a green Browse button may be bound to a variable to dynamically assign their setting or value. The variable must have a value when this action executes. You can assign the value to the variable in a previous action in the workflow or use the variable's default value. Click Browse to select the variable or create a new one.

InputsThe inputs are listed individually at the top of the inspector.


138


Source. Specifies the input source to use. Capture sources are defined in the Vantage Management Console > Capture Inventory.

When Live Stream and Capture are Used on the Same ServerThe following Warning only applies when Live Stream and Live Capture are used on the same Lightspeed Live server:

WARNING: Capture supports SDI, RTMP, and Transport Stream inputs only. If your server is configured with both Capture and Lightspeed Live Stream the 'File Loop', or 'Slate’ sources may appear in the Source drop-down menu. These are NOT supported for use by Capture workflows and are reserved for Lightspeed Live Stream. The actual name of the sources created in Live Stream can be any name they have been given, and may not be called File Loop, RTMP, and so on. Please consult the Lightspeed Live Stream documentation for additional details.

Channel Group. Specifies the Channel Group (Nexus Group) in which you want this workflow to reside.

Expected LabelsMetadata Labels created in the Vantage Management Console can be selected using the drop-down menu. When selected, they are available to configure in the Tape Capture web application.

Primary and Secondary OutputsThe Primary and optional Secondary Output panels are used to create Configuration Templates that are selectable from within the Tape Capture user interface. For each respective output panel, select the output storage location where the captured file will be written, edit the file name using tokens or variables, and specify the output nickname. Configuration Templates can be added to each output type and consist of a container format and the video and audio codecs to be use for the captured output. There is no limit to the number of Configuration Templates that can be added to the Output panels.

Secondary output templates which are named identically to a respective Primary template name are paired together when capturing clips. If no matching Primary template name is found the first Secondary template is used.

Add. Create a new Configuration Template, by first choosing the template's output container format from the drop-down menu. Specify a container type, give it a unique template name and configure setting details by clicking on the video and audio streams on the left and making selections in the panel on the right. Add all of the output configurations that you want to have available in the Tape Capture web app.

Click the Capture button in the Tape Capture web app to select the primary output container format you want to use for each capture operation.


139



- Vantage Store: Write the output to a Live Store. Select any available Live Store from the drop down list.

- Path: Write the output to a specific Windows file system server and directory. Manually enter a Windows share (UNC path) or drive letter (not recommended on Vantage arrays) or click Browse to navigate and select the location. Or, click the green Browse button and select a variable which supplies the fully-qualified path.

WARNING: In rare instances two capture processes writing to the same Path location folder could result in one file overwriting the other. To prevent this it is best to use a unique folder location for each workflow, or append a Time token set to 'mmm' to the file name in one workflow by using Edit Filename, which will return seconds down to a thousandth of a second and add this onto the file name.

Edit Filename. Displays the Filename Pattern Editor and specifies the pattern for the file you are creating. Default: Base Name. Use the menu on the right to select one or more tokens to insert to create the exact filename pattern you require.

Available tokens:

- Base Name: Select to add the base (clip) name as part of the file name. The Base Name token is populated with the Clip Name selected in Clip Panel of the Tape Capture user interface.

- Workflow Name: Select to add the name of the workflow as part of the file name.

- Source Name: Select to add the name of the live source as part of the file name.

- Variable: Select to choose and add a variable to the file name.

- Date: Select to add the date as part of the file name.

- Time: Select to add the time as part of the file name.


Select Media Nickname. Specifies the nickname for this media.


Settings PanelSpecify settings to use for each output configuration. Binding any of these parameters to variables will make those parameters configurable from within the Tape Capture user interface.

Ignore Lost Frames. When checked, lost frames do not cause the capture to stop.


140


Pre-Roll Duration. Specifies the number of seconds that tape rolls before a scheduled recording begins. You can also assign a variable defined elsewhere in the workflow.

Note: Setting Pre-Roll Duration to 0 (zero) may have a use in some cases, such as capturing digital sources. A 0 (zero) setting could cause issues when capturing from tape sources. The default Pre-Roll is 3, which often works fine for a tape source.

Post-Roll Duration. Specifies the number of seconds that tape rolls after a scheduled recording ends. You can also assign a variable defined elsewhere in the workflow. Note that the VTR stops only after all frames have been captured, so post-roll may continue longer than the duration you specify.

Timecode Override Enable. When checked, activates and overrides the Input Source timecode with the one entered in the Timecode Override control. When enabled, Timecode Override overrides the Input Source timecode during a capture with the one specified and puts this timecode at the beginning of the output file. All clips in the Tape clip list will have their timecode overwritten by this timecode.

Timecode Override. Specifies the timecode value to use to put at the beginning of the output file when Timecode Override Enable is active.

Discontinuity Threshold. Specifies the minimum number of skipped frames that constitutes a discontinuity (timecode break) state. This threshold affects both Create New File on Discontinuity and Abort on Discontinuity, when enabled. Note that decremented and repeated frames always count as timecode discrepancies, and for these discrepancies, the threshold setting is ignored.

See Timecode Break Recording and Timecode Discontinuity Definition in the Using the Tape Capture Web Application chapter for discontinuity details.

Create New File on Discontinuity. When checked and timecode discontinuity is detected, specifies that the current media file is closed and a new media recording file is opened. During an active capture recording, if a discontinuity is encountered, the current capture file will complete, and a new media file recording will immediately start.

Time code discontinuities are defined as follows:

- Time code increments: If time code increments by a value equal to or greater than the selected Discontinuity Threshold value.

- Time code repeats: The Discontinuity Threshold value is ignored in this case.

- Time code decrements: The Discontinuity Threshold value is ignored in this case.

Example 1: A time code incrementing from 00:00:30;10 to 00:00:30;15 would be detected by a threshold of 4 or less.

Example 2: A time code repeating from 00:00:30;10 to 00:00:30;10 would be detected.

Example 3: A time code decrementing from 00:00:30;10 to 00:00:29;00 would be detected.


141


Abort on Discontinuity. When enabled, capture aborts when a timecode discontinuity is detected as specified by the Discontinuity Threshold or when the VTR servo is not locked.

Note: Create New File on Discontinuity and Abort on Discontinuity options are mutually exclusive; when both are checked, Abort on Discontinuity takes precedence. That is, if discontinuity is detected, the job is aborted.

Ignore Frames When Servo is Not Locked. If enabled, all frames captured while the servo is in the unlocked state (as reported by the VTR) are excluded from the output file.

Create New File When Servo Relocks. If enabled, creates a new media file when the servo relocks after being in the unlocked state. When a servo relock is encountered during an active capture recording, the current capture file will complete, and a new media file recording starts.

If Create New File When Servo Relocks is enabled and Ignore Frames When Servo is Not Locked is disabled, the system may create unwanted (unlocked) frames at the end of output files.

If Create New File on Discontinuity is enabled and Ignore Frames When Servo is Not Locked is also enabled, the result may be an output file that contains a discontinuous timecode, even though Create New File on Discontinuity is enabled and the timecode was always incrementing. This occurs because of the system ignoring frames, regardless of the timecode, while the servo is unlocked. With this configuration, the frames captured during the period when the servo was unlocked will be excluded from the output file. New frames would then be added to the file when the servo relocks, which would cause the output file to have discontinuous timecode. To avoid this scenario, enable the Create New File When Servo Relocks option. In this state the relock of the servo will start a new file where the discontinuity in the output file would have been.

As described above, repeating timecodes are counted as discontinuities. Most VTRs repeat timecodes when the servo is unlocked; therefore, if Ignore Frames When Servo is Not Locked is disabled and Create New File on Discontinuity is enabled, the result may be many single frame files while the servo is unlocked. This will not happen if Ignore Frames When Servo is Not Locked is enabled.

With many VTRs, particularly an SRW-5800, there can be gray frames after the servo relocks. Timecode for these frames is often invalid. Because the system is only able to respond to the status the VTR provides, it will not detect and exclude these gray frames.

No two passes of the same section of tape are likely to be identical. This occurs because the VTR can sometimes take longer than others to lock the servo after the control track is detected. Therefore, it is important to check the logs to verify whether the servo was locked while a specific frame was captured.

For past users of Telestream’s Pipeline tape capture product, enabling all three settings above will provide the cleanest results and the closest to what Pipeline used to do.


142


Use Duration Over Markout. Ignores mark out and rolls tape for the specified duration regardless of time code.

Treat input as Progressive. Assumes input is progressive even if it is interlaced.

RS422 time code delay. Adjusts RS422 time code by specified number of frames. RS422 time code delay can be used to compensate for VTR decks requiring adjustments to frame timing. Frames can appear early or late, depending on the type and/or age of the VTR deck used. This adjustment compensates for VTR decks that are not 100% frame accurate (or for systems with routing latency to the associated timecode). Most VTR decks do not require this offset adjustment. If you have a VTR deck that requires this adjustment it is necessary to use a trial and error process to determine the correct offset. The default is 0, the minimum is -3 frames, and the maximum is +3 frames.

Rewind Tape. When checked, a Rewind command is sent to the VTR after capture is complete. If there are multiple clips on a tape slated for capture, the Rewind command is sent once; after all clip capture jobs have completed.

Stitch Clips. When checked, stitches the aggregated content from all captured clips into a self-contained or reference output file. See Stitch Behavior below.

Stitch Clip Base Name. Specifies the base name to use in job names and the "Base Name" part of the file name pattern. When blank, StitchedClip is the default base name.

Stitch Behavior. Specifies the stitched file behavior:

- Direct Convert. Creates a self-contained output file for the Primary and/or Secondary outputs, which contains the aggregated content from all captured clips in the order specified by the user.

- Reference Movie. Creates a small reference output file, for the Primary and/or Secondary outputs, referencing all captured clips in the order specified by the user.

The Direct Convert and Reference Movie output files can be used by a downstream action for additional processing. The referenced clips must remain in their original location for the Reference Movie to be playable.

Allow Secondary Output to be Disabled. Check to add the option to disable the secondary output in the Tape Capture web application. When selected, the "Disable Secondary Output" option is added to the Tape Capture web app Capture Clips dialog.

Note: When Allow Secondary Output to be Disabled is selected, no downstream processing can be done for the secondary output. With this enabled, you cannot save the workflow if it is set to process the secondary output.

When you need to have downstream actions process the secondary output, but you want the option to disable the secondary output in the Tape Capture web app, add the Poster Frame secondary output so that can be selected in the web app as the disabled option.


143


You must create one or more MP4 secondary outputs when Allow Secondary Output to be Disabled is selected, in order to have the option to enable and create a secondary output in the Tape Capture web app.

Is Output Stitched. When checked, enables the ability to detect if an output is a stitched type, or not. Select or create a variable to generate, which is used in a downstream action to make the decision to select the clip when the variable is True. (Typically a Decide action is used downstream for the selection, then other actions for further processing.)

Primary Configuration. When checked, specifies the name of the primary configuration, in the selected text variable for use in downstream actions. This string is entered by you in the output Config Name field.

Secondary Configuration. When checked, specifies the name of the secondary configuration, in the selected text variable for use in downstream actions. This string is entered by you in the Tape action output Config Name field.

Time Code Burn-in FilterCheck to enable this filter and configure it. The Time Code Burn-in filter writes the current value of the time code into the video frame at the specified location and font size, typically for use in proxy files.

Controls with a green Browse button can be specified dynamically, on a job-by-job basis by assigning a variable whose value has been set in an upstream action.

X Position. The X position of the top-left of the timecode in the output video frame. The range is from 0 to 4096 pixels.

Y Position. The Y position of the top-left of the timecode in the output video frame. The range is from 0 to 2160 pixels.

Font Size. Sets the font size of the timecode. The range is from 6 to 120 pixels.

Text Color. Sets the text color of the timecode. The default is black. You can enter simple color names, such as red, green, or white. Or enter a color hexadecimal code such as #0000DDFF, which is dark blue. The "FF" characters in this example specify the opacity, and are optional. When these characters are not included the text is completely opaque (no transparency). The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the black default is used.

Background Color. Set the color of the area behind the timecode. The default is white. You can enter simple color names, such as red, green, or blue, or enter a color hexadecimal code such as #0000DD, which is dark blue. The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the white default is used.

Timecode Transparency. The opacity of the timecode. 1.00 is fully opaque, or 100 per cent opacity, 0 is transparent.

Note: The burned-in Timecode will always represent the actual input timecode being used by the Input Source.


144


Creating the Tape Action WorkflowFollow these steps to create and activate the Tape action workflow:

1. Open the Vantage Workflow Designer.

2. Select File > Create New Workflow to start a new workflow.

3. Drag the Tape action from the Live service to the design area. A workflow can consist of only this one action. Other actions can be added to perform specific additional functions. See Appendix B: Containers, Codecs, and Vantage Actions.


145


4. Open the Tape action inspector and make these selections:

Source—Select an input source.

Channel Group—Select a Channel (Nexus) Group.

Expected Labels—Select labels you created, if any, to contain metadata. When selected, they are available to configure in the Tape Capture web application.

5. Make selections in the Primary and Secondary Outputs and the Settings Panel described previously.

6. When finished with Tape action configuration, click Save.

7. Click Activate to start the workflow. This workflow must be running to connect the Web app to the VTRs.

Creating Capture & Tape Action WorkflowsBinding Variables to Configuration Parameters

146


Binding Variables to Configuration ParametersBinding variables to a Tape or Capture action's General, Container, Video, or Audio configuration settings enables you to configure those settings directly from the Tape Capture or Live Capture web application.

For more information on using and creating variables, click the ? to display the Vantage Users Guide.

To bind a variable to a control (setting), select the green Variable browse button next to the control:

The Select Variable dialog displays:

Any control that has been bound to a variable can be configured in the Tape Capture web app Customize Parameters dialog. See Configuring Tape Parameters that are Bound to Variables.

Any parameter that has been bound to a variable can be configured in the Live Capture web app Customize Parameters dialog. See Channel Options.

Creating Capture & Tape Action WorkflowsEnabling Open Workflows in Vantage

147


Enabling Open Workflows in VantageAlthough you can use Capture workflows in normal mode (where actions execute serially), you can speed processing by enabling Open Workflow mode. Open Workflow enables workflow actions consuming the output of a Capture or Tape action to operate concurrently, providing much greater processing efficiency and total workflow execution speed. You create an open workflow in the same way as a standard workflow in Workflow Designer.

Note: Open Workflows is an optional, licensed feature in Vantage. It is enabled in Vantage domains hosted on Live Stream servers by the standard license.

Open workflows must be enabled in three places:

• Domain Level—in the Vantage Management Console Settings & Options > General.

• Workflow Level— in Workflow Designer, in the target workflow’s details panel above the action selector panel: check the Open Mode option.

• Action Level—on each action, right-click and select Workflow Mode > Open.

Note: When you enable open workflows, the affected Vantage services must be restarted for the feature to take effect. For more information about enabling open workflows, open the Vantage User Guide—click the question mark (?) in the upper right corner of the action inspector.

If your Live Capture system has been joined to a multiple server Vantage domain (an array), all actions in Live Capture and Tape workflows (those starting with Capture or Tape actions) operate in open mode, regardless of whether the Vantage system is specifically licensed to support open workflows or not.

Creating Capture & Tape Action WorkflowsEnabling Open Workflows in Vantage

148


149

Using Live Capture with Avid Workflows

This chapter describes the licensing requirements and components necessary to capture, transcode, and deliver media to Avid Interplay. It also describes how to create and configure workflows for processing media in Vantage-to-Avid workflows, and deliver metadata to update Interplay user properties.

■ Licensing Live Capture Systems for Avid Workflows

■ Using the Interplay Advanced Encoder

■ Required Avid Components Installed by User/Avid

■ Prototype Single Resolution Avid Workflow

■ Prototype Multiple Resolution Avid Workflow

■ Updating Avid User Properties in Capture Jobs

■ Creating an Avid User Properties Metadata Label

■ Creating a Capture-to-Interplay-with-Metadata Workflow

■ Creating a Dynamic-Metadata-Update Workflow

Using Live Capture with Avid WorkflowsLicensing Live Capture Systems for Avid Workflows

150


Licensing Live Capture Systems for Avid WorkflowsUse of Live Capture with Avid systems requires an optional license, depending on the architecture of your Vantage domain.

Live Capture-only Vantage DomainsTo use Avid Interplay Advanced Encoder and Avid Notify functionality, an optional license must be included in your Lightspeed Live Capture license, part code LS-LIVE-AVID-OPT.

For Live Capture System as Part of a Separate Vantage Domain

To use Avid Interplay Advanced Encoder and Avid Notify functionality when Capture systems are part of a separate Vantage domain/array requires a Vantage Transcode Pro Connect with the Advanced Avid Option in your Vantage license, part code V-AVID.

Required Avid Components Installed by User/AvidThe Avid NEXIS Client Manager is required, which is installed by the user or by Avid personnel. Telestream cannot install or modify Interplay components or configurations.

You can also see the Avid Integration Guide on the Telestream web site for a list of required components and for more information about how to configure the Notify action and Interplay Advanced Encoder in the Flip action, and other topics relevant to using Vantage in conjunction with Avid products.

https://www.telestream.net/pdfs/app-notes/app-Avid-Integration-Guide.pdf

Using Live Capture with Avid WorkflowsUsing the Interplay Advanced Encoder

151


Using the Interplay Advanced EncoderYou can use the Interplay Advanced Encoder and Notify action with Avid to transcode and deliver media to Interplay or Media Composer.

Note: The Interplay Advanced Encoder on Live Capture systems is intended to be used in a Live Capture Server-only Vantage domain (whether single or multiple Capture nodes). If your Live Capture system is joined to a Vantage transcoding domain, all Interplay Advanced Encoder processes must be executed on Vantage transcode nodes that are hosted on servers other than Live Capture servers—not on the Live Capture system(s). In this configuration, the Vantage Transcode Service must be removed from the Live Capture systems, using the Vantage Management Console.The Multi-Res container is not implemented in the Interplay Advanced Encoder when the Vantage Transcode Service is hosted directly on the Live Capture Server.

The Interplay Advanced Encoder is implemented in the Flip action and produces Avid MXF media and associated files. There are two container options:

• Interplay Single-Res—Which includes integrated delivery to ISIS/NEXIS share stor-age and Interplay check-in.

• Media Composer—For creating an Avid AAF and individual Avid MXF media files.

This graphic illustrates the settings in the Flip action’s Interplay Advanced Encoder when configured to produce media in an Interplay Single-Res container:

Using Live Capture with Avid WorkflowsUsing the Interplay Advanced Encoder

152


This graphic illustrates the settings in the Flip action’s Interplay Advanced Encoder when configured to produce media in a Media Composer container:

Using Live Capture with Avid WorkflowsPrototype Single Resolution Avid Workflow

153


Prototype Single Resolution Avid WorkflowThis prototype workflow illustrates the simplest Avid workflow for capturing live streaming media from a Live Stream Capture server and converting it into a single-resolution file. This Avid workflow consists of two actions—Capture and Flip:

Note: To use this action in Open mode, enable Open File Decoding Mode. See Enabling Open Workflows in Vantage for details.

This workflow produces Avid MXF OP-Atom media with associated AAF files.

Configure the actions to create this workflow:

1. Configure the Capture action Primary Output to use a TIFO container set with the video essence (AVC Intra, DNxHD, DNxHR, DV25, DVCPro, DVCProHD, IMX, XAVC, XDCAM 4:2:0, or XDCAM 4:2:2) that you desire to check into Interplay.

2. The Flip action enables you to use the Interplay Advanced Encoder. This action takes the TIFO file generated by Capture and direct-converts it (no transcoding required).

Note: The codec used to create the TIFO file in the Capture action must match the Direct Convert option selected in the Flip action’s Interplay Advanced Encoder.

3. When using the Interplay Single-Res container, you should include the Interplay and Avid shared storage data, and set the decoder to Telestream. The MOB ID is automatically generated.

Note: In the context of the Interplay Advanced Encoder, selection of the Interplay or Media Composer container does not change the wrapper or file format; instead, they are used to specify the selected product as the target, and to configure the encoder to inter-operate correctly with it.

Using Live Capture with Avid WorkflowsPrototype Multiple Resolution Avid Workflow

154


Prototype Multiple Resolution Avid WorkflowThis prototype workflow illustrates an Avid workflow for capturing live streaming media and converting it into two different files, each with different resolutions. This workflow consists of three actions: a Capture action and two Flip actions—one high-res file and a proxy file.

Note: The Multi-Res container is not implemented in the Flip action’s Interplay Advanced Encoder when the Vantage Transcode Service is hosted directly on the Live Capture Server.This workflow generates two single-res files in separate Flip actions, which is functionally equivalent to using the Multi-Res container when the Vantage Transcode service is hosted on a standard Windows server.

This workflow produces Avid MXF OP-Atom media with associated AAF files.

Configure the actions in this manner:

1. Configure the Capture action Primary Output to create a TIFO file with the codecs to use to create the Avid high-res file.

Using Live Capture with Avid WorkflowsPrototype Multiple Resolution Avid Workflow

155


2. In the Generate Variables panel, check both Mob IDs and specify text variables. This creates MOB IDs that are passed to the downstream Flip actions.

3. Two Flip actions are used in this workflow to encode the video using the Interplay Advanced Encoder.

– Flip 1—The first Flip action ingests the TIFO file generated by Capture and direct converts it (no transcoding needed). When using the Interplay Single-Res container, you should include the Interplay and Avid shared storage data, and specify the Telestream decoder.

– Flip 2—The second Flip action also ingests the same TIFO file and transcodes it into an Avid Proxy (H.264 Proxy and Telestream H.264 (which supports 1080i 29.97, 1080i 25, 1080p 29.97, 1080p 25, 1080p 23.976). When using the Interplay Single-Res container, include the Interplay and Avid shared storage data, and specify the Telestream decoder.

Note: The type of Direct Convert process (IMX, AVC Intra, etc.) you specify to create this file must match the codec you specified in the Capture action.Both of these actions must have the MOB ID bound from the Capture action in the Asset Attributes panel to identify them properly in Interplay.

For more information about how to configure the Interplay Advanced Encoder in the Flip action see the Avid Integration Guide on the Telestream web site.

https://www.telestream.net/pdfs/app-notes/app-Avid-Integration-Guide.pdf

Using Live Capture with Avid WorkflowsUpdating Avid User Properties in Capture Jobs

156


Updating Avid User Properties in Capture JobsLive Capture supports updating user properties in Interplay from metadata values in Vantage while recording video via a capture job.

Note: In the context of this guide and Vantage, reference is often made to metadata labels and their fields or parameters. In the context of Avid Interplay, these fields/parameters are referred to as properties or user properties. The terms are interchangeable and all refer to the same item.

When you update metadata in Interplay from Vantage workflows, the changes to user properties display the updated data in Interplay Access.

To display specific user properties in Interplay Access when you’re viewing an asset, check the properties you want to display, as shown below.


157


In this example, two user properties were added as shown in the Properties tab, below the system properties:

You can update user properties in Interplay from Vantage metadata in two ways:

• Each time you start recording in the Web app—using current (default) metadata values in the Capture web app and a Capture-to-Interplay-with-Metadata workflow

AND

• Update metadata dynamically—after you have started recording, by changing the metadata values in the Capture web app and using an additional Dynamic-Meta-data-Update workflow.

Updating user properties in Interplay requires these Vantage resources (creating them is a one-time task):

1. Create metadata labels in Vantage to transport the values through from the Live Capture server to Vantage and on into Interplay (see Creating an Avid User Properties Metadata Label).

2. Create a Capture-to-Interplay-with-Metadata workflow (see Creating a Capture-to-Interplay-with-Metadata Workflow).

3. Optionally, create a Dynamic-Metadata-Update workflow (see Creating a Dynamic-Metadata-Update Workflow).

Note: Capture-to-Interplay-with-Metadata workflows must be in Open Workflows mode to update metadata during a capture operation. See Enabling Open Workflows in


158


Vantage. Also see Using Open Workflows in the Vantage User Guide for licensing requirements and more information about setting up and using open workflows.

The first two topics describe how to use the Capture web app to set default metadata values for all recording jobs and also how to update the metadata values in Interplay during recording—after the job has already started.

If you haven’t already created labels and workflows in Vantage, use the remaining topics to learn how to create metadata labels to meet your needs, and the prototype Capture-to-Interplay-with-Metadata workflow and Dynamic-Metadata-Update workflow which you can use as an example for creating your own.

■ Setting Default Metadata Values for Capture Operation

■ Updating Metadata Values During an In-Progress Capture

Setting Default Metadata Values for Capture OperationAlthough not required, default values are typically specified in metadata labels defined in the Capture workflow and are automatically transmitted to Interplay as part of each capture job that starts when you begin recording video from the Capture Web app.

Note: Ensure that the Capture-to-Interplay-with-Metadata workflow has been started in Workflow Designer, in order to deliver the labels to the Capture web app. If it is not started, no labels display in the Labels dialog.

To set or update default metadata values for future recordings (captures) directly in the Capture web app, follow these steps (this does not update metadata for the current recording, if underway):

Note: The Labels dialog that you display from the icon on a Channel card enables you to set default values for future recordings, not the current recording.

http://www.telestream.net/pdfs/user-guides/Vantage-UserGuides/Vantage-User-Guide.pdf


159


1. Click Channels in the Selection panel to the left to display the channel preview card(s):

2. Click the menu icon on the target Channel card and select Labels to display the Labels dialog:


160


3. In the Label dialog, select a label from the list (which was populated by the target Capture workflow for this channel) on the left and enter or update the values in the metadata label’s parameter fields on the right.

4. Click Save to store the label in the Web app for future captures. This metadata is transmitted to the Dynamic-Metadata-Update workflow via the Capture-to-Interplay-with-Metadata workflow when each capture job starts (whether manually, via the Live Capture web service or other available trigger), which communicates with Interplay to update the associated user properties in Interplay.

Updating Metadata Values During an In-Progress CaptureDuring recording (a capture job is currently executing in Vantage), you can dynamically update metadata label values directly in the Capture web app, which are then transmitted to Interplay immediately to update the user properties.

The Capture Web app passes each updated label to the Capture workflow job, which in turn, starts a job for the target Dynamic-Metadata-Update workflow (specified in the Capture workflow) to deliver the data to the target Interplay system.

To update metadata while a capture workflow is actively recording, follow these steps:

1. Click Status in the Selection panel to the left to display the channel status:


161


2. In the center column (above, dark gray), click the icon on the current recording to display the Labels dialog (see step 3).

Alternatively, click Channels and click the click the recordings icon. Then, click on the current recording to display the Labels dialog:

3. In the Label dialog, select a label from the list (which was populated by the target Capture workflow for this channel) on the left and enter or update the values in the metadata label’s parameter fields on the right.

4. Click Update to send the updated label to the Capture workflow, which starts a Metadata Update workflow job and updates Avid Interplay’s user properties.

Using Live Capture with Avid WorkflowsCreating an Avid User Properties Metadata Label

162


Creating an Avid User Properties Metadata LabelThe labels that display in the Capture Web app are defined in Vantage and attached to the Capture-to-Interplay-with-Metadata workflow’s Capture action so they can be accessed by you in the Web app.

In order to provide a schema for the metadata being delivered to Interplay, a metadata label with the required parameters (fields, or User Properties in Interplay) must created in Vantage (and optionally, pre-configured with default values and pick lists as appropriate). This one-time task is performed in the Vantage Management Console.

Note: For complete details on managing metadata labels in the Management Console, click the icon to display the Vantage User Guide.You can also optionally create labels directly in Workflow Designer.

Use these steps to create labels for use in the Capture Web app and Vantage workflows:

1. Open the Vantage Management Console and select Workflow Design Items > Metadata Labels.

a. Create a new label and name it appropriately. The console adds it to the list and displays the design panel so you can configure it for your requirements.

b. In the design panel, add parameters and configure each as required. Specify the Category as General when the property exists in Interplay. (Once you type in a new category, it is added to the category pick list for use in other parameters.)

You can specify the type, length, value pick lists/default values, etc. Or, you can leave the default value empty and provide it later while the job is in progress.

As you configure each parameter, it displays in the Preview/Test panel to the right so you can monitor your work and adjust default values.

c. If you want to be able to add new parameters (properties) to Interplay—properties that do not exist—create a pair of parameters (New Property Name and New Property Value) and set the Category of each to Add New Property Name and Value. Later, while the capture job is in progress, you can create a new property (or many new properties) and assign a value in Interplay.

Using Live Capture with Avid WorkflowsCreating a Capture-to-Interplay-with-Metadata Workflow

163


Creating a Capture-to-Interplay-with-Metadata Workflow

A Capture-to-Interplay-with-Metadata workflow is created (in Workflow Designer) to ingest and transcode s live source, update the label data and store it in variables, and transcode the video and pass it and the label to Interplay in Avid shared storage.

Note: For details on action configuration, click the icon to display the help page for the action or for general help, click the icon to open the Vantage User Guide.

1. Create a new workflow and start it with a Capture action, configured as follows:

a. Make all typical selections: Source, Channel Group, Trigger, Outputs, etc.b. In the Generate Variables panel, enable Master and Source Mob ID and specify a

text variable for each, to generate Mob IDs. (Select <<Create New Variable>> to create new master and source Mob ID variables if required.)

c. Enable Update Workflow and decide on the name of the Dynamic-Metadata-Update workflow you are going to create next. Enter the name of the workflow here, to update the property values and deliver them to Interplay. See Creating a Dynamic-Metadata-Update Workflow for creating this workflow, following.

d. Open the Expected Labels menu and check each label to ingest (Creating an Avid User Properties Metadata Label). These are populated with values when each job is submitted.

e. Save changes.

2. Add a Populate action (or a series, if required—one for each label) to the Capture action. Configure each Populate action to convert label data passed to it by the Capture action into variables:

a. Select Variables from Label Parameters and click Next.b. Select Label: Select the Label to use.c. Select the Variables...: Notice that the category panels are dynamically named

per the definition of categories you defined in the target label you created. Open each category then select which parameters (properties) you want to use, and select the variable to generate for that value (creating new variables if needed).

d. Click Next and then Finish to save the changes.

Using Live Capture with Avid WorkflowsCreating a Capture-to-Interplay-with-Metadata Workflow

164


3. Connect a Flip action to the (last) Populate action and configure it:

a. For the Encoder, select Interplay Advanced Encoder and configure it per your transcoding requirements.

b. Select the Interplay Sing-Res container and configure the Web Service Settings, Interplay Settings (to identify your Interplay system), and Physical File Settings. The settings are specific to your Avid system. For information on these settings, see the Avid Integration Guide on the Telestream web site.

c. In the container, open the Asset Attributes panel and bind the Master and Source MOB ID settings to the variables passed in from the Populate action.

d. Open the Metadata panel and check Set User Properties. Note that the parameters listed are dynamically populated per your target label.

e. For each item, bind the Value to the variable you assigned to the same parameter in the Populate action.

f. Save your changes.g. Configure the workflow to operate in Open Workflows mode. Right-click each

action and select Workflow Mode > Open.

4. Activate the workflow.

http://www.telestream.net/pdfs/app-notes/app-Avid-Integration-Guide.pdf

Using Live Capture with Avid WorkflowsCreating a Dynamic-Metadata-Update Workflow

165


Creating a Dynamic-Metadata-Update WorkflowYou use a Dynamic-Metadata-Update workflow to process the metadata delivered from the Capture Web app. Dynamically update metadata as an asset is being written into the Avid Interplay system. The Update Metadata workflow is executed when you update the metadata in the Web app’s Status dialog.

Follow these steps to create this workflow:

1. Create a new workflow and name it with the same name identified in the Capture action in the Capture-to-Interplay-with-Metadata workflow, previously.

2. Start with a Receive action (so that jobs of this workflow can be triggered by another workflow), open the inspector and configure it as follows:a. In the Labels menu, check the same label(s) specified in the Capture action of

the Capture-to-Interplay-with-Metadata workflow.b. Save your changes. c. Right-click on the Receive action and select Add Variables from the menu.

d. Click the Add Variables icon then select (or add, if necessary) the Avid Master Mob ID, so that the workflow can advise Interplay which media to update with the associated metadata.

3. Add a Populate action (or a series of Populate actions) to the Receive action. Configure each Populate action (one for each label) to convert the label data to

Using Live Capture with Avid WorkflowsCreating a Dynamic-Metadata-Update Workflow

166


variables just as you configured the Populate action in the Capture-to-Interplay-with-Metadata workflow.a. Select Variables from Label Parameters, then click Next.b. Select the Label to use, then select the variables to generate for that label. c. Click Next and then Finish to save the changes.

4. Add a Notify action and connect it to the (last) Populate action. 5. Open the configuration dialog, select Interplay Notifier and click Next.6. , Enter your Interplay Web Service credentials and click Next. 7. From the Select the Interplay operation menu choose Add metadata to clip. 8. Enter the ASF Workgroup, then bind the Master MOB ID variable specified earlier in

the Receive action to the Master MOB ID control.a. Open the Metadata panel and check Set User Properties. Note that the

parameters listed are dynamically populated per your target label.b. For each item, bind the Value to the variable you assigned to the same parameter

in the Populate action.

Note: See the Avid Integration Guide Set User Properties option in the Metadata Configuration Panel topic for more information on the settings to use and how to bind the variables.

9. Click Next then Finish to save changes.

10. Activate the workflow.

http://www.telestream.net/pdfs/app-notes/app-Avid-Integration-Guide.pdf

167

Using the Live Capture Web Application

This chapter describes the Lightspeed Live Capture web application, how to access it and how to use it.

This chapter covers the following topics:

■ Prerequisites to Using Live Capture

■ Accessing the Lightspeed Live Capture Web App

■ Lightspeed Live Capture Web App Overview

■ Live Capture Controls and Operation Status

■ Triggers Determine the Method of Channel Control

■ Recorded File Location and Format

■ Using the Vantage Job Status Views

Note: Only the Chrome browser (version 50 or greater) is supported for the Lightspeed Live Capture web application.

Using the Live Capture Web ApplicationPrerequisites to Using Live Capture

168


Prerequisites to Using Live CaptureTo use the Live Capture web application, some components must be set up before you can begin configuring and using the Live Capture web application. See Configuring Settings for Your Facility and Configuring Ingest Sources for instructions.

After the prerequisites, you will need to create the Capture workflows. See Creating, Configuring, and Activating Capture Workflows.

To install the Live Capture web application, see Installing the Live Capture & Tape Capture Web Apps.

For additional details, open the Help menu (?) from the upper right corner of the applications, or the circled (M) in action inspectors.

Using the Live Capture Web ApplicationAccessing the Lightspeed Live Capture Web App

169


Accessing the Lightspeed Live Capture Web AppOnly the Chrome browser (version 76.0.3809.100 or greater) is supported to work with the Lightspeed Live Capture web application. Follow these steps to log into the app:

1. Access the locally installed Live Capture web application using this URL for the Vantage Web Applications menu home page:

http://localhost/Vantage/

If you are accessing the Live Capture web app remotely, replace “localhost” with the DNS server name or IP address:

http://<ServerName>/Vantage/

2. If log in is requested, enter your assigned Vantage user name and password. the default user name is Administrator with no password.

Note: If you do not have an authorized user name, contact your Vantage domain administrator.

3. Click the green Live Capture title from among the listed web applications.

For more details on using and configuring Vantage web applications see the Vantage User’s Guide. This guide is available from the User Guide link in the Job Status Views web application.

Creating and Using External LinksExternal Links provides access to a convenient bookmarks page where frequently used Internet links can be stored. Use the Vantage Management Console to create and manage External Links.

Open the Live Capture application

Access the External Links Page

http://www.telestream.net/telestream-support/vantage/help.htm

http://www.telestream.net/telestream-support/vantage/help.htm

Using the Live Capture Web ApplicationAccessing the Lightspeed Live Capture Web App

170


To create External Links, open the Vantage Management Console on the Lightspeed Live server and choose Settings & Options in the left panel then select the Dashboard Links tab. For more information see “Creating Dashboard Links” in the Domain Management Guide, which can be accessed by clicking the “?” in the upper right of the Vantage Management Console interface.

Create a Separate Account for Each UserMultiple users accessing the Lightspeed Live Capture web application should each have their own unique account, and not use the administrator login credentials. This allows the administrator to provide appropriate access parameters for each user, and helps improve system efficiency by keeping resource usage lower. User accounts are created and managed in the Vantage Management Console.

Multiple User Access to the Capture or Tape Web AppsWhen a user is logged into the Capture or Tape web application they are consuming communication resource cycles, particularly while viewing multiple channels. When viewed, each channel connects a thumbnail and preview stream to that instance of the web application. Multiple users connected to the web application can degrade its performance. Therefore, care must be taken to insure that the Live Capture web application does not consume resources unnecessarily when it is not being used.

Close Instances of the Web Application when Not in Use It is important for each user to close their instance of the Live Capture web application when it is not being used. Keeping multiple web applications open can cause performance issues.

Changing the Target DomainIf you have changed your server's hostname, you should verify that the Lightspeed Live Capture web application is using the new domain. The current domain name displays after Vantage Domain: at the right of the Title panel in the Vantage Web app menu:

If it is not connected to the correct domain, change the domain with these steps:

1. Click on Change Domain in the Title panel.

2. Click OK to log out,

3. Click Search in the dialog that appears,

4. Select the correct domain, and click OK.

5. Enter the user name and password to log into the target domain.

You can also change the domain from the Live Capture web app title panel. See Title Panel.

Using the Live Capture Web ApplicationLightspeed Live Capture Web App Overview

171


Lightspeed Live Capture Web App OverviewThese are some key features of the Lightspeed Live Capture web application:

• Select Live Capture channels and channel groups

• View information, images of the content, and status about each capture channel

• Control the operation of each Manual or Recurring Segment trigger channel

Note: A user must have appropriate permissions for full access to all features.

The Live Capture web application is presented in four panels:

Title Panel—Displays the home button, Vantage domain and user name, controls to change domains, access the About menu, and to log out or log in.

Selection Panel—Select Channel Group, Channels, or show the Job Status view.

Channel Previews Panel—Provides channel previews and controls.

Display and Information Panel—Displays the selected channel video, shows audio level (8 stereo), and provides channel information.

What is a Channel?One Channel card is displayed for each Capture action in an activated workflow. Information, settings, and options are presented that are specified in each workflow.

Channel Previews Display & InfoSelection Panel Title Panel UserLogout

ChangeDomain

About Menu

Using the Live Capture Web ApplicationLive Capture Controls and Operation Status

172


Live Capture Controls and Operation StatusThe Lightspeed Live Capture web application provides controls, content previews, and status information for live capture functionality.

Title PanelThe Title panel at the top of the application provides these options:

Selection PanelThe Selection panel at the far left of the application enables selection of Channel Groups, Status view, and Channels.

Channel Groups—Click Channel Groups to select from a drop-down list of available groups. This is the first selection you must make. See Configuring a Channel Group Nexus to create the Channel Groups.

Status—Click Status to open the Job Status panel, which shows the status and jobs of all active workflows contained in the selected channel group.

Channels—Click Channels to display the Channel Previews and Display panels.

Home—Click to open the Vantage web applications menu.

User Name—Displays the current user name. Click and select Log Out if you want to log out and log in as a different user.

Vantage Domain—Displays the current Vantage domain. Click and select Change Domain to open the dialog to select a different Vantage domain.

About menu—Click to open the About menu and access the User Guide (this document), application information, and support information. A Preferences selection allows you to choose if you want a safety prompt before stopping recording.


173


Channel Previews PanelWhen the Channels option is selected, the Channel Previews panel displays a thumbnail of video from each of the available workflow channel cards.

• The selected channel card, indicated by blue bars on the top and bottom of the channel card, plays in the Display and Information panel to the right.

• Selections and menus along the top control channel ganging (triggering multiple records at once but not necessarily on all channels), channel filtering, and recording settings.

• Each channel shows a channel name and displays a thumbnail of incoming video.

• Each channel shows a gray trigger type, a yellow gang/ungang button, a red and green Recording or Ready (Stopped) bar, and a yellow queued job bar.

• A vertical ellipsis button provides access to menus for each channel.

• The bottom right corner includes red Record and Record Options buttons for one-button recording and easy access to recording settings.

Channel Previews panel controls are described in detail in the following topics:

■ Channel Previews Controls

■ Configuring the Custom Ganged Recording Defaults

■ Channel Controls

■ Channel Options

■ Channel Recording Information

■ Display and Information Panel

■ Loss of Signal Behavior

■ Limited Bandwidth Behavior


174


Channel Previews Controls

Record All—Select Record All to record the currently ganged channels. Record All operates in two different modes depending on whether Time-Shift has been enabled in the workflow. (See the Capture action help topic for details about Time-Shift.)

• When Time-Shift is NOT enabled in the workflow, all channels start recording immediately with no attempt to synchronize the start timecode.

• When Time-Shift has been enabled in the workflow, the system attempts to syn-chronize all of the selected channels to the exact same start timecode before start-ing the recording. When recording starts, some portion of the frames in the Time-Shift buffer are added to the start of the recorded file (going back in time to included frames from the past). As a rule, add 10 seconds of Time-Shift for each ganged channel. For example, in a Live Capture system consisting of three servers capturing 12 channels (4 per server) each channel should be given 40 seconds of Time-Shift (4 channels X 10 seconds per channel = 40 seconds).

• Note that all ganged channels must use the same timecode source in order to be synchronized to the exact same frame during the gang recording operation.


175


Stop All—Select Stop All to immediately stop recording all ganged manual channels in the channel group that have not been filtered out.

Gang Record menu—Select Gang Record to open a dialog in which you can control ganged recording. Ganged recording allows you to trigger recording on multiple channels simultaneously without necessarily triggering all channels. Using this menu, you can turn ganging on or off for all channels (Gang All/Ungang All), start/stop gang recording (Record Ganged), and set up customized gang recording to specify which channels are ganged (Record Ganged Custom). See Record All above for details about how Time-Shift affects Gang Record.

Sort—Sort channel cards by Name, Source, or Trigger. You can also drag and drop channels.

Filter—Filter by typing portions of the workflow name to see only the channels that contain the typed characters. Use * as a wildcard character.

Global Metadata menu—Contains standard Variables and Custom Defaults.

Select Set Variables to set common variables for all channels. For example if you set a bound variable in Set Variables, the value for that variable is used in every recorded channel it is associated with, except when explicitly set in a workflow's Variable dialog.

Select Set Custom Defaults to specify a default base name for all channel files, and default global primary and secondary output locations.

Values entered and saved in the Global Metadata menu are persisted in memory as long as the browser remains open. If no persisted value is present (for example, a new variable is assigned to a workflow that has just been activated), the default value configured in the Vantage Management Console is used.

Note: Variable and Label data entered while a channel is in the Waiting state are applied to a job at the time the job is queued for recording. Variable and Label data entered while a job is in a Recording or Pending state is applied to the next job queued.


176


Configuring the Custom Ganged Recording DefaultsWhen you select Record Ganged - Custom, a dialog opens to select which channels to include in the record operation and the settings to use for all channels.

Channel Name(s)—For each Manual Trigger or Recurring Segment Trigger, displays the name of the workflow channel and the name of the input for that channel. The channels that are checked are included in the record operation.

Primary Output Location—Select a Vantage folder address book entry for the destination of the primary output, or use the default location specified in the Capture action workflow.

Secondary Output Location—Select a Vantage folder address book entry for the destination of the secondary output, or use the default location specified in the Capture action workflow. The secondary output must be enabled in the Capture action for each channel included in the record operation for this to be active.

Base Name—Type a name for the Base Name token. This name appears in the job name and is only used in the output media filename pattern when the Base Name token is added in the Filename Pattern Editor in the Capture action for this channel. The Base Name entered are applied to all channels selected for recording. To add the Base Name token, see Configuring Primary and Secondary Outputs.


177


Timed Recording—Enable Timed Recording so you can set start, stop, and duration times and options. Timed Recording is not active for channels with Recurring Segment triggers.

• Start (Timecode)—If all selected channels have a common timecode, the values of Start are automatically entered. You may enter any desired timecode.

Setting a Start Timecode to a value that is less than 60 seconds in the past will result in a recording starting immediately. For example, if the current timecode is 02:30:00;20 and a start timecode of 02:30:00;18 is used in the job, recording will begin immediately at the current timecode of 02:30:00;20.

Setting a Start Timecode to a value that is more than 60 seconds in the past will result in an job to be schedule for recorded in 24 hours. For example, if the current timecode is 02:30:00;20 and a start timecode of 02:29:00;18 is used in the job, recording will begin at 02:29:00;18 the next day (nearly 24 hours later).

• Stop (Timecode)—Enter the desired Stop timecode.

• Duration—When you enter a Start and Stop timecode, the resulting duration is automatically displayed. When Record Duration (see below) is enabled, the dura-tion entered here is used.

• Record Duration—When the Record Duration option is enabled, capture record-ing ignores the Stop timecode and will stop when the Duration entered is reached. When not enabled, the recording will stop when the Stop timecode is reached, and the Mark-OUT frame is not included in the captured file.

• Ignore Discontinuity—When Ignore Discontinuity is enabled, recording ignores any timecode discontinuity if they are detected. When not enabled, recording will stop when a timecode discontinuity is detected.

See Timecode Break Recording and Timecode Discontinuity Definition in the Using the Tape Capture Web Application chapter for discontinuity details.


178


Channel Controls The Channel control panels provide information and controls for each channel that has an active workflow.

Trigger Type—Indicates the Trigger assigned to the channel:

Icon Trigger Type

Manual Trigger

DAI (Dynamic Ad Insertion) Trigger

Schedule Trigger

Web Service Trigger

Recurring Segment Trigger

Trigger Type

Thumbnail

Timecode

Current State

Channel Options: Labels, Variables, Recordings

Record, Open Record Options, or Stop

Gang Record On/Off

Queued Job Information


179


Trigger TypeName—Shows the source name.

Thumbnail—Displays a still image of the channel input, updating about once every 3-5 seconds (depending on server usage load).

Timecode—Displays the current channel timecode.

Gang Recording—Toggles gang recording for the channel. Yellow indicates ON, and gray is OFF. Channels configured with a Trigger type of Manual, Recurring Segment, or Web Service (when Manual Override is enabled) can be added to a record gang.

Current State—Indicates the current channel recording state by color and message:

• Green—Indicates the channel is ready to record, with a message of Ready (Manual, Recurring Segment, and DAI), Listening... (Web Service), or Awaiting... (Schedule).

• Yellow—In a transition state and preparing to record or stop.

• Red—Recording is occurring. The elapsed duration of the recording is displayed. A blue progress bar indicates the current recording progress.

Channel Options—Opens the Channel Options menu. See Channel Options.

Queued Job Information—The number displayed indicates how many jobs are queued to start. Click to open the Recordings dialog, which displays information about the current, queued, and previous recordings. See Channel Recording Information.

Record/Stop—Click Record to immediately start recording for the channel. When recording, click Stop to end recording.

Record Options—Click Record Options to open the Record options dialog for the channel. See Configuring the Custom Ganged Recording Defaults.


180


Channel OptionsSelect the icon on a Channel card to open the Channel Options menu.

Labels—When specific Labels have been enabled in the Capture action for the channel, click to open the Configure Labels dialog to adjust Label settings. The contents of labels depends on the metadata labels you created in the Vantage Management Console and enabled in the Capture action. Labels can be used in downstream Vantage actions or transformed into text or XML for out-of-band delivery. To add labels to the Capture action, see Expected Labels.

Note: If a label’s parameters are changed or modified in the Vantage Management Console, the changes must be applied to the workflow’s Capture action before they will display in the Live Capture web app. To apply the updates to a Label you must: 1. Put the workflow into edit mode and open the Capture action configuration panel 2. In the Expected Labels control, disable the target label(s); then re-enable them. 3. Save the action and reactivate the workflow. The updated label(s) will now display the correct information in the Live Capture app.

Note: Variable and Label data entered while a channel is in the Waiting state are applied to a job at the time the job is queued for recording. Variable and Label data entered while a job is in a Recording or Pending state are applied to the next job queued.


181


Variables—Configuration parameters bound to Variables during Capture action setup or via the Add Variables context menu in the Capture action are displayed in the Customize Parameters dialog. You can turn selected Variables on or off, enter configuration variables or adjust specific settings.

Any variable values entered and saved in the dialog are persisted in memory as long as the browser remains open. If no persisted value is present (for example, a new variable is assigned to a workflow that has just been activated), the default value configured in the Vantage Management Console is used.

Note: All configuration variable values are passed to downstream workflow actions where they can be analyzed or used in your entire workflow.

Recordings—Opens the Recordings dialog that displays information about the current, queued, and previous recordings. See Channel Recording Information following.


182


Channel Recording InformationThe Recordings dialog for each channel provides information about completed, queued, or in-process recordings, and provides the ability to copy the output path to your clipboard.

Note: Status details for any workflow can also be found in the Job Status View tab. See Using the Vantage Job Status Views.

Note: If you use multiple Capture actions in a single workflow and each action is actively recording, inaccurate state information is displayed reported for the workflow Status in the thumbnail card and Status Panel. For best practices, use only one Capture action per workflow.

Recordings Dialog Icons—Indicates the state of each channel recording:

Name—Displays the job name. The name varies for different trigger types and can include information such as Base Name, workflow name, or capture start time entries.

Duration—The duration that was specified to record, or the final duration. The Start and Stop timecode may also be displayed.

Icon Recording State

Successfully completed recording.

In a transition state, either queued for or stopping recording.

Recording is occurring.

Recording was not successful. Check the Job Status View for details of failed jobs. See Using the Vantage Job Status Views.


183


Primary Output—The primary output file name and location path. Click the icon to copy the output path to your clipboard. You can paste the copied path into your Windows File Explorer, then log into the Lightspeed Live server to open the file with an appropriate application.

Secondary Output—The secondary output file name and location path. Click the icon to copy the output path to your clipboard.

Customization—Custom defaults that apply to the channel.

Display and Information PanelThe Display and Information panel plays video and audio from the currently selected channel and provides channel status and information.

Timecode

Primary Output

Preview Display

Secondary Output

Vantage Domainand Input

Audio Metersand Controls

Workflow Name

Video/Audio Details

Source file selections


184


Workflow Name—Displays the channel workflow name.

Current State—Indicates the current recording state of the channel. Shows the elapsed time and the scheduled duration. A blue progress bar indicates the duration of the recording that has completed.

Primary and Secondary Filename Pattern and Output Location—Displays the location where the output file is saved and shows the filename pattern set for the channel.

Vantage Domain and Input—Displays the Vantage Domain and the input name.

Preview Display—Displays the content of the selected channel.

Source File Selections—Lists source file selections added to the media.

Audio Meters and Controls—Displays audio levels for all audio channels. The Preview Display can play just one channel pair at a time. Toggle a channel pair on to hear the audio for that pair. A level display bar shows variations in the audio level with green, yellow, and red indications and a decibel scale. Includes up to eight (8) audio pairs.

Timecode—Displays the current timecode.

Video/Audio Details—Displays video resolution, frame rate, bit depth, number of audio channels, and whether captions are present.

Icon Current State

Ready for recording to be initiated

In a transition state, either queued up to record or stopping recording

Recording is occurring


185


Loss of Signal BehaviorIf LOS is detected on an input at start-up and that state continues and does not change, then:

The thumbnail and preview will show the LOS Video Test Pattern with LOS overlay indicating that the input channel is currently in an LOS state. The input will have a defaulted, un-configurable, frame rate and resolution. Starting a Capture recording when the input is in this state will result in a job failure with a LOS error.

If LOS occurs after the input had good active video and channels associated with this input are not currently recording, then:

If Freeze on LOS is enabled the thumbnail and preview will show the last frame of good video; otherwise, if Freeze on LOS is disabled the thumbnail and preview will show the LOS Video Test Pattern. In either case the thumbnail and preview display an LOS overlay. The frame rate and resolution of the input is that of the previous active video. Starting a Capture recording when the input is in this state results in an immediate job failure with an LOS error.

If LOS occurs after the input had good active video and channels associated with this input are currently recording, then:

If Freeze on LOS is enabled the thumbnail and preview will show the last frame of good video; otherwise, if Freeze on LOS is disabled, the thumbnail and preview will show the LOS Video Test Pattern. In either case the thumbnail and preview display an LOS overlay. The frame rate and resolution of the input is that of the previous active video.

• Jobs that are recording with the Ignore Lost Frames option disabled will stop immediately. If the system is so configured, a new recording will start when the sig-nal is regained.

• Jobs that are recording with the Ignore Lost Frames option enabled will continue capturing for their scheduled duration, and will contain the frozen frame/color bar frame or active video if it returns.


186


Limited Bandwidth BehaviorIf more than 1 second of preview data is buffered, a message displays stating that the available resources are limited and audio is turned off in order to play video in the preview: Preview is degraded due to resource limitations. See User Guide for details. Likely causes of the problem include network bandwidth or CPU/GPU over-saturation. Taking actions to reduce the load on the network and processors may resolve the issue.

Channel Status PanelWhen you select Status in the left panel, the Channel Status panel displays the current state of each channel in the current Channel Group, including current recording job status, and the previous job history. See the descriptions below for display details and Channel Recording Information for Recordings panel details.

Channels—The status display left column lists the channels in the channel group. Both the name of the channel and its description are shown. The trigger type appears beside the name.

Jobs—The status display middle column shows the current (pending or in-progress) job for each channel. The job's name, scheduled duration, and current progress counter are displayed.

Labels—The Labels icon opens the Labels dialog, which shows labels and associated values generated by the channel workflow.

Variables—The Variables icon opens the Variables dialog, which shows variables and associated values used by the channel workflow.

Captured Files—Primary and Secondary file outputs are listed. To quickly access captured files you can click the file name and path in the right-most column. The Captured Files dialog opens. Click the icon to copy a file output path to your clipboard. You can paste the copied path into your Windows File Explorer, then log into the Lightspeed Live server to open the file with an appropriate application.

Channels Jobs FilesLabels/Vars Change Domain

FiltersUserRecordings


187


Filtering Job Status Channels—Select to filter the channel list by typing a portion of the

channel name to see only the channels that contain the typed characters.

Jobs—Select to filter by typing portions of the job name to see only the jobs in each channel that contain the typed characters. You can also select sorting options for additional refinements.

Click X to clear the settings

Using the Live Capture Web ApplicationTriggers Determine the Method of Channel Control

188


Triggers Determine the Method of Channel ControlThe Trigger that is set in the Capture action workflow for each channel determines the method by which channel recording is controlled. For information about selecting triggers and setting options, see Configuring Trigger Settings in the Workflows chapter.

The following triggers are explained in this topic.

■ DAI Trigger

■ Manual Trigger

■ Recurring Segment Trigger

■ Schedule Trigger

■ Web Service Trigger

DAI TriggerThe DAI (Dynamic Ad Insertion) trigger enables automatic recording to start and stop based on incoming SCTE-104 markers contained in the VANC data stream of the workflow’s SDI input. Recording begins when a Start Program marker is detected and stops when an associated Stop Program marker with an Event ID that matches the Start Program’s ID is detected. Channels set to DAI trigger are presented in a read-only status unless Allow manual stop is checked in the Capture action to expose a manual stop button in the web app.

The following steps explain how to set up an example DAI trigger. Steps shown here may vary according to your needs:

1. Create a Capture workflow that uses a DAI trigger.


189


2. Load the rules XML file (example shown below) into the DAI configuration (using Select Rules File) and make other DAI configuration selections. The file must include program start and end triggers and the UPID (identifier) of an ad to insert.

3. Use the Vantage Management Console > Variables panel to create a variable to extract the UPID value from the program triggers in the rules. (Using the UPID to populate a variable is optional.)

4. Use the variable in the Filename editor to capture the UPID value as part of the output base file name. (Using the UPID to populate the filename from a variable is optional.)

When the workflow operates correctly, the SCTE triggers in the source create a new job at the expected frame, the job stops at the expected frame, and the name of the inserted file matches the associated segmentation UPID.

The following partial example illustrates a typical rules XML file:<?xml version="1.0" encoding="utf-8"?><triggers><rule><description>Default Start - Program Start</description><captureaction>Start</captureaction><ignoreeventids/><extracttovariable variablename="segmentation_upid_name">segmentation_upid</extracttovariable>

<scte104><multiple_operation_message><time_signal_request_data><pre-roll_time>0</pre-roll_time>

</time_signal_request_data><insert_segmentation_descriptor_request_data><segmentation_type_id>16</segmentation_type_id>

</insert_segmentation_descriptor_request_data></multiple_operation_message>

</scte104></rule><rule><description>Default Stop - Program End</description><captureaction>Stop</captureaction><ignoreeventids/><scte104><multiple_operation_message><time_signal_request_data><pre-roll_time>0</pre-roll_time>

</time_signal_request_data><insert_segmentation_descriptor_request_data><segmentation_type_id>17</segmentation_type_id>

</insert_segmentation_descriptor_request_data></multiple_operation_message>

</scte104>


190


</rule></triggers>

Note: SCTE-104 rules files can be complex. It is best to contact your Telestream Sales Engineer for details on configuring them correctly.

See Configuring Trigger Settings in the Capture Workflows chapter for specific DAI Trigger settings and details. You can also get help from Telestream Support in putting together workflows to enable DAI triggers. See Appendix A: Support for contact information.

Manual TriggerThe Manual start trigger enables you to control channel start and stop operation in the Live Capture web app. Click Record to open the Record dialog so you can select settings for the record operation. You can also select the Record All option in the top bar of the Channel Previews panel to start the record operation for multiple channels.

See Configuring the Custom Ganged Recording Defaults for descriptions of the Record dialog options.

https://www.telestream.net/telestream-support/lightspeed-live/support.htm

www.telestream.net/telestream-support/lightspeed-live/support.htm


191


Recurring Segment TriggerThe Recurring Segment trigger enables you to capture files of the duration specified in the Capture action workflow. The available durations are a 5 minutes (default), 10, 15, 20, or 30 minutes, or 1 hour. The Recurring Segment trigger record start is controlled in the Live Capture web app, unless Begin recording on workflow activation is selected, in which case, the recording starts as soon as you activate the workflow.

The first and last segments captured could be a shorter time than the specified duration, depending on when the recording start and stop commands are initiated. The captured files are frame accurate, so the files can be played continuously from one to the next with no dropped or added frames.

When capturing recurring segments, Capture attempts to start a new segment at the exact start of a minute. The job name reflects this with a naming convention record-HH:MM:SS:00. If it is not possible to record a full-length segment, the name reflects the estimate of the time required, and the delineation for seconds is omitted from the name: record-HH:MM:SS.

The Timed Recording option does not apply to recurring segments. See Configuring the Custom Ganged Recording Defaults for descriptions of the Record dialog options.


192


Schedule TriggerThe Schedule trigger enables you to record based on events in a CalDAV-compatible calendar, such as Google. Channels set to Schedule trigger are presented in a read-only status view in the Live Capture web app. For configuration instructions see Schedule Trigger in the Creating Capture and Tape Workflows chapter.

Web Service TriggerSelect Web Service to trigger live video capture using commands from the Lightspeed Live Capture Web API. You can queue up a maximum of 16 Web Service Trigger jobs per Live Capture host server at any one time. Channels set to Web Service trigger with Allow Manual Control disabled are presented in a read-only status view in the Live Capture web app. If Allow Manual Control is enabled, manual controls and web service data is present on the channel’s thumbnail card, allowing for full manual control (see Channel Controls for additional details).

For more information see Web Service Trigger in the Creating Capture and Tape Workflows chapter.

The Lightspeed Live Web API Reference document is available on the Telestream website: Lightspeed Live Capture Web API Reference.

http://www.telestream.net/pdfs/user-guides/Lightspeed-UserGuides/Live-Capture-API-Reference.pdf

Using the Live Capture Web ApplicationRecorded File Location and Format

193


Recorded File Location and FormatWhen recording is active, captures are written to the Live Store, or the path specified in the Live Capture action under Output Location in the Primary Output or Secondary Output. To set the output locations see Configuring Primary and Secondary Outputs.

To access the recorded files from the Live Capture web app, see Channel Recording Information and Captured Files under the Channel Status Panel heading in this chapter.

Selecting Output Encoders and FormatThe Primary Output and Secondary Output in the Capture action enable you to select the container format and the video and audio encoders to use for the captured output. See Configuring Primary and Secondary Outputs for more information.

Deleting Captured FilesIt is important to configure the Live Store correctly to ensure captured files are deleted when jobs are deleted or expired. Otherwise, obsolete recordings build up in the Live Store, possibly filling up storage unnecessarily. For details about Live Store configuration, see When to Specify a UNC Path for Live Stores in the Configuring the Lightspeed Live Capture Server and Apps.

Using the Live Capture Web ApplicationUsing the Vantage Job Status Views

194


Using the Vantage Job Status ViewsJob Status Views for Vantage is a web application that enables basic Vantage job management via a web browser. You can use Job Status Views to access job information and manage jobs in your Vantage or Live Capture domain from anywhere on the LAN, or via the Internet if you provide such access to your Vantage domain.

You can use the Job Status Views web application to do the following:

• Display information about submitted jobs, including any errors that have occurred

• Sort and filter job entries

• Highlight and identify jobs in different states

• Troubleshoot job processing issues and view error messages.

The views that you see in Job Status Views are defined by Vantage administrators, who control which job information displays and which job control functions (such as the ability to delete a job) are allowed. Views may be public or private and are configured in the Vantage Management Console. Public views are available to everyone, and private views are for use by specified Vantage users. See Configuring Settings for Your Facility.

Opening Vantage Job Status ViewsTo open Job Status Views for Vantage or Live Capture, first click the Home button in the title panel to access the Vantage Web Applications home page.

On the Vantage Web Applications home page, click Job Status Views, as shown below.

Click the Home button to access the Vantage home page


195


The Vantage Job Status Views Web ApplicationThe following shows an example of information provided in the Job Status Views web application, this example is set to display All Workflows.

Open Job Status Views


196


If no job status information is appearing in Job Status Views, you should make sure that this feature has been enabled in the Vantage Management Console. Open the Vantage Management Console and select Application Configurations > Job Status Views. Check the Enable option, shown in the red circle in the image below, then click the Save icon.

Configuring Job Status Views Information The information displayed in Job Status Views, and public or private access permissions, is configured in the Vantage Management Console. For details on customizing the Vantage Job Status Views see the Configuring Job Status Views topic in the Domain Management Guide on the Telestream web site.

http://www.telestream.net/pdfs/user-guides/Vantage-UserGuides/VantageDomainManagement.pdf

197

Using the Tape Capture Web Application

This chapter describes the Lightspeed Tape Capture web application, how to access it and how to use it.

The following topics are included in the chapter:

■ Prerequisites to Using Tape Capture

■ Configuring the VTR Connection

■ Accessing the Lightspeed Tape Capture Web App

■ Tape Capture Overview

■ Tape Capture Controls and Operation Status

■ Using the Tape Capture Web App

■ Using the Job Status View in Tape Capture

Note: Only the Chrome browser (version 50 or greater) is supported for the Lightspeed Tape Capture web application.

Using the Tape Capture Web ApplicationPrerequisites to Using Tape Capture

198


Prerequisites to Using Tape CaptureTo use the Tape Capture web application, you must already have a Lightspeed Live Capture system installed and connected to VTRs or other sources. This system must also include the Lightspeed Tape Capture web app, which allows you to control VTRs, create clips, and capture the clips into corresponding media files. Most VTRs and video sources capable of SDI I/O and RS-422 control can be used.

Some components msut be set up before you can begin configuring and using the Tape Capture web application. For instructions, see Configuring Settings for Your Facility and Configuring Ingest Sources.

To install the Tape Capture web application, see Installing the Live Capture & Tape Capture Web Apps.

After the prerequisites, perform these tasks to complete connections and configurations:

■ Configuring the VTR Connection

■ Creating and Activating a Tape Action Workflow

For additional details, open the Help menu (?) from the upper right corner of the applications, or the circled (M) in action inspectors.

Using the Tape Capture Web ApplicationConfiguring the VTR Connection

199


Configuring the VTR ConnectionTo capture video data from a VTR, the VTR must be properly connected to the Lightspeed Live server and configuration settings set in the Vantage Management Console > Capture Inventory panel to complete the connection.

Follow these steps to configure the VTR connection:

1. Make sure the VTR is properly installed and connected to the Lightspeed Live server. See Appendix B: Containers, Codecs, and Vantage Actions.

2. Power up the VTR and switch it into the proper Remote mode for RS-422 control.

3. Open the Vantage Management Console and select Capture Inventory in the left panel to open the Capture Inventory panel for editing.

4. In the upper panel, select the SDI Input you want to use for the VTR connection. This needs to be the one that matches the terminal number the VTR is connected to on the RS-422 interface box. For example, when connected to Channel 1 (CH1) on the RS-422 interface box you must select SDI Input 1in the Capture Inventory.

5. In the Configuration panel select RS-422 from the TimeCode Source drop-down menu.

6. Click the Save button to save the Capture Inventory changes.

If you have additional VTRs, configure and save each SDI input that has a VTR connected to it.


200


Checking the VTR Connection StatusOnce activated the workflow’s Monitor Status panel should display the status of Initializing: VTR connected, as shown in the following image.

If, instead, the status Initializing: VTR not connected displays, proceed to the following section: Troubleshooting the VTR Connection.

When the VTR connection is successfully initialized, use the Tape Capture web app to set recording parameters and control the VTR to ingest media from tape.

Troubleshooting the VTR ConnectionIf you have an active Tape Capture workflow that is configured as described above, but its Monitor Status displays Initializing: VTR not connected, attempt to solve the problem using these troubleshooting steps:

1. Make sure that the RS-422 interface box is correctly installed, all adapters and cables are properly connected, and the VTR is powered up. See Appendix C: RS-422 VTR Interface for complete instructions.

2. Check that the Source input of the Capture action matches the RS-422 port that the VTR is connected to. For example, when using SDI Input 1 for the Lightspeed Live server in the Capture action you must connect to Channel 1 (CH1) on the RS-422 interface box. See Connecting a VTR to the Lightspeed Live Server in Appendix C for a diagram and details.

3. Check that the RS-422 interface box’s Serial Ports are shown in the server Device Manager. Open the Device Manager and toggle open the “Ports (COM & LPT)” devices. When properly connected, the ports of the RS-422 interface box displays as USB Serial Port (COM3) through USB Serial Port (COM6) as shown in the following image.


201


4. Check the Properties for each USB Serial Port to verify that its Port Settings are set correctly to:

Bits per Second — 9600Data Bits — 8Parity — NoneStop Bits — 1Flow Control — None

5. In Advanced... confirm that Latency Timer (msec) is set to 1. For details on adjusting this setting, see Configuring an RS-422 COM Port's Latency Time in Appendix C.

6. Verify that the SDI Input associated with the VTR has been connected to an SDI video source.

7. If the VTR is not connecting after performing steps 1 through 6, you can try replacing the system cables.

After performing each step above, check the workflow’s Monitor Status panel to see if the Status has changed to Initializing: VTR connected.

When the VTR connection is successfully initialized, use the Tape Capture web app to set recording parameters and control the VTR to ingest media from tape.

Using the Tape Capture Web ApplicationAccessing the Lightspeed Tape Capture Web App

202


Accessing the Lightspeed Tape Capture Web AppOnly the Chrome browser (version 70 or greater) is supported to work with the Lightspeed Tape Capture web application. Follow these steps to log into the app:

1. Access the locally installed Tape Capture web application using this URL for the Vantage Web Applications menu:

http://localhost/Vantage/

If you are accessing the Tape Capture web app remotely, replace “localhost” with the DNS server name or IP address.

2. If log in is requested, enter your assigned Vantage user name and password. the default user name is Administrator with no password.

Note: If you do not have an authorized user name, contact your Vantage domain administrator.

3. Click the green Tape Capture title from among the listed web applications.

The Tape Capture browser interface, shown on the following page, opens and is ready to use.

Changing the DomainIf you have changed your server's hostname, when accessing the Tape Capture web application you should verify that it is using the new domain. You can see the current domain name after Vantage Domain: on the right of the Title panel in the Vantage Web app menu.

Open the Tape Capture application

Using the Tape Capture Web ApplicationAccessing the Lightspeed Tape Capture Web App

203


If not using the correct domain, you can change the domain by clicking on Change Domain in the web apps title panel. Click OK to log out, then click Search in the dialog that appears, select the correct domain, and click OK. Enter the user name and password to log into the selected domain.

Using the Tape Capture Web ApplicationTape Capture Overview

204


Tape Capture OverviewThese are some of the key features of the Lightspeed Tape Capture web application:

• Supports complete tape log and capture functionality in an HTML 5 browser client.

• Allows logging multiple tapes and marking clips to be extracted from tape.

• Captures clips from tapes into output media files with selectable container/codec.

• Supports metadata labels and variables.

• Includes full VTR transport controls with standard keyboard shortcuts.

• Includes audio meters with 8 selectable stereo pairs.

• Allows full user account controls for administrator and general users.

• Provides source input locking to prevent users from competing for the same source.

Note: A user must have appropriate permissions for full access to all tape sources.

The Tape Capture web application is presented in four vertical panels:

Title Panel—Displays the home button, Vantage domain and user name, controls to change domains, access the About menu, and to log out or log in.

Selection Panel—Select Channel Group and Workflows or shows Status View.

Workflow/Status Panel—Shows workflows (if selected) or job status (if selected).

Log Panel—Shows and controls tapes, clips, and media.

Preview Player Panel—Plays video, displays audio (8 stereo), provides VTR controls.

Log Panel Preview PlayerSelection Panel Workflow/StatusUser

DomainAbout Title Panel

Using the Tape Capture Web ApplicationTape Capture Controls and Operation Status

205


Tape Capture Controls and Operation StatusThe Lightspeed Tape Capture web application provides controls, options, and status information for tape log and capture functionality.

Selection PanelThe Selection panel at the far left of the display permits selections of Channel Groups, the Status View, and Workflows.

Channel Groups—Click the Channel Groups button to select from a drop-down list of available groups. This is the first selection you must make.

Status—Click Status to open a job status view panel, which shows clips that have been created.

Workflows—Click the Workflows button to display the Workflows column with a list of activated workflows in the selected Channel Group. Click a workflow in the list to select it and display its details. The selected workflow, which contains a configured Tape action, determines which tape deck source is available for capture.

Workflow/Status PanelWhen the Workflows button is selected in the left column, this panel displays a list of available workflows. Select the workflow you want to use for viewing sources, marking clips, and creating media. The selected workflow displays details about its configuration.

When you select the Status button, this panel provides a job status display.


206


Log PanelThe Log Panel displays the selected tape source and allows adding new tapes, controls the current clip to be extracted from tape, logs clip to a list when you press the Log button, and captures clips in the Clip Log to media files when you press Capture.

To begin using the Log Panel, use the default tape or add a tape and select it in the Tapes list, use the Preview Player and the current clip in the Clip Log to mark in and mark out the clip start and end points, and click Log to enter the clip into the log. Repeat as required, and when ready to capture the clips to media files, click Capture. See below for control details.

Note: To close dialogs, you can use the mouse, or you can press Enter to confirm or Esc to cancel. When editing timecode, click on a pair of digits to edit them. Use Tab to move between digits. Pressing Enter brings the focus back to the entire timecode and retains changes. Esc exits timecode edits without saving changes.

Workflow Name—The top left corner displays the selected workflow name. To change this, change the workflow selected in the Workflow panel.

For details about the Stitch, Gear, and Capture controls, see Capturing Clips.


207


Clip PanelClip Name—Place the cursor in this field and enter a clip name.

Use Current Preview Frame—Click to use the preview frame as the thumbnail.

Remove Thumbnail—Click to remove the thumbnail image from the display.

Mark In—Click the left arrow and bar button (|<) to update the Mark In point to the tape’s current timecode position, or manually enter the timecode. Click the right arrow button (->) to cue the machine to the previously set mark in point.

Mark Out—Click the right arrow and bar button (>|) to update the Mark Out point to the tape’s current timecode position, or manually enter the timecode. Click the right arrow button (->) to cue the machine to the previously set mark out point.

Duration—The duration is calculated as the out time minus the in time. Enter a new duration in the timecode fields to change the duration. The out timecode changes to match and the in timecode remains the same.

When entering timecode in the In, Out, or Duration fields, when you click on a pair of numbers, you can use the tab key to advance to the next pair of numbers in the timecode.

The lock feature still allows manual editing when locked (blue lock) but prevents the duration from changing automatically (as explained below).

Click to disengage the lock and allow duration changes. Entering a new in timecode changes the duration timecode but leaves the out timecode unchanged. Conversely, entering a new out timecode changes the duration timecode but leaves the in timecode unchanged.

Click again to engage the lock to protect the duration. Duration always stays the same unless entered manually. If you change the in timecode, the out timecode adjusts to match the new in time and the locked duration. If you change the out timecode, the in timecode adjusts to match the new out timecode and the locked duration.

Duration Lock—Locks or unlocks automatic duration calculation. When locked (lock top closed), duration always remains the same even though in and out times change. When unlocked (lock top open), duration can change automatically with changes to in or out times. Manual duration entries are always allowed whether locked or unlocked.


208


Metadata—Click the metadata button to open the Configure Labels dialog to access and modify metadata contained in any Label added to the Tape action.

The contents of the metadata depends on the metadata labels you created in the Vantage Management Console and added to the Tape action. Labels can be used in downstream Vantage actions or transformed into text or XML for out-of-band delivery. To make labels see Configuring Settings for Your Facility, Step 7. To add labels to the Tape action use the Expected Labels option, see Creating and Activating a Tape Action Workflow.


209


Log Log—The Log button commits the current clip to the Clip Log using the associated Mark in and Mark Out points, Duration, Label metadata, clip name, and thumbnail. Clips are associated with the currently selected Tape name.

EDL File Import and Export Import—The import button imports a CSV clip list that has been previously created and exported to a file. The imported file populates the Clip Log.

Clips can be Imported with a simple CSV EDL file using the following format:

[Tape Name], [Clip Name], [Mark In], [Mark Out]

Example CSV file in EDL (Edit Decision List) format:

Tape 1,Clip 1,00:11:45:00,00:12:13:00

Tape 2,Clip 2,00:14:15:00,00:16:20:00

Export—The export button exports the current Clip Log to a standard CSV clip list file that can be re-imported again later. Exported lists are named [workflowname].csv (using the associated Vantage workflow name) and are exported to the default download folder specified by the Chrome browser. You can see and set the default folder in Chrome > Settings > Advanced Settings > Downloads.


210


Capturing an Entire Tape Capture an entire tape—When selected, enters Mark In and Mark Out timecode

values that instruct the Tape Web app to capture the entire tape from the beginning of the tape to the ending of the tape. A dialog asks you to confirm that you want to capture the whole tape. When you click CAPTURE, the tape is rewound to the beginning and captures the content on the whole tape until EOT (End of Tape) is reached.

Source Display—The bottom of the panel displays the VTR source for the current clips.

Timecode Break RecordingTo set up a timecode break clip capture, which is a process that automatically creates a new recorded clip file when a break in the timecode is detected, insert the tape and make sure the Tape Capture action is configured as described below.

See Timecode Discontinuity Definition below for details about what constitutes a timecode break.

In the Tape action these configuration options control timecode break recording:

If you wish to adjust these configuration options from the Tape Web app, you may bind them to variables so they are available directly from the Tape Web app. If you prefer, you can create new variables and name them so that they make sense to you when you access them in the Tape Web app. Your variables display and can be enabled, disabled, or changed under the gear icon in the Tape Capture Customize Parameters menu.

After you’ve set up your workflow configuration and logged your clips, click Capture to initiate timecode break recording. Another option is to use the Capture Entire Tape feature. See Capturing an Entire Tape above.

Generally tapes configured with timecode breaks have been recorded using time of day timecode. Once activated, the Timecode Break feature creates separate files when it detects a break in the timecode. To accommodate dropped frames when the tape was recorded, use the Frame Threshold parameter.

Note: The following configuration options affect how files are created in a Timecode Break workflow. It is important to understand how each option affects the files that are created. Some experimentation may be necessary to create the results desired.


211


Discontinuity Threshold—Specifies the minimum number of skipped frames that constitutes a discontinuity (timecode break) state. This threshold affects both Create New File on Discontinuity and Abort on Discontinuity, when enabled. Note that decremented and repeated frames always count as timecode discrepancies, and for these discrepancies, the threshold setting is ignored.

Create New File on Discontinuity—When checked and timecode discontinuity is detected, specifies that the current media file is closed and a new media recording file is opened. During an active capture recording, if a discontinuity is encountered, the current capture file completes and a new media file recording immediately starts.

Timecode Discontinuity DefinitionTime code discontinuities are defined as follows:

• Time code increments by a value equal to or greater than the selected Discontinu-ity Threshold value.

• Time code repeats. The Discontinuity Threshold value is ignored in this case.

• Time code decrements. The Discontinuity Threshold value is ignored in this case.

Example 1: A time code incrementing from 00:00:30;10 to 00:00:30;15 would be detected by a threshold of 4 or less.

Example 2: A time code repeating from 00:00:30;10 to 00:00:30;10 would be detected.

Example 3: A time code decrementing from 00:00:30;10 to 00:00:29;00 would be detected.

Ignore Frames When Servo is Not Locked—If enabled, all frames captured while the servo is in the unlocked state (as reported by the VTR) are excluded from the output file.

Create New File When Servo Relocks—If enabled, creates a new media file when the servo re-locks after being in the unlocked state. When a servo relock is encountered during an active capture recording, the current capture file completes and a new media file recording starts.

• If Create New File When Servo Re-locks is enabled and Ignore Frames When Servo is Not Locked is disabled, the system may create unwanted (unlocked) frames at the end of output files.

• If Create New File on Discontinuity is enabled and Ignore Frames When Servo is Not Locked is also enabled, the result may be an output file that contains a discontinu-ous timecode, even though Create New File on Discontinuity is enabled and the timecode was always incrementing. This occurs because of the system ignoring frames, regardless of the timecode, while the servo is unlocked. With this configura-tion, the frames captured during the period when the servo was unlocked are excluded from the output file. New frames would then be added to the file when the servo re-locks, which would cause the output file to have discontinuous time-code. To avoid this scenario, enable the Create New File When Servo Relocks option. In this state the re-lock of the servo starts a new file where the discontinuity in the output file would have been.


212


• As described above, repeating timecodes are counted as discontinuities. Most VTRs repeat timecodes when the servo is unlocked; therefore, if Ignore Frames When Servo is Not Locked is disabled and Create New File on Discontinuity is enabled, the result may be many single frame files while the servo is unlocked. This won’t hap-pen if Ignore Frames When Servo is Not Locked is enabled.

• With many VTRs, particularly an SRW-5800, there may be gray frames after the servo re-locks. Timecode for these frames is often invalid. Because the system is only able to respond to the status the VTR provides, it won’t detect and exclude gray frames.

• No two passes of the same section of tape are likely to be identical. This occurs because the VTR can sometimes take longer than others to lock the servo after the control track is detected. Therefore, it is important to check the logs to verify whether the servo was locked while a specific frame was captured.

• For previous users of Telestream’s Pipeline tape capture product, enabling all three settings above provide the cleanest results and the closest to what Pipeline did.

Abort on Discontinuity—Ends the current recording when timecode discontinuity is detected. Mutually exclusive with Create New File on Discontinuity. See Timecode Discontinuity Definition above for details about what constitutes a timecode break.


213


TapesThe Tapes panel allows you to create tape names and add them to the list. You can then associate clips with the names of the tapes where they originated. This can be done by selecting a tape before selecting Log to log a clip, or you can drag a clip from the Clip Log onto a tape to make the association.

+ (plus)—Opens the Configure Tape dialog. Enter the name of the tape and click Save to save (or Cancel to cancel) the new tape to the Tapes list.

Trash—Click trash to delete all tapes from the tape list.

Modify—The modify (three dots) button opens a dialog to edit or delete the tape. Click Edit to view and modify tape details. Click Delete to delete the tape. Deleting a tape deletes the associated logged clips. Deleting all tapes deletes all logged clips.

Clip LogThe Clip Log consists of a list of clips that have been marked for recording in the media output file. After you set up a clip in the Clip Panel, clicking Log adds the clip to the Clip Log. The name displayed for the Clip Log changes depending on which tape is selected. The format of the name is: “Clips On + Name of Selected Tape”.

Captured Files Folder—To quickly access captured files you can select the folder icon. The Captured Files dialog opens. Select the icon to copy a file output path to your clipboard. You can paste the copied path into your Windows File Explorer, then log into the Lightspeed Live server to open the file with an appropriate application.

Metadata—Click the metadata button to access and modify the Labels metadata list. The contents of the metadata depends on the metadata label(s) you created in the Vantage Management Console. See Metadata above in Clip Panel for more information.

Modify—The modify (three dots) button opens a dialog for selecting Edit Entry to view and modify clip details, or Remove Entry to remove the clip.

Trash—Click trash to delete all clips from the Clip Log.


214


Capturing ClipsThe Capture controls are at the top of the Log panel, just above the current clip panel. See the Log Panel descriptions for details about the Stitch, Gear, and Capture controls. The procedure for using those controls to capture clips to tape is described below.

Set the order in which clips are stitched—Click to open a dialog listing the clips included on a tape. Click to select a clip and use the up and down arrows to move the clip in the clip order list.

Gear—Click the gear icon to open the Customize Parameters dialog and configure any Tape action parameters that have been bound to a variable. Any description contained in a variable is displayed by selecting the question mark tooltip (?) next to each parameter. The question mark (?) also provides a tooltip to explain the parameter.

Also see Configuring Tape Parameters that are Bound to Variables.

Capture—Click Capture to capture clips in the current Clip Log to corresponding output media files. When Capture is selected the Capture Clips dialog opens.


215


From Capture Clips you can make these selections for the capture operation:

Primary Output Configuration—Select a container configuration that was added in the Tape action for the Primary Output. The configuration names are in alphabetical order and the full name is displayed.

Output Location—Select a Vantage Folder Address Book entry or select Follow Workflow Specification to use the location set in the Tape action workflow.

Secondary Output Configuration—Select a container configuration that was added or enabled in the Tape action for the Secondary Output. The configuration names are in alphabetical order and the full name is displayed.

To add Primary and Secondary outputs, see Configuring Primary and Secondary Outputs.

Activate CapturingWhen you click Capture in the Capturing Clips dialog, the dialog closes and Capturing starts and the blue Capture button in the top bar changes to during the recording operation.

Monitoring CapturingWhen a capture is in progress, the Clip Log indicates which clip is currently recording and which clips are submitted to be recorded. The time that has elapsed during the recording operation is displayed, along with a progress circle.


216


Preview Player PanelThe Preview Player panel plays video and audio from the current VTR source so that you can locate and mark clips. Additionally, the player includes these features:

• Includes audio level displays and controls for up to eight (8) stereo pairs.

• Shows tape source video and audio details.

• Contains a full set of VTR controls with standard keyboard shortcuts.

Source Display—The upper left corner displays the VTR source currently playing.

Source Lock—Click to lock the current source to your user account. When locked, the source cannot be controlled by other users. Click again to unlock (lock top opens). Note that you can forcibly unlock a source; a dialog states the user name and domain of the person who has reserved the source. The source is automatically locked when any RS-422 transport control is in use.

Tape In Indicator—White indicates a tape is inserted; red TAPE OUT indicates the tape is not inserted.

Remote Indicator—White indicates VTR remote control; red LOCAL indicates local control.

RS-422 Indicator—White when Tape Capture has VTR control; red NO RS-422 when not in control (and Tape and Remote indicators are hidden).

Alarm—Red Alarm appears below RS-422 only if a problem occurs with the source.

Source Lock

RS-422 IndicatorAlarm (visible and red if active)

Tape InRemote

Audio Levels

Audio On/Off

VTR Controls Cue

Source

Video/Audio Details


217


Audio Level Buttons and Displays—Click a button to turn an audio pair on or off. When on, a level display bar shows variations in the audio level.

Video/Audio Details—Displays video resolution, frame rate, bit depth, number of audio channels, and whether captions are present.

Cue—Cues video to the timecode you enter. Enter timecode and click the arrow to cue.

VTR Controls and Keyboard ShortcutsThe VTR controls operate in a standard fashion. Enter SHIFT+? to display the list of VTR keyboard shortcuts (shown below).

Buttons Keyboard Shortcuts Function

i Mark In

o Mark Out

p Log Clip

j Rewind (press 1-3 times to increase speed)

[ Step Backward

k Stop

] Step Forward

Space Bar Play

l Fast Forward (press 1-3 times to increase speed)

Using the Tape Capture Web ApplicationUsing the Tape Capture Web App

218


Using the Tape Capture Web AppThis topic explains how to do typical tasks using the Lightspeed Tape Capture web application and presents them in the order you would follow to capture clips. The display indicator state for parameters that have the on/off toggle is:

• Enabled

• Disabled

Setting up for LoggingBefore you begin logging and capturing, you must make preliminary selections:

1. Select a Channel Group and VTR source in the upper left corner.

2. Select Workflows and then select a specific workflow from the list.

3. Configure capturing using the steps in the next topics.

Creating Tape NamesBefore you begin logging, you should create tape names in the Tape web app to match the tapes you plan to use in the VTR to make clips:

1. In the Tapes panel, click the + (plus) button.

2. Enter tape information and press Enter.

3. Repeat to create as many tape names as needed for the clips you plan to make.

The tape name is embedded in the output of the QuickTime and the container and is viewable in the following supported editing applications: Final Cut Pro, Adobe Premiere Pro, and DaVinci Resolve.In DaVinci Resolve, the Assist Using Reel Names... setting must be changed for the Tape Reel Name to display. Go to File > Project Settings > General Options and enable Assist Using Reel Names from the: and set it to Embedding in source clip file.

Creating a ClipTo create a clip, make sure the VTR is connected and selected as the source, and follow these steps:

1. Insert the source tape for the clip into the VTR. The Tape In indicator on the Preview Player should be white.

2. Select a tape name in the Tapes list to associate the current clip with the tape.

3. Play or scrub the video using the VTR controls to find the point where you want your clip to start.

4. Click the Mark In button in the Clip Panel to set the start timecode of your clip.

5. Play or scrub the video using the VTR controls to find the point where you want the clip to end.


219


6. Pick one of the two alternatives below as your next step:

Click the Mark Out button to mark the ending timecode of your clip. The dura-tion is calculated automatically.

Optionally, instead of marking an out point, you can enter a duration after marking in, and the ending timecode is calculated for you.

7. Click the metadata button to open the Configure Labels dialog to access and modify metadata contained in any Label added to the Tape action (if any).

8. Click Log to create the clip and add it to the Clip Log.

Configuring Clip StitchingClip Stitching allows you to create an MP4 reference file of source clips from multiple tapes, and arrange the clips in the order you want to stitch them together. During capture, individual files are created of each clip. When capture from all tapes is complete, the MP4 reference file is created with the clips in the order they were arranged in the Clip Ordering dialog.

To configure clip stitching, follow these steps:

1. Enable Clip Stitching in the Tape action, and then activate the workflow.

2. In the Tape Capture web app, create a clip list for each tape, either using manual IN/OUT/LOG or by importing an EDL. This is done for every tape to be included in the MP4 reference file.

3. Select the Clip Ordering button to open the dialog that provides the ability to arrange the clips in the order that you want them to appear in the MP4 reference file. The clips could be moved up/down either by drag/drop or by using up/down arrows.

4. Set the Timecode Override value, if desired. If Timecode Override is not enabled in the Tape action, the output clip has an initial timecode of 01:00:00;00.

5. Select any other configuration setting.

6. Select Capture.

a. The Web app captures just like it does in the non-Stitching mode, by asking for the first tape by name and wait for confirmation that the tape has been inserted into the VTR. After confirmation, the Web app controls the VTR and captures each of that tape's clips in linear TC order.

b. After all clips for the tape have been captured, the Web app prompts you to insert the next tape and the same process (step 6a) is executed. This process continues until all clips from all tapes have been captured into individual files.

7. When complete, the system outputs an MP4 reference file that contains references to all of the clips in the order that they were arranged in the Clip Ordering dialog.


220


Capturing ClipsWhen your Clip Log is complete (the list contains all the clips you want to capture), click the Capture button to open the Capture Clips dialog. Select the Configuration method and Output Location, and then click Capture.

The Tape Capture app begins recording and capture the clips in the log into corresponding final output media files. For multiple tapes, the Tape Capture app prompts you to insert the first tape when you start the capture.

If the Rewind tape setting is enabled, when all clips from the first tape are complete, the Tape Capture app sends the VTR a command to rewind the tape (Note that Rewind tape defaults to disabled.) The app also selects the next tape in the list, and indicates that a tape needs to be inserted. Then, insert the tape and press the Capture button to resume capture (the button displays yellow and reads Resume).


221


Configuring Tape Parameters that are Bound to VariablesAny parameter that has been bound to a variable during Tape action setup, or any variable added to the Tape action via the Add Variables context menu, can be configured in the Customize Parameters dialog. This dialog is opened by selecting the gear button next to the Capture button. To bind variables in the Tape action, see Binding Variables to Configuration Parameters.

Any description contained in a variable is displayed by selecting the question mark tooltip (?) next to each parameter. The question mark (?) also provides a tooltip to explain the parameter.


222


Setting Drop/Non-Drop Frame CharacteristicsYou can change between drop frame and non-drop frame in the Customize Parameters dialog to change the characteristics of the captured file. For this option to be available in the Customize Parameters dialog you must have Timecode Override Enable activated in the Tape action, and have it bound to a variable. See Creating and Activating a Tape Action Workflow > Settings Panel.

To change between drop frame and non-drop frame:

1. Click the Gear icon to open the Customize Parameters dialog.

2. Enable TC-Toggle to enable Time Code Override.

3. Select a frame rate of 29.97 fps or 59.94 fps if you want to use drop frame. (Drop frame is only available for 29.97 fps or 59.94 fps.) Select any frame rate for non-drop frame.

4. Select the timecode by clicking it once or by selecting the line below it. When selected, the line and TC Override name displays in blue. (All numbers must be highlighted in white. If only one section of numbers is highlighted then you can not change between drop frame and non-drop frame.)

5. Type a semicolon “;” to set for drop frame, or a colon “:” for non-drop frame. The character should change in the timecode.

6. Click Save to save your changes and close the dialog.

When the capture is activated the output file uses the drop frame or non-drop frame characteristic you have set.


223


Creating a Stitched Clip The Clip Stitching feature allows you to create a list of clips from one or more tapes, arrange the clips in the order in which they should be stitched together, capture all the clips to individual files, and then create a stitched output file (or files) containing all captured clips in the order specified.

Note: When clips or tapes have different frame rates, the job stops at the stitch location where the frame rate changes. Frames rates must be the same for stitch operations to complete successfully.

Follow these steps to create a Stitched Clip:

1. In the Vantage Workflow Designer, open the Tape action to configure it. (See Creating and Activating a Tape Action Workflow for more details.)

2. In the Tape action Settings panel, enable the Stitch Clips option by binding it to a True variable. (To bind variables in the Tape action, see Binding Variables to Configuration Parameters.)

3. In the Tape action, set the Stitch Behavior to Direct Convert or Reference Movie (Reference Movie is the default) and enable “Is Output Stitched” if desired. See the Tape action Settings Panel.

Note: Clip Stitching is only supported for MXF OP1a, QuickTime, and MP4 outputs.

4. When the Tape action workflow is fully configured, Activate the workflow.

5. In the Tape Capture web app, create the list of clips you want to log, either by using the Mark In > Mark Out > Log method, or by importing an EDL file.

6. When your Clip Log is complete, select the Clip Stitch Order button to open the Clip Stitch Order dialog. The Clip Stitch Order dialog allows you to order the clips the way you want them to appear in the stitched output file. The clips can be


224


moved up or down either by drag-and-drop or by using the up/down arrows next to each clip.

7. After the clips have been ordered, adjust any other parameters, as needed.

8. Click the Capture button to open the Capture Clips dialog. Select the Configuration method and Output Location, and then click Capture.

9. The Tape Capture app begins recording and capture the clips in the log into corresponding final output media files.

With multiple tapes, the Tape Capture app prompts you to insert the first tape when you start the capture. When the tape completes, the Tape Capture app selects the next tape in the log list, and indicates that tape needs to be inserted. Then, insert the tape and click the Capture button to resume the capture (the but-ton displays yellow and displays Resume).

10. Once all individual clips have been captured from all tapes, the system automatically creates a Primary output of individual clips and a stitched clip, or clips, depending on your workflow settings.

11. The Primary and Secondary files can be processed by any downstream action in the same way they are in the non-stitched mode.


225


Recording a Complete Tape—Even if It Has ErrorsUsing the “Complete Tape” procedure, you can force the recording of the entire tape, even if it has various errors, such as discontinuities in timecode, loss of the tape control track, or if alarms are triggered in the VTR.

To record the entire tape and ignore errors, select the Capture an entire tape button . This button enters Mark In and Mark Out timecode values that instruct the Tape Web app to capture the entire tape from the beginning of the tape to the ending of the tape. A dialog asks you to confirm that you want to capture the whole tape. When you click CAPTURE, the tape is rewound to the beginning and captures the content on the whole tape until EOT (End of Tape) is reached.

Alternatively, without using the Capture an entire tape button, you can set the Mark In timecode to 00:00:00:00 and the Mark Out timecode to 23:59:59:00. When you start the Capture recording process, the tape rewinds to the start (no matter where it was parked) and tape playback and recording starts. When the end of the tape is reached recording stops.

Note: The capture progress indicator does not function when performing a Complete Tape capture since the duration of the capture is unknown. The user can observe the timecode display to confirm the current state. However, with tapes that have no timecode or are without a control track the true state cannot be known. Direct observation of the VTR may be necessary.

Note: Both the Abort on Discontinuity and Use Duration Over Markout options, located in the Tape action, should be disabled when performing a Complete Tape capture. See the Tape action Settings Panel for a description of these options. Also see Timecode Break Recording and Timecode Discontinuity Definition in the Using the Tape Capture Web Application chapter for discontinuity details.

Using the Tape Capture Web ApplicationUsing the Job Status View in Tape Capture

226


Using the Job Status View in Tape Capture Click the Status button in the upper left corner of the web app to display the status

of running and completed Tape Capture jobs.

For details see the Vantage Job Status Views web app and Using the Vantage Job Status Views.

227

Calculating Live Capture Resources

This chapter provides information to help you calculate Lightspeed Live Capture resource usage.

■ Lightspeed Live Capture Resource Calculator

■ Determining the Time-Shift Buffer Duration

■ Calculating your Resource Usage Capacity

Calculating Live Capture ResourcesLightspeed Live Capture Resource Calculator

228


Lightspeed Live Capture Resource CalculatorLightspeed Live Capture uses a variety of codecs and format containers to encode live video into media files. At the simplest level, Lightspeed Live Capture consists of customizable workflow actions that automate the live capture process. A workflow is the mechanism you create that takes an incoming live source and encodes it into one of many available codec and container formats.

Note: When Live Capture and Live Stream are used on the same Lightspeed Live server, use the Live Stream CPU and GPU Resource Usage Guide (located in the Lightspeed Live Stream Guide, Social Media Platform Workflows chapter) along with the Live Capture Resource Calculator describe here to determine how Capture and Stream can best share a Lightspeed Live server's resources.

The Lightspeed Live server has four (4) SD/HD/3G-SDI inputs that can be used to capture up to four (4) SD/HD formatted files or one (1) UHD/4K formatted file. One or more Lightspeed Live Capture workflows can be driven by a single source input. This allows the user to configure their system to create more than one output format type from a single source input. For example, if your capture workflow requires two hi-res capture output files, such as DNxHD 220 and Apple ProRes HQ, Lightspeed Live Capture can be used for this by creating two Capture origin actions that use the same source input.

The figure below shows four (4) SDI-HD inputs. SDI Input 1 is connected to two (2) workflows, and SDI Input 2, 3, and 4 are each connected to a single workflow.

The input source/workflow flexibility described above, combined with the wide array of codecs available on a Lightspeed Live server, make it important that all processes being performed on a Lightspeed Live server do not exceed its total processing capabilities.


229


Care must be taken not to exceed the limits of the Lightspeed Live server's available resources. The factors that consume the Lightspeed Live server's resources are described in the following topics. The following items have an effect on resources used by individual workflows.

Browser Operation is Not Included in Usage CalculationsTelestream recommends that you connect to the Lightspeed Live Web Applications from browsers running on client computers, and you do not run these browser-based Web apps directly on the Lightspeed Live servers. This avoids additional decoding load for the Live Web app’s preview displays on a Live Capture server.

Live Web Apps include:

• Live Capture

• Live Tape

• Source Manager

Browser operation on the Lightspeed Live servers are not included in the resource usage calculations.

Determining the Time-Shift Buffer DurationThe Time-Shift buffer has a maximum duration of 60 seconds for each source input. The amount of memory used by each instance of Time-Shift buffer is directly related to the frame size and frame rate of the inputs source video. The Lightspeed Live server contains 64GB of RAM where Time-Shift data is buffered. Best practice is to limit each input source's Time-Shift buffer to 15 seconds when using large frame sizes and high frame rates.

Use the following data as a baseline when determining the duration of each input source's Time-Shift buffer.

Standard Definition (SD) Codecs• NTSC and PAL—No limit to the duration of a source's Time-Shift buffer is required.

High Definition (HD) Codecs• 720p/1080i /1080p up to 30fps—The total for all input source Time-Shift buffers

combined should not exceed 120 seconds.

• 720p/1080p above 30fps—The total for all input source Time-Shift buffers com-bined should not exceed 100 seconds.

UHD/4K Codecs• Limit the Time-Shift buffer to a maximum of 10 seconds.

Note: For information on where to set the Time-Shift buffer, see Creating a Capture Action Workflow in the Creating Capture and Tape Workflows chapter.


230


Calculating your Resource Usage CapacityUse the processing resource charts below to determine whether your Lightspeed Live server can process all of your desired Live Capture workflow's video codec requirements. The charts are organized based on input signal type and list available codecs used with each input type. Each codec is rated based on the resource requirements needed to capture into the respective codec type selected, both for high resolution Primary outputs and Secondary Proxy outputs.

In the case of a UHD capture job, resource utilization for UHD capture operations is generally high, so it is important the source bit depth match the transcoder for an efficient operation. Generally, a UHD source should be set to 10-bits when recording to ProRes or DNXHR HQX.

RUF reference settings for UHD transcodes are derived with the assumption that the source bit depth matches the transcoder.

Each Lightspeed Live server is capable of a maximum of one (1) full Resource Use Factor (RUF). By adding all of your workflows resource requirements together, along with the Time-Shift buffer limits from above, this can determine if your Lightspeed Live server can reliably perform the tasks required.

To determine the Resource Use Factor for each workflow being concurrently processed you should review each workflow, determine the workflow's Resource Use Factor, and add all of the workflow Resource Use Factors together. The resulting number must be less than or equal to one (1). See the examples below. If your total Resource Use Factor value is greater than one (1) you should modify your workflows to achieve a Resource Use Factor less than or equal to one (1).

These calculations take into account the resources required for the Capture or Tape actions only. Other actions, such as a Copy Action in Open mode, may use resources that adversely affect the performance of your server. Always test workflows when the RUF total is higher than 0.80.


231


Resource Use Factor (RUF) ChartsUse the following charts to determine your Resource Use Factor (RUF) for Live Capture. The charts provide the typical RUF for each codec. The total of all of your concurrently active workflow Resource Use Factors must be less than or equal to one (1) RUF, which is the maximum process handling load that you should place on each Lightspeed Live server.

Primary Outputs—RUF Values

* DNxHR and ProRes 4K/UHD at 50/59.94/60 frame rates requires the LS-LIVE-4TB-OPTION media storage option. DNxHR (4444) and ProRes (444) are not supported in high frame rate.

NTSC/PAL

1080i25/29.97

720p-1080p23.98/24/25/29.97

720p-1080p50/

59.942160p23.98/24/25/30

2160p50/59.94

AVC- H.264 0.10 0.10 0.25 0.25 1 --

AVC-Intra -- 0.20 0.25 0.25 -- --

AVC-Ultra -- 0.33 -- -- -- --

DVCPro HD -- 0.15 0.20 0.20 -- --

DV/DVCPro 0.10 -- -- -- -- --

DNxHD -- 0.15 0.20 0.20 -- --

DNxHR -- -- 0.25 0.25 1 1*

HEVC -- -- 0.25 0.25 -- --

IMX 0.10 -- -- -- -- --

J2K Lossless YUV 8-bit 0.20 0.25 0.50 0.50 -- --

J2K Lossless YUV 10-bit 0.25 0.33 0.50 0.50 -- --

J2K Lossy YUV 8-bit 0.20 0.25 0.33 0.33 -- --

J2K Lossy YUV 10-bit 0.25 0.33 0.50 0.50 -- --

J2K Lossless RGB 8-bit 0.25 0.33 0.50 0.50 -- --

J2K Lossless RGB 10-bit 0.33 0.50 1 -- -- --

J2K Lossy RGB 8-bit 0.25 0.33 0.50 0.50 -- --

J2K Lossy RGB 10-bit 0.33 0.50 1 1 -- --

ProRes 0.10 0.15 0.20 0.20 1 1*

x264 0.15 0.25 0.33 0.33 -- --

x265 -- -- 0.25 0.25 -- --

Uncompressed 10-bit See Capacity for Capturing Uncompressed Media Via 3G-SDI Inputs

XAVC-Intra -- 0.20 0.25 0.25 -- --

XDCAM 420/422 -- 0.20 0.25 0.25 -- --


232


CAUTION: A Secondary Output should not be concurrently generated when the primary output is recording UHD/4K.

Secondary Outputs - RUF Values

640x480 (default) Same as Source

Proxy MP4 0.05 0.10

Proxy HLS 0.05 0.10

Proxy MXF RDD25 0.05 0.10

Proxy TIFO 0.05 0.10


233


Example 1—Uses a Total of 1.00 RUFExample 1 shows four (4) SDI-HD inputs. Each SDI Input is connected to a separate workflow to create a variety of file outputs. In this example, the total of the Resource Use Factor value from all Live Capture workflows equals one (1) RUF.


234


Example 2—Uses a Total of 0.90 RUFExample 2 shows two (2) SDI-SD inputs and two (2) SDI-HD inputs. SDI 1 and SDI 2 are standard definition creating IMX and ProRes with Proxy files respectively, while SDI-3 and SDI-4 are 1080p60 creating AVC-Intra and Proxy files. In this example, the total of the Resource Use Factors from all Live Capture workflows equals 0.90 RUF.


235


Capacity for Capturing Uncompressed Media Via 3G-SDI Inputs

Lightspeed Live Capture can capture Uncompressed SD or HD in 8-bit or 10-bit via the 3G-SDI inputs. Several factors determine what your Lightspeed Live Capture system is able to reliably capture. Use the chart below to calculate the Resource Use Factor (RUF) when capturing Uncompressed. A Lightspeed Live Capture server RUF value should never exceed 1.

• Storage Location—Local Media drive or Shared Storage of NAS (Network Attached Storage), or SAN (Storage Area Network).

• Drive Configuration—The drive configuration is governed by the number of drives making up your Live Capture system's media drive and the RAID type that the media drive is configured for. A standard Live Capture server ships with a media drive containing 4 drives striped as RAID 5. In addition, a Lightspeed Live Capture system's media drive can be expanded to 8 drives by purchasing the media drive option “LS-LIVE-4TB-OPTION”. The RAID type of the media drive can be changed from RAID 5 by the user to RAID 0 if disk I/O is more desirable than data redun-dancy. See Rebuilding the Lightspeed Live Storage RAID.

• Frame Size, Frame Rate, and Scan Type—The incoming input's frame size, the frame rate, and scan type of interlaced (i) or progressive (p) affects the require-ments for capturing an Uncompressed file output.

*A Lightspeed Live server is capable of a total of one (1) RUF. **Assumes that the shared storage hardware can support the required disk I/O for these operations.***See the LS-LIVE-4TB-OPTION to add 4 additional drives to a Lightspeed Live server.

Capture Resource Use Factor*

Local Media Storage Setup

SD - NTSC/PAL with Proxy

1080i50/60 with Proxy

1080p30/50/60 with Proxy

1080p23.98/24 with Proxy

UHD / 4K

4 Drive RAID 5 0.25 0.5 1 0.33 Not Supported

4 Drive RAID 0 0.25 0.5 1 0.25 Not Supported

8 Drive RAID 5***

0.25 0.25 1 0.25 Not Supported

8 Drive RAID 0***

0.25 0.25 0.5 0.25 Not Supported

Shared Storage**

SD - NTSC/PAL with Proxy

1080i50/60 with Proxy

1080p50/60 with Proxy

1080p23.98/24 with Proxy

UHD / 4K

NAS 0.5 Not Supported Not Supported Not Supported Not Supported

SAN connected via 16 GB Fibre

0.25 0.25 0.25 0.25 Not Supported


236


Example 3—Uncompressed 10-bit - Uses a Total of 1 RUFExample 3 shows two (2) HD-SDI (1080i60) inputs capturing Uncompressed 10-bit with a concurrent Proxy. The output files are to be written to the local 4 drive RAID 5 media drive. The total Resource Use Factors for these capture workflows equals 1 RUF.


237


Example 4—Uncompressed 10-bit - Uses a Total of 1 RUFExample 4 shows four (4) HD-SDI (1080i60) inputs capturing Uncompressed 10-bit with a concurrent Proxy. The output files are to be written to a shared Storage Area Network (SAN) location connected via 16Gb Fibre. The total Resource Use Factors for these capture workflows equals 1 RUF.


238


239

Appendix A: Support

This appendix provides contact resources for Telestream Support services, RMA procedures, and troubleshooting information.

These topics are included:

■ Obtaining Support | Information | Assistance

■ Return Material Authorization (RMA) Procedure

■ Using Log Files and Other Support Information

Appendix A: SupportObtaining Support | Information | Assistance

240


Obtaining Support | Information | AssistanceContact Telestream as indicated below.

Telestream Contact Information

Resource Contact Information

Lightspeed Live Support Website: www.telestream.net/telestream-support/lightspeed-live/support.htm

Support Email. [email protected]

Terms and times of support services vary, per the terms of your current service contract with Telestream.

Lightspeed Live Information, Assistance, FAQs, Forums, & Upgrades

Website: www.telestream.net/telestream-support/lightspeed-live/support.htm

Support Email: [email protected]

For details about the Web API, see the Lightspeed Live Stream/Capture Web API Reference on Telestream.net or click the three dot menu in the web app, select About and Web API Reference.

Telestream Website: www.telestream.net

Sales and Marketing Email: [email protected]

Telestream848 Gold Flat RoadNevada City, CA USA 95959

Telestream Reseller Support

If you purchased your Lightspeed Live server from a reseller, please contact your reseller for support.

International Reseller Support

Website: www.telestream.net

See the Telestream website for your regional authorized Telestream reseller.

Telestream Technical Writers

Email: [email protected]

If you have comments or suggestions about improving this document, or other Telestream documents—or if you've discovered an error or omission, please email us.



mailto:[email protected]










Appendix A: SupportReturn Material Authorization (RMA) Procedure

241


Return Material Authorization (RMA) ProcedureIf your Lightspeed Live server requires service of any kind, regardless of whether you purchased the Lightspeed Live server from Telestream or an authorized reseller, contact Telestream directly for a Return Material Authorization (RMA).

CAUTION: Except for the modular power supplies and disk drives, the Lightspeed Live server is a sealed device, with no user serviceable parts inside. You should never open the top cover or attempt to upgrade or alter the server. Doing so exposes you to electrical hazard, may damage the unit, and may invalidate your warranty.

Please contact Telestream for all internal service of the server:

• Email: [email protected]

• In the US, telephone: 1-877-257-6245

• From international locations, telephone: 1-530-470-2036.

Provide your organization name, and contact information, the serial number of the inoperative unit, and request a Return Material Authorization.

Before returning your Lightspeed Live server, back up the entire contents of all server drives to protect against data loss. See Backing up the Lightspeed Live Server for details.

mailto://[email protected]

Appendix A: SupportUsing Log Files and Other Support Information

242


Using Log Files and Other Support InformationThe following topics explain log files and provide other troubleshooting and service information.

Log Files for Live CaptureLog files can provide valuable information about the operation of Lightspeed Live Capture. The following describes how to access the log files and how to change the information they contain.

Accessing the Log FilesThe Lightspeed Live Capture log files are available and configurable as follows:

• Logging is configured with config files in the Capture ComponentPac folder (for example, C:\Program Files (x86)\Telestream\Vantage\Components\Cap-ture.7.1.5.xxxxxx)

• Capture logs are saved to: C:\Windows\System32\config\systempro-file\AppData\Roaming\Telestream\Capture\

• Logging can be customized by changing the config files, for example, C:\Program Files (x86)\Telestream\Vantage\Components\Capture.7.1.5.xxxxxx\CaptureRe-cord.exe.config.

Changing Log Content SettingsThe information written to the log files can be changed by editing settings in the configuration files that control logging file generation.

CAUTION: Before making changes to the configuration files, make backups by copying the existing files and saving them to a safe location.

The configuration files are:

• CaptureProgram.exe.config

• CaptureRecord.exe.config

• TapeRecord.exe.config.

The following fields in the configuration files can be edited to change logging results:

• logconsole

• logfile

• elastic.


243


The above fields can be edited to use any of these logging levels (from most restrictive to most verbose):

• Off

• Fatal

• Error (default)

• Warn

• Info

• Debug

• Trace.

For details about using NLog to modify log file outputs, refer to the NLog tutorial: https://github.com/NLog/NLog/wiki/Tutorial#log-levels.

Downloading Log Files for SupportThe contents of the log files may be helpful to Telestream Customer Support to troubleshoot system problems. You may want to access and save the log files before making a support call so you can email them to Telestream as part of the support process.

To download the Capture logs in a single zip file, log into the Capture Source Manager: http://[host]:8090/. Select the Main Menu and choose Download System Logs.

A zip file downloads to your default download folder. You can open the zip file and examine the logs or forward the file to Telestream Support with a request for assistance.

https://github.com/NLog/NLog/wiki/Tutorial#log-levels


244


These log files are included in the download:

• Devices.csv

• EventLog-Application.evtx

• EventLog-System.evtx

• LiveRegistry.csv

• Processes.csv

• Services.csv

• Stats.txt

• versions.csv

Additional Support Log FoldersThe following folders containing additional logging data are also downloaded:

■ SNMPLogs

■ SNMPLogs\traceLog

■ Logs

SNMPLogsThe SNMPLogs folder contains the following additional items:

• SourceService-[date].log.txt—The Source service log records any activity with the sources. This includes various activities, such as loss of signal, change of format, sources being added, or sources being removed.

• LiveService-[date].log.txt—The Stream service log records any encoder failures and the service starting.

SNMPLogs\traceLogThe SNMPLogs\traceLog folder contains trace logs for the input sources.

LogsThe Logs folder contains the Capture Record, Capture Program, Tape Record, and other Capture-related log files.


245


Resolving Capture Error MessagesA list of error messages and their resolutions is provided below.

Loss of Signal—Tape CaptureIf you encounter a loss of signal condition while capturing a clip with Tape Capture and Ignore Lost Frames in the action is disabled, the logged clip fails with this error: Loss of signal detected. Data invalid.

You can resolve this by enabling Ignore Lost Frames in the action. Then, any signal interruptions are ignored and the capture continues.


246


247

Appendix B: Containers, Codecs, and Vantage Actions

This appendix includes descriptions of the containers and codecs available in the Capture and Tape actions and briefly describes other actions included in the Vantage Workflow Designer to support Lightspeed Live Capture and Tape Capture.

For more details on Vantage action operation and configuration, open the application help (M) or the Vantage Help menu (?) from the upper right corner of the action inspector.

These topics are included in the appendix:

■ Capture Action Output Containers

■ Tape Action Output Containers

■ Primary Output - Video Codecs

■ Primary Output - Audio Codec

■ Secondary Output - Video Codecs

■ Secondary Output - Audio Codecs

■ Vantage Actions

Appendix B: Containers, Codecs, and Vantage ActionsCapture Action Output Containers

248


Capture Action Output ContainersThese output containers are included in the Capture action:

■ MXF OP1a Output

■ MPEG2-TS Output

■ QuickTime Output

■ QuickTime Open Output

■ TIFO Output

■ Proxy TIFO Output

■ Proxy MP4 Output

■ Proxy MXF RDD 25 Output

■ Proxy HLS Output

Appendix B: Containers, Codecs, and Vantage ActionsMXF OP1a Output

249


MXF OP1a OutputMXF OP1a Output produces an MXF Operational Pattern 1a (OP-1a, SMPTE 379M-2004) file with a generic container mapped to video and audio formats encoded by codecs implemented in Lightspeed Live Capture.

Note: Most Lightspeed Live Capture MXF files containing IMX, XDCAM or AVC-Intra, and all QuickTime Open files, are created in such a way that they can be opened for editing/playing (in Adobe Premiere Pro CC, Telestream Switch and other media applications) while they are still growing during capture. Check with your edit/player application software documentation for further details on supported formats.

Generic MXF Format Summary

VideoAVC | Avid DNxHD | Avid DNxHR | DV | DVCPRO HD | IMX | JPEG2000 Lossless | JPEG2000 Lossy | Panasonic AVC-Intra | Panasonic AVC-Ultra | Sony XAVC | Sony XDCAM | Uncompressed | x264

AudioPCM 16/20/24-bit, 48Kbps, up to 16 channels

PCM/Dolby E (pass through,16 bit only)

TimecodeSMPTE 377M, Timecode track

SMPTE 385M, System item

SMPTE 405M, System item (DNxHD)

MXF Applicable StandardsSMPTE 331M-2004, Elements and Metadata Definitions for SDTI-CP

SMPTE 377M-2004, Material Exchange Format (MXF)

SMPTE 378M-2004, MXF Operational Pattern 1a

SMPTE 379M-2004, MXF Generic Container

SMPTE 382M-2007, Mapping AES3 and Broadcast Wave Audio into MXF Generic Container - DV (AES3), DNxHD, (BWF)

SMPTE 383M-2008, Mapping DV-DIF Data into MXF Generic Container - DV


250


SMPTE 385M-2004, Mapping SDTI-CP Essence and Metadata into MXF Generic Container - DV, IMX

SMPTE 386M-2004, Mapping Type D-10 Essence Data to MXF Generic Container - IMX

SMPTE 394M-2006, System Scheme 1 for MXF Generic Container DNxHD

SMPTE 405M-2006, Elements and Individual Data Items for MXF Generic Container System Scheme 1 - DNxHD

SMPTE 436M-2006, MXF Mappings for VBI Lines and Ancillary Data Packets

SMPTE 2019-4-2008, Mapping VC-3 Coding Units into MXF Generic Container - DNxHD

SMPTE RDD03, eVTR MXF Interoperability Specification - DV, IMX

SMPTE RDD 9-2009, MXF Interoperability Specification of Sony MPEG Long GOP Product

SMPTE ST 298-2009, Universal Labels for Unique Identification of Digital Data

SMPTE ST 326:2000, Television -SDTI Content Package Format (SDTI-CP)

SMPTE ST 381-1:2005, Television-Material Exchange Format (MXF) - Mapping MPEG Streams into the MXF Generic Container

SMPTE RDD 25:2014, AVC MXF Proxies

Note: The resulting MXF (OP-1a) file can contain VANC data (SMPTE 436M) if present in the incoming SDI stream.

Container SettingsThe MXF OP1a Container wraps the specified media in MXF OP-1a file format.

GeneralFile Extension. Specifies mxf. No other extensions are provided.

436 Data Track. Specifies how to add SMPTE 436 data (None | Ancillary | VBI) to the output.

Partition Strategy. Specifies how to apply the MXF partitioning.

Broadcast Wave Audio. When checked, sets the audio tracks to Broadcast Wave format, adding metadata such as timestamps to the audio stream.

Mpeg Picture Element. Specifies that MPEG picture elements should be used for Avid and Adobe Premiere Pro compatibility.

Telestream Index. When enabled, a proprietary Telestream Index file is created for use in specific customer workflows.


251


Aspect Ratio ModeAspect Ratio Mode. Specifies how to set the display or pixel aspect ratio of the output.

- Automatic - Set the aspect ratio setting automatically, based on detected content.

- Display Aspect Ratio - Specifies 4:3 | 16:9.

- Pixel Aspect Ratio - Specifies the selected pixel aspect ratio.

Video Stream DetailsSelect the Video Stream component to display its options on the right.

CodecCodec. Specifies which codec to use to encode video streams. For configuration details, see appropriate topic following.

AVCProfile. Specifies the encoding profile: Baseline | Main | High.

Bit Rate (in kbps). Specifies the target bit rate (512 - 50,000).

Avid DNxHDQuality. Specifies video quality profile: 444 | HQX (10 bit) | HQ (220/185 Mbps) | HQ TR (145/20 Mbps) | SQ (145/120 Mbps) | SQ TR (100/100 Mbps) | LB (45/36 Mbps).

Avid DNxHRQuality. Specifies video quality profile: 444 | HQX (10 bit) | HQ | SQ | LB.

DVQuality. Specifies video quality profile: DV 25 Mbps | DVCPRO 25 Mbps | DVCPRO 50 Mbps

DVCPRO HDNo user-configurable settings available.

IMXQuality. Specifies video quality profile: 30 Mbps | 40 Mbps | 50 Mbps

JPEG2000 Lossless (Comprimato)The Comprimato JPEG2000 Lossless codec encodes the input video into one output video file in JPEG2000 format, using the JPEG2000 codec in lossless mode.


252


Comprimato-based ISO/ITU still image compression provides a fast and flexible solution for high-quality, wavelet-based compression.

JPEG-2000 is an intra-frame HD video codec specified by ISO/IEC 15444-1. It uses wavelet transformations to compress the image which results in high quality images in both lossy and lossless modes. JPEG 2000 offers higher compression ratios over standard JPEG video. It offers resolution, color, quality and position progression scalability, and also supports 4:2:2 and 4:4:4 chroma subsampling methods.

Codec SettingsPixel Format. Specifies the color space, chroma subsampling, and bit depth to use for encoding: RGB 4:4:4 8 bit or 10 bit | YUV 4:2:2 10 bit | YUV 4:2:2 8 bit.

Tile Partition Width. Specifies the tile partition width in pixels.

Tile Partition Height. Specifies the tile partition height in pixels.

Precinct Width and Height. Specifies the precinct size.

Code-block Width and Height. Specifies the height and width (in pixels) of a code block to process.

Packet Progression Order. Specifies the order of packet progression.

Decomposition Levels. Specifies the maximum number of discrete wavelet transform levels, or stages, to use (also known as Discrete Wavelet Transformation resolution).

Tile-Part Length Markers. When checked, specifies that Tile Length Markers will be used.

End of Packet Header Markers. When checked, EPH marker segments are generated.

Start of Packet Markers. When checked, SOP marker segments are generated.

CUDA Memory Limit. Specifies the CUDA memory limit in MB.

Note: When the CUDA Memory Limit is set to 0, GPU processing is disabled.

CUDA Tile Limit. Specifies the CUDA tile limit.

Encoder Queue Size. Specifies the encoder queue size.

Encode Less VBI. When checked, the codec removes the top 32 lines for SD sources that contain VBI data, ignoring more VBI lines in favor of frame size, in both NTSC and PAL. In NTSC (512), the video is 486 lines; in PAL (608), the video is 576 lines.

JPEG2000 Lossy (Comprimato)The Comprimato JPEG2000 Lossy codec encodes the input video into one output video file in JPEG2000 format, using the JPEG2000 codec in lossy mode. Comprimato-based ISO/ITU still image compression provides a fast and flexible solution for high-quality, wavelet-based compression.


253


JPEG 2000 is an intra-frame HD video codec specified by ISO/IEC 15444-1. It uses wavelet transformations to compress the image which results in high quality images in both lossy and lossless modes. JPEG 2000 offers higher compression ratios over standard JPEG video. It offers resolution, color, quality and position progression scalability, and also supports 4:2:2 and 4:4:4 chroma subsampling methods.

Codec SettingsVideo Bit Rate. Specifies the bit rate of the output in bits per second.

Quantization Coefficient. Specifies quality (1-100). If set toward the lower bound it reduces data correspondingly and quality decreases; if set toward the upper bound it increases data and quality. The default value of 100 allows the full quality as set by the bitrate to be used.

Pixel Format. Specifies the color space, chroma subsampling, and bit depth to use for encoding: RGB 4:4:4 8 bit or 10 bit | YUV 4:2:2 10 bit | YUV 4:2:2 8 bit.















Panasonic AVC-IntraQuality. Specifies video quality profile: Class 50 - 4:2:0 | Class 100 - 4:2:2 | Class 200 - 4:2:2.


254


Panasonic AVC-UltraQuality. Specifies video quality profile: Long GOP 25 | Long GOP 50

Sony XAVCQuality. Specifies video quality profile: 100 Mbps 4:2:2

Sony XDCAMQuality. Specifies video quality profile: XDCAM HD 18 Mbps CBR | XDCAM HD 25 Mbps CBR | XDCAM HD 35 Mbps VBR | XDCAM HD422 18 Mbps CBR | XDCAM HD422 25 Mbps CBR | XDCAM HD422 35 Mbps CBR | XDCAM HD422 50Mbps CBR | XDCAM EX 35 Mbps VBR

UncompressedEncode Less VBI. When checked, the codec removes the top 32 lines for SD sources that contain VBI data, ignoring more VBI lines in favor of frame size, in both NTSC and PAL. In NTSC (512), the video is 486 lines; in PAL (608), the video is 576 lines.

x264Quality. Specifies video quality profile: Baseline | Main | High | High 10 | High 4:2:2

Bit Rate (in kbps). Specifies the video bit rate (512 - 50,000)

Command Line (option)Configure the compressor using x264 command line syntax. For setting specific x264 parameters, you can enter x264 CLI commands (separated by spaces) to execute them. For best results, be sure to use long form: --bframe 5, for example. Use of short form (-b 5) is not recommended.

The following x264 command line parameters are not supported: --fake-interlaced, --nal-hrd cbr, --profile, --video-format, --bitrate.

Time Code Burn-in FilterWhen checked, this filter rasterizes the current timecode value into each output video frame.

X Position. The X position of the top-left of the timecode in the output video frame (range 0 - 4096 pixels).

Y Position. The Y position of the top-left of the timecode in the output video frame of the timecode in the output (range: 0 - 2160 pixels).

Font Size. Sets the font size of the timecode (range 6 - 120 pixels).

Text Color. Set the text color of the timecode. The default is black. You can enter simple color names, such as red, green, or white. Or enter a color hexadecimal code such as


255


#0000DDFF, which is dark blue. The "FF" characters in this example specify the opacity, and are optional. When these characters are not included the text is completely opaque (no transparency). The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the black default is used.

Background Color. Set the color of the area behind the timecode. The default is white. You can enter simple color names, such as red, green, or blue. Or enter a color hexadecimal code such as #0000DD, which is dark blue. The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the white default is used.

Timecode Transparency. The opacity of the timecode. 1.00 is fully opaque, or 100% opacity, 0 is transparent.


Audio Stream DetailsSelect the Audio Stream component to display its details on the right.

Codec (PCM)Codec. Specifies PCM as the codec to use to encode audio tracks. No other codecs are provided.

GeneralChannel Configuration. Specifies Mono | Stereo | number of the audio channels. Note: 32 channels not supported from SDI sources.

Label Channel Pairs Left/Right. When checked, causes the first channel pair to be labeled Left and Right, unless Force One Track Per Channel is checked, in which case this setting is ignored.

Bit Depth. Specifies the output audio bit depth. 16 | 20 | 24.

Force One Track Per Channel. When checked, creates multiple mono tracks instead of a single multi-channel track.

Channel Map. Allows re-mapping of the incoming source audio channels to the captured file output channels. Channels are numbered from 1 to 32. Specify the number of the audio input channel to use for each output channel.

Appendix B: Containers, Codecs, and Vantage ActionsMPEG2-TS Output

256


MPEG2-TS OutputThe MPEG2-TS output container encodes media and saves it as an MPEG2 Transport Stream file.

MPEG-2 TS Format Summary

VideoHEVC H/W | MPEG-2 | x264

AudioAAC | PCM

Container SettingsFile Extension. Specifies ts | mpg |m2t.

File Bit Rate. Default: 19,000,000 bits per second. If unchecked, the Multiplexer will use the minimum rate as computed from the sum of all maximum rates for elementary streams, data streams, PSI streams and necessary overhead.

List Audio Streams Before Video Streams. When checked, will list audio streams before video streams in the PMT stream order.

PAT Rate. Defaults to 10.0 tables per second. This function specifies the repetition rate of the Program Association Table in the output stream. The PAT lists all programs in a transport stream, each of which is identified by a 16-bit Program Number.

PMT Rate. Defaults to 10.0 tables per second. This function specifies the repetition rate of the Program Map Table in the output stream. Each program listed in the PAT has a PMT (with PID) containing information about the program.

Transport ID. Defaults to 0. This function sets the ID number for this transport stream.

PAT Version. Defaults to 0. This function sets the version number of the Program Association Table.

Program Number. Defaults to 1. This sets the ID number of a specific program.

PMT PID. Defaults to 480. This sets the Packet ID used for the Program Map Table.

PCR PID. Defaults to unselected/zero. This specifies the Packet ID that carries the Program Clock Reference for this program. Set to the first video PID value if not specified.

Maximum PCR Interval. Defaults to 37 milliseconds. This function defines the maximum time between Program Clock References for this stream.

PCR on every PES header. When selected (default), a PCR is inserted on each packet that has a PES header.


257


No Empty Adaptation Fields. When selected (default), the multiplexer avoids using zero length adaptation field video packets.

VBR Transport stream. Defaults to unselected. When selected, the Multiplexer creates a variable bit rate transport stream, and no attempt is made to maintain the bit rate.

Error Behavior. Defaults to Fail on Error. Species Fail on Error | Always Complete | Fail on Warning or Error.

Error/Warning Threshold. Defaults to 1 (range 1 - 100). Specifies the number of errors permitted before file generation fails and the number of warnings that trigger a Fail on warning or error. This parameter has no effect when Error Behavior is set to Always Complete.

Treat Buffer Underflows/Overflow Warnings as Errors. Defaults to selected. When selected, buffer underflow or overflow warnings are treated as errors.

2-Pass Multiplexing. Only use if you need to correct excessive bitrate fluctuations in the encoded stream resulting in video decoder underflow errors. The second pass is only executed if the first pass fails.

Generate Config File. Generates and places a Manzanita-compliant configuration file using the current UI settings into the same location as the muxed output. The file can be augmented and specified under Manzanita Configuration File in Advanced Settings.


CodecCodec. Specifies which codec to use to encode video streams. For configuration details, see appropriate topic following.

HEVC H/WHEVC H/W is available only when hosted on a platform having the required hardware.

Profile. Main | Main 10 | Main 10 4:2:2

Bit Rate. Specifies the video bit rate (in kbps).

MPEG-2

GeneralBit Rate. Specifies the video bit rate (in kbps). Between 512 and 300,000.

GOP Structure. Sets the GOP Structure as a combination of I frames, B frames, and P frames. I frame-only structures have a lower visual quality but are well suited for editing. Longer GOP structures have higher visual quality and are best suited for playout.


258


GOP Configuration. Specifies the type of GOP structure: Open GOP or Closed GOP.

Start with I Frame. When checked, specifies that the GOP start with an I-frame (display and coded order).

Motion Estimation Factor. Indicates how much motion estimation to use when encoding the video stream. A higher value results in higher quality and increases the encode time. The default is 80 and the range is 1 to 100.

Profile. Specifies the MPEG profile to use during encoding: High | Main | 4:2:2.

Level. Specifies the MPEG level to use during encoding: High | High 1440 | Main.

Video Performance Setting. Indicates the video quality setting to use when encoding the video stream. A higher value results in higher quality and increases the encode time. The default is 9 and the range is 0 to 31.

MPEG Encoder Version. Specifies the MainConcept MPEG encoder version to use, or set to Auto.

Video Buffer VerifierVideo Buffer Verifier. Specifies how to configure Video Buffer Verifier buffer size and delay settings:

- Do not specify VBV settings

- Specify VBV settings. When Specify VBV Settings specified, configure these settings:

VBV Buffer Size. Specifies the size of the VBV buffer in kbps. Larger values allow the encoder greater flexibility during encoding.

VBV Delay. Specifies how much time is allowed between the transmission of the first frame and its actual decode. Larger values allow the encoder greater flexibility during encoding.

x264Profile. Baseline | Main | High | High 10 | High 4:2:2


Command Line (optional)Configure the compressor using x264 command line syntax. For setting specific x264 parameters, you can enter x264 CLI commands (separated by spaces) to execute them. For best results, be sure to use long form: --bframe 5, for example. Use of short form (-b 5) is not recommended.

The following x264 command line parameters are not supported: --fake-interlaced, --nal-hrd cbr, --profile, --video-format, --bitrate.


259



X Position. The X position of the top-left of the timecode in the output video frame (range: 0 - 4096 pixels).

Y Position. The Y position of the top-left of the timecode in the output video frame (range: 0 - 2160 pixels).

Font Size. Sets the font size of the timecode (range: 6 - 120 pixels).

Text Color. Set the text color of the timecode. The default is black. You can enter simple color names, such as red, green, or white. Or enter a color hexadecimal code such as #0000DDFF, which is dark blue. The "FF" characters in this example specify the opacity, and are optional. When these characters are not included the text is completely opaque (no transparency). The pound sign (#) must be included with the hexadecimal code. When a color entry is not valid, the black default is used.



Note: The burned-in timecode will always represent the actual input timecode being used by the Input Source.


CodecCodec. Specifies which codec to use to encode audio tracks. No other codecs are provided. For configuration details, see appropriate topic following

AAC Codec

GeneralChannel Configuration. Specifies the number and layout of the audio channels: Mono | Stereo | 5.1 (C L R BL BR LFE | None).


260


PCM Codec

GeneralChannel Configuration. Specifies the number and layout of the audio channels: Mono | Stereo | number of audio channels. Note: 32 channels not supported from SDI sources.


Bit Depth. Specifies the output audio bit depth: 16 | 20 | 24.

Force One Track Per Channel. When checked, creates multiple mono tracks instead of a single multi-channel track. When checked, overrides the Label Channel Pairs Left and Right control.

Channel MapChannel Map. When checked, enables re-mapping of the incoming source audio channels to the captured file output channels. Channels are numbered from 1 to 32. Specify the number of the audio input channel to use for each output channel.

Appendix B: Containers, Codecs, and Vantage ActionsQuickTime Output

261


QuickTime OutputThe QuickTime container conforms to the IEC 14496-14 MP4 File Format standard and the QuickTime File Format Specification.

QuickTime Format Summary

VideoApple ProRes | AVC | Avid DNxHD | Avid DNxHR | DV | DVCPro HD | HEVC | HEVC H/W | IMX | Panasonic AVC-Intra | Sony XDCAM | Uncompressed | x264 | x265.

AudioPCM, 16/20/24-bit, 48Kbps, up to 32 channels; PCM/Dolby E.

Container SettingsThe QuickTime Container wraps the specified media into a QuickTime file format.

GeneralFile Extension. Specifies QuickTime (MOV). No other file extensions are available.

Tape Reel Name. This name is embedded into the container for later identification. The string that is embedded in the output should be viewable in the following supported editing applications: Final Cut Pro, Adobe Premiere Pro, and DaVinci Resolve.

Timecode Track. Specifies None | Hidden | Visible.

Caption Track. (Closed caption track) Specifies None | C608 | C708.

Fast Start. Check to improve web-based playback when downloading the file.

Header Compression. When checked, compresses QuickTime header information to improve playback responsiveness when downloading the file.

Color Space. Specifies the QuickTime file color space:

- Do not specify

- ITU-R Recommendation BT.601

- XYZ with SMPTE 428-1 (DCDM) Transfer Characteristics

- ITU-R Recommendation BT.601 with SMPTE-C Color Primaries (NTSC)

- ITU-R Recommendation BT.601 with SMPTE-C Color Primaries (PAL)




262


- RGB with BT.709 Color Primaries

Conform Aperture. Check to enable, then choose one of these options:

- Disabled

- Classic - Displays the image without applying either the pixel aspect ratio or the clean aperture. The image is displayed using the track header dimensions, meaning the decompressed picture is scaled into the track header dimensions if the encoded dimensions are different.

- Clean Aperture - Both the clean aperture and the pixel aspect ratio are applied. The dimensions of the track become equal to the clean dimensions which are equal to the display dimensions (with conformed contents).

- Production Aperture - Applies the pixel aspect ratio but not the clean aperture. The image is presented in the correct aspect ratio, but the extra pixels outside of the image that exist in the source material will be presented. The track dimensions are equal to the result of applying the pixel aspect ratio.

- Encoded Pixels - The encoded pixels are displayed intact in this mode. Under this mode the track dimensions are equal to the encoded dimensions. No scaling or transformation takes place.

Note: The Clean Aperture selection should not be used in conjunction with the Enable CLAP Atom selection. Only one or the other should be used.

Enable CLAP atom. Enables the QuickTime Clean Aperture atom.

Note: CLAP Atom insertion should not be used in conjunction with Conform Aperture > Clean Aperture selection above. Only one or the other should be used.





Clean ApertureSpecify the crop settings for Left, Right, Top, and Bottom pixels to apply to the Clean Aperture. Options include:

- Not Enabled - Turns off the crop settings for Clean Aperture.

- Specify Inset - Enables the ability to specify the Clean Aperture crop settings.


263



CodecCodec. Specifies which codec to use to encode video streams. For details, see the appropriate topic following.

Apple ProResQuality. Specifies video quality profile: 422 HQ | 422 SQ | 422 LT | 422 Proxy | 444.

AVCQuality. Specifies video quality profile: Baseline | Main | High.



Avid DNxHRQuality. Specifies video quality profile: 444 | HQX (10 bit) | HQ (220/185 Mbps) | SQ (145/120 Mbps) | LB (45/36 Mbps).

DVQuality. Specifies video quality profile: DV 25 Mbps | DVCPRO 25 Mbps | DVCPRO 50 Mbps.

DVCPRO HDNo user-settable settings are provided.

HEVCBit Rate (in kbps). Specifies the target bit rate (512 - 50,000).

HEVC (H/W)Profile. Main | Main 10 | Main 10 4:2:2 |



264


IMXQuality. Specifies video quality profile: 30 Mbps | 40 Mbps | 50 Mbps.

Panasonic AVC-IntraQuality. Specifies video quality profile: Class 50 - 4:2:0 | Class 100 - 4:2:2 | Class 200 - 4:2:2.

Sony XDCAM

Quality. Specifies video quality profile: XDCAM HD 18 Mbps CBR | XDCAM HD 25 Mbps CBR | XDCAM HD 35 Mbps VBR | XDCAM HD422 18 Mbps CBR | XDCAM HD422 25 Mbps CBR | XDCAM HD422 35 Mbps CBR | XDCAM HD422 50Mbps CBR | DCAM EX 35 Mbps VBR


x264Profile. Specifies video quality profile: Baseline | Main | High | High 10 | High 4:2:2.



The following x264 command line parameters are not supported:

--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate

x265Profile. Specifies video quality profile: Main | Main 10 | Main 10 Intra.



265




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate










266




Channel ConfigurationSpecifies the number and layout of the audio channels:

- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels

- 32 channels (currently not supported from SDI sources)


Bit Depth. Specifies the desired audio bit depth: 16 | 20 | 24 bit.

Force One Track Per Channel. When checked, creates multiple mono tracks instead of a single multi-channel track. QuickTime audio channel Assignment metadata is set to 'Mono'.


Appendix B: Containers, Codecs, and Vantage ActionsQuickTime Open Output

267


QuickTime Open OutputQuickTime Open is implemented in the Capture action with Capture ComponentPac 7.0.4 or later.

Note: Most Lightspeed Live Capture MXF files containing IMX, XDCAM or AVC-Intra, and all QuickTime Open files, are created in such a way that they can be opened for editing/playing (in Adobe Premiere Pro CC, Telestream Switch and other media applications) while they are still growing during capture. Check with your edit/player application software documentation for further details on supported formats.

Because of the unique characteristics of QuickTime Open files created by Live Capture, the duration set in the QuickTime header is hard-coded to the value of the Default Duration setting during capture. If a capture is stopped prior to the timecode specified in the Default Duration, the QuickTime Open process updates the captured file's header with the actual duration of the clip. See Important Information about Default Duration below for important details.

The QuickTime container conforms to the IEC 14496-14 MP4 File Format standard and the QuickTime File Format Specification.

Format Summary

VideoApple ProRes | Avid DNxHD | Avid DNxHR

AudioPCM, 16/20/24-bit, 48Kbps, up to 32 channels; PCM/Dolby E


GeneralFile Extension. Specifies QuickTime (MOV). No other file extensions are provided.

Tape Reel Name. This name is embedded into the container for later identification. The string that is embedded in the output should be viewable in the following supported editing applications: Final Cut Pro, Adobe Premiere Pro, and DaVinci Resolve.

Note: In DaVinci Resolve, the following setting must be changed for the Tape Reel Name to appear: Go to File > Project Settings > General Options. Enable "Assist using reel names from the:" and set it to "Embedding in source clip file".


268


Timecode Track. None, Hidden, or Visible.

Caption Track. (Closed caption track) None, C608, or C708.

Default Duration. The maximum possible duration for a captured file.

Important Information about Default DurationBe aware that the Default Duration is the maximum possible duration that can be captured with the QuickTime Open container. The default value is set to 9 hours and can be changed to any value less than 9 hours by a user.

The QuickTime Open container's Default Duration is used to set the initial duration written to the QuickTime Open file's header. This value will be reported by the QuickTime media file when it is opened by a media player or edit application while the captured file is being written to and is growing. If a capture session is stopped before the Default Duration is reached the QuickTime Open process will update the captured file's QuickTime header with the actual captured duration of the clip.

Here are three possible scenarios that you may encounter when using the QuickTime Open container:

1. A capture session is stopped before reaching, or exactly at, the Default Duration set in the Workflow. In these cases the Workflow will complete successfully. The captured QuickTime file's header will be updated with the actual captured duration of the clip.

2. Your capture session attempts to record to a duration that is beyond the Default Duration set in the Workflow. In this case the associated Workflow's origin action (and any subsequent downstream actions) will indicate that they have 'FAILED'. The Capture origin action will report the following error:

".... Failed to write sample. The Default Duration of this workflow has been reached. Capture actions configured with a QuickTime 'Open' container will automatically stop at the container's Default Duration regardless of the requested record duration. The output file created by this action will contain a duration equal to the Default Duration. In most cases the resulting output file will be playable and can be used for editing. The default duration has been exceeded."

3. If scenario #1 or #2 occur with a Workflow in the Open mode, and the action immediately following the capture origin action is an Open Copy action, the file copied by the Open Copy action will retain the original Default Duration. The copied media file will show a duration equal to the Workflow's Default Duration and will be playable and editable. Captured files stopped prior to the Default Duration (scenario #1) will contain no active media data from the point where the capture session was stopped through the end of the file. Some media players or edit applications may display errors or faults when trying to access the timeline locations with no active media data.

Header Compression. Compresses QuickTime header information to improve playback responsiveness when downloading the file.

Color Space. Set the QuickTime file color space. Options include:


269


- Do not specify









- Disabled







Note: CLAP Atom insertion should not be used in conjunction with Conform Aperture > Clean Aperture selection above. Only one or the other should be used.





270









Avid DNxHDQuality. Specifies video quality profile: 444 | HQX (10 bit, 220/185 Mbps) | HQ (220/185 Mbps) | SQ (145/120 Mbps) | SQ TR (100 Mbps) | LB (45/36 Mbps).

Quality- 444

- HQX (10 bit, 220/185 Mbps)

- HQ (220/185 Mbps)

- SQ (145/120 Mbps)

- SQ TR (100 Mbps)

- LB (45/36 Mbps)

Avid DNxHRQuality. Specifies video quality profile: 422 HQ | 422 SQ | 422 LT | 422 Proxy | 444.



271




Font Size. Sets the font size of the timecode (range: 6 - 120 pixels).







Channel ConfigurationSpecifies the number and layout of the audio channels.

- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels


272


- 12 Channels

- 14 Channels

- 16 Channels



Bit Depth. Select the desired audio bit depth. 16, 20, or 24 bit.

Force One Track Per Channel. Select to make multiple mono tracks instead of a single multi-channel track. QuickTime audio channel Assignment metadata will be set to 'Mono'.


Appendix B: Containers, Codecs, and Vantage ActionsTIFO Output

273


TIFO OutputTelestream Intermediary Format (TIFO) is an intermediate media wrapper format designed by Telestream as a uniform, interchangeable file format to ensure interoperability among Telestream's media processing solutions, including Vantage, Lightspeed Live Capture, and Pipeline. TIFO provides a lightweight, low-overhead wrapper that is essence-agnostic, with out-of-band metadata, timecode, and closed caption support.

Using TIFO improves the ability to move media files between Telestream's media processing solutions with all media essence elements and metadata intact, preserving the widest range of transcoding options.

Note: TIFO files can be opened, as they are being captured, by Telestream's Switch player and Vantage systems at a time when the captured file reports a non-zero file size. Requires Switch 4.0 or later.

TIFO Format Summary

VideoApple ProRes | AVC | Avid DNxHD | Avid DNxHR | DV | DVCProHD | HEVC | HEVC H/W | IMX | JPEG2000 Lossless | JPEG2000 Lossy | MPEG-2 | Panasonic AVC-Intra | Panasonic AVC-Ultra | Sony XAVC | Sony XDCAM | Uncompressed | x264 | x265.


Container SettingsThe TIFO Container wraps the specified media into a TIFO file format.

GeneralFile Extension. Specifies .tifo. No other extensions are provided.






274





Video Buffer VerifierChoose to specify Video Buffer Verifier buffer size and delay settings, or to use default settings.


- Specify VBV settings

VBV Buffer SizeWhen Specify VBV Settings is selected, this setting specifies the size of the VBV buffer in kbps. Larger values allow the encoder greater flexibility during encoding.

VBV DelayWhen Specify VBV Settings is selected, this setting specifies how much time is allowed between the transmission of the first frame and its actual decode. Larger values allow the encoder greater flexibility during encoding.


Avid DNxHRQuality. Specifies video quality profile: 444 | HQX (10 bit) | HQ | SQ | LB.

AVC

Profile- Baseline

- Main

- High



275


DVQuality. Specifies video quality profile: DV 25 Mbps | DVCPRO 25 Mbps | DVCPRO 50 Mbps.

DVCPRO HDNo user-settable settings are provided.

HEVCBit Rate (in kbps). Specifies the target bit rate (512 - 50,000).

HEVC H/WHEVC H/W is available only when hosted on a platform with the required hardware.

Quality. Specifies video quality profile: Main | Main 10 | Main 10 4:2:2.


IMXQuality. Specifies video quality profile: 30 Mbps | 40 Mbps | 50 Mbps.

JPEG2000 Lossless (Comprimato)The Comprimato JPEG2000 Lossless codec encodes the input video into one output video file in JPEG2000 format, using the JPEG2000 codec in lossless mode. Comprimato-based ISO/ITU still image compression provides a fast and flexible solution for high-quality, wavelet-based compression.


Configuration SettingsPixel Format. Specifies the color space, chroma subsampling, and bit depth to use for encoding.

- RGB 4:4:4 8 bit or 10 bit

- YUV 4:2:2 10 bit

- YUV 4:2:2 8 bit





276















SettingsVideo Bit Rate. Specifies the bit rate of the output in bits per second.


Pixel Format. Specifies the color space, chroma subsampling, and bit depth to use for encoding.



277


- YUV 4:2:2 10 bit

- YUV 4:2:2 8 bit















MPEG-2Bit Rate (in kbps). Specifies the target bit rate (512 - 300,000).

GOP StructureSets the GOP Structure as a combination of I frames, B frames, and P frames. I frame-only structures have a lower visual quality but are well suited for editing. Longer GOP structures have higher visual quality and are best suited for playout.

GOP ConfigurationSpecifies the type of GOP structure: Open GOP or Closed GOP.

Start with I FrameWhen checked, specifies that the GOP start with an I-frame (display and coded order).


278


Motion Estimation FactorIndicates how much motion estimation to use when encoding the video stream. A higher value results in higher quality and increases the encode time. The default is 80 and the range is 1 to 100.

Profile- High

- Main

- 4:2:2

Level- High

- High 1440

- Main

Video Performance SettingIndicates the video quality setting to use when encoding the video stream. A higher value results in higher quality and increases the encode time. The default is 9 and the range is 0 to 31.

Panasonic AVC-Intra

QualityClass 50 - 4:2:0 | Class 100 - 4:2:2 | Class 200 - 4:2:2

Panasonic AVC-Ultra

Quality- Long GOP 25

- Long GOP 50

Sony XAVCQuality. Specifies video quality profile: 100 Mbps 4:2:2.

Sony XDCAMQuality. Specifies video quality profile:

- XDCAM HD 18 Mbps CBR


- XDCAM HD 35 Mbps VBR


279


- XDCAM HD422 18 Mbps CBR



- XDCAM HD422 50Mbps CBR

- XDCAM EX 35 Mbps VBR

Uncompressed

Encode Less VBIWhen checked, the codec ignores more VBI lines in favor of frame size, in both NTSC and PAL. In NTSC (512), the video is 486 lines; in PAL (608), the video is 576 lines.

x264

Profile- Baseline

- Main

- High

- High 10

- High 4:2:2




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate


280


x265

Profile- Main

- Main 10

- Main 10 Intra




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate


X Position. The X position of the top-left of the timecode in the output video frame ( range 0 - 4096 pixels).

Y Position. The Y position of the top-left of the timecode in the output video frame (range 0 - 2160 pixels).





281






Channel ConfigurationSelect the number and layout of the audio channels.

- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels




Force One Track Per Channel. Select to make multiple mono tracks instead of a single multi-channel track.


Appendix B: Containers, Codecs, and Vantage ActionsProxy TIFO Output

282


Proxy TIFO OutputTelestream Intermediary Format (TIFO) is an intermediate media wrapper format designed by Telestream as a uniform, interchangeable file format to ensure interoperability among Telestream's media processing solutions, including Vantage, Lightspeed Live Capture, and Pipeline. TIFO provides a lightweight, low-overhead wrapper that is essence-agnostic, with out-of-band metadata, timecode, and closed caption support.


Note: TIFO files can be opened as they are being captured, by Telestream's Switch player and Vantage systems at a time when the captured file reports a non-zero file size. Requires Switch 4.0 or later.

TIFO Format Summary

VideoApple ProRes | AVC | Avid DNxHD LB










283



AVC

Profile- Baseline

- Main

- High


DNxHDQuality. Specifies video quality profile: LB (45/36 Mbps).

Apple ProResQuality. Specifies video quality profile: 422 Proxy.









284






- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels






Appendix B: Containers, Codecs, and Vantage ActionsProxy MP4 Output

285


Proxy MP4 OutputThe Proxy MP4 container conforms to IEC 14496-14 MP4 file format standard.

Note: MP4 files do not contain a timecode track.

Container SettingsThe Proxy MP4 Container wraps the specified media into an MP4 file format.

File Extension. MP4 selected by default. No other selections are available.

Video Stream DetailsSelect the Video Stream component to display its details on the right.

Codec (AVC)Codec. Specifies AVC as the codec to use to encode video tracks. No other codecs are provided.

AVCSame as Source. When enabled, the width and height of the source is passed through. Width and Height parameters set in the action for the AVC codec are ignored.

CAUTION: Same as Source cannot be used when UHD/4K is set as the primary output.

Width. Specifies the width of the frame, in pixels (320 - 720).

Height. Specifies the height of the frame, in pixels (240 - 480).



Codec (AAC)Codec. Specifies AAC as the codec to use to encode audio tracks. No other codecs are provided.

Channel Configuration. Specifies the number and layout of the audio channels. Mono | Stereo | 5.1 (C L R BL BR LFE).

Appendix B: Containers, Codecs, and Vantage ActionsProxy MXF RDD 25 Output

286


Proxy MXF RDD 25 OutputThe Proxy MXF RDD 25 container conforms to the RDD 25 MXF file format standard.

Note: RDD 25 proxy files can be opened in Telestream's Switch player, and other applications, as they are being captured and are growing in size. Requires Switch 4.0 or later.

Container SettingsThe Proxy MXF RDD 25 container wraps the specified media into a MXF file format.

File Extension. Specifies .mxf. No other extensions are available.


Codec (AVC)Codec. Specifies AVC as the codec to use to encode video tracks. No other codecs are provided.

AVC

Same as SourceWhen enabled, the width and height of the source is passed through. Width and Height parameters set in the action for the AVC codec are ignored.







Channel Configuration. Select the number and layout of the audio channels.


287


AAC- Mono

- Stereo

- 5.1 (C L R BL BR LFE)

Appendix B: Containers, Codecs, and Vantage ActionsProxy HLS Output

288


Proxy HLS OutputHTTP Live Streaming (HLS) is an HTTP-based adaptive bitrate streaming communications protocol.

Container SettingsThe Proxy HLS Container wraps the specified media into an HLS file format.

File Extension. m3u8 selected by default. No other selections are available.

GOP Length. Specifies the GOP length in number of frames.

GOPs per Segment. Number of GOPs per Segment.

Note: Segment duration should be a multiple of GOP duration. Lower segment duration can reduce latency.

SCTE date range. Adds SCTE date messages to the manifest files.

Floating point duration. Enables floating point duration. When disabled, integer values are used.


Codec (AVC)Codec. Specifies AVC as the codec to use to encode video. No other codecs are provided.

AVCSame as Source. When enabled, the width and height of the source is passed through. Width and Height parameters set in the action for the AVC codec are ignored.






Appendix B: Containers, Codecs, and Vantage ActionsProxy HLS Output

289



Channel Configuration. Specifies the number and layout of the audio channels. Mono | Stereo | 5.1 (C L R BL BR LFE).


Appendix B: Containers, Codecs, and Vantage ActionsTape Action Output Containers

290


Tape Action Output ContainersThese output containers are included in the Capture action:

■ MXF OP1a Output

■ MPEG2-TS Output

■ QuickTime Output

■ QuickTime Open Output

■ TIFO Output

■ Proxy TIFO Output

■ Proxy MP4 Output

■ Proxy MXF RDD 25 Output

■ Poster Frame


291


MXF OP1a OutputThe MXF container encodes the media and produces an MXF Operational Pattern 1a (OP-1a, SMPTE 379M-2004) file with a generic container mapped to Lightspeed Live Capture's available video essences.

Note: Most Lightspeed Live Tape Capture MXF files containing IMX, XDCAM or AVC-Intra are created in such a way that they can be opened for editing/playing (in Adobe Premiere Pro CC, Telestream Switch and other media applications) while they are still growing during capture. Check with your edit/player application software documentation for further details on supported formats.


Select the container to display its settings in the configuration panel on the right.

Generic MXF Format Summary

VideoAVC | Avid DNxHD | DV | DVCProHD | IMX | JPEG2000 Lossless | JPEG2000 Lossy | Panasonic AVC-Intra | Panasonic AVC-Ultra | Uncompressed |Sony XAVC | Sony XDCAM | x264

AudioPCM, 16/20/24-bit, 48Kbps, up to 16 channels

TimecodeThe following standards, available from SMPTE, describe the timecode track:

SMPTE 377M, Timecode track

SMPTE 385M, System item

SMPTE 405M, System item (DNxHD)

MXF Applicable StandardsThe following standards, available from SMPTE, describe the MXF format:

SMPTE 331M-2004, Elements and Metadata Definitions for SDTI-CP


292


SMPTE 377M-2004, Material Exchange Format (MXF)

SMPTE 378M-2004, MXF Operational Pattern 1a

SMPTE 379M-2004, MXF Generic Container

SMPTE 382M-2007, Mapping AES3 and Broadcast Wave Audio into MXF Generic Container - DV (AES3), DNxHD, (BWF)

SMPTE 383M-2008, Mapping DV-DIF Data into MXF Generic Container - DV

SMPTE 385M-2004, Mapping SDTI-CP Essence and Metadata into MXF Generic Container - DV, IMX

SMPTE 386M-2004, Mapping Type D-10 Essence Data to MXF Generic Container - IMX

SMPTE 394M-2006, System Scheme 1 for MXF Generic Container DNxHD

SMPTE 405M-2006, Elements and Individual Data Items for MXF Generic Container System Scheme 1 - DNxHD

SMPTE 436M-2006, MXF Mappings for VBI Lines and Ancillary Data Packets

SMPTE 2019-4-2008, Mapping VC-3 Coding Units into MXF Generic Container - DNxHD

SMPTE RDD03, eVTR MXF Interoperability Specification - DV, IMX

SMPTE RDD 9-2009, MXF Interoperability Specification of Sony MPEG Long GOP Product

SMPTE ST 298-2009, Universal Labels for Unique Identification of Digital Data

SMPTE ST 326:2000, Television -SDTI Content Package Format (SDTI-CP)

SMPTE ST 381-1:2005, Television-Material Exchange Format (MXF) - Mapping MPEG Streams into the MXF Generic Container

SMPTE RDD 25:2014, AVC MXF Proxies

Note: The resulting MXF (OP-1a) file can contain VANC data (SMPTE 436M) if present within the incoming SDI stream.

Output SettingsMXF OP-1a Config Name. Specifies the custom name of this output configuration. Displayed as a Configuration Template (along with all other outputs in this action) in the Capture Web app, so that the operator can select a specific Output configuration for the current capture session.


293


Container Settings

GeneralFile Extension. Specifies the extension of the output file.

436 Data Track. Specifies how to add SMPTE 436 data (None | Ancillary | VBI) to the output.

Partition Strategy. Specifies how to apply the MXF partitioning (or None).

Broadcast Wave Audio. When checked, sets the audio tracks to Broadcast Wave format, adding metadata such as timestamps to the audio stream.

Mpeg Picture Element. When checked, specifies that MPEG picture elements should be used for Avid and Adobe Premiere Pro compatibility.

Telestream Index. When checked, a proprietary, sidecar Telestream Index file is created for use in specific customer workflows. For details, please contact Customer Service.

Aspect Ratio ModeAspect Ratio Mode. Specifies how to set the display or pixel aspect ratio of the output:

When Automatic is selected, the aspect ratio is set automatically, based on the detected content.

Display Aspect Ratio. When Display Aspect Ratio is selected, specifies 4:3 | 16:9.

Pixel Aspect Ratio. When checked, specifies the selected pixel aspect ratio.

Video Stream DetailsSelect the Video Stream component to display its settings on the right.

CodecCodec. Specifies the codec used to encode the output video stream.

AVCProfile. Specifies the profile to use for encoding.

Bit Rate. Specifies the bit rate, in kbps.

Avid DNxHDQuality. Specifies the quality setting to use for encoding.

DVQuality. Specifies the quality setting to use for encoding.


294


DVCPRO HDThere are no user-settable options for the DVCPRO HD codec.

IMXQuality. Specifies the quality setting to use for encoding.


















295




















296





Panasonic AVC-IntraQuality. Specifies the quality setting to use for encoding.

Panasonic AVC-UltraQuality. Specifies video quality profile: AVC Ultra Long GOP 25 | AVC Ultra Long GOP 50

Sony XAVCQuality. Specifies the quality setting to use for encoding.

Sony XDCAMQuality. Specifies the quality setting to use for encoding.


x264Profile. Specifies the profile to use for encoding.

Bit Rate. Specifies the bit rate, in kbps.

Command Line. Enables you to optionally configure the codec using x264 command line syntax. For setting specific x264 parameters, you can enter x264 CLI commands (separated by spaces) to execute them. For best results, be sure to use long form.

Time Code Burn-in FilterCheck to implement the Time Code Burn-in Filter, which imprints the media timecode into each output video frame.

Note: The burned-in timecode always represents the actual input timecode being used by the Input Source.

X|Y Position. Specifies (in pixels from the upper left corner origin) the line upon which to place the timecode text on the video frame.


297


Font Size. Specifies the font size, in pixels.

Text Color. Specifies the color of the text. Enter a color name (white, red, green, etc.) or an #RGBA code (for example, #0000DD). The alpha channel is optional.

Background Color. Specifies the color of the area behind the text. Enter a color name (white, red, green, etc.) or an #RGBA code (for example, #0000DD). The alpha channel is optional.

Timecode Transparency. Specifies the opacity of the timecode text as a real number. Zero is fully transparent, and 1.00 (100%) is fully opaque.


Codec (PCM)Codec. Specifies PCM as the codec used to generate audio tracks. No other codecs provided.

GeneralChannel Configuration. Specifies Mono | Stereo | number of the audio channels. Note: 32 channels not supported from SDI sources.

Label Channel Pairs Left/Right. When checked, forces the first channel pair to be labeled Left and Right, unless Force One Track Per Channel is selected, in which case this setting is ignored.

Bit Depth. Specifies the output audio bit depth. 16 | 20 | 24.

Force One Track Per Channel. When checked, creates multiple mono tracks instead of a single multi-channel track.



298


MPEG2-TS OutputThe MPEG2-TS output container encodes media and saves it as an MPEG2 Transport Stream file.



Format Summary

VideoMPEG-2 | x264

AudioPCM

ContainerMPEG2-TS Config Name. Specifies the custom name of this output configuration. Displayed as a Configuration Template (along with all other outputs in this action) in the Capture Web app, so that the operator can select a specific Output configuration for the current capture session.

Container SettingsFile Extension. Specifies the file extension of the generated MPEG2 TS file.

File Bit Rate. (Default 19,000,000 bps). If unchecked, the Multiplexer uses the minimum rate as computed from the sum of all maximum rates for elementary streams, data streams, PSI streams and necessary overhead.

List Audio Streams Before Video Streams. When checked, lists audio streams before video streams in the PMT stream order.

PAT Rate. (Default 10.0 tables per second.) Specifies the repetition rate of the Program Association Table in the output stream. The PAT lists all programs in a transport stream, each of which is identified by a 16-bit Program Number.

PMT Rate. (Default 10.0 tables per second.) Specifies the repetition rate of the Program Map Table in the output stream. Each program listed in the PAT has a PMT (with PID) containing information about the program.


299


Transport ID. (Default 0.) Specifies the ID number for this transport stream.

PAT Version. (Default 0.) Specifies the version number of the Program Association Table.

Program Number. (Default 1.) Specifies the ID number of a specific program.

PMT PID. (Default 480.) This sets the Packet ID used for the Program Map Table.

PCR PID. (Default unselected/zero.) Specifies the Packet ID that carries the Program Clock Reference for this program. Set to the first video PID value if not specified.

Maximum PCR Interval. (Default 37 ms.) Specifies the maximum time between Program Clock References for this stream.

PCR on every PES header. When checked, inserts a PCR in each packet that has a PES header.

No Empty Adaptation Fields. When checked, forces the Multiplexer to avoid using zero-length adaptation field video packets.

VBR Transport stream. When checked, the Multiplexer creates a VBR transport stream; no attempt is made to maintain the bit rate.

Error Behavior. (Default: Fail on error.) Specifies how the action responds to an error.

Error/Warning Threshold. (Default 1.) Specifies the number of errors before the action enters the error state and the number of warnings that trigger a Fail on Warning or Error. This parameter has no effect when Error Behavior is set to Always Complete.

Treat Buffer Underflows/Overflows as Errors. When checked, buffer underflow or overflow warnings are treated as errors.

2-Pass Multiplexing. When checked, performs 2-pass multiplexing. Only use if you need to correct excessive bitrate fluctuations in the encoded stream resulting in video decoder underflow errors. The second pass is only executed if the first pass fails.

Generate Config File. Generates and places a Manzanita-compliant configuration file using the current settings into the same location as the output. The configuration file can be utilized in the IPTV transcoder action or in other actions that utilize Manzanita configuration files.


CodecGenerate Config File. Specifies which codec to use to encode the output file.


300


MPEG-2 Codec

GeneralBit Rate (in kbps). Specifies the bit rate in kbps.

GOP Structure. Specifies the GOP Structure as a combination of I frames, B frames, and P frames. I frame-only structures have a lower visual quality but are well suited for editing. Longer GOP structures have higher visual quality and are best suited for playout.

GOP Configuration. Specifies the type of GOP structure.

Start with I Frame. When checked, specifies that the GOP start with an I-frame (display and coded order).

Motion Estimation Factor. Specifies how much motion estimation to use when encoding the video stream. A higher value results in higher quality and increases encoding time.

Profile. Specifies the profile to use for encoding.

Level. Specifies the level to use for encoding.

Chroma. Select the Chroma Subsampling to use.

Video Buffer VerifierVideo Buffer Verifier. Specifies whether or not to use the default settings or custom VBV settings. When Specify VBV Settings is set, configure these controls:

VBV Buffer Size. Specifies the size of the VBV buffer in kbps. Larger values allow the encoder greater flexibility during encoding.

VBV Delay. Specifies how much time is allowed between the transmission of the first frame and its actual decode. Larger values allow the codec greater flexibility during encoding.

x264 CodecProfile. Specifies the profile to use for encoding.

Bit Rate (in kbps). Specifies the bit rate in kbps.

Command Line. Enables you to optionally configure the codec using x264 command line syntax. For setting specific x264 parameters, you can enter x264 CLI commands (separated by spaces) to execute them. For best results, be sure to use long form.



301









CodecSpecifies that the audio is encoded using the PCM codec. No other codecs are available.

GeneralChannel Configuration. Specifies the number and layout of the audio channels.

NOTE: 32 channels are not supported from SDI sources.


Bit Depth. Specifies the audio bit depth.

Force One Track Per Channel. When checked, the codec creates multiple mono tracks instead of a single multi-channel track.

Channel MapOutput Channel (1... 32). When checked, enables re-mapping of the incoming source audio channels to the captured file output channels. Channels are numbered from 1 to 32. Specify the number of the audio input channel to use for each output channel.


302


QuickTime OutputThe QuickTime container conforms to the IEC 14496-14 MP4 File Format standard and the QuickTime File Format Specification.


QuickTime Format Summary

VideoApple ProRes | AVC | Avid DNxHD | Avid DNxHR | DV | DVCProHD | HEVC | HEVC (H/W) | IMX | Panasonic AVC-Intra | Sony XDCAM | Uncompressed | x264 | x265



General PanelFile Extension. QuickTime (MOV) selected by default. No other selections are available.

Timecode Track. None, Hidden, or Visible.

Caption Track. (Closed caption track) None, C608, or C708.

Fast Start. Enable Fast Start to improve web based playback when downloading the file.

Header Compression. Compresses QuickTime header information to improve playback responsiveness when downloading the file.

Color Space. Set the QuickTime file color space. Options include:

- Do not specify






303


- ITU-R Recommendation BT.709 Color Primaries



- Disabled







CLAP Atom insertion should not be used in conjunction with Conform Aperture > Clean Aperture selection above. Only one or the other should be used.

Aspect Ratio ModeSelect an option to specify the display aspect ratio of the output.

- Automatic - Automatically select aspect ratio setting based on detected content.

- Display Aspect Ratio - Select either 4:3 or 16:9.

- Pixel Aspect Ratio - Select 1:1, 4:3, 8:9, 10:11, 12:11, 16:11, 16:15, 32:27, 40:43, or 64:45.





304



CodecSelect a codec to produce the desired capture output. Additional configuration parameters may also be present.

Apple ProRes

Quality- 422 HQ

- 422 SQ

- 422 LT

- 422 Proxy

- 444

AVC

Profile- Baseline

- Main

- High

Bit Rate (in kbps) - Between 512 and 50,000

Avid DNxHD

Quality- 444

- HQX (10 bit)

- HQ (220/185 Mbps)

- SQ (145/120 Mbps)

- SQ TR (100/100 Mbps)

- LB (45/36 Mbps)


305


Avid DNxHR

Quality- 444

- HQX (10 bit)

- HQ

- SQ

- LB

DV

Quality- DV 25 Mbps

- DVCPRO 25 Mbps

- DVCPRO 50 Mbps

DVCPRO HDNo options

HEVC


HEVC (H/W)

Profile- Main

- Main 10

- Main 10 4:2:2

Bit Rate (in kbps)- Between 512 and 50,000

IMX

Quality- 30 Mbps


306


- 40 Mbps

- 50 Mbps

Panasonic AVC-Intra


Sony XDCAM

Quality- XDCAM HD 18 Mbps CBR








Uncompressed (10-bit)Encode Less VBI. When checked, the codec removes the top 32 lines for SD sources that contain VBI data, ignoring more VBI lines in favor of frame size, in both NTSC and PAL. In NTSC (512), the video is 486 lines; in PAL (608), the video is 576 lines.

x264

Profile- Baseline

- Main

- High

- High 10

- High 4:2:2



307




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate

x265

Profile- Main

- Main 10

- Main 10 Intra




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate


- X Position: Burn timecode in at 0-4096 pixels from upper left corner.


308


- Y Postion: Burn in timecode at 0-2160 pixels from upper left corner.

- Font Size: Burned in timecode font size, 6-120 points.

- Text Color: Color of the text characters. Enter a color name (white, red, green, etc.), an #RGB code, or #0000DD.

- Background Color: Color of the area behind the text. Enter a color name (white, red, green, etc.), an #RGB code, or #0000DD.

- Timecode Transparency: The opacity of the timecode characters from 0.00 to 1.00 (0 to 100%). Zero is fully transparent, and 1.00 (100%) is fully opaque.


CodecPCM is selected by default. No other selections are available.

General


- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels




Force One Track Per Channel. Select to make multiple mono tracks instead of a single multi-channel track. QuickTime audio channel Assignment metadata will be set to 'Mono'.


309


Channel MapAllows re-mapping of the incoming source audio channels to the captured file output channels. Channels are numbered from 1 to 32. Specify the number of the audio input channel to use for each output channel.


310


TIFO OutputTelestream Intermediary Format (TIFO) is an intermediate media wrapper format designed by Telestream as a uniform, interchangeable file format to ensure inter-operability among Telestream's media processing solutions, including Vantage, Lightspeed Live Capture, and Pipeline. TIFO provides a lightweight, low-overhead wrapper that is essence-agnostic, with out-of-band metadata, timecode, and closed caption support.



TIFO Format Summary

VideoApple ProRes | AVC | Avid DNxHD | Avid DNxHR | DV | DVCProHD | HEVC | HEVC H/W | IMX | JPEG2000 Lossless | JPEG2000 Lossy | MPEG-2 | Panasonic AVC-Intra | Panasonic AVC-Ultra | Sony XAVC | Sony XDCAM | Uncompressed | x264 | x265



General PanelFile Extension. TIFO selected by default. No other selections are available.

Aspect Ratio ModeSelect an option to specify the display aspect ratio of the output.

- Automatic - Automatically select aspect ratio setting based on detected content.

- Display Aspect Ratio - Select either 4:3 or 16:9.

- Pixel Aspect Ratio - Select 1:1, 4:3, 8:9, 10:11, 12:11, 16:11, 16:15, 32:27, 40:43, or 64:45.


311



CodecSelect a codec to produce the desired capture output. Additional configuration parameters may also be present.

Apple ProRes

Quality- 422 HQ

- 422 SQ

- 422 LT

- 422 Proxy

- 444

AVC

Profile- Baseline

- Main

- High


Avid DNxHD

Quality- 444

- HQX (10 bit)

- HQ (220/185 Mbps)

- SQ (145/120 Mbps)

- SQ TR (100/100 Mbps)

- LB (45/36 Mbps)


312


Avid DNxHR

Quality- 444

- HQX (10 bit)

- HQ

- SQ

- LB

DV

Quality- DV 25 Mbps

- DVCPRO 25 Mbps

- DVCPRO 50 Mbps

DVCPRO HDNo options

HEVC


HEVC H/WHEVC H/W is available only when hosted on a platform having the required hardware.

Profile- Main

- Main 10

- Main 10 4:2:2

Bit Rate. Specifies the video bit rate (in kbps).

IMX

Quality- 30 Mbps

- 40 Mbps


313


- 50 Mbps



















314





















315



MPEG-2






Profile- High

- Main

- 4:2:2

Level- High

- High 1440

- Main



- Specify VBV settings: VBV Buffer Size (512-300,000); VBV Delay (50-750).


316


When Specify VBV Settings is selected, VBV Buffer Size specifies the size of the VBV buffer in kbps. Larger values allow the encoder greater flexibility during encoding.

When Specify VBV Settings is selected, VBV Delay specifies how much time is allowed between the transmission of the first frame and its actual decode. Larger values allow the encoder greater flexibility during encoding.

Panasonic AVC-Intra


Panasonic AVC-UltraQuality. Specifies video quality profile: AVC Ultra Long GOP 25 | AVC Ultra Long GOP 50

Sony XAVC

Quality- 100 Mbps 4:2:2

Sony XDCAM











317


x264

Profile- Baseline

- Main

- High

- High 10

- High 4:2:2




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate

x265

Profile- Main

- Main 10

- Main 10 Intra




318



--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate

HEVC (H/W)

Profile- Main

- Main 10

- Main 10 4:2:2



- X Position: Burn timecode in at 0-4096 pixels from upper left corner.

- Y Postion: Burn in timecode at 0-2160 pixels from upper left corner.

- Font Size: Burned in timecode font size, 6-120 points.

- Text Color: Color of the text characters. Enter a color name (white, red, green, etc.), an #RGB code, or #0000DD.

- Background Color: Color of the area behind the text. Enter a color name (white, red, green, etc.), an #RGB code, or #0000DD.

- Timecode Transparency: The opacity of the timecode characters from 0.00 to 1.00 (0 to 100%). Zero is fully transparent, and 1.00 (100%) is fully opaque.


CodecPCM is selected by default. No other selections are available.


319


General


- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels







320


Proxy TIFO OutputTelestream Intermediary Format (TIFO) is an intermediate media wrapper format designed by Telestream as a uniform, interchangeable file format to ensure interoperability among Telestream's media processing solutions, including Vantage, Lightspeed Live Capture, and Pipeline. TIFO provides a lightweight, low-overhead wrapper that is essence-agnostic, with out-of-band metadata, timecode, and closed caption support.


Note: TIFO files can be opened as they are being captured, by Telestream's Switch player and Vantage systems at a time when the captured file reports a non-zero file size. Requires Switch 4.0 or later.

TIFO Format Summary

VideoApple ProRes | AVC | Avid DNxHD LB










321



AVC

Profile- Baseline

- Main

- High


Avid DNxHDQuality. Specifies video quality profile: LB (45/36 Mbps).

Apple ProResQuality. Specifies video quality profile: 422 Proxy.









322






- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels







323


Proxy MP4 OutputThe Proxy MP4 output container encodes media and saves it as an MP4 file. The MP4 container conforms to IEC 14496-14 MP4 file format standard.

MP4 files do not contain a timecode track.



Format Summary

VideoAVC

AudioPCM

ContainerMP4 Config Name. Specifies the custom name of this output configuration. Displayed as a Configuration Template (along with all other outputs in this action) in the Capture Web app, so that the operator can select a specific Output configuration for the current capture session.

Container SettingsFile Extension. Specifies the file extension of the generated MP4 file.

Aspect Ratio ModeAspect Ratio Mode. Specifies how to set the display or pixel aspect ratio of the output:

When Automatic is selected, the aspect ratio is set automatically, based on the detected content.

Display Aspect Ratio. When Display Aspect Ratio is selected, specifies 4:3 | 16:9.

Pixel Aspect Ratio. When checked, specifies the selected pixel aspect ratio.


324



Codec (AVC)Codec. Specifies AVC. No other codecs provided.

Same as Source. When enabled, the width and height of the source is passed through. Width and Height parameters are ignored.


Width. Specifies the output frame width in pixels.

Height. Specifies the output frame height in pixels.

Bit Rate. Specifies the output video bit rate in kbps.









CodecSpecifies that the audio is encoded using the PCM codec. No other codecs are available.


325


GeneralChannel Configuration. Specifies the number and layout of the audio channels.

NOTE: 32 channels are not supported from SDI sources.


Bit Depth. Specifies the audio bit depth.

Force One Track Per Channel. When checked, the codec creates multiple mono tracks instead of a single multi-channel track.

Channel MapOutput Channel (1... 32). When checked, enables re-mapping of the incoming source audio channels to the captured file output channels. Channels are numbered from 1 to 32. Specify the number of the audio input channel to use for each output channel.


326


Proxy MXF RDD 25 OutputThe Proxy MXF RDD 25 container conforms to the RDD 25 MXF file format standard.

Note: RDD 25 proxy files can be opened in Telestream's Switch player, and other applications, as they are being captured and are growing in size. Requires Switch 4.0 or later.

Container SettingsThe Proxy MXF RDD 25 container wraps the specified media into a MXF file format.

File Extension. Specifies .mxf. No other extensions are available.


Codec (AVC)Codec. Specifies PCM as the codec to use to encode audio tracks. No other codecs are provided.

AVC








Channel Configuration. Select the number and layout of the audio channels.

Appendix B: Containers, Codecs, and Vantage ActionsPoster Frame

327


AAC- Mono

- Stereo


Poster FrameThe Poster Frame output creates a small thumbnail bitmap image of the first frame of the input.

Use the Poster Frame output option when you need to have some type of output to satisfy the ability to activate the workflow when you have downstream actions, but you plan to delete the file and want the output to be a small file size that uses very little computing power and takes a small amount of hard drive space.


Container SettingsThe Poster Frame Container creates a small bitmap image file.

File Extension. Specifies the extension of the file name: bmp. No other selections are available.

Appendix B: Containers, Codecs, and Vantage ActionsPrimary Output - Video Codecs

328


Primary Output - Video CodecsThe following Primary Output video codecs are available when configuring the Capture and Tape actions. The codec availability and options vary for different containers.

■ Apple ProRes

■ AVC

■ Avid DNxHD

■ Avid DNxHR

■ DV/DVCPro

■ DVCPRO HD

■ HEVC

■ IMX

■ JPEG2000 LossLess (Comprimato)

■ JPEG2000 Lossy (Comprimato)

■ MPEG-2

■ Panasonic AVC-Intra

■ Panasonic AVC-Ultra

■ Sony XDCAM

■ Uncompressed (10-bit)

■ x264

■ x265/HEVC

■ XAVC

Apple ProRes

Supported Container- QuickTime

- QuickTime ‘Open’

- TIFO

Quality- 422 HQ

- 422 SQ

- 422 LT

- 422 Proxy

- 444


329


AVC

Supported Container- MXF OP1a

- QuickTime

- TIFO

Profile- Baseline

- Main

- High


Avid DNxHD


- QuickTime

- TIFO

Quality- 444

- HQX (10 bit, 220/185 Mbps)

- HQ (220/185 Mbps)

- HQ TR (145/120 Mbps)

- SQ (145/120 Mbps)

- SQ TR (100 Mbps)

- LB (45/36 Mbps)

Avid DNxHR


- QuickTime

- TIFO


330


Quality- 444

- HQX (10 bit)

- HQ

- SQ

- LB

DV/DVCPro


- QuickTime

- TIFO

Quality- DV 25 Mbps

- DVCPRO 25 Mbps

- DVCPRO 50 Mbps

DVCPRO HD


- QuickTime

- TIFO

HEVC


- TIFO


HEVC (H/W)

Profile- Main


331


- Main 10

- Main 10 4:2:2


IMX


- QuickTime

- TIFO

Quality- 30 Mbps

- 40 Mbps

- 50 Mbps

JPEG2000 LossLess (Comprimato)

Supported Containers - MXF OP1a

- TIFO

DescriptionThe Comprimato JPEG2000 LossLess codec encodes the input video into one output video file in JPEG2000 format, using the JPEG2000 codec in lossless mode. Comprimato-based ISO/ITU still image compression provides a fast and flexible solution for high-quality, wavelet-based compression.


General Pixel Format. Specifies the color space, chroma subsampling, and bit depth to use for encoding.



332


- YUV 4:2:2 10 bit

- YUV 4:2:2 8 bit




Code Block Width and Height. Specifies the height and width (in pixels) of a code block to process.


Decomposition Levels. Specifies the Discrete Wavelet Transform resolution.

Tile-Part Length Markers. When checked, specifies that Tile Length Markers are used.


Start of Packet Header Markers. When checked, Start of Packet marker segments are generated.





JPEG2000 Lossy (Comprimato)

Supported Containers - MXF OP1a

- TIFO

DescriptionThe Comprimato JPEG2000 Lossy codec encodes the input video into one output video file in JPEG2000 format, using the JPEG2000 codec in lossy mode. Comprimato-based ISO/ITU still image compression provides a fast and flexible solution for high-quality, wavelet-based compression.



333


GeneralVideo Bit Rate. Specifies the bit rate, per second.

Quantization Coefficient. Specifies quality (0-100). If set toward the lower range it reduces data correspondingly and quality decreases; if set to the upper range it increases data and quality. However, the default value of 0 (zero) applies no coefficient (effectively disables the feature), resulting in the video being encoded at the full data rate. Un-check the Use Default Quantization Coefficient option to enable this ability to specify the quality.

Pixel Format. Specifies the color space, chroma subsampling, and bit depth to use for encoding.

- RGB 4:4:4 8 bit or 10 bit @50,000 bp/s

- YUV 4:2:2 10 bit @50,000 bp/s

- YUV 4:2:2 8 bit @50,000 bp/s




Code Block Width and Height. Specifies the height and width (in pixels) of a code block to process.

Packet Progression. Specifies the order of packet progression.

Decomposition Levels. Specifies the Discrete Wavelet Transform resolution.

Tile-Part Length Markers. When checked, specifies that Tile Length Markers are used.


Start of Packet Markers. When checked, Start of Packet marker segments are generated.






334


MPEG-2

Supported Container- MPEG2-TS

- TIFO






ProfileAdjusts MPEG profile:

- High

- Main

- 4:4:2

LevelAdjusts MPEG level:

- High

- High 1440

- Main

ChromaAdjusts chroma subsampling:

- 4:2:0


335


- 4:4:2

Video Performance SettingIndicates the video quality setting to use when encoding the video stream. A higher value results in higher quality and increases the encode time. The default is 9 and the range is 0 to 31.



- Specify VBV settings

VBV Buffer SizeWhen Specify VBV Settings is selected, this setting specifies the size of the VBV buffer in kbps. Larger values allow the encoder greater flexibility during encoding.

VBV DelayWhen Specify VBV Settings is selected, this setting specifies how much time is allowed between the transmission of the first frame and its actual decode. Larger values allow the encoder greater flexibility during encoding.

Panasonic AVC-Intra


- QuickTime

- TIFO

Quality- 50 Mbps 4:2:0

- 100 Mbps 4:2:2

- 200 Mbps 4:2:2

Panasonic AVC-Ultra


- TIFO


336


Quality. Specifies video quality profile: AVC Ultra Long GOP 25 | AVC Ultra Long GOP 50

Sony XDCAMSupported Container- MXF OP1a

- QuickTime

- TIFO









Uncompressed (10-bit)


- QuickTime

- TIFO

x264

Supported Container- MPEG2-TS

- MXF OP1a

- QuickTime

- TIFO

Profile- Baseline


337


- Main

- High

- High 10

- High 4:2:2




--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate

x265/HEVC

Note: x265/HEVC supports progressive scan inputs only.


- TIFO

Profile- Main

- Main 10

- Main 10 Intra


Command Line (option)Configure the compressor using x265 command line syntax. For setting specific x265 parameters, you can enter x265 CLI commands (separated by spaces) to execute them.


338


For best results, be sure to use long form: --bframe 5, for example. Use of short form (-b 5) is not recommended.


--fake-interlaced

--nal-hrd cbr

--profile

--video-format

--bitrate

XAVC


- TIFO

Quality- Class 100 Mbps 4:2:2

- Class 300 Mbps 4:2:2

- Class 480 Mbps 4:2:2

Appendix B: Containers, Codecs, and Vantage ActionsPrimary Output - Audio Codec

339


Primary Output - Audio CodecThe following Primary Output audio codec is available in Capture and Tape actions.

PCMSupported Containers- MPEG2-TS

- MXF OP1a

- QuickTime

- TIFO

Channel ConfigurationSelect the audio output channel configuration.

- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels


Bit DepthSelect the desired audio bit depth.

- 16-bit

- 20-bit

- 24-bit

Force One Track Per ChannelSelect to make multiple mono tracks instead of a single multi-channel track. QuickTime audio channel Assignment metadata is set to 'Mono'.

Appendix B: Containers, Codecs, and Vantage ActionsPrimary Output - Audio Codec

340



Appendix B: Containers, Codecs, and Vantage ActionsSecondary Output - Video Codecs

341


Secondary Output - Video CodecsThe following Secondary Output video codecs are available when configuring the Capture or Tape actions.

AVCSupported Container- Proxy MXF OP1a RDD25

- Proxy MP4

- Proxy TIFO



Width- 320-720

Height - 240-480

Bit Rate (in kbps) - 512-10,000

ProRes ProxyNo configurable options. Output is the same size as the source.

DNxHD LBNo configurable options. Output is the same size as the source. DNXHD LB only supports 1080p sources at these resolutions: 23.98,24, 25, 29.97.

Appendix B: Containers, Codecs, and Vantage ActionsSecondary Output - Audio Codecs

342


Secondary Output - Audio CodecsThe following Secondary Output audio codecs are available when configuring the Capture or Tape actions.

AACSupported Container- Proxy MXF OP1a RDD25

- Proxy MP4

- Proxy TIFO

Channel Configuration- Mono

- Stereo


PCMSupported Container- MP4

Channel ConfigurationSelect the audio output channel configuration.

- Mono

- Stereo

- 4 Channels

- 6 Channels

- 8 Channels

- 10 Channels

- 12 Channels

- 14 Channels

- 16 Channels


Bit DepthSelect the desired audio bit depth.

- 16-bit

Appendix B: Containers, Codecs, and Vantage ActionsSecondary Output - Audio Codecs

343


- 20-bit

- 24-bit

Force One Track Per ChannelSelect to make multiple mono tracks instead of a single multi-channel track. QuickTime audio channel Assignment metadata is set to 'Mono'.


Appendix B: Containers, Codecs, and Vantage ActionsVantage Actions

344


Vantage ActionsThe following topics briefly describe workflow actions available in the Capture edition of the Vantage Workflow Designer. Details of action features and operation are described in the man page and Vantage User Guide available in each action’s Inspector. Click (M=man page / ?=User Guide) in the Inspector upper right corner.

For additional information about using the Workflow Designer and its actions to create Capture and Tape workflows, refer to the Creating Capture & Tape Action Workflows chapter in this guide.

■ Live Actions

■ Cloud Actions

■ Metadata Actions

■ Transcode Actions

■ Transport Actions

■ VidChecker Action

Live ActionsThe Live Service operates in Vantage on a Lightspeed Live Capture Server and includes the Capture and Tape actions that capture files from live or tape sources.

■ Capture Action

■ Tape Action

Capture ActionA Capture action is an origin action—it can only be used as the first action in a workflow. It operates in normal mode and also supports Open Workflows on the outbound side and starts jobs that capture live SDI inputs and output captured media files to Live Storage using the specified output container and encoder.

The Capture action is executed by the Live Service, and only works in a Vantage domain running on a Lightspeed Live Server. information capturing tape-base media, see Creating Capture & Tape Action Workflows

Tape ActionThe Tape action is an origin action. This action is executed by the Live Service. It is used to start SDI tape capture workflows created in a Vantage domain installed on a Lightspeed Live server. Use the Tape action inspector to select and configure VTR sources for processing, filtering, transcoding, and output. You can also use the action to add metadata labels. For information capturing tape-base media, see Creating Capture & Tape Action Workflows.


345


SubClip Action (Technology Preview)This action is executed by the Live Service. The SubClip action enables subclip editing of high resolution files based on edit decisions made in the Live Edit web app. The SubClip action is used in conjunction with media created by a Capture action. The Live Edit web app utilizes an HLS proxy created by the Capture Action and served to the Live Edit web app via an Origin server. For more information, see SubClip Action.

Cloud ActionsThe Cloud Service enables Vantage to interact with a Telestream Cloud account to provide cloud storage and processing, including transcoding, quality checking, and speech-to-text conversion. The following actions are executed by the Cloud Service:

■ Cloud Flip Action

■ Cloud QC Action

■ Cloud Speech Action

Cloud Flip ActionThe Cloud Flip action submits media from Vantage workflows via the Telestream Cloud Service and the Telestream Cloud API to the Telestream Cloud for transcoding. To use the Cloud Flip action you must have a Telestream Cloud account and enter the account credentials in the Vantage Management Console Settings to enable Vantage to access the account. When the Cloud Flip action executes, the input file is uploaded and processed according to the Cloud Flip factory chosen in the Cloud Flip action, and the results are returned to the workflow for downstream use.

Cloud QC ActionThe Cloud QC action submits media from Vantage workflows via the Telestream Cloud Service and the Telestream Cloud API to the Telestream Cloud for quality checking. To use the Cloud QC action you must have a Telestream Cloud account and enter the account credentials in the Vantage Management Console Settings to enable Vantage to access the account. When the Cloud QC action executes, the input file is uploaded and processed according to the Cloud Quality Control project chosen in the Cloud QC action, and the results are returned to the workflow for downstream use.

Cloud Speech ActionThe Cloud Speech action submits media from Vantage workflows via the Telestream Cloud Service and the Telestream Cloud API to the Telestream Cloud for speech-to-text conversion. To use the Cloud Speech action you must have a Telestream Cloud account and enter the account credentials in the Vantage Management Console Settings to enable Vantage to access the account. When the Cloud Speech action executes, the input file is uploaded and processed according to the Cloud Timed Text Speech project chosen in the Cloud Speech action, and the results are returned to the workflow for downstream use.


346


Metadata ActionsThe Metadata Service Vantage component executes the actions the extract metadata values, and perform conversions between attachment files, metadata labels, and variables.

■ Extract Action

■ Populate Action

■ Transform Action

Extract ActionThe Extract action, executed by the Metadata Service, is used to extract specific values from element attributes in XML or key-value pairs in JSON metadata. The Extract action identifies and extracts specific values from structured metadata and populates variables for use in downstream actions. The Extract action enables you to browse a sample file and identify the location in the structured data where the value is located.

The workflow can ingest an XML or JSON file during job execution or by making web service calls. The Extract action automatically generates XPATH or JSONPath references from the structured metadata in these files to extract the data, and populates a variable with the value. During execution, each extraction path is evaluated against the input and the associated variables are populated for use in downstream actions. This action can operate in Open Workflow mode.

Populate ActionA Populate action uses the Metadata Service to read and write metadata labels. During ingest, metadata labels can be added to ingested media and generally include trim information, audio levels, file properties, and commercial metadata. The metadata labels can then be reviewed and modified by operators using Workflow Portal. At any stage of a workflow, Vantage can extract information from labels using the Populate action, allowing Vantage for example to use trim points during a transcode, or audio level information when creating the final broadcast asset. This action can operate in Open Workflow mode.

Transform ActionA Transform action uses the Metadata Service to transform metadata between XML files (attachments) and labels. XSL style sheets are used to perform these transformations; style sheets can be managed in the Vantage Management Console: Workflow Design Items > Style Sheets. This action can operate in Open Workflow mode.

Transcode ActionsThe Transcode Service is the Vantage component that executes the Flip, Flip64, Split, and Stitch actions—transforming media from one format to another.

■ Flip Action

■ Flip64


347


■ Split

■ Stitch

Flip ActionA Flip action is executed by the Transcode Service, and implements the specified codec, which is used to transcode decoded digital baseband media into another media encoding format. The Telestream Media Transcode and Analysis Engine performs the transcode on behalf of Vantage. The Flip action has an Export command, which allows you to save the configured Flip action as an XML file, for use in SDK applications. This action is Open Workflow capable.

The Interplay Advanced Encoder is the only encoder available to use with the Capture action and includes the ability to direct-convert high resolution codecs and transcode to one of two H.264 Proxy types. See Using Live Capture with Avid Workflows for more information about using the Flip action’s Interplay Advanced Encoder.

The Interplay Advanced Encoder produces Avid MXF media and associated files. Two container options are available:

• Interplay Single-Res—Which includes integrated delivery to ISIS/NEXIS share stor-age and Interplay check-in.

• Media Composer—For creating an Avid AAF and individual Avid MXF media files.

Note: The codec used in the TIFO file created by Capture must match the Direct Convert option selected in the Interplay Advanced Encoder.

This action is open workflow capable.

See Using Live Capture with Avid Workflows for more information about using the Flip action’s Interplay Advanced Encoder.

Flip64The Flip64 action is a 64-bit multi-core-optimized encoder executed by the Transcode Service, which transcodes media from one or more input files into another format as


348


specified by the output configuration. Available resolutions extend from SD to UltraHD and 4K in a broad range of file formats, from QuickTime to MPEG-4 and TIFO, and including encoding for x264, x265 (H.265 HEVC), MXF, and many more. This action is Open Workflow capable.

SplitThe Split action is an optional, licensed feature that divides media files into multiple media reference files, for the purpose of significantly speeding up transcoding of long-form media by enabling parallel transcoding.

In the context of a split-and-stitch workflow, the workflow, actions, services, and the Vantage domain in general should be configured to ensure that the parallel transcoding actions execute in the most efficient manner in order to achieve the highest performance gains.

The Split and Stitch actions are used in conjunction with each other. The Split action divides the incoming media into segments. After transcoding the divided media segments by parallel transcoding actions, the Stitch action creates a media reference file that defines the reconstituted media. The Stitch action is typically located at the nexus of all preceding, parallel transcoding actions, where it passes the reference file to a Flip64, Tempo, or Conform action where the final, reconstituted media file is generated.

StitchThe Stitch action is an optional, licensed feature that ingests multiple media files and creates a reference file, for the purpose of significantly speeding up transcoding of long-form media. The reference file defines a single instance of media to be reconstituted from the member clips in a downstream transcoding action.

In the context of a split-and-stitch workflow, the workflow, actions, services, and the Vantage domain in general should be configured to ensure that the parallel transcoding actions execute in the most efficient manner in order to achieve the highest performance gains.

The Split and Stitch actions are used in conjunction with each other. The Split action divides the incoming media into segments. After transcoding the divided media segments by parallel transcoding actions, the Stitch action creates a media reference file that defines the reconstituted media. The Stitch action is typically located at the nexus of all preceding, parallel transcoding actions, where it passes the reference file to a Flip64, Tempo, or Conform action where the final, reconstituted media file is generated.

Transport ActionsTransport actions are executed by the Transport Service and perform file operations on specified files.

Copy Action


349


Copy actions can be executed on any action state. This action is Open Workflow capable.

Deploy Action

Move Action

Copy ActionA Copy action is executed by the Transport Service and is used to replicate a file from a source target (file system/device and directory) to a destination target (file system/device and directory). It typically performs this task by copying the file to the destination.

Copy actions can be executed on any action state. This action is Open Workflow capable.

Delete ActionA Delete action is executed by the Transport Service, and is used to permanently remove a file from a source target (file system/device and directory). Delete actions can be executed on any action state.

Deploy ActionA Deploy action is executed by the Transport Service, and is used to save the specified files to a destination outside the Vantage domain. Unlike Delete, Move, or Copy actions, Deploy actions allow multiple files to be operated on simultaneously, and do not maintain a reference to those files in the binder after completion.

The Deploy action can deliver to a wide variety of file systems, including Aspera, Azure, Avid MediaStream, Amazon AWS S3, FTP, Windows, and many others.

Move ActionA Move action is executed by the Transport Service, and is used to move a file from a source target (file system/device and directory) to a destination target (file system/device and directory). It performs this task by copying the file to the destination, then deleting the source. The copy first, delete last process insures that the move completes normally before deleting the source file.

Move actions can be executed on any action state.


350


Common ActionsCommon actions are typically light-weight, short duration, utilitarian actions, and do not have a dedicated Vantage service to execute them. Instead, these actions are implemented in every Vantage service, so that any service available can execute them efficiently and instantaneously.

Compute Action

Construct Action

Decide Action

Forward Action

Receive Action

Synchronize Action

Compute ActionA Compute action uses variables to set other variables. For example, you can use Compute to add two numbers and assign the result to the selected variable. Compute can perform mathematical operations such as addition, subtraction, division and multiplication. It can also convert variables between types (such as converting a time code to a string), string manipulation, such as appending strings together into an output variable, and comparison functions.


Construct ActionA Construct action enables you to construct complex strings, paths, and math expressions from literals, variables, and tokens, for use in downstream actions.


Decide ActionA Decide action allows you to explicitly set the action state based upon analysis of variable values at runtime. It is most commonly used to determine whether or not subsequent actions (or actions in a given branch) in a workflow should execute. When the Decide action is used, the state set by the Decide action is passed to the next action.

Typically, more than one Decide action is required to support decision branches.

For example, if one branch is for HD, it starts with a Decide action that sets the state to Success for HD content, and ignore otherwise; if another branch is for everything else, it starts with a Decide action that performs the opposite behavior.


351


Forward ActionA Forward action starts a new job for the target workflow, delivering a binder and all current variables from the originating workflow. A Forward action can only be added to the end of a workflow, and requires that the target workflow has a Receive action as its first action.

The Forward action is the only terminating action in Vantage—it does not have a connecting pin on the right side. Thus, once you add a Forward action to a workflow (or branch in a workflow), you cannot add any more actions, because control has passed to another workflow with a Receive action as its origin action.

Receive ActionA Receive action is an origin action which is implemented in every service. Receive actions are designed to receive files from other systems: workflows, SDK-based applications, and Workflow Portal, for example. Files can also be automatically submitted to a workflow starting with a Receive action from another workflow using the Forward action.

Typically, workflows are created with a Receive action when they are intended for execution by another workflow that immediately precedes this one. This ability to chain workflows enables you to create run-time customizable workflows consisting of smaller workflow building blocks.

Note: An origin action is required as the first action in a workflow, even if you plan to only manually submit jobs to this workflow.

Synchronize ActionA Synchronize action is a connector action, for the sole purpose of uncluttering workflow connectors. In workflows with a many-to-many relationship, instead of drawing connections between them all, you simply connect them to a common Synchronize action. There is no Inspector for the Synchronize action, because no configuration is required.

The Synchronize action is used in workflows where multiple actions connect to multiple subsequent actions. Synchronize provides a common connection point, where all upstream actions must be connected to all downstream actions.


352


Communicate ActionsCommunicate actions are used to communicate with external systems. They are executed by the Communicate Service.

Automate Action

Message Action

Notify Action

Automate ActionAutomate action features are not enabled with a Capture license.

Message ActionA Message action enables you to generate and transmit an email. You must configure Vantage to use an SMTP server before email can be utilized; this can be done in the Vantage Management Console.


Notify ActionA Notify action transfers job information to external systems via Web Services or other methods to transfer data. The job information may also be transferred via an XML file or files of other formats. You can also use the Notify action to invoke a command shell.


Only the XML Dump, Interplay, and MOB ID Generator Notifier are available with a Capture license.

VidChecker ActionA VidChecker action is an optional, licensed feature in Vantage. It uses the VidChecker Service to enable Vantage workflows to utilize and interact with various QC tests provided by the VidChecker software.

353

Appendix C: RS-422 VTR Interface

This appendix provides information about installing and using the optional 4-Port RS-422 VTR Interface Kit. These instructions apply only to those using RS-422 to control a VTR using Lightspeed Tape Capture.

Also included are a description and operational details about the Video Disk Communications Protocol (VDCP) implementation which uses the RS-422 interface.

These topics are included:

■ What the RS-422 VTR Interface Kit Includes

■ Installing the USB Cable Retainer on the Lightspeed Live Server

■ Assembling & Installing the RS-422 Interface Box and Rack Mount Tray

■ Connecting a VTR to the Lightspeed Live Server

■ Creating the Tape Capture Workflow

■ RS-422 Connector Pin Assignments

■ Configuring an RS-422 COM Port's Latency Time

■ Video Disk Communications Protocol (VDCP)

Appendix C: RS-422 VTR InterfaceRS-422 Interface Kit Assembly and Installation

354


RS-422 Interface Kit Assembly and InstallationThe 4-Port RS-422 VTR Interface Kit provides the ability to connect up to four VTR units to the Lightspeed Live server, and allows a VTR to be remotely controlled by the Lightspeed Tape Capture application to facilitate conversion of video tape data into video files.

What the RS-422 VTR Interface Kit IncludesThe 4-Port RS-422 VTR Interface Kit includes these components:

• One USB to RS-422 Interface Box, providing four RS-422 serial ports.

• USB cable to connect the RS-422 Interface Box to the Lightspeed Live server.

• USB Cable Retainer that secures the USB cable to the Lightspeed Live server.

– Phillips flat-head 6-32 x 3/4” screw, lock-washer and 6-32 1/4” nut to install the Cable Retainer. (This replaces one of the standard screws in the Lightspeed Live server cover.)

• RS-422 DB9-to-RJ45 (Ethernet style) adapter kit, which includes:

– Four Female DB9-to-RJ45 blue adapters to connect to the RS-422 Interface Box.

– Four Male DB9-to-RJ45 gray adapters to connect to a VTR.

• Rack Mount Tray that fits in a standard 1 RU rack space and can hold up to two RS-422 Interface Boxes.


355


• Rack Mount Tray mounting hardware kit (see image below), which includes:

– Four 10-32 rack screws and washers.

– Four G-Type Cage Nuts.

– Four Stainless Steel Phillips rounded-head M3 x 0.5 mm-thread x 5 mm-long screws to mount the RS-422 interface to the tray.

– One small tie-wrap to secure the USB cable to the tray.

The RS-422 Interface Box is powered by the Lightspeed Live server’s USB port, so no additional power supply is required. Drivers for the USB to RS-422 Interface Box are included in the software package and are installed as one of the steps below.

User-Supplied CableA user-supplied cable is required to connect a VTR to the RS-422 Interface Box, by plugging into the RJ45 (Ethernet style) jack in each DB9-to-RJ45 adapter.

A Cat5E (Cat5 Enhanced) cable is recommended; the standard pin-to-pin type (not crossover). The maximum cable length is 100 meters (328 feet).


356


Installing the USB Cable Retainer on the Lightspeed Live Server

The USB Cable Retainer holds the USB cable firmly into the USB port on the back of the Lightspeed Live server, to prevent accidental removal.

The USB Cable Retainer is installed on the back of the Lightspeed Live server, and sufficient space is needed above the server to operate a screwdriver to replace one of the screws in the cover. This is best accomplished before installing the server in the rack, but can be performed when the server is in the rack if sufficient space is available above the server.

These tools are recommended to install the Cable Retainer, and RS-422 Interface Kit:

• 1/4” nut driver

• Phillips screw driver

To install the USB Cable Retainer:

1. Remove the screw in the center of the top cover on the back of the Lightspeed Live server.

2. Install the Phillips flat-head 6-32 x 3/4” screw in place of the removed screw, and tighten to secure the cover.

3. Slide the Cable Retainer onto the newly installed screw, and secure it with the lock-washer and 6-32 1/4” nut. Tighten firmly using a 1/4” nut driver.

4. Install the Lightspeed Live server into the rack, if not already installed.


357


Assembling & Installing the RS-422 Interface Box and Rack Mount Tray

The USB to RS-422 Interface Box and Rack Mount Tray must first be assembled and then installed. It is best installed in the rear of the equipment rack, to be close to the Lightspeed Live server USB ports. The rack tray can hold two RS-422 Interface Boxes, but the standard 4-Port RS-422 Interface Kit only includes one RS-422 Interface Box.

To assemble and install the USB to RS-422 Interface Box and Rack Mount Tray, follow these steps:

1. Position the RS-422 Interface Box on the Rack Mount Tray so the USB port is on the back side and the four RS-422 ports face the front, where the rack mounting brackets are located.

2. Align two of the tray holes with the RS-422 Interface Box screw holes and use two of the Stainless Steel Phillips rounded-head M3 x 0.5 mm-thread x 5 mm-long screws to attach the Interface Box.

Note: There are two sets of holes in the Rack Mount Tray at each Interface Box position, the extra holes are to accommodate other models of interface devices. One set of holes aligns with the RS-422 Interface Box.

3. Insert the USB cable into the rear of the RS-422 Interface Box. Fasten the USB cable to the tray by inserting the tie wrap through the raised anchor tab and tighten it to secure the cable.


358


4. To prepare the tray mounting location, place the four G-Type Cage Nuts onto holes of an open rack space that is close to the Lightspeed Live Server.

5. Install the Rack Mount Tray with the 10-32 rack screws and washers into the G-Type Cage Nuts.

6. To attach the USB cable to the server, loosen the retaining-arm screw of the USB Cable Retainer and slide the arm away from the rear of the Lightspeed Live server.

7. Insert the USB cable into the top port of the server.


359


8. Slide the USB cable retaining-arm forward to secure the cable, then tighten the retaining arm screw.

9. To prepare for VTR connection, attach a Female DB9-to-RJ45 blue adapter to the Channel 1 (CH1) RS-422 serial port on the interface box. Attach additional Female DB9-to-RJ45 blue adapters to other channels if you plan to connect more than one VTR.

Proceed to the next step of Connecting a VTR to the Lightspeed Live Server.


360


Connecting a VTR to the Lightspeed Live ServerWhen connecting a VTR to the RS-422 Interface Box and a Lightspeed Live server, you must use the same terminal number on the RS-422 interface and SDI Input on the Lightspeed Live server. For example, when using SDI Input 1 on the Lightspeed Live server you must connect to Channel 1 (CH1) on the RS-422 Interface Box. See the following diagram:

Follow these steps to connect a VTR to the RS-422 Interface Box and the Lightspeed Live server SDI input.

1. Position or install the VTR in a convenient location.

2. Attach one Male DB9-to-RJ45 gray adapter to the appropriate RS-422 remote terminal on the VTR.

Note: If an RS-422 router is between the RS-422 Interface Box and the VTR, the Male DB9-to-RJ45 gray adapter should be plugged into the router on the Lightspeed Live server side of the system.

3. Connect a Cat5E cable into the RJ45 jack on the adapter connected to the VTR.

4. Connect the other end of the Cat5E cable into the RJ45 jack on the adapter connected to the RS-422 Interface Box, using the terminal number that corresponds to the SDI Input number you want to use on the Lightspeed Live server.

5. Connect an SDI cable to the appropriate Output terminal on the VTR.

6. Connect the other end of the SDI cable to the SDI Input terminal on the Lightspeed Live server that corresponds to the same terminal number you connected to on the RS-422 Interface Box.

7. Power up the VTR and switch it into the proper Remote mode for RS-422 control.


361


When all connections are complete between the RS-422 Interface Box, the VTR, and the Lightspeed Live server, the VTR connection is initialized and CH1 (Channel 1) of the RS-422 Interface Box automatically synchronizes with SDI Input 1 on the Lightspeed Live server, CH2 with SDI 2, CH3 with SDI 3, and CH4 with SDI 4.

Creating the Tape Capture WorkflowTo enable capture of data from the VTR, configuration settings must be made in both the Vantage Management Console and the Vantage Workflow Designer > Tape action. See Configuring Settings for Your Facility, Configuring Ingest Sources, and Creating and Activating a Tape Action Workflow chapter for detailed instructions.

RS-422 Connector Pin AssignmentsUse the pin assignment diagram below if you want to create custom RS-422 cables for your Lightspeed Live Capture’s USB to RS-422 Interface Box.


362


Configuring an RS-422 COM Port's Latency TimeThe RS-422 COM Port configuration is set at the factory prior to product shipment. However, if new drivers are installed or a new USB to RS-422 Interface Box is used the latency value may not persist and should be reconfigured to 1 msec.

Follow these steps to set each USB Serial Port’s Latency Timer value to 1 msec:

1. Open Device Manager on the Lightspeed Live Capture server.

2. Click on Ports > USB Serial Port.

3. Select the first USB Serial Port, right-click and select Properties.

4. Select the Port Settings tab and click on Advanced. The Advanced Settings dialog opens (see below).

5. Change Latency Timer from 16 to 1 msec and click OK.

6. Repeat steps c to e for the remaining three (3) USB Serial Ports.

7. Close Device Manager.

Appendix C: RS-422 VTR InterfaceVideo Disk Communications Protocol (VDCP)

363


Video Disk Communications Protocol (VDCP)The VDCP interface allows an external device to control the Capture action via serial control, where the external control acts as the server and Vantage Capture is the client. A simple way to describe this implementation is RS-422 deck control in reverse. The optional RS-422 hardware kit described previously provides the necessary USB to serial control.

Making ConnectionsTo connect to the Capture VDCP interface, connect the RS-422 output of the automation system to one of the RS-422 connectors on the Serial-to-USB converter box that is installed as part of the Lightspeed Live RS-422 option kit. For pin assignments, see RS-422 Connector Pin Assignments covered previously in this chapter.

Communications SignalThe VDCP communications signals follow these standards:

• Asynchronous bit serial, word serial

• EIA RS-422A

• Full duplex

• 38.4 Kb/s transfer rate


364


Configuring VDCP ControlFollow these steps to configure VDCP control of the Capture action:

1. In the Vantage Management Console, select Capture Inventory in the left panel.

2. Select a Capture Channel (source) in the Capture Inventory panel.

3. In the Configuration tab at the bottom of the Capture Inventory panel, check (enable) the VDCP check box.


365


4. In the Capture action, set a Manual Trigger, and configure the trigger:

– Check the Enable VDCP control check box.

– Set the VDCP Port number to match the device port where you connected the automation machine.

– Check the Set Base Name with VDCP Cue Command, if desired.

5. Activate the Capture workflow, and test the interface by sending each of the commands listed in the next topic.


366


VDCP CommandsTelestream VDCP support is limited to a subset of the published VDCP commands. It is intended to allow an automation system to issue a RECORD command against a Lightspeed Live Capture channel. If required, the automation system can provide a standard (8 character) or extended filename for the Lightspeed Live Capture channel to use as a base name for the output file.

Support is limited to the following VDCP commands.

Sense Requests30.01 OPEN PORT—Capture always grants this request.

30.05 PORT STATUS—Capture respects the bit mask field but returns empty status words. The currently-selected port is returned. Status 1 returns 0x04 if the last command was RECORD, 0x01 if the last command was STOP, and 0x80 if the last command was RECORD INIT.

30.06 POSITION REQUEST—Capture returns empty position status words.

30.20 SYSTEM STATUS REQUEST—Capture returns empty system status words, with the exception of the space available words which return a constant large value. The bit mask extended flag is respected.

30.08 DEVICE TYPE REQUEST—Capture returns this string response: tele:capture.

All other commands cause Capture to return an undefined error NAK message.

Variable ID Length Sense RequestsB0.11 ID LIST—Capture returns empty is list words

BO.16 ID REQUEST—Capture returns the default response {1, 1, 0}

B0.18 ID’S ADDED LIST—Capture returns empty added list words

B0.19 ID’S DELETED LIST—Capture returns empty deleted list words


Immediate Commands10.00 STOP—Capture returns an ACK

10.02 RECORD—Capture returns an ACK

Preset / Select Commands20.21 CLOSE PORT—Capture returns an ACK

20.22 SELECT PORT—Capture returns an ACK

20.23 RECORD INIT—Capture returns an ACK


367


20.25 CUE WITH DATA—Capture returns an ACK


Variable ID Preset / Select CommandsA0.21 CLOSE PORT—Capture returns an ACK

A0.22 SELECT PORT—Capture returns an ACK

A0.23 RECORD INIT—Capture returns an ACK. Capture stores extended length filename for use as a filename base in the next captured file.

A0.25 CUE WITH DATA—Capture returns an ACK


Frame Accurate RecordingCapture implements frame accurate recording in this manner:

• Capture must have received a 20.22 select port command with the port configured in the Capture action.

• Capture marks the frame received over the SDI port at the time that the 10.02 RECORD command is received at the VDCP port.

• The time-shift buffer must be configured in the Capture action with sufficient time for the Capture Record process to start after receipt of the 10.02 RECORD command.

• The captured file begins with the frame identified as the marked frame.


368


369

Appendix D: Technology Previews

This appendix describes the current Lightspeed Live Capture Technology Previews.

SubClip ActionThe SubClip action allows for sub clip editing of high resolution files based on edit decisions made from within the Live Edit web app user interface. The SubClip action is used with media created by a Capture action. The Live Edit web app UI utilizes an HLS proxy created by the Capture Action and served to the Live Edit UI via an Origin server.

This action is open workflow capable if the Open Workflows license is installed; right-click the action and select Workflow Mode > Open. Open Workflows must also be enabled for the current workflow and in the Vantage Management Console Settings.

Note: Controls with a green Browse button may be bound to a variable to dynamically assign their setting or value. The variable must have a value when this action executes. You can assign the value to the variable in a previous action in the workflow or use the variable's default value. Select the variable or create a new one.

Channel GroupSpecifies the Channel Group (Nexus Group) in which you want this workflow to reside.

Expected LabelsMetadata Labels created in the Vantage Management Console can be selected using the drop-down menu. When selected, they are available to configure in the ??? web application.

SubClip OutputThe Output panel is used to select the medial file type, the output storage location where the file will be written, edit the file name using tokens or variables, and specify the output nickname.

Appendix D: Technology PreviewsSubClip Action

370


Select. Select the medial file type:

- MPEG-4

- MPEG-4 Reference


- Available Vantage Store: Let Vantage select an available Vantage Store.

- Vantage Store/Folder: Select to specify a Vantage Store or Vantage Folder to write the output to. Select any available Live Store or folder from the drop down list.

- Path: Select to write the output to a specific Windows file system server and directory. Manually enter a Windows share (UNC path) or drive letter (not recommended on Vantage arrays) or click Browse to navigate and select the location. Or, click the green Browse button and select a variable which supplies the fully-qualified path.

WARNING: In rare instances two processes writing to the same Path location folder could result in one file overwriting the other. To prevent this it is best to use a unique folder location for each workflow, or append a Time token set to 'mmm' to the file name in one workflow by using Edit Filename, which will return seconds down to a thousandth of a second and add this onto the file name.

- Collision Resolution: Specifies what should happen if the folder already contains a file with the same name as the output file being written. The choices are: Create Unique Name, Overwrite, or Set Failure State.

Edit Filename. Displays the Filename Pattern Editor and specifies the pattern for the file you are creating. Default: Base Name. Use the menu on the right to select one or more tokens to insert to create the exact filename pattern you require.

Available tokens:

- Insert Base Name: Select to add the base (clip) name as part of the file name. The Base Name token is populated with the Clip Name selected in Clip Panel of the Tape Capture user interface.

- Insert Workflow Name: Select to add the name of the workflow as part of the file name.

- Insert Variable: Select to choose and add a bound variable to the file name.

- Insert Date: Select to add the current date when the file name is constructed as part of the file name.

- Insert Time: Select to add the current time when the file name is constructed as part of the file name.


Select Media Nickname. Specifies the nickname for this media.


371



Settings PanelSpecify settings to use for the output configuration. Binding any of these parameters to variables will make those parameters configurable from within the user interface.

Uri. Enter the Web server URI (Uniform Resource Identifier).

Levels Deep. Specifies how many levels deep to look for files.

ContainerSpecifies the file extension to use. Only MP4 is available.


372


Documents

Lightspeed Live User Guide