User`s guide

4
Information About Ingesting
When ingesting live media from a K2 media server and the target media is also being
recorded or transferred from another K2 media server, the K2 media server delays any data
being transferred by 20 seconds. This delay is set by the K2 media server policy. Therefore,
you should let enough media material accumulate before attempting to use Avid’s FTP
Media Browser to engage any ingest.
n
When performing a Generic FTP ingest, the audio is limited to 8 tracks and PCM-based
only. Dolby E is not supported.
When a K2 media server is simultaneously performing several activities, such as captures,
ingests, and transfers, the K2 FTP might become unresponsive when the FTP Media
Browser attempts to read the MXF header bytes from a K2 source MXF file. The K2 FTP
capabilities are limited to 4 ongoing FTP streams. You might see an error message such as
“Cannot read requested bytes” due to this condition.
When creating FTP Server Profiles for Send to Playback and Ingest make sure the Default
Directory text box contains different locations for the playback and ingest media to avoid
accidentally overwriting the media.
The setup and configuration for working with Long GOP XDCAM HD assets with a K2
media server are similar to the procedures described in the “Configuring Capture and
Playback of MXF DHM OP1a File Formats” in the Avid Interplay Transfer Setup and User’s
Guide.
K2 Audio Tracks Ingest Limitations
When you are ingesting MXF audio tracks into an Avid workgroup environment using Avid
Generic FTP ingest, each non-mono channel tracks are first demuxed into its constituent
sequential mono channel tracks. Only the first 8 sequential mono-channel tracks are later
ingested as OpAtom audio files. If tracks are already mono-channel in nature, they are
ingested as it is, subject to the 8 track limit.
n
Original tracks in mono-channel are directly ingested with 8 tracks, the defined track limit.
Any non-PCM tracks must be wrapped as a pseudo-PCM MXF track to be ingested, because
non-PCM-based material is not supported. All the MXF audio essence tracks are expected to
have the same channel counts per track. For example, mono-channel, bi-channel, etc. Per
track, mixed channel count across MXF audio tracks is not supported.
c
After ingesting non-PCM audio tracks, do not edit or mixdown any of the non-PCM
audio tracks, because this leads to destruction and non-recoverable audio tracks.