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

07 April 2010 K2 System Guide 91
Pinnacle support
• The time-code used in the header file and recorded into the MPEG Video GOP
header starts out as 00:00:00:00 by default. If the option to extract VITC is not
enabled, or no VITC is detected on import, timecode extracted from the MPEG
Video GOP manifests as the timecode track for the imported K2 clip.
• Pinnacle servers preserve non-MPEG-1 (Musicam) audio as Pinnacle-private
elementary streams within the program stream std file. Pinnacle clips allow up to
8 channels of audio. On import the K2 system detects the private stream audio
packets when they are present and generates the appropriate K2 audio track(s).
• When importing Pinnacle content recorded as an MPEG1 system stream, any
Pinnacle-private audio from MPEG2 program stream based clips is lost.
• The K2 system supports extraction of the following kinds of Pinnacle-private
audio:
• PCM-16, PCM-20 (PCM-20 is converted into PCM-24 on import)
• DolbyE and AC-3
• If you enable the option via registry key, the K2 system examines specific VBI
lines when it detects Pinnacle-private VBI lines, as follows:
• Line 21 (default, can be overridden via registry) is examined for the presence of
close captioning or SDP teletext. If detected, this is appropriately de-modulated
into EIA-608 close caption or OP-47 subtitling packets and inserted as ancillary
data packets into an ancillary data track on the imported clip.
• Line 19-PAL and 14-NTSC (default, can be overridden via registry) is examined
for the presence of VITC. If detected, this is appropriately de-modulated into
SMPTE 12M compliant time-code values which is inserted as time-code values
into the time-code track on the imported clip.
• The following applies to the Pinnacle emulation K2 FTP import:
• All supported FTP commands, with the exception of those mentioned below,
respond as they do for a conventional K2 FTP session. For instance, commands
such as renames and deletes operate on K2 clips, directory listings reveal K2
clips and bins, and so on.
• Navigation (cd) to K2 bins is allowed. By default, the default K2 bin is projected
as the FTP root.
• The MKD/XMKD command does not create a K2 bin for the argument specified,
but merely retains the argument as the name of the K2 clip to be created based
on following STOR commands.
• The CWD/XCWD command does not allow navigation to a K2 bin. If the
Pinnacle clip name used in a previous MKD command is used as an argument to
CWD, the K2 FTP server does not internally navigate to that “bin”, but rather
merely returns a success status.
• The STOR command only honors ft, std, or header as arguments, or filenames
with a .mxf extension. When the K2 FTP server receives data for the std file it
creates a K2 clip with the name issued by a previous MKD/XMKD command.