Transferring between different types of systems, Transfer mechanisms – Grass Valley K2 System Guide v.9.0 User Manual
Page 75
audio types cannot stream to other devices, nor can they be exported to a file. Refer to release notes
for the specific software versions for details.
MXF OP1A supports transfer of simple media types only, which are a subset of the K2
encode/decode/metadata capabilities. For example, MXF OP1A does not support the transfer of
complex clips, such as a subclip that spans two media files. Do not attempt MXF OP1A transfers
of complex clips.
Transferring between different types of systems
While GXF transfer of media with mixed format (such as an agile playlist) is supported between
K2 systems, it might not be supported between a K2 system and a non-K2 system, depending on
system software versions. Refer to the release notes for the software version.
You can also use remote control protocols to initiate transfers.
Related Topics
on page 209
on page 215
Transfer mechanisms
You can move material between systems using the following mechanisms, each of which offers a
different set of features:
•
Manual mechanisms — These are the AppCenter transfer features. Refer to the K2 AppCenter
User Manual for AppCenter instructions. When transferring between K2 systems you can browse
and select files for transfer. When transferring between K2 systems and other types of systems,
one or more of the following might be required, depending on software versions. Refer to release
notes for the version information:
•
Specify the IP address, path, and file name to initiate a transfer.
•
Add the remote host in Configuration Manager before the transfer.
•
Enter machine names in compliance with UIM naming conventions.
•
Automatic mechanisms, including the following:
•
K2 FTP interface — This interface supports transfers via third party FTP applications, such
as automation systems. To demonstrate this, you can use Internet Explorer to transfer files
between a PC and the FTP interface on a stand-alone K2 Summit Production Client or a K2
Media Server on the same network.
•
Remote control protocols — Industry standard remote control automation applications can
initiate transfers. The protocol command must be sent to the K2 client. This applies to both
stand-alone and shared storage K2 systems.
Related Topics
on page 209
on page 76
06 November 2012
K2 System Guide
75
System connections and configuration