Grass Valley Aurora Edit LD v.6.5 Installation - Manual (Page 57)

November 25, 2008 Aurora Edit Installation Guide
43
Shared SmartBins
Shared SmartBins
Shared SmartBins map clips — a process known as “winking” — from a K2 media
server to an Aurora Edit bin or MediaFrame database. As with drag and drop via Media
Manager, this automatic synchronization never moves actual media files, but instead
provides a different view into the shared media file system.
Shared SmartBins support simple (flattened) movies, but not sequences, sub-folders, or
sub-clips that the K2 cannot use directly. SmartBins do not support sub-bins. The
workstation running the SmartBins SAN service must have a Fibre Channel-SCSI
connection to the Open SAN and a CVFS or SNFS license.
When you first create a bin in Aurora Edit, you can map that bin to a K2 bin; after an
Aurora Edit bin is created, it cannot be mapped. Once an association is created, the
Aurora Edit and K2 bins are kept synchronized.
When the SmartBins Service starts, it determines which Aurora Edit bins are associated
with media server bins and then queries the media server database for the movies in each
associated bin. Any movies in media server bins that are not in the associated Aurora
Edit bin are registered to the Aurora Edit database. The SmartBins service does not
verify that Aurora Edit clips are in the media server database, so the synchronization is
one way only—media server to Aurora Edit.
Media Import SmartBins
Media Import SmartBins facilitate the automatic import of QuickTime DV25 and DV50
.mov files into Aurora Edit or MediaFrame. This allows you to use Apple’s Final Cut
Pro video editing application within a NAS environment to create news or sports
footage, and then import it into an Aurora Edit bin or MediaFrame database. Media
Import SmartBins work with MOV import for Final Cut Pro (FCP).
Only one Media Import SmartBin server can be active at any given time.