Warning! This documentation is outdated. Visit help center for the latest documentation.

Storage scenario

We learned in Sharing files and media that ftrack is tracking your files as Asset versions and Components. A Component represents the existance of a file, but does not tell your where the data is located. To keep track of this ftrack uses the concept of Locations.

To simplify the setup of locations a Storage scenario can be used instruct ftrack on how your files should be stored when publishing from ftrack connect or integrations.

When starting ftrack connect for the first time you will be asked to Configure a storage scenario.

Centralised storage scenario

The default Centralised storage scenario will copy your published files into a folder structure generated from the object names where the Asset version is published, along with the Asset name and version number.

As an example we can say that you have a project named CarCommerical with a folder called Images. Now you publish a file component named front.png on an asset named DarkImage. It becomes version 3 of the asset and will yield a path:

carcommercial/images/darkimage/v003/front.png

Configured correctly ftrack will know where the storage is mounted on your machine and produce a file path suitable for your OS:

/Volumes/MyStorage/carcommercial/images/darkimage/v003/front.png

See also

Locations overview for a thorough explanation of locations.