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

successful if the K2 system hosts the command. Transfers fail if the Profile XP system hosts the
command.
Transfers initiated by AMP between K2 systems and M-Series iVDRs are not supported.
AMP channel designations
When using AMP protocol with Ethernet and the K2 Summit/Solo system, the first port maps to
the first channel, the second port maps to the second channel, and so on.
AMP internationalization
AMP supports UTF-8 2 and 3 byte characters. Unicode movie names pass through as opaque bits.
Using VDCP protocol to control K2 systems
Video Disk Control Protocol (VDCP) commands are available via RS-422 serial ports.
Preroll is 1 second for mixed compression format playout. Preroll is 10 frames for same compression
format playout.
The K2 AppCenter Recorder application in protocol mode allows a default bin to be assigned to
each record channel.
In AppCenter, you must set a channel’s options to enable protocol control of the channel.
Subsequently, when the K2 Summit/Solo system starts up, the channel is immediately available for
protocol control. Manual log on is not required.
For channels in gang mode, the protocol must connect to the lowest numbered channel in the gang.
This is required to support jog/shuttle of ganged channels.
Loop-play mode on the K2 Summit/Solo system is not supported under VDCP control.
The following categories of VDCP commands are not supported:
• Deferred (Timeline) Commands --these are the basic timeline commands but use the time specified
by the PRESET STANDARD TIME
• Macro commands
• Archive Commands
• To control a given K2 channel, use only that channel’s specific RS-422 rear panel connector.
Send the VDCP “Open Port” and “Select Port” commands only to the RS-422 connector that is
associated with the channel being controlled.
VDCP two-head player model
The VDCP protocol supports the use of a two-head player model in that two clips may be loaded
for playout, as follows:
• Current clip — The VDCP “preset id” is the current clip.
06 November 2012 K2 System Guide 211
Remote control protocols