Define Your Reviewable Content and Deliverables

Now that your workflow, objects, task types, milestones, and statuses have been established, the final step is to define what kinds of media and files need to be reviewed at each stage of your project before your tasks can be approved. Simply put, what is the task output, and does it need to be reviewed?

This is what asset versions (aka versions) represent. Both the reviewable media file and relevant components relate to that asset version in one package. These components could include:

  • The thumbnail file of your uploaded media
  • The transcoded .mp4 media file
  • The project file published from an artist's DCC using Connect
  • Any other relevant files that need to be passed downstream to other departments or delivered as a final part of your project

An asset version doesn't require additional components or publishes in its "package" if all you need is an uploaded media file. Still, the option is there if you would like to bundle all relevant files with the media up for review. Alternatively, an asset version can represent a component with no media file, but then the version can't be played back in your preferred player or Review.


Image: The Sidebar detailed view of an asset version (side_table_tall_01_turn - v1) and its components listed below.

Asset types are used to categorize your asset versions within ftrack Studio. They can use the same terminology as your task types to keep them aligned, or they can differ if you need something more specific. For example, the asset version published under a modeling task could have the asset type of "model" or "geometry" depending on what terminology is used in your facility.

It is important to note that asset types are for advanced configurations of ftrack Studio that will use Connect, Integrations, or the API. We mention it now as it is part of the Workflow configuration should you use those features and need to plan in advance. Please visit the linked articles for more details on each since this series focuses on the basic configuration of your workspace.

If you will only be uploading asset versions directly within Studio, then your asset type is automatically "Upload", and there is no need to plan for other asset types.


Image: An example of asset types displayed for each asset version in the Versions Page.

Asset version statuses can be the same or differ from your object and task statuses. For example, are there situations where you need an artist to publish their work in its current state, even if it's not completed? A version-specific status such as WIP (Work In Progress) would provide visibility to the team come review time that there is still more work to complete and it's not being submitted for final approval. Or perhaps you need a "Kicked Back" status to indicate a version submitted for final was not approved and to look for notes.


Image: An asset version status is highlighted on the Versions Page.

Take Action

  • For each task type established for your object(s), determine what kind of media/files, if any, will need to be output and included in the asset version. 
    • Examples: If it's an animation model, do you want the geometry, rig, and turntable media file of the model? If it's a Storyboard, do you want a PDF file? If it's a voiceover, do you want an audio file? Click here to see a list of compatible files.
  • What asset types will you use to define your asset version further? This is only for workspaces that plan to use Connect, Integrations, or the API.
    • Example: Concept, Storyboard, Geometry, Lighting, Animation, FX, Compositing, Image Sequence, etc.
  • Which statuses will you use on your asset versions to define your submission and approval workflow?
Was this article helpful?
0 out of 0 found this helpful

Articles in this section