K2
Media Platform
System Guide
Software Version 7.2
071-8726-01 April 2010
Affiliate with the N.V. KEMA in The Netherlands
CERTIFICATE
Certificate Number: 510040.001 The Quality System of:
Thomson Inc, and it’s wordwide Grass Valley division affiliates DBA GRASS VALLEY
Headquarters |
15655 SW Greystone Ct. |
10 Presidential Way |
400 Providence Mine Rd |
Beaverton, OR 97006 |
Suite 300 |
Nevada City, CA 95959 |
United States |
Woburn, MA 01801 |
United States |
|
United States |
Kapittelweg 10 |
7140 Baymeadows Way |
2300 So. Decker Lake Blvd. |
4827 HG Breda |
Ste 101 |
Salt Lake City, UT 84119 |
The Nederlands |
Jacksonville, FL 32256 |
United States |
|
United States |
|
Rue du Clos Courtel |
1 rue de l’Hautil |
Technopole Brest-Iroise |
CS 31719 |
Z.I. des Boutries BP 150 |
Site de la Pointe du Diable |
35517 Cesson-Sevigné Cedex |
78702 Conflans-Sainte |
CS 73808 |
France |
Honorine Cedex |
29238 Brest Cedex 3 |
|
France |
France |
40 Rue de Bray |
Spinnereistrasse 5 |
Brunnenweg 9 |
2 Rue des Landelles |
CH-5300 Turgi |
D-64331 Weiterstadt |
35510 Cesson Sevigné |
Switzerland |
Germany |
France |
|
|
Carl-Benz-Strasse 6-8 |
|
|
67105 Schifferstadt |
|
|
Germany |
|
|
Including its implementation, meets the requirements of the standard:
ISO 9001:2008
Scope:
The design, manufacture and support of video and audio hardware and software products and related systems.
This Certificate is valid until: |
June 14, 2012 |
This Certificate is valid as of: |
June 14, 2009 |
Certified for the first time: |
June 14, 2000 |
H. Pierre Sallé
President
KEMA-Registered Quality
The method of operation for quality certification is defined in the KEMA General Terms And Conditions For Quality And Environmental Management Systems Certifications. Integral publication of this certificate is allowed.
KEMA-Registered Quality, Inc. |
Accredited By: |
4377 County Line Road |
ANAB |
Chalfont, PA 18914 |
|
Ph: (215)997-4519 |
|
Fax: (215)997-3809 |
|
CRT 001 073004
K2
Media Platform
System Guide
Software Version 7.2
071-8726-01 April 2010
Copyright
Disclaimer
U.S. Government
Restricted Rights
Legend
Trademarks and
Logos
Copyright © Grass Valley, Inc. All rights reserved. Printed in the United States of America. Portions of software © 2000 – 2010, Microsoft Corporation. All rights reserved. This document may not be copied in whole or in part, or otherwise reproduced except as specifically permitted under U.S. copyright law, without the prior written consent of Grass Valley, Inc., P.O. Box 59900, Nevada City, California 95959-7900. This product may be covered by one or more U.S. and foreign patents.
Product options and specifications subject to change without notice. The information in this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Grass Valley, Inc. Grass Valley, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication.
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7013 or in subparagraph c(1) and (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19, as applicable. Manufacturer is Grass Valley, Inc., P.O. Box 59900, Nevada City, California 95959-7900 U.S.A.
Grass Valley, K2, Aurora, Summit, Dyno, Solo, Infinity, Turbo, Profile, Profile XP, NetCentral, NewsBrowse, NewsEdit, NewsQ, NewsShare, NewsQ Pro, and Media Manager are either registered trademarks or trademarks of Grass Valley, Inc. in the United States and/or other countries. Grass Valley, Inc. products are covered by U.S. and foreign patents, issued and pending. Additional information regarding Grass Valley, Inc. trademarks and other proprietary rights may be found at www.grassvalley.com. Other trademarks and logos used in this document are either registered trademarks or trademarks of the manufacturers or vendors of the associated products, such as Microsoft® Windows® operating system, Windows Media® player, Internet Explorer® internet browser, and SQL Server™. QuickTime and the QuickTime logo are trademarks or registered trademarks of Apple Computer, Inc., used under license therefrom.
Revision Status
Rev Date |
Description |
|
|
|
|
November 2005 – |
Initial release and revisions for 3.1 and 3.2 releases — |
July 2007 |
071-8460-00, 071-8460-02, 071-8460-03 |
|
|
September 7, |
Revised information for direct-connect storage, teaming, HotBins, |
2007 |
software version 3.2.5 — 071-8460-03 |
|
|
January 11, 2008 |
Added information for capture services and Type II motherboard — |
|
071-8460-04 |
|
|
July 28, 2008 |
Added information for software version 3.2.7, XML Import capture |
|
service, ancillary/data track specs ,MIBs — 071-8460-05 |
|
|
March 20, 2009 |
Version for K2 Summit Client, removed K2 Media Client-specific |
|
information — 86231160 |
|
|
October 27, 2009 |
Added K2 Solo Media Server, MPEG-2, AVC-Intra and other |
|
information for software version 7.1 — 071-8726-00 |
|
|
April 7, 2010 |
Added ChannelFlex Suite features, K2 Transmission, and other |
|
information for software version 7.2 — 071-8726-01 |
|
|
4 |
K2 System Guide |
07 April 2010 |
Contents |
|
|
|
Finding Information........................................................................................... |
11 |
|
Grass Valley Product Support ................................................................................. |
15 |
|
Web Technical Support ...................................................................................... |
15 |
|
Telephone Support ............................................................................................. |
15 |
|
Waste Electrical and Electronic Equipment Directive......................................... |
17 |
Chapter 1 |
Product Description |
|
|
K2 Summit Production Client and K2 Solo Media Server features ......................... |
20 |
|
Features of internal storage models ................................................................... |
21 |
|
Features of external storage models .................................................................. |
21 |
|
Product identification ............................................................................................... |
22 |
|
Front panel indicators.............................................................................................. |
23 |
|
Rear panel view....................................................................................................... |
24 |
|
K2 Summit Production Client rear panel........................................................ |
24 |
|
K2 Solo Media Server rear panel..................................................................... |
25 |
|
ChannelFlex Suite rear panel connections ................................................... |
26 |
|
Considerations for first startup out of box................................................................ |
26 |
|
K2 Summit Production Client and K2 Solo Media Server system overview ............ |
27 |
|
Application System ............................................................................................. |
27 |
|
Real Time System .............................................................................................. |
27 |
|
Media control and processing............................................................................. |
27 |
|
Loop through, E to E, and feeds......................................................................... |
28 |
|
Ports used by K2 services .................................................................................. |
30 |
|
RAID drive numbering ........................................................................................ |
31 |
Chapter 2 |
Using K2 system tools |
|
|
Configuration Manager............................................................................................ |
33 |
|
Accessing Configuration Manager...................................................................... |
33 |
|
Saving and restoring Configuration Manager settings ....................................... |
33 |
|
Restoring default Configuration Manager settings ............................................ |
34 |
|
K2 System Configuration......................................................................................... |
35 |
|
Storage Utility .......................................................................................................... |
36 |
|
NetCentral ............................................................................................................... |
37 |
|
Windows Remote Desktop Connection................................................................... |
37 |
|
................................................................................................................................ |
38 |
|
SiteConfig — a ProductFrame application .............................................................. |
38 |
Chapter 3 |
System connections and configuration |
|
|
About networks........................................................................................................ |
42 |
|
Control network description ................................................................................ |
42 |
|
Streaming/FTP network description ................................................................... |
42 |
|
Media (iSCSI) network description ..................................................................... |
42 |
|
Network connections ............................................................................................... |
43 |
|
Cable requirements ............................................................................................ |
43 |
|
About network ports............................................................................................ |
43 |
|
Making network connections .............................................................................. |
44 |
|
Network configuration.............................................................................................. |
45 |
|
About network functionality................................................................................. |
45 |
|
About modifying or restoring network settings.................................................... |
46 |
|
Configure network settings for a stand-alone K2 systems ................................. |
46 |
|
Streaming video between K2 systems ............................................................... |
48 |
|
Using FTP for file transfer ....................................................................................... |
52 |
|
About the K2 FTP interface ................................................................................ |
53 |
|
Limitations with complex media types ................................................................ |
53 |
|
Transferring between different types of systems................................................ |
53 |
|
Transfer mechanisms ......................................................................................... |
53 |
|
FTP access and configuration ............................................................................ |
54 |
07 April 2010 |
K2 System Guide |
5 |
Contents
|
FTP access by automation................................................................................. |
54 |
|
FTP security ....................................................................................................... |
55 |
|
FTP internationalization...................................................................................... |
55 |
|
FTP access by Internet Explorer ........................................................................ |
56 |
|
FTP commands supported ................................................................................. |
59 |
|
Using FTP on a K2 Nearline SAN ...................................................................... |
60 |
|
Using the HotBin service......................................................................................... |
61 |
|
About the HotBin service.................................................................................... |
61 |
|
Prerequisite for using the HotBin service ........................................................... |
62 |
|
Configuring the HotBin service........................................................................... |
62 |
|
HotBin service components................................................................................ |
65 |
|
Using the Pathfire capture service .......................................................................... |
66 |
|
About the Pathfire capture service ..................................................................... |
66 |
|
Prerequisites for using the Pathfire capture service........................................... |
66 |
|
Considerations for the Pathfire capture service ................................................. |
67 |
|
Configuring the Pathfire capture service ............................................................ |
67 |
|
Testing the Pathfire capture service................................................................... |
69 |
|
Pathfire capture service components ................................................................. |
69 |
|
Pathfire capture service procedures................................................................... |
70 |
|
Installing Pathfire Transfer Service software...................................................... |
70 |
|
Licensing Pathfire Transfer Service software..................................................... |
73 |
|
Using the DG capture service ................................................................................. |
75 |
|
About the DG capture service ............................................................................ |
75 |
|
Prerequisites for using the DG capture service.................................................. |
75 |
|
Configuring the DG capture service ................................................................... |
76 |
|
Testing the DG capture service.......................................................................... |
77 |
|
DG capture service procedures.......................................................................... |
78 |
|
DG capture service components ........................................................................ |
78 |
|
Using the XML Import capture service .................................................................... |
79 |
|
About the XML Import capture service ............................................................... |
79 |
|
Prerequisites for using the XML Import capture service..................................... |
79 |
|
Considerations for the XML Import capture service ........................................... |
80 |
|
Configuring the XML Import capture service ...................................................... |
80 |
|
Testing the XML Import capture service............................................................. |
82 |
|
XML Import capture service components........................................................... |
82 |
|
Using the P2 Import capture service ....................................................................... |
83 |
|
About the P2 Import capture service .................................................................. |
83 |
|
Prerequisites for using the P2 Import capture service........................................ |
83 |
|
Considerations for the P2 Import capture service .............................................. |
84 |
|
Configuring the P2 Import capture service ......................................................... |
84 |
|
Testing the P2 Import capture service................................................................ |
86 |
|
P2 Import capture service components.............................................................. |
86 |
|
Licensing K2 capture service software.................................................................... |
86 |
|
Pinnacle support ..................................................................................................... |
87 |
|
Compressed VBI import .......................................................................................... |
92 |
|
About compressed VBI import processes .......................................................... |
92 |
|
Specifications ..................................................................................................... |
92 |
|
................................................................................................................................ |
93 |
|
Quicktime and Final Cut Pro support ...................................................................... |
93 |
|
About connecting to K2 storage with Final Cut Pro............................................ |
93 |
|
Install and configure Macintosh Final Cut Pro systems on K2 storage .............. |
94 |
|
Using Final Cut Pro on a K2 storage.................................................................. |
104 |
|
Connecting RS-422................................................................................................. |
105 |
|
Connecting GPI....................................................................................................... |
106 |
Chapter 4 |
Managing Stand-alone Storage |
|
|
About the internal storage system........................................................................... |
107 |
6 |
K2 System Guide |
07 April 2010 |
|
K2 Summit Production Client internal storage system ....................................... |
107 |
|
K2 Solo Media Server internal storage system .................................................. |
107 |
|
About the direct-connect storage system ................................................................ |
108 |
|
Using Storage Utility................................................................................................ |
109 |
|
About Storage Utility........................................................................................... |
110 |
|
Opening Storage Utility....................................................................................... |
110 |
|
Overview of Storage Utility ................................................................................. |
112 |
|
Checking storage subsystem status................................................................... |
113 |
|
Checking controller microcode ........................................................................... |
113 |
|
About identifying disks........................................................................................ |
114 |
|
Identifying internal disks ..................................................................................... |
114 |
|
Get controller logs .............................................................................................. |
115 |
|
Check disk mode pages ..................................................................................... |
115 |
|
Disabling a disk .................................................................................................. |
115 |
|
Forcing a disk to rebuild ..................................................................................... |
116 |
|
Unbind LUN ........................................................................................................ |
116 |
|
Bind Luns............................................................................................................ |
117 |
|
Changing RAID type for internal storage............................................................ |
119 |
|
Making a new media file system on a K2 Summit/Solo...................................... |
120 |
|
Checking the media file system.......................................................................... |
120 |
|
Cleaning unreferenced files and movies ............................................................ |
121 |
|
Downloading controller microcode ..................................................................... |
121 |
|
Downloading disk drive firmware........................................................................ |
122 |
|
Placing the K2 system into online mode............................................................. |
123 |
Chapter 5 |
Managing stand-alone K2 systems with SiteConfig |
|
|
About managing stand-alone K2 clients with SiteConfig......................................... |
126 |
|
SiteConfig and stand-alone K2 clients checklist...................................................... |
126 |
|
System requirements for SiteConfig control point PC ............................................. |
127 |
|
About installing SiteConfig ...................................................................................... |
128 |
|
Installing/upgrading SiteConfig................................................................................ |
128 |
|
Creating a system description for stand-alone K2 clients ....................................... |
130 |
|
Creating the control network for stand-alone K2 clients.......................................... |
131 |
|
Creating the FTP/streaming network for stand-alone K2 clients (optional) ............. |
133 |
|
Adding a group ........................................................................................................ |
134 |
|
Adding stand-alone K2 clients to the system description ........................................ |
134 |
|
Modifying stand-alone K2 client unassigned (unmanaged) interfaces .................... |
135 |
|
Discovering devices with SiteConfig ....................................................................... |
137 |
|
Assigning discovered devices ................................................................................. |
138 |
|
Modifying stand-alone K2 client managed network interfaces ................................ |
139 |
|
Adding a control point PC placeholder device to the system description................ |
144 |
|
Assigning the control point PC ................................................................................ |
145 |
|
Making the host name the same as the device name ............................................. |
146 |
|
Pinging devices from the control point PC .............................................................. |
146 |
|
About hosts files and SiteConfig ............................................................................. |
146 |
|
Generating host tables for devices with SiteConfig................................................. |
147 |
|
Configuring deployment groups .............................................................................. |
148 |
|
About deploying software for stand-alone K2 clients .............................................. |
149 |
Chapter 6 |
Managing K2 system software |
|
|
About K2 system software....................................................................................... |
151 |
|
Software components installed........................................................................... |
152 |
|
Installing Control Point software.............................................................................. |
152 |
|
Installing K2 software .............................................................................................. |
154 |
|
Pre-installed software.............................................................................................. |
154 |
|
Backup and recovery strategies .............................................................................. |
154 |
07 April 2010 |
K2 System Guide |
7 |
Contents
Chapter 7 |
Administering and maintaining the |
|
|
K2 system |
|
|
About the write filter ................................................................................................ |
155 |
|
Enabling the write filter............................................................................................ |
156 |
|
Disabling the write filter ........................................................................................... |
156 |
|
Committing a file to disk with write filter enabled .................................................... |
156 |
|
Licensing ................................................................................................................. |
157 |
|
Software version licenses................................................................................... |
157 |
|
Licensable options.............................................................................................. |
157 |
|
Configuring K2 security ........................................................................................... |
158 |
|
Overview of K2 security features........................................................................ |
159 |
|
Example: Setting up user access to bins ........................................................... |
160 |
|
Example: Setting up user access to channels.................................................... |
160 |
|
Security and user accounts ................................................................................ |
161 |
|
Configuring media access security for K2 bins .................................................. |
161 |
|
AppCenter operations and media access security ............................................. |
163 |
|
FTP and media access security ......................................................................... |
163 |
|
K2 SANs and media access security ................................................................. |
164 |
|
Protocol control of channels and media access security.................................... |
164 |
|
Configuring channel access security.................................................................. |
165 |
|
K2 and NetCentral security considerations ............................................................. |
167 |
|
Mapping a NetCentral administrator to the K2 administrator level ..................... |
167 |
|
Microsoft Windows updates .................................................................................... |
168 |
|
Virus scanning policies............................................................................................ |
169 |
|
Network and firewall policies................................................................................... |
169 |
|
Enabling and disabling the USB ports..................................................................... |
170 |
|
Configuring auto log on ........................................................................................... |
171 |
|
Regional and language settings.............................................................................. |
171 |
Chapter 8 |
Direct Connect Storage |
|
|
Setting up direct-connect RAID storage.................................................................. |
173 |
|
Powering up K2 RAID ............................................................................................. |
177 |
Chapter 9 |
K2 Summit Transmission Server Package |
|
|
K2 Summit Transmission Server Package features................................................ |
179 |
|
K2 Summit Transmission Server Package requirements and restrictions .............. |
180 |
|
Storage Utility procedures for the K2 Summit Transmission Server Package ........ |
180 |
Appendix A |
Remote control protocols |
|
|
Using AMP protocol to control K2 systems ............................................................. |
182 |
|
Using VDCP protocol to control K2 systems........................................................... |
183 |
|
Using BVW protocol to control K2 systems............................................................. |
185 |
|
Special considerations for automation vendors ...................................................... |
186 |
|
Harris settings .................................................................................................... |
186 |
|
RS-422 connections on the K2 Summit Production Client or K2 Solo Media Server187 |
|
|
Security and protocol control................................................................................... |
187 |
Appendix B |
Specifications |
|
|
AC power specification............................................................................................ |
190 |
|
Environmental specifications................................................................................... |
190 |
|
Mechanical specifications ....................................................................................... |
192 |
|
Electrical specifications ........................................................................................... |
192 |
|
Serial Digital Video (SDI).................................................................................... |
192 |
|
Genlock Reference............................................................................................. |
193 |
|
System Timing.................................................................................................... |
194 |
|
AES/EBU Digital Audio....................................................................................... |
194 |
|
LTC Input/Output................................................................................................ |
196 |
8 |
K2 System Guide |
07 April 2010 |
|
VITC Input/Output............................................................................................... |
196 |
|
RS-422 specification........................................................................................... |
196 |
|
GPI I/O specifications ......................................................................................... |
197 |
|
Operational specifications ....................................................................................... |
198 |
|
Video codec description K2 Summit/Solo........................................................... |
199 |
|
Playout of multiple formats ................................................................................. |
200 |
|
Active Format Description (AFD) specifications ................................................. |
203 |
|
VBI/Ancillary/data track specifications................................................................ |
210 |
|
Internationalization ............................................................................................. |
214 |
|
Naming specifications for assets and bins ......................................................... |
214 |
|
Video network performance................................................................................ |
216 |
|
Supported file input/output formats on K2 Summit/Solo/SAN ............................ |
216 |
|
MXF export behavior on K2 Summit/Solo .......................................................... |
218 |
|
Media file system performance on K2 systems .................................................. |
218 |
|
Transition effects formats supported .................................................................. |
219 |
|
Protocols supported............................................................................................ |
220 |
|
Transfer compatibility with K2 Summit/Solo ....................................................... |
221 |
|
Control Point PC system requirements .............................................................. |
224 |
|
MIB specifications ................................................................................................... |
225 |
|
K2 client MIBs..................................................................................................... |
226 |
|
K2 Media Server MIBs........................................................................................ |
227 |
|
K2 Appliance (Generic Windows computer based) MIBs................................... |
228 |
|
................................................................................................................................ |
229 |
Appendix C |
Connector Pinouts |
|
|
K2 Summit Production Client connector pinouts ..................................................... |
232 |
|
AES Audio .......................................................................................................... |
232 |
|
RS-422 connector pinouts .................................................................................. |
233 |
|
LTC connectors pinouts...................................................................................... |
234 |
|
GPI I/O connector pinouts .................................................................................. |
235 |
|
K2 Media Client connector pinouts.......................................................................... |
236 |
|
RS-422 connector pinouts .................................................................................. |
236 |
|
LTC connectors pinouts...................................................................................... |
237 |
|
GPI I/O connector pinouts .................................................................................. |
238 |
|
K2 Media Server connector pinouts ........................................................................ |
239 |
|
Redundant server heartbeat cable ..................................................................... |
239 |
Appendix D |
Rack mounting |
|
|
Rack-mount considerations ................................................................................ |
241 |
|
Rack mount hardware shipped with the K2 system............................................ |
242 |
|
Mounting the Rack Slides................................................................................... |
243 |
|
Installing the K2 system on the rack mount rails ................................................ |
244 |
|
Making Rack Slide Adjustments ......................................................................... |
245 |
|
Index ...................................................................................................................... |
247 |
07 April 2010 |
K2 System Guide |
9 |
Contents
10 |
K2 System Guide |
07 April 2010 |
This manual describes K2™ systems and provides the information you need to go beyond factory default settings and customize your system’s configuration to meet your site-specific needs. The manual covers K2 Summit™ Production Client, K2 Solo™ Media Server, including ChannelFlex™ Suite features, and K2 SAN devices.
How this manual is organized
This manual is organized around the tasks required to install and configure K2 systems. The following chapters are included in this manual:
Chapter 1, Product Description
Chapter 2, Using K2 system tools
Chapter 3, System connections and configuration
Chapter 4, Managing Stand-alone Storage
Chapter 6, Managing K2 system software
Chapter 7, Administering and maintaining the K2 system
Chapter 8, Direct Connect Storage
Chapter 9, K2 Summit Transmission Server Package
Appendix A, Remote control protocols
Appendix B, Specifications
Appendix C, Connector Pinouts
Appendix D, Rack mounting
07 April 2010 |
K2 System Guide |
11 |
Finding Information
Getting more information
The following sections help you find the information you need in product manuals and elsewhere.
For the installer of a K2 product with internal storage
If you are installing a K2 client with stand-alone internal storage or a K2 Solo Media Server, refer to documentation in the following sequence:
|
Find this document… |
In these locations… |
In these formats: |
|
|
|
|
|
|
|
|
1 |
K2 Release Notes |
K2 product shipping box |
Printed |
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
2 |
Quick Start Guide for the K2 product |
K2 product shipping box |
Printed |
|
|
|
|
|
|
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
3 |
K2 System Guide |
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
For the installer of a K2 client with direct connect storage
If you are installing a K2 client with stand-alone direct connect storage, refer to documentation in the following sequence:
|
Find this document… |
In these locations… |
In these formats: |
|
|
|
|
|
|
|
|
|
|
|
1 |
K2 |
Release Notes |
K2 product shipping box |
Printed |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
2 |
K2 |
Storage Cabling Guide |
K2 RAID shipping box |
Printed |
|
|
|
|
|
|
|
|
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
2 |
Quick Start Guide for the K2 product |
K2 product shipping box |
Printed |
|
|
|
|
|
|
|
|
|
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
3 |
K2 |
System Guide |
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
12 |
K2 System Guide |
07 April 2010 |
For the installer of K2 clients and K2 SAN shared storage
If you are installing a K2 SAN with connected K2 clients, refer to documentation in the following sequence:
|
Find this document… |
In these locations… |
In these formats: |
|
|
|
|
|
|
|
|
|
|
|
1 |
K2 |
Release Notes |
K2 product shipping box |
Printed |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
2 |
K2 |
Storage Cabling Guide |
K2 RAID shipping box |
Printed |
|
|
|
|
|
|
|
|
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
2 |
Quick Start Guide for the K2 product |
K2 product shipping box |
Printed |
|
|
|
|
|
|
|
|
|
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
3 |
K2 |
SAN Installation and Service Manual |
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
3 |
K2 |
System Guide |
K2 Documentation CD |
PDF file |
|
|
|
|
|
|
|
|
Grass Valley Website |
PDF file |
|
|
|
|
|
Quick Start Guide
You receive this guide in the product packaging with your K2 product. The Quick Start Guide provides step-by-step installation instructions for basic installation and operation of your K2 product, including recording and playing clips.
Release Notes
The K2 Release Notes contain the latest information about the software shipped on your system. The release notes include software upgrade instructions, software specifications and requirements, feature changes from the previous releases, and any known problems. Because release notes contain the latest information, they are printed out and included in the K2 product shipping box, rather than included in the Documentation CD-ROM. You should always check the Grass Valley Website to determine if there is an updated version of release notes available.
K2 Storage Cabling Guide
The cabling guide provides instructions for K2 Storage Area Network cabling and external configuration. The cabling guide provides instructions for each pre-defined level of K2 SAN and covers both redundant and basic (non-redundant) systems. You can find the cabling guide packaged with the primary RAID storage chassis.
Documentation CD
Except for the release notes, the full set of support documentation, including this manual, is available on the K2 Documentation CD-ROM that you received with your K2 product.
07 April 2010 |
K2 System Guide |
13 |
Finding Information
The K2 Documentation CD includes the following documents:
• K2 AppCenter User Manual — Provides instructions for configuring and operating the media channels of product.
• Quick Start Guides — The Quick Start Guide provides step-by-step installation instructions for basic installation and operation of the K2 product.
• K2 System Guide — Contains the product specifications and instructions for modifying system settings.
• Service Manuals — Contains information on servicing and maintaining the K2 product.
• K2 SAN Installation and Service Manual — Contains installation, configuration, and maintenance procedures for shared storage options.
• K2 Storage Cabling Guide — Contains diagrams for cabling the devices of the K2 Summit Production Client.
• RAID Instruction Manuals — There is an Instruction Manual for each type of RAID storage device that can be a part of a K2 Summit Production Client. These manuals contain procedures for configuring and servicing the device.
• Fibre Channel Switch Installation Manual — Contains information on configuring and servicing the Fibre Channel switch.
On-line Help Systems
K2 AppCenter Help — In the AppCenter user interface menu bar select Help, then choose from the drop-down menu.
SiteConfig Help — In the SiteConfig user interface menu bar select Help, then choose SiteConfig Help Topics from the drop-down menu.
NetCentral Help — From the NetCentral interface select Help | NetCentral Help Topics.
NetCentral documentation
The NetCentral product has its own documentation set, described as follows:
• NetCentral Quick Start Guide — Provides an overview of the installation process to quickly set up and run NetCentral.
• NetCentral Installation Guide — Identifies requirements and procedures to correctly set up servers and devices, as well as provides detailed instructions to install and configure NetCentral software.
• NetCentral User Guide — Describes how to use the NetCentral Manager to monitor devices.
•NetCentral Help — From the NetCentral interface access on-line help. Select Help | NetCentral Help Topics.
14 |
K2 System Guide |
07 April 2010 |
Grass Valley Web Site
This public Web site contains all the latest manuals and documentation, and additional support information. Use the following URL.
http://www.grassvalley.com.
Grass Valley Product Support
To get technical assistance, check on the status of a question, or to report a new issues, contact Grass Valley Product Support via e-mail, the Web, or by phone or fax.
To access support information on the Web, visit the product support Web page on the Grass Valley Web site. You can download software or find solutions to problems.
World Wide Web:http://www.grassvalley.com/support/
Technical Support E-mail Address:gvgtechsupport@grassvalley.com
Use the following information to contact Product Support by phone.
Our international support centers are available 24 hours a day, 7 days a week.
Support Center |
Toll free |
In country |
|
|
|
|
|
|
France |
+800 80 80 20 20 |
+33 1 48 25 20 20 |
|
|
|
United States |
+1 800 547 8949 |
+1 530 478 4148 |
|
|
|
A local support representative may be available in your country. To locate a support center during normal local business hours, refer to the following list. This list is regularly updated on the website for Grass Valley Product Support
(http://www.grassvalley.com/support/contact/phone/)
After–hours local phone support is also available for warranty and contract customers.
07 April 2010 |
K2 System Guide |
15 |
Finding Information
Region |
County |
Telephone |
|
|
|
|
|
|
|
|
|
Asia |
China |
+86 |
10 5883 7575 |
|
|
|
|
|
Hong Kong, Taiwan, Korea, |
+852 2531 3058 |
|
|
Macau |
|
|
|
|
|
|
|
Japan |
+81 |
3 6848 5561 |
|
|
|
|
|
Southeast Asia - Malaysia |
+603 7492 3303 |
|
|
|
|
|
|
Southeast Asia - Singapore |
+65 6379 1313 |
|
|
|
|
|
|
India |
+91 |
22 676 10300 |
|
|
|
|
Pacific |
Australia |
1 300 721 495 |
|
|
|
|
|
|
New Zealand |
0800 846 676 |
|
|
|
|
|
|
For callers outside Australia or |
+61 |
3 8540 3650 |
|
New Zealand |
|
|
|
|
|
|
Central America, South America |
All |
+55 |
11 5509 3440 |
|
|
|
|
North America |
North America, Mexico, |
+1 800 547 8949; |
|
|
Caribbean |
+1 530 478 4148 |
|
|
|
|
|
Europe |
UK, Ireland, Israel |
+44 |
118 923 0499 |
|
|
|
|
|
Benelux – Netherlands |
+31 |
(0) 35 62 38 421 |
|
|
|
|
|
Benelux – Belgium |
+32 |
(0) 2 334 90 30 |
|
|
|
|
|
France |
+800 80 80 20 20; |
|
|
|
+33 |
1 48 25 20 20 |
|
|
|
|
|
Germany, Austria, |
+49 |
6150 104 444 |
|
Eastern Europe |
|
|
|
|
|
|
|
Belarus, Russia, Tadzhikistan, |
+7 095 258 09 20; |
|
|
Ukraine, Uzbekistan |
+33 |
(0) 2 334 90 30 |
|
|
|
|
|
Nordics (Norway, Sweden, |
+45 40 47 22 37; +32 2 333 00 02 |
|
|
Finland, Denmark, Iceland) |
|
|
|
|
|
|
|
Southern Europe – Italy |
Rome: +39 06 87 20 35 28 ; +39 |
|
|
|
06 8720 35 42. Milan: +39 02 48 |
|
|
|
41 46 58 |
|
|
|
|
|
|
Southern Europe – Spain |
+34 |
91 512 03 50 |
|
|
|
|
|
Switzerland |
+41 |
56 299 36 32 |
|
|
|
|
Middle East, Near East, Africa |
Middle East |
+971 4 299 64 40 |
|
|
|
|
|
|
Near East and Africa |
+800 80 80 20 20; |
|
|
|
+33 |
1 48 25 20 20 |
|
|
|
|
16 |
K2 System Guide |
07 April 2010 |
Waste Electrical and Electronic Equipment Directive
07 April 2010 |
K2 System Guide |
17 |
Finding Information
18 |
K2 System Guide |
07 April 2010 |
Chapter 1
The K2™ Summit™ Production Client and K2 Solo™ Media Server are cost-effective Broadcast Enterprise Servers that incorporate IT server platform and storage technologies to deliver a networked solution to facilities for ingest, playout, news integration, sports, and media asset management. They provides a suite of user applications and system tools. The manual contains information for all models and options, including ChanneFlex™ Suite. Refer to the sections that apply to your particular model and options.
Control
Point PC
K2 Summit Production Clients,
K2 Media Clients, and K2 Solo Media Servers
Communication over Ethernet network
K2 SUMMIT |
K2 SUMMIT |
Operation, configuration, and monitoring from a remote location
The K2 Summit Production Client and K2 Solo Media Server are designed for “headless” operation from a remote control point using Grass Valley Control Point software. You can also use the Microsoft Windows Remote Desktop Connection application on your PC to connect to the K2 system for configuration or administration.
The K2 Summit Production Client and K2 Solo Media Server products are further described in the following sections:
•“K2 Summit Production Client and K2 Solo Media Server features” on page 20
•“Product identification” on page 22
•“Front panel indicators” on page 23
•“Rear panel view” on page 24
•“K2 Summit Production Client and K2 Solo Media Server system overview” on page 27
Also refer to Chapter 9, K2 Summit Transmission Server Package for information unique to that product.
07 April 2010 |
K2 System Guide |
19 |
Chapter 1 Product Description
The following features apply to the K2 Summit Production Client:
•Two or four channels per chassis
•SDI video inputs and outputs
•AES/EBU or embedded audio inputs and outputs.
•Redundant power supply, cooling fans for reliability
•System drive — compact flash protected by a file-based write filter
•RAID media storage
•Remote operation and configuration via AppCenter
•NetCentral™ provides remote error reporting and monitoring via SNMP (Optional for models using local storage only)
•Gigabit Ethernet
•AMP, VDCP, and BVW remote control protocols supported
•Remote control over RS-422 or Ethernet
•Super Slo-Mo, Multi-cam, and 3D/Video + Key features are available as part of the ChannelFlex Suite
The following features apply to the K2 Solo Media Server:
•Two channels per chassis
•SDI video inputs and outputs
•AES/EBU or embedded audio inputs and outputs.
•System drive — compact flash protected by a file-based write filter
•RAID 0 media storage
•Remote operation and configuration via AppCenter
•NetCentral™ provides remote error reporting and monitoring via SNMP (Optional for models using local storage only)
•Gigabit Ethernet
•AMP, VDCP, and BVW remote control protocols supported
•Remote control over RS-422 or Ethernet
•ExpressCard
•Super Slo-Mo, Multi-cam, and 3D/Video + Key features are available as part of the ChannelFlex Suite
20 |
K2 System Guide |
07 April 2010 |
The K2 Summit Production Client and K2 Solo Media Server have bi-directional video codecs, which means each channel supports both record and play operations. You can encode and decode video using the DVCPRO HD, DVCPRO 25/50, or DVcompression standards. You can also decode MPEG-2. Options include MPEG-2 encode and AVC-Intra encode/decode. All channels support Standard Definition (SD) video and, if licensed, each pair of channels can also support High Definition (HD) video. For more information on available codecs, see “Operational specifications” on page 198.
You can play a sequence of clips of different compression standards and, if licensed, HD and SD formats back-to-back on the same timeline with no channel configuration changes. Both HD and SD clips are played out in the format specified for the output assigned to the channel. All clips are either upor down-converted appropriately to play on that output, and their aspect ratios are adjusted.
For the K2 Summit Production Client, stand-alone internal storage, stand-alone external direct-connect storage, and external shared (SAN) storage models are available.
Features of internal storage models
An internal storage K2 Summit Production Client can have eight media drives. A K2 Solo Media Server has two media drives. Compact Flash serves as the system drive. This makes the internal storage K2 system a self-contained, stand-alone unit, with no external devices for storage connections required. You can transfer media in and out of the internal storage K2 system via Gigabit Ethernet. You can also export media to a mapped drive or USB-attached storage. With the K2 Solo Media Server, you can also export media via the ExpressCard.
The external storage K2 Summit Production Client contains only the Compact Flash that serves as the system drive. There are no media drives in an external storage K2 Summit Production Client. There are two types of external storage for media, as follows:
•Shared storage — Multiple external storage K2 Summit Production Clients connect to the K2 SAN via Gigabit Ethernet or Fibre Channel to share a common pool of storage.
•Direct-connect storage — A single K2 Summit Production Client with the optional Fibre Channel board installed connects directly to its own external (non-shared) RAID storage device. This makes the direct-connect K2 Summit Production Client a self-contained, stand-alone unit, with no external (non-shared) devices for storage, audio, or video connections required. You can transfer media in and out of the direct-connect K2 Summit Production Client via Gigabit Ethernet.
07 April 2010 |
K2 System Guide |
21 |
Chapter 1 Product Description
The K2 Summit Production Client has labels affixed to the chassis that provide product identification as in the following diagram:
Serial Number
(e.g. K2—01AA00010) This is also the factory default hostname
USB compartment
(Compartment swivels up.) Note: removing the bezel takes
the fans offline. Replace the bezel assembly within one minute to maintain system cooling.
The K2 Solo Media Server has labels affixed to the chassis that provide product identification as in the following diagram:
Serial Number
(e.g. K2—01AA00010) This is also the factory default hostname
22 |
K2 System Guide |
07 April 2010 |
Front panel indicators
With the front bezel in place, the indicator LEDs are visible. The LEDs indicate the status of the machine. For example, when the Service LED is a steady yellow light, this could signify that one of the power cables is unplugged. For more information on indicator LEDs, see the service manual for your K2 product.
PRODUCTION |
K2 SUMMIT CLIENT |
Standby Power Service
switch LED LED
Disk Module
LEDs
Standby Power Service
switch LED LED
07 April 2010 |
K2 System Guide |
23 |
Chapter 1 Product Description
The following drawings identify the rear panel connectors and components.
SDI video in and out supports embedded audio.
|
SDI ina |
Channel Flex a |
SDI out a |
SDI monitor out. a, b |
|
|||||
|
I/O |
SDI IN1 |
SDI IN2 |
SDI IN3 |
SDI OUT1 |
SDI OUT2 |
LTC I/O |
LTC in/out |
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
AES AUDIO |
|
RS422 |
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
AES audio |
|
|
|
|
|
|
|
RS-422 |
|
(connect via optional |
|
|
|
|
|
|
|
|
|
|
multi-connector cable) |
|
|
|
|
|
|
|
|
|
|
|
Channel 1 |
|
Channel 2 |
Channel 3 |
Channel 4 |
|
||||
SDI IN1 SDI IN2 SDI IN3 |
SDI OUT1 SDI OUT2 LTC I/O SDI IN1 |
SDI IN2 |
SDI IN3 |
SDI OUT1 SDI OUT2 |
LTC I/O |
SDI IN1 |
SDI IN2 SDI IN3 |
SDI OUT1 SDI OUT2 |
LTC I/O SDI IN1 SDI IN2 SDI IN3 SDI OUT1 |
SDI OUT2 LTC I/O |
AES AUDIO |
RS422 |
AES AUDIO |
RS422 |
|
|
AES AUDIO |
RS422 |
AES AUDIO |
RS422 |
|
C1 |
|
|
|
|
C2 |
C3 |
|
|
|
C4 |
OK |
OK |
! |
! |
|
GPI |
~AC |
~AC |
USB/1394 100BT/1000BT VGA REF. LOOP THROUGH
Power Optional Fibre Channel |
IEEE |
USB |
VGA |
Reference |
GPI |
Power |
card for connection to |
1394 |
(keyboard, |
monitor |
Loop Thru c |
|
|
direct-connect storage |
(Do not |
mouse) |
|
|
|
|
or shared (SAN) storage |
use) |
|
|
|
|
|
Port 2: Media (iSCSI) A
Media Connection #1
Port 2: FTP/Streaming |
|
|
|
Media Connection #1 |
|
|
|
Stand-alone direct-connect |
|
|
|
or internal storage |
|
|
|
1394 |
100BT/1000BT |
1394 |
100BT/1000BT |
Port 3: Media (iSCSI) B
for redundant SAN
Media Connection #2
Shared (SAN)
storage
Port 1: Control |
Port 4: Control |
Port 1: Control A |
Port 4: Control B |
||
Control Connection #1d |
(Optional) |
Control Connection #1d |
for redundant SAN |
||
|
|
Control Connection #2 d |
|
Control Connection #2 d |
|
a Supports |
bSupports Super Out, |
c Tri-level sync |
dControl Connections are teamed |
||
Channel Flex Suite, |
which requires |
not supported |
and share the same IP address |
||
which requires |
AppCenter Pro or |
|
|
|
|
AppCenter |
Elite license |
|
|
|
|
Elite license |
|
|
|
|
|
24 |
K2 System Guide |
07 April 2010 |
K2 Solo Media Server rear panel
SDI video in and out supports embedded audio.
SDI ina |
Channel Flex a |
SDI out a |
SDI monitor out. a, b |
||
I/O |
SDI IN1 |
SDI IN2 SDI IN3 |
SDI OUT1 SDI OUT2 |
LTC I/O |
LTC in/out |
|
|
|
|
||
|
|
AES AUDIO |
RS422 |
|
|
|
|
|
|
|
C |
AES audio |
|
|
|
|
RS-422 |
(connect via optional |
|
|
|
|
|
multi-connector cable) |
|
|
|
|
|
|
|
Channel 1 |
Channel 2 |
|
SDI IN1 |
|
OUT1 |
SDI OUT2 |
LTC I/O |
|
AES AUDIO |
RS422 |
AES AUDIO |
|
RS422 |
|
C1 |
|
|
|
|
C2 |
|
|
USB/1394 |
|
|
|
|
|
100BT/1000BT |
|
|
|
|
100-240 V- |
|
GPI |
|
|
|
4-2A, |
VGA |
REF. LOOP THROUGH |
||
|
|
||||
|
60-50Hz |
|
|
|
|
Power |
IEEE |
USB |
VGA |
Reference |
GPI |
|
1394 |
(keyboard, |
monitor |
Loop Thru c |
|
|
(Do not |
mouse) |
|
|
|
|
use) |
|
|
|
|
Port 2: FTP/Streaming
Media Connection #1
1394 |
100BT/1000BT |
|
Port 1: Control |
Port 4: Control |
|
|
Control Connection #1d |
(Optional) |
|
|
|
Control Connection #2 d |
|
a Supports |
bSupports Super Out, |
c Tri-level sync |
dControl Connections are teamed |
Channel Flex Suite, |
which requires |
not supported |
and share the same IP address |
which requires |
AppCenter Pro or |
|
|
AppCenter |
Elite license |
|
|
Elite license |
|
|
|
07 April 2010 |
K2 System Guide |
25 |
Chapter 1 Product Description
ChannelFlex Suite features require the AppCenter Elite license. Super Slo-Mo also requires the HD license. When configured for these features, channel connections are as follows:
Multi-Cam Recorder
Video 1 |
Video 2 |
Super Slo-Mo Recorder
Phase 1 Phase 2 Phase 3
O |
SDI IN1 |
SDI IN2 |
SDI IN3 |
SDI OUT1 SDI OUT2 |
LTC I/ |
O |
SDI IN1 |
SDI IN2 |
SDI IN3 |
SDI OUT1 SDI OUT2 |
LTC I/ |
|
|
|
|
AES AUDIO |
RS422 |
AES AUDIO |
RS422 |
3D/Video + Key Recorder
Video or |
Key or |
|
|
|
Left eye |
Right eye |
|
|
|
O |
SDI IN1 |
SDI IN2 SDI IN3 |
SDI OUT1 SDI OUT2 |
LTC I/ |
|
|
|
||
|
|
AES AUDIO |
RS422 |
|
3D/Video + Key Player
|
Video or |
Key or |
||
|
Left eye |
Right eye |
||
O |
SDI IN1 SDI IN2 SDI IN3 |
SDI OUT1 |
SDI OUT2 |
LTC I/ |
|
|
|
||
|
AES AUDIO |
|
RS422 |
|
Refer to the K2 AppCenter User Manual for more information on ChannelFlex Suite features.
When you receive a K2 system from the factory, one or more End User License Agreements (EULAs) appear on the screen at first startup. Software licensing agreements require that you accept these EULAs. When you do so, start up processes can proceed. This behavior occurs only at first startup. Subsequent startups do not exhibit this behavior.
The following are examples of the EULAs that you might see.
On a K2 Media Server, at first startup the following behavior occurs:
•A Windows Server 2003 End User License Agreement (EULA) opens on the screen.
26 |
K2 System Guide |
07 April 2010 |
K2 Summit Production Client and K2 Solo Media Server system overview
The K2 Summit Production Client and K2 Solo Media Server are purpose-built clients based on COM Express compact computer with dedicated systems to provide the video disk recorder functionality. This section explains the major architectural blocks.
The K2 Summit Production Client and K2 Solo Media Server application system architecture uses the COM Express form factor to provide functionality similar to that of standard PC-type computers. The carrier module contains a CPU module, built in Ethernet, and USB ports. On the K2 Summit Production Client, the carrier module also includes one PCIe board slot for expansion.
The Application system uses a Windows XP embedded operating system upon which all internal storage K2 system applications run for configuration and control of the unit.
Each channel hosts a complete Real Time system that provides the core video disk recorder functionality. Primary components are as follows:
•Dedicated processor for media access and processing.
•Codec circuits responsible for encoding/decoding video and processing audio and timecode, including the media-related input and output connectors.
The Real Time system uses a dedicated operating system. This operating system manages all the hardware involved in controlling the flow of video, audio, timecode, genlock, and GPI in and out of the K2 system.
The following section explains how the Application system and the Real Time system work together to provide K2 system functionality.
The high processing requirements of digital video can overwhelm the processor on a standard desktop PC, resulting in wait-times that destroy the video’s essential real-time aspect. The K2 system avoids this problem by providing dedicated systems that isolate processing needs. The components that work together to provide this functionality are as follows:
The Application system is dedicated to control, configuration, and networking functions that do not require real-time accuracy. The Application system has the following components:
•Application software provides the user interface for operating the K2 system. The software runs as Windows programs.
•The Media File system manages clips. It includes a database that associates the clip with its video, audio, and timecode files and a dedicated file system (separate from the Windows file system) that controls access to the raw data that makes up each file. Any reading and writing of clips, be it through play and record operations or through file transfers and media streaming, is managed by the database. The
07 April 2010 |
K2 System Guide |
27 |
Chapter 1 Product Description
database and file system run as Windows programs.
The Storage system includes the media disk drives, controllers, drivers, and adapters necessary for access and movement of the data. While the primary data flow is within the overall control of the Real Time system, some components and their communication pathways cross over into the Application system. For example, the media drives appear as the V: drive to the Windows operating system.
The Real Time system manages the media flow between the Storage system and the inputs and outputs. The Real Time system has dedicated processors and time-sensitive mechanisms to serve media processing needs while maintaining real-time accuracy.
When you control play and record operations from within the Application system you trigger a chain of events that eventually crosses over into the Real Time system and results in media access. The following sequence is an example of this type of chain of events:
1.A user operates the Player application to play a particular clip. The Player application asks the Media File system for permission to access the clip. The Media File system grants access. In shared storage models, the Media File system enforces shared storage policies in order to grant the access. When access is granted, the Player application initiates play access to the clip.
2.The database identifies the files that make up the clip and the file system instructs the Storage system to open access to the files.
3.The Storage system finds the raw data and opens the appropriate read access. At this point both the Application system and the Real Time system are involved. Windows controls the media drives and controllers, so the Real Time system makes file requests to Windows and it causes the data to be transferred to buffers on the Real Time processor. The data is then available to the Real Time system so that it can be processed at exactly the right time.
4.The Real Time system processes the media, decompresses it, adjusts its timing, and moves it as required to play the clip as specified by the user.
Behaviors related to input signals routed to output connectors are described in the following sections. Also refer to Appendix A, Remote control protocols for information regarding E to E commands.
For best results in all workflows, use synchronous feeds, defined as follows:
•All outputs are locked to the house reference
•All inputs are genlocked to the house reference and at zero time
The SD-00 K2 Media Client, the HD-00 K2 Media Client, the K2 Summit Production Client and K2 Solo Media Server can record inputs that are asynchronous, with the following considerations:
•The encoder clock and the audio clock are derived from the input signal, which enables frame accurate recording of all inputs.
28 |
K2 System Guide |
07 April 2010 |
Loop through, E to E, and feeds
•Outputs are timed to the reference and if no reference is present, the output runs free.
•If the input video rate does not equal the output video rate (asynchronous) then video tearing or jumping can occur when input/output synch is critical, such as in the following:
•K2 TimeDelay
•SD-00 or Summit E-to-E (LoopThru) mode
•HD-00 Loopback
The Player/Recorder application has a “E-to-E (LoopThru) mode” selection on the Control menu. This mode applies when the channel is under local AppCenter control as well as when it is under remote control, for all protocols.
This “E-to-E (LoopThru) mode” feature allows you to monitor the video that is being recorded. The video is routed back essentially untouched. Any audio or timecode that is on the input video stream is still there on the loop through output. The K2 Summit/ Solo, or SD-00 K2 Media Client, and the loop through videos must be locked to a video reference for the loop through feature to work properly. This “E-to-E (LoopThru) mode” feature should not be confused with true E to E, such as that on the SDA-00 K2 Media Client. True E to E is not supported on theK2 Summit/Solo or SD-00 K2 Media Client.
When “E-to-E (LoopThru) mode” is not selected, the channel behaves as follows:
•“PB” is displayed on the channel pane, next to the Timecode Source indicator.
•When no clip is loaded, black plays out.
•When a record operation stops, Recorder becomes Player and the clip remains in the Player. The clip’s last frame plays out.
When “E-to-E (LoopThru) mode” is selected, the channel behaves as follows:
•“EE” is displayed on the channel pane, next to the Timecode Source indicator.
•When no clip is loaded, the signal that is currently present at the channel input plays out.
•When a record operation stops, Recorder stays Recorder and the clip remains in the Recorder. The signal that is currently present at the channel input plays out.
07 April 2010 |
K2 System Guide |
29 |
Chapter 1 Product Description
The following ports are used by the applications and system tools of the K2 family of products:
Port # |
Type of |
Service name |
Description |
|
|
connection |
|
|
|
|
|
|
|
|
|
|
|
|
|
20 |
TCP |
Can be |
FTP |
|
|
|
mpgsession.exe, |
|
|
|
|
mxfsession.exe, |
|
|
|
|
gxfsession.exe, or |
|
|
|
|
ftpd.exe |
|
|
|
|
|
|
|
21 |
TCP |
ftpd.exe |
FTP data |
|
|
|
|
|
|
161 |
UDP |
snmp.exe |
SNMP |
|
|
|
|
|
|
162 |
UDP |
snmptrap.exe |
SNMP trap |
|
|
|
|
|
|
3389 |
TCP |
Remote Desktop |
Used by SiteConfig. |
|
|
|
|
|
|
3811 |
TCP |
Grass Valley |
Used by 3rd party applications to communicate |
|
|
|
AppService |
using AMP protocol |
|
|
|
|
|
|
18262 |
TCP |
GV ProductFrame |
Used by SiteConfig. |
|
|
|
Configuration Service, |
|
|
|
|
ProductFrame |
|
|
|
|
Discovery Agent |
|
|
|
|
Service |
|
|
|
|
|
|
|
18263 |
UDP |
ProductFrame |
GV NetConfig Device Broadcast/Unicast |
|
|
|
Discovery Agent |
Protocol. Used by SiteConfig. Sent by |
|
|
|
Service |
ControlPoint, received by Devices |
|
|
|
|
|
|
18264 |
UDP |
ProductFrame |
GV NetConfig Controller Protocol. Used by |
|
|
|
Discovery Agent |
SiteConfig. Sent by Devices, received by |
|
|
|
Service |
ControlPoint |
|
|
|
|
|
|
49168 |
HTTP |
Grass Valley |
K2 System Configuration application connection |
|
|
|
K2 Config |
between a control point PC and the K2 system |
|
49169 |
TCP |
|||
|
device configured. Both HTTP and TCP |
|||
|
|
|
||
|
|
|
connections are required. Most functions use the |
|
|
|
|
HTTP connection, but a few functions that |
|
|
|
|
require longer time periods use TCP. |
|
|
|
|
|
|
49170 |
HTTP |
Grass Valley |
Transfer Manager connection between source |
|
|
|
Transfer Queue Service |
system and destination system. |
|
|
|
|
|
|
49171 |
TCP |
Grass Valley |
AppCenter connection for connection between |
|
|
|
AppService |
control point PC and K2 client/Solo. |
|
|
|
|
|
|
49172 |
HTTP |
Grass Valley |
Connection for Storage Utility between the |
|
|
|
Storage Utility Host |
control point PC and the K2 system being |
|
|
|
|
configured. |
|
|
|
|
|
30 |
K2 System Guide |
07 April 2010 |