Postprocesses
Postprocesses run after a publish and are linked to components. They will trigger a post process script to run from the primary server to run various post process operations and example being triggering a movie creation job on deadline.
Scripts are written in python and exist in the default install location and have to be available for the primary server to run the job. These can be updated and customized by following the default examples.
C:\Program Files (x86)\Taskforger\scripts\postprocesses
Create a Postprocess
To create a new postprocess, follow these steps:
Access the "Postprocesses" Tab: Click on the cog to access configuration tabs. Right-click anywhere inside the "Postprocesses" tab.
Open the Actions Context Menu: Click on the actions context menu.
From the context menu, select the "New" option.

- Postprocess Created: Congratulations! You've successfully created a new document for your Postprocess. You can now proceed with postprocess management. Sort by Id to find the newly created by time created.
Update a Postprocess
To update a postprocess, follow these steps:
Pick the collection for your Postprocesses: eg projects.
Name Your Postprocesses: Enter the name you want for the postprocess this can overlap with others as is linked by Id.
-2c371069dbb8ed13c59e341dc6e8aede.png)
- Fill the color space and codec parameters eg. date
-1dc3d773bee59c1b9a2f301ad910a6e9.png)
- Updated quality parameters:
-389a7f70a78c5ee33177f78f58be0337.png)
- Set the script and validation parameters:
The script is just the name of the python script minus the extension. It will only ever run scripts inside the install directory.
Validation uses regex and can also check the file type eg. only run on frame sequences.
-c6684f9a4a013d5d79ff544f4118fcc1.png)