General Publisher

General Publisher

Table of Contents


What’s the General Publisher?

This tool was introduced to batch publish a bunch of files onto ftrack hierarchy structures.
It will not create hierarchy structures, so all ftrack objects need to exist before uploading will succeed.

There are various ways to analyze the filename in order to have the publish be successful and correct.


Overview

image-20250416-075247.png

File(s)

At the top you can add the files you want to publish. (drag and drop enabled).

  • Add will allow you to browse for a file

  • Remove will remove the selected file from the list

  • Clear will remove all files from the list

Task

To the right you can select a task name, on which these files need to be published. There are a lot of different tasks available.

The possible actions will change according to the task you select.

Action

There are quite a lot of different actions that have several input settings. These are explained here.

Depending on the selected task, the option Thumbnail on task might become available. This will make your uploaded file the thumbnail of the task on ftrack.

Thumbnails on ftrack cannot exceed 8192px so an additional smaller image is automatically created by the tool every time you publish

Conversion

Below the action display, there is the conversion display. Here you can choose how the publisher should handle the given files / filenames, so it can translate in what hierarchy/ftrack structure the files belong.

There are several different types, which are explained here.

You can see a preview of the conversion by selecting one file in the file list.

Status

At the top right there is a Task Status and Version Status display, which will alter the status of the published asset tasks and versions.

image-20250416-075409.png

The statuses are pulled directly from ftrack and can therefore differ from project to project.

Publish

At the very bottom you can find how to publish it, and a Publish button to start the execution. Local means everything is done with your computer, Deadline will send it to the farm.


Actions

Depending on which task is selected, the available actions will variate.

General

Image Sequence

Uploads an image sequence as Image Sequence asset type.

Movie

Uploads a mov or mp4 as Movie asset type.

Image

Uploads a single image as Image asset type.

Audio Upload

Uploads an audio file as Audio asset type.

Copy Audio Upload

Copies the original file to a location in the pipeline folder structure and uploads that file as Audio asset type.

Maya

Deadline MayaScene Playblast

Send a MayaScene to the farm to render a certain render layer with a given camera.

Deadline MayaScene Playblast + Publish

Send a MayaScene to the farm to render and try publish it afterwards.

Deadline MayaScene Turntable Playblast

Send a MayaScene to the farm to render a turntable (of an asset).

Deadline MayaScene Turntable Playblast + Publish

Send a MayaScene to the farm to render a turntable and try publish it afterwards.

Deadline MayaScene Publish (requires Review)

Send a MayaScene to the farm to publish it.
(This requires reviews (review images) to be present in the correct review folder structure.)

Deadline MayaScene Python Script

Send a MayaScene to the farm to run a script.

Nuke

Deadline NukeScript Render

Send a NukeScript to the farm to render given write nodes.

Deadline NukeScript Render + Publish

Send a NukeScript to the farm to render given write nodes and try to publish afterwards.

Deadline NukeScript Publish (requires Review + Render [+ Matte])

Send a NukeScript to the farm to publish it.
(This requires reviews (review images) and renders (exr, dpx, ..) to be present in the correct review folder structure.)

Deadline NukeScript Python Script

Send a MayaScene to the farm to run a script.


Conversions

There are various ways of analyzing a file / filename, resulting in the correct publish.

Chapter_Sequence_Shot[..] filename

This will split up according to the filename {Chapter}_{Sequence}_{Shot}[_..].

Original the Conversion part in the tool will Converted Fields and nothing else.

When you click the files you added, you can see if the conversion succeeded with an example.

This example uses hoatXX_XXXX_XXXXX_v005.mov

So this will work on the following structure on ftrack:

Filename/Folder conversion by template

This conversion will use a pipeline=defined template to analyze a filename and construct a hierarchy accordingly.

Filename/Folder conversion by template elements_asset_filename

This conversion will use a pipeline defined template named elements_asset_filename to analyze a filename and construct a hierarchy accordingly.

This represents the filename structure: {FileContext}_{Task}_{Version}[.{FileSequence}].{FileType}.
([..] means optional)

  • FileContext represents the hierarchy structure (joined by _), starting from 601_library and 602_shots.

  • Task will contain an abbreviation (3 letters) to define the department. (mdl, rig, tex, ..)

  • Version needs to be vXXX.

  • FileSequence is optional (and usually contains 4 digits).

  • FileType is the extension of the file.

Indexed filename separation

This conversion will use File Separator to split up the filename and construct a hierarchy by index (-1 meaning second last item of the split).

This example uses hoatXX_XXXX_XXXXX_v005.mov

So this will work on the following structure on ftrack:

If you want to publish a file with additional suffixes behind the version (for example, multiple views of the same Design, Video, …), setup you conversion like this:

image-20250416-081128.png