Open topic with navigation

You are here: User Guide > Nuke > Organizing Scripts > Collaborative Work Flow Example

Collaborative Workflow Example

In this example, a compositor is responsible for the main comp that is delivered to the client. A lighting TD is responsible for providing a multi-layered CG render for use in the main comp. The following describes how the compositor and lighting TD could use the Precomp node to enable a collaborative workflow.

To Enable a Collaborative Workflow

1.   The compositor starts building the main comp.
2.   The lighting TD does a render of the CG element and a comp of the layers, saving the script as cg_v01.nk.

WARNING:  Note that we recommend rendering precomp images as .exr files. This way, Nuke writes the hash value of the incoming node tree into the rendered file. If the precomp script changes so that the hashes won’t match, Nuke can notify the user who can then update the resulting image. If you use a file format other than .exr, the user does not get this notification and the rendered file is likely to become out of date.
For more information on hash values, see Creating Precomp Nodes.

3.   The compositor creates a Precomp node reading from the file cg_v01.nk, and continues working on the main comp.
4.   The lighting TD continues to revise the CG render and the comp, versioning up the Write node and the precomp script .nk name. (See To View and Edit a Precomp Script.)

When better results are achieved, the lighting TD notifies the compositor of the new and improved version of the precomp script.

5.   The compositor versions up the Precomp node to the new, improved version and reloads the precomp script. (See To Reload a Revised Precomp Script.)