User`s guide

Important Information
3
Information About FTP Server Profiles
The FTP server profile configurations vary depending on whether it is used for ingesting or
send to playback and with SD (IMX) or HD (Long GOP) media formats. Typically, one FTP
profile is created for a K2 ingest and one or several FTP profiles are created for send to
playback to a target K2 server. By creating separate FTP profiles for ingest and playback you
avoid accidentally overwriting existing media on the K2 server.
For better performance, Avid recommends using the K2’s high performance network
connection. When creating a FTP Server Profile use <K2 server host name>_he0 for the
Server Name, whereas, <K2 server host name>_he0 is the designated Gigabit Ethernet
Jumbo network NIC address for the K2 server.
n
<K2 server host name>_he0 is the K2 Media Server’s FTP and streaming network IP
address, not the K2 Media Client’s IP address. Do not use the K2 Control NIC for FTP
transfer, ingest or sent to playback, because it is typically of lower bandwidth and used
mainly for K2 metadata control purpose. For more information, see “Streaming video
between K2 systems” in the Thomson Grass Valley “K2 Media Client System Guide.
Information About Send to Playback
Before using Send to Playback to transfer items to a K2 media server, from an Avid editing
application, make sure the following conditions are met to prevent a transfer failure:
• The receiving target FTP directory on the K2 server must be configured and the
privileges set to support accepting incoming OP1A MXF media stream.
• The Send to Playback Tape ID must be alphanumeric characters. The maximum length
of a name is 32 characters with no intervening spaces and no dots “.” characters.
n
The FTP directory must be a K2 clip bin created by the K2 server’s APPCenter GUI. You
can not use a directory created by a direct FTP mkdir command. For more information, see
the “Administering and Maintaining the K2 System” chapter in the Thomson Grass Valley
“K2 Media Client System Guide.”