Operation considerations
• Do not neglect to make a “first birthday” image of each K2 product shortly after
installation and configuration is complete.
• Changing system video standards (NTSC/PAL) requires a restart as part of the
channel changes as soon as the new standard is selected. Configuration Manager
causes an immediate restart of the K2 client if the system reference standard is
changed and AppCenter is being used.
• 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. For example, on
a K2 Summit Production Client, AppCenter allows you to create bin names and
clip names longer than 32 characters. However, names of this length are not
supported on Aurora products.
• Tri-level sync is not supported on K2 systems.
• Before configuring audio tracks on a channel, eject all clips. This is required to put
changes into effect.
• The K2 client and K2 Media Server can operate continuously for a long period of
time, but the recommended operational practice is to restart at least once every
three to six months.
• When restoring from a system-specific recovery image (an image you have created
from your K2 system or the image on your K2 system's USB recovery flash drive),
follow the procedure in the K2 product's service manual. When restoring from a
generic recovery image (a baseline image for the K2 product), you must also restore
network configuration, install K2 software, install SNFS software, and make a new
file system.
• Mix effects (an AppCenter Pro feature) are supported as follows:
• Supported between like compression formats: DV-to-DV, MPEG-to-MPEG,
etc.
• Not supported between between different compression formats.
• Not supported for MPEG long GoP.
• A 3D/Video+Key player channel does not support agile play, mix effects, or a
two-head player model.
• 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 Production
Client and K2 Solo Media Server components on page 11 earlier in these release
notes. 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.
100 K2 Version 7.2.7 Release Notes & Upgrade Instructions 12 May 2010
Operation considerations
To Next Page
Loading...
