Specifications for pinnacle support – Grass Valley K2 System Guide v.9.0 User Manual
Page 120
3. Put the following Pinnacle clip files in the directory in the following order:
header
ft
info (optional)
std
Use the following example as a guideline:
J:\>ftp mx-proto-b14
Connected to mx-proto-b14.
220 FTP Server (1, 0, 0, 1) ready.
User (mx-proto-b14:(none)): video_fs
331 Password required for user video_fs.
Password:
230 Logged in, and aspect successfully set to MOVIE, stream mode PIN.
ftp> bin
200 Type set to IMAGE.
ftp> mkdir pinnacle_clip
250 Command “XMKD pinnacle_clip” succeeded.
ftp> cd pinnacle_clip
250 Change of directory to explodedFile/V:/default/pinnacle_clip
successful, xfer mode PIN.
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.
Related Topics
on page 73
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.
120
K2 System Guide
06 November 2012
Import/export services