Other Topic Library Versions

Operation considerations

  • 6xSSM with Audio requires that a larger RTIO number be entered into SNFS.
  • If you have problems using SiteConfig to discover a Windows Server 2008 K2 Media Server, make sure the server has an IP address. SiteConfig cannot discover Windows Server 2008 systems that do not have an IP address, such as those configured for DHCP.
  • Do not neglect to make a “first birthday” image of each K2 product shortly after installation and configuration is complete.
  • Changing system timing requires a restart. This takes effect immediately as soon as the new video standard (NTSC/PAL) is selected. Save all your configuration changes prior to changing the system timing.
  • Refer to the “Remote control protocols” appendix in the K2 System Guide for operation considerations related to AMP, VDCP, BVW, Harris, RS-422, etc.
  • To import/export between systems using AppCenter, in Configuration Manager on the Remote tab, add each system that you want to have available as a source or a destination. Do this for K2 systems as well as non-K2 systems, such as Profile XP.
  • When transferring between K2 systems and other types of systems, such as Profile XP, you must specify the IP address, path, and file name to initiate a transfer.
  • Constrain media names and filepaths for support across systems. While AppCenter allows you to create bin names and clip names longer than 32 characters, names of this length are not supported on all products.
  • Before configuring a channel, eject all clips from the channel. This is required to put changes into effect.
  • K2 Summit/Solo systems and K2 Media Servers can operate continuously for a long period of time. A restart at least once every six months is the recommended operational practice. A restart once every year is required.
  • Mix effects (an AppCenter Pro feature) are not supported between different compression formats.
  • A 3D/Video+Key player channel does not support agile playback or transition (mix) effects.
  • A 3D/Video+Key player channel does not support a two-head player model.
  • A 3D/Video+Key player channel does not support offspeed play greater than 1 or less than -1. During these offspeed play operations the video is not synchronized between the two video tracks. However, both video outputs will resync when recued.
  • On a K2 Solo Media Server, before making a new file system, first upgrade drive firmware to the latest version, as specified in Compatible K2 Summit/Solo components. Failure to do so generates a Storage Utility error.
  • Grass Valley recommends that you use a frame synchronizer on incoming video sources that are recorded in AVC-Intra format.
  • If Dyno PA connects to an internal storage first generation K2 Summit system, there are special requirements for media disk labels. Refer to the Dyno Production Assistant Configuration Manual.
  • When configuring editors on a K2 SAN with 1 Gig TOEs, do not assign editors and K2 clients (K2 Summit or K2 Media Client) to the same TOE. Instead, assign editors to their own TOE.
  • A K2 10G (NEC D4) RAID controller connected to a Fibre Channel switch must have its "Link Attach" parameter set to "Point-to-Point". A K2 10G RAID controller connected directly to a K2 Summit system must have its "Link Attach" parameter set to "LOOP". When you purchase your K2 10G RAID system from Grass Valley, it comes configured correctly for your intended use. If you re-use a K2 10G RAID system and change the way it is connected, contact Grass Valley for instructions to change the Fiber Channel port configuration. The K2 10Gv2 (NEC M100) RAID controller detects this automatically and so no manual configuration is required.
  • A best practice is to check the K2 Summit log weekly to monitor the database size. Every 15 minutes the K2 Summit system reports a "Completed database backup..." message that includes the database size. If the size exceeds 80 MB, reduce the number of markers and/or the amount of metadata in clips.
  • If you have a first generation K2 Summit system with a Type II (ADLINK with 4GB RAM), Type III (ADLINK with 8GB RAM), or Type IV (ADLINK with 8GB RAM) CPU carrier module or a 3G codec, consult 3G service procedures in the "Servicing the K2 Summit system" section of the K2 Topic Library when doing any service work or replacing any Field Replaceable Units (FRUs). This is true even if replacing an original FRU that has not been upgraded. System dependencies involving FRUs require 3G service procedures.
  • It is not recommended to use 720p tri-level sync for interlace output formats (such as SD and 1080i) Output timing can be off by a field.
  • In the AppCenter Import dialog box there can be a long wait time while network devices are discovered. An improvement with the Windows 7 operating system is that a message opens asking if you want to continue waiting. If you continue waiting, eventually network devices are discovered and AppCenter continues operating.

Copyright © 2015 Grass Valley USA, LLC. All rights reserved. K2 Summit 9.5 gvtp_20151106_14:27:14