Operation Considerations - GRASS VALLEY K2 7.3.8 - RELEASE NOTES AND Quick Start Manual

Operation considerations

Do not neglect to make a
con guration 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. Con guration 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 Con guration 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 Pro le XP.
When transferring between K2 systems and other types of systems, such as Pro le XP, you must
specify the IP address, path, and le name to initiate a transfer.
Constrain media names and lepaths 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 con guring 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-speci c recovery image (an image you have created from your
K2 system or the image on your K2 system's USB recovery ash 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 con guration, install K2 software,
install SNFS software, and make a new le system.
Mix effects (an AppCenter Pro feature) are supported as follows:
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 le system, rst upgrade drive rmware to
the latest version, as speci ed in
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 K2 system, there are special requirements for media
disk labels. Refer to the Dyno Production Assistant Con guration Manual.
When con guring 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.
To export AVI format les to a shared CIFS drive, rst export to the local disk, then copy the
le to the share.
23 November 2010
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.
rst birthday image of each K2 product shortly after installation and
Compatible K2 Summit/Solo components
K2 Version 7.3.8 Release Notes & Upgrade Instructions
on page 31. Failure
30