Grass Valley K2 Media Client System Guide v.3.3 - Manual (Page 172)

172 K2 Media Client System Guide June 9, 2009
Appendix A Remote control protocols
Using AMP protocol to control K2 systems
Advanced Media Protocol (AMP) is an extension of the Odetics protocol.
AMP commands are available via Ethernet or RS-422 serial ports.
The automation setting for preroll should be at least 10 frames.
The AMP's socket interface uses IANA assigned port number 3811 for TCP.
E to E commands have no effect on the HD-00 K2 Media Client. Do not issue E to E
commands to the HD-00 K2 Media Client. Also refer to
“Loop through and E to E”
on page 38 .
In AppCenter, you must set a channel’s options to enable protocol control of the
channel. Subsequently, when the K2 client 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.
AMP PlayAt and StopAt commands do not work on a SD-00 K2 Media Client
channel that is cued for play or is playing, if the channel is configured for VITC
timecode. Under these conditions the VITC-input reader is not connected. To make
those commands work, configure the channel for a different timecode source.
The AMP device type request (00.11) command returns a unique value for SD-00 K2
Media Clients (D8.03) and HD-00 K2 Media Clients (D8.04).
Two-Head Player Model
The AMP protocol supports the use of a two-head player model in that two clips can
be loaded for playout, as follows:
• Current clip — The AMP “preset id” is the active clip.
• Preview clip — The AMP “preview preset id” is the preview clip. The preview clip
becomes the current clip and begins playing when the current clip completes.
When controlling AMP in Auto mode, the “in preset” (and “out preset”) command
should be sent before the Preview in commands.
Controlling transfers with AMP
Remote control automation applications can initiate transfers via AMP. The AMP
command must be sent to the K2 client, not the K2 Media Server. This applies to both
stand-alone and shared storage K2 clients.
If using AMP to initiate transfers between K2 systems and Profile XP systems, you
must send the AMP 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 AMP between K2 systems and M-Series iVDRs are not
supported.