Grass Valley K2 System Guide v.9.0 - Manual (Page 212)

• Preview clip — The VDCP “preview preset id” is considered the preview clip. When a play
command is received, the preview clip becomes the active clip and begins playing after the preroll
time has passed. If a play command has not been issued by the end of the clip, playout stops
according to the VDCP end mode settings for that channel (last frame, black, first frame of
preview clip).
Related specifications are as follows:
• A 3D/Video+Key player channel does not support a two-head player model.
Controlling transfers with VDCP
Remote control automation applications can initiate transfers via VDCP. The VDCP command must
be sent to the K2 Summit/Solo system, not the K2 Media Server. This applies to both stand-alone
and shared storage K2 Summit/Solo system.
If you are using VDCP to perform video network transfers, you must configure the K2 Summit/Solo
system so that there is a unique Controller ID for each host.
If using VDCP to initiate transfers between K2 systems and Profile XP systems, you must send the
VDCP command to the K2 system, not the Profile XP system. Transfers (both push and pull) are
successful if the K2 system hosts the command. Transfers fail if the Profile XP system hosts the
command.
Transfers initiated by VDCP between K2 systems and M-Series iVDRs are not supported.
VDCP internationalization
VDCP does not support UTF-8 or Unicode, so use ASCII only for clip names and bin names.
PitchBlue workflow considerations
The K2 Summit system supports the H.264 format used in the PitchBlue workflow. However, you
must consider the intended PitchBlue workflow when using this H.264 media, as it is not supported
for general purpose use outside of the PitchBlue workflow.
The K2 Summit system ingests the PitchBlue material without any error correction. The material
often has anomalies, such as a broken last frame, that the K2 Summit system accepts as-is. When
PitchBlue plays out this material under VDCP automation control, it plays the known-good material
only. PitchBlue determines where the anomalies exist and makes sure that they are not played out.
In this way PitchBlue avoids the errors that would otherwise occur if the material were used for
general purpose playout without PitchBlue control.
Therefore, you must adhere to the complete PitchBlue workflow from ingest through playout for
all PitchBlue material. Do not attempt to play out PitchBlue material except as part of the prescribed
PitchBlue workflow. Playing out PitchBlue material in any other way can cause errors.
212 K2 System Guide 06 November 2012
Remote control protocols