You can upload files within your ftrack workspace to quickly create new asset versions (a.k.a. versions). Uploaded files will then be available for other people to view, download or import as assets in integrations.
If the uploaded file is a supported file type, an encoding job will be started, and once finished, the version can be reviewed within the review web player (or preferred player).
The component created to represent the file will be added to the ftrack.server location and can be accessed from the version sidebar in the Component tab.
|
There are two ways to upload files within the workspace:
|
|
Please note: Creating versions on the Versions page is not supported at this time. It is not possible to change the asset type, description, or version number of the created version. |
Upload using the sidebar
- Go the to Tasks Spreadsheet and click the object/task name you want to create a version for.
- The sidebar opens. Select the Versions tab.
- Drag and drop the file you want to upload to the designated box - OR - click the browse button to browse for the file.
Upload using the Upload media dialog
|
The Upload media option to create a version is available in three places:
|
Image: Tasks spreadsheet right click menu of a task
Image: Sidebar More menu
- Find your object in either the Project navigation, Tasks spreadsheet or sidebar and access the right-click or More menu as mentioned above.
- Select Upload media from the menu.
- Drag and drop or select a file for each of the upload areas and fill in the fields.
- Once the required fields are completed, the Create and Create and review buttons are enabled.
- Click Create to upload the new versions and close the window - OR - click Create and review to upload the versions and launch the review web player for the newly created versions.
How versioning works
When creating versions by uploading them in the workspace, an asset of the type 'Upload' will be created. If a file with the same filename had been previously uploaded, the version number of the existing asset will be incremented instead. This way, each time you upload the same file, a new version will be created.
|
Example: Say you upload a file with the filename Project proposal.doc. This will generate an asset version with the name Project proposal v1. After you have done some changes, you upload the file again. The resulting version will have the name Project proposal v2. You then upload a new file called Project budget.doc, this will generate a new version with the name Project budget v1. We will also try to detect any version numbers specified as part of the filename. Uploading a file named Project proposal v4.doc will generate version 4 of an asset named Project proposal. Should this version already exist, the next available version will be used instead. |
When looking for versions in filenames, we look for a separator (space, dot, underscore, or hyphen) followed by the character v and a number.
See the table below for a few examples:
