Grass Valley K2 System Guide v.7.2 - Manual (Page 53)

07 April 2010 K2 System Guide 53
About the K2 FTP interface
About the K2 FTP interface
An application writer may choose to initiate media file transfers via FTP. The K2 FTP
interface has a GXF folder and an MXF folder. Use the appropriate folder, depending
on if you are transferring GXF or MXF. Refer to
“FTP access by Internet Explorer”
on page 56 for examples.
The K2 FTP server runs on K2 Media Server that has the role of FTP server. While it
also runs on the K2 Solo Media Server, stand-alone storage K2 Summit Production
Clients and K2 Media Clients, it is important to understand that it does not run on
shared storage K2 clients. When you FTP files to/from a K2 SAN, you use the FTP
server on the K2 Media Server, not on the K2 client that accesses the shared storage
on the K2 SAN.
If clips are created by record or streaming on a K2 file system such that media files
have holes/gaps, i.e. unallocated disk blocks, in them, then that clip represents a
corrupt movie that needs to be re-acquired. The K2 system handles corrupt movies of
this type on a best-effort basis. There is no guarantee that all available media,
especially media around the edges of the holes/gaps, is streamed.
You can also apply K2 security features to FTP access. Refer to “Configuring K2
security” on page 158 .
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 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 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.
If using remote control protocols to initiate transfers, refer to Appendix A, Remote
control protocols.
Also refer to “Specifications” on page 189 .
Transfer mechanisms
You can move material between systems using the following mechanisms, each of
which offers a different set of features: