Grass Valley K2 Media Client System Guide v.3.3 - Manual (Page 108)

108 K2 Media Client System Guide June 9, 2009
Chapter 3 System connections and configuration
ftp> put header
200 PORT command okay.
150 Opening MOVIE mode data connection for header.
226 Transfer complete.
ftp: 132 bytes sent in 0.00Seconds 132000.00Kbytes/sec.
ftp> put ft
200 PORT command okay.
150 Opening MOVIE mode data connection for ft.
226 Transfer complete.
ftp: 393216 bytes sent in 0.11Seconds 3574.69Kbytes/sec.
ftp> put std
200 PORT command okay.
150 Opening MOVIE mode data connection for /
explodedFile/V:/default/pinnacle_clip.
226 Transfer complete.
ftp: 56097960 bytes sent in 16.25Seconds 3452.18Kbytes/
sec.
ftp> quit
221 Goodbye.
Specifications for Pinnacle support
• Pinnacle clips do not indicate timecode as “drop-frame”. The K2 import assumes
non-drop-frame values.
• 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