Q: Contentbase Device

In Proximity Artbox, a Contentbase device was one that allowed infinite versions of the same exact named file to be loaded in as completely separate assets. This was accomplished because the file directory structure underneath the root folder of a Contentbase consisted of sequentially numbered folders in a hexidecimal format. As each file was uploaded into Artbox as an asset, and into a Contentbase, it would be renamed with a unique hex number, and that number would be tracked in the asset's metadata. So you could upload an asset with the same filename a thousand times, and a thousand unique hex filenames would be created. That's how you were able to have multiple assets with the exact same name. They all had unique asset ID's and filenames.

Final Cut Server already comes with a few Contentbase type devices. The most obvious is the Proxy device. Ever notice how the Proxy device isn't included in the devices tab of the FCS Preferences Panel? Also, Contentbase is not an option when you try and add a new device. To create a Contentbase, do the following:

1. Create one of those 'bundle' type folders with the name of your new Contentbase. FCS will only use a 'dot bundle' file as a CB. So it's 'mkdir NewDeviceName.bundle'

2. Go into the Java App, and in Administration - Devices, create a new device of type 'Contentbase'.

3. Point it at the full path and file name of the 'dot-bundle' file you created, and when you gve it a name and save it, you have a new Contentbase that you can use.

Final Cut Server automatically appends a '-1, -2, -3, etc...' when you try and upload same named files into a regular Filesystem device. But with a Contentbase, you can keep the exact same file name. That unique hex file name is for internal purposes only. If you download that asset or copy it someplace, it will come out with it's original file name, NOT the hex name.