Grass Valley K2 Media Client System Guide Oct.10 2006 - Manual (Page 68)

68 K2 Media Client System Guide September 7, 2006
Chapter 3 System connections and configuration
Using FTP for file transfer
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 70 for examples.
If connecting to the FTP server on a K2 system from a third-party Windows PC, make
sure that the PC has TCP Window scaling enabled. (For more information on TCP
Window scaling, see the Microsoft Support Knowledge Base web site.)
The K2 FTP server runs on K2 Media Servers that have the role of FTP server. While
it also runs on internal storage K2 Media Clients (stand-alone), it is important to
understand that it does not run on external storage K2 Media Clients. When you FTP
files to/from a K2 Storage System, you use the FTP server on the K2 Media Server,
not on the K2 Media Client that accesses the shared storage on the K2 Storage System.
For information on streaming/transfer procedures in general, see the K2 Media Client
User Guide.
K2 FTP protocol supports clip and bin names in non-English locales (international
languages) using UTF-8 character encoding. Refer to
“Internationalization” on
page 136 .
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. Streaming in/out such a movie on a K2
system will be handled on a best-effort basis. There is no guarantee that all available
media, especially those around the edges of the holes/gaps, will be made use of for
streaming.
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.