Grass Valley K2 AppCenter v.9.0 - Manual (Page 150)

NOTE: If you export to a file or stream media that has the same name as an asset already existing
in the destination location, an Abort/Rename/Retry dialog box appears.
Related Topics
Operational specifications on page 231
About sending files to external drives
Transferring to and from a USB drive is supported on a local standalone K2 Summit/Solo system.
(You can also transfer files in K2 Solo Media Server using a PCIE Express card.) USB drive transfers
on K2 Summit SAN-attached system or Control Point PCs are not supported. Assets must be exported
to a USB drive one at a time. Attempts to export more than one asset at the same time will result in
the transfer aborting.
The following are operational considerations when sending files to external drives:
• Estimating clip file sizes - AppCenter does not prevent you from sending a file that is larger
than the space available on the target disk. The transfer fails when the disk becomes full. To
avoid this problem, check the clip size reported in the clip properties dialog box. You can use
this to estimate the disk space required for the clip.
• Best transfer performance - File transfers are handled concurrently, up to four at a time.
Additional transfer requests are queued.
• Adding/Removing USB devices - The USB connectors on the rear panel and front panel can
be used to connect a mouse, keyboard, USB drive, or other USB device. Do not plug or unplug
these devices while the K2 Summit/Solo system is being used for critical play to air activity.
• Maximum file sizes when exporting assets to USB drives - Exporting assets with long durations
may result in file sizes that exceed 4GB. Some USB drives are formatted using FAT/FAT32,
which has the 4GB maximum file size limitation. Attempting to send a file to these disk volumes
will cause the transfer operation to fail. Disk volumes formatted using NTFS allow larger
maximum file sizes. Before exporting an asset, be sure to check that the file size is less than
4GB, otherwise, ensure that the file system on the target drive supports larger files sizes.
Related Topics
Passwords and security on Grass Valley systems on page 30
To export to a file
The destination must be a verified destination for file export. Examples of verified destinations are
as follows:
• When using AppCenter on a standalone K2 Summit/Solo system and the destination is a local
drive, the local drive is a verified destination. It is not necessary to share a folder or map a drive.
On the K2 Summit SAN-attached system, share a folder.
• When using AppCenter on an K2 Summit SAN-attached system and the destination is a local
drive on the K2 Summit SAN-attached system, create a verified destination as follows: On the
K2 Summit SAN-attached system, map the shared folder as a network drive.
• When using AppCenter on a Control Point PC and the destination is a local drive on the Control
Point PC, create a verified destination as follows: On the Control Point PC, share a folder. On
the Control Point PC, map the shared folder as a network drive.
150 K2 AppCenter User Manual 29 October 2012
Importing and exporting media