Grass Valley K2 System Guide v.9.0 User Manual
Media platform
Advertising
This manual is related to the following products:
Table of contents
Document Outline
- Contents
- Safety Summaries
- Preface
- Product description
- About K2 systems
- K2 Summit 3G system features
- K2 Summit system features
- K2 Solo 3G system features
- K2 Solo system features
- K2 Summit/Solo formats, models, licenses, and hardware support
- Features of internal storage models
- Features of external storage models
- Product identification K2 Summit 3G
- Product identification first generation K2 Summit
- Product identification K2 Solo
- Front panel indicators K2 Summit 3G system
- Front panel indicators first-generation K2 Summit
- Front panel indicators K2 Solo
- Rear panel view
- Considerations for first startup out of box
- K2 Summit/Solo system overview
- Ports used by K2 services
- RAID drive numbering K2 Summit 3G system
- RAID drive numbering first generation K2 Summit system
- RAID drive numbering K2 Solo system
- Overview of K2 System Tools
- System connections and configuration
- About networks
- Network connections
- Network configuration
- Configuring Server 2008 for domain
- Using FTP for file transfer
- About the K2 FTP interface
- Limitations with complex media types
- Transferring between different types of systems
- Transfer mechanisms
- FTP access and configuration
- FTP access by automation
- FTP and media access security
- About FTP internationalization
- Setting the FTP language
- FTP access by Internet Explorer
- FTP commands supported
- Using FTP on a K2 Nearline SAN
- Using reference files
- Quicktime and Final Cut Pro support
- Connecting RS-422 K2 Summit/Solo 3G system
- Connecting RS-422 first generation Summit
- Connecting GPI
- Import/export services
- Managing Stand-alone Storage
- About the internal storage system
- About the direct-connect storage system
- Using Storage Utility
- About Storage Utility
- Opening Storage Utility
- Overview of Storage Utility
- Checking storage subsystem status
- Checking controller microcode
- About identifying disks
- Identifying internal disks
- Get controller logs
- Check disk mode pages
- Disabling a disk
- Forcing a disk to rebuild
- Unbind LUN
- Bind Luns
- Changing RAID type for internal storage
- Making a new media file system on a K2 Summit/Solo
- Checking the media file system
- Cleaning unreferenced files and movies
- Downloading controller microcode
- Downloading disk drive firmware
- Placing the K2 system into online mode
- Managing stand-alone K2 systems with SiteConfig
- About managing stand-alone K2 clients with SiteConfig
- SiteConfig and stand-alone K2 clients checklist
- System requirements for SiteConfig host PC
- About installing SiteConfig
- Installing/upgrading SiteConfig
- Creating a system description for stand-alone K2 clients
- Creating the control network for stand-alone K2 clients
- Creating the FTP/streaming network for stand-alone K2 clients (optional)
- Adding a group
- Adding stand-alone K2 clients to the system description
- Modifying stand-alone K2 client unassigned (unmanaged) interfaces
- Discovering devices with SiteConfig
- Assigning discovered devices
- Modifying stand-alone K2 client managed network interfaces
- Adding a control point PC placeholder device to the system description
- Assigning the control point PC
- Making the host name the same as the device name
- Pinging devices from the PC that hosts SiteConfig
- About hosts files and SiteConfig
- Generating host tables using SiteConfig
- Configuring deployment groups
- About deploying software for stand-alone K2 clients
- Managing K2 system software
- Administering and maintaining the K2 system
- Licensing
- Configuring K2 security
- Overview of K2 security features
- Example: Setting up user access to bins
- Example: Setting up user access to channels
- Passwords and security on Grass Valley systems
- Configuring media access security for K2 bins
- AppCenter operations and media access security
- FTP and media access security
- K2 SANs and media access security
- Protocol control of channels and media access security
- About channel access security
- K2 and STRATUS security considerations
- Understanding virus and security policies
- About tri-level sync
- Auto log on
- Regional and language settings
- Checking RAM
- Direct Connect Storage
- About the direct-connect Fibre Channel card
- Setting up direct-connect K2 G10v2 RAID storage
- Setting up direct-connect K2 G10 RAID storage
- Uninstalling Multi-Path I/O Software on a direct-connect K2 system
- Installing Multi-Path I/O Software on a direct-connect K2 system
- Powering on K2 G10v2 RAID
- Powering on K2 G10 RAID
- K2 Summit Transmission models
- Proxy/live streaming
- Remote control protocols
- Specifications
- K2 Summit transmission models specifications
- AC power specification
- Environmental specifications
- Mechanical specifications
- Electrical specifications
- Operational specifications
- Video codec description K2 Summit/Solo
- Playout of multiple formats
- Active Format Description (AFD) specifications
- VBI/Ancillary/data track specifications
- VBI/Ancillary/data track definitions
- Luma/Chroma VBI support on K2 Summit/Solo
- VBI data support on K2 Summit/Solo
- Data track support on K2 Summit/Solo SD channels
- Data track support on K2 Summit/Solo HD channels
- Captioning system support
- About FCC requirements
- About privately defined data packets
- Data bridging of VBI information on K2 Summit/Solo HD channels
- Line mapping of ancillary data packets on K2 Summit/Solo HD channels
- PitchBlue/H.264 ancillary data and timecode
- Internationalization
- Limitations for creating and naming assets and bins
- Video network performance
- About file interchange mechanisms on K2 systems
- Media file system performance on K2 systems
- Transition effects formats and limitations
- Protocols supported
- Transfer compatibility with K2 Summit/Solo
- Control Point PC system requirements
- MIB specifications
- Connector pinouts
- Rack mounting
- Trademarks and Agreements
- Index