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

78 K2 Media Client System Guide June 9, 2009
Chapter 3 System connections and configuration
NOTE: When using FTP in a shared storage environment, ensure that all FTP
communication takes place on the FTP/Streaming network, and not on the
Command/Control network.
Limitations with complex media types
• Depending on the system software versions of source and destination devices, it is
possible that lists or programs made from lists that contain movies with mixed
video compression types or mixed 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
K2’s 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.
If using remote control protocols to initiate transfers, refer to Appendix A, Remote
control protocols.
Also refer to “Transfer compatibility with K2 Media Client” on page 220 .
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
Media Client 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. For example, you can use Internet Explorer to transfer files
between a PC and the FTP interface on a stand-alone K2 Media Client or a K2
Media Server on the same network. For more information, refer to
“FTP access
by automation” on page 79 .
• Remote control protocols — Industry standard remote control automation
applications can initiate transfers. The protocol command must be sent to the K2