Jump to content

Versions, Transitions, Translations


B4adle7

Recommended Posts

Good Morning.  Am an FTrack noob, Shotgun veteran.

   Am in the processes of experimenting and looking through how to's.  

   However there are a few concepts we will need for production that seem to be a little unclear, or may not work.

   Can anyone help?

 

Versions:

   The base data structure we use is

Project > Sequence/Episode > Shot > Task > Version

 

   -   Version is not a data entity in FTrack.  (Will be a deal breaker?)

   -   Asset Builds, Asset Types might be the idea of versions?  

         The idea of which is which and how to use isn't clear yet.  

         (Am API dev, so these concepts need to be clear)

 

Data Linking:

   Aside from the entity class's specific linking, there doesn't seem to be any way to set other entity links.

 

   -   Currently you seem to only be allowed to link/parent specific entities.

   -   Can sub-class the python classes, and create your own type of entity links

 

 

   Really liking what FTrack is doing.  However some mechanisms are not clear yet, or are missing.  Any guidance will be very welcome.

Link to comment
Share on other sites

Hi,

 

thank you for your questions.

 

Versions:

 

The version hierarchy looks like

Project > Sequence/Episode > Shot > Asset > Version -> Component

Where a task is linked to the version to keep track of what task created the version.

http://rtd.ftrack.com/docs/ftrack/en/latest/developing/api_tutorial/publishing.html

 

Asset build is just like any other hierarchy object such as Sequence or Shot or task. While Asset is the grouper for versions. The asset has a name and an asset type.

 

Data linking

There are a few different ways to link things. 

 

Linking versions to versions to keep track of what was used to make another version.

http://rtd.ftrack.com/docs/ftrack/en/latest/developing/api_tutorial/linking_asset_versions.html

 

Linking between tasks/shots, asset builds etc.

http://rtd.ftrack.com/docs/ftrack/en/latest/developing/api_reference/index.html#ftrack.Task.addPredecessor

 

I should mention that the current api treats all objects as "Task" even if it is a Shot or Sequence. We have a new api in the works which will handle this better and be available in the new year.

 

Let us know if you need more details on any of the topics or feel free to send in a support case if you need to share more details of your workflow.

 

Kind regards 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...