Q100275: How to create separate directories for each comp version with Export Presets

Follow
  1. Foundry
  2. Nuke Family
  3. NukeStudio & Hiero Workflow Help

SUMMARY

This article will highlight the recommended workflow for creating individual directories for each comp version you create in Nuke Studio.

MORE INFORMATION

Users often find it helpful to customize their directory structures for better file and asset management. Nuke Studio offers the tools to achieve this, and one example of good workflow management is to generate separate directories for each comp version that is rendered.

More information about how to accomplish this, or how to use the same directory for all versions, can be found in the dropdown sections below.

Create one 'render' directory for all comp versions:
When using the following preset structure (example from the Basic Nuke Shot preset), Nuke Studio's default presets will place the comp version files into the same directory. Also please note that the bold text represents a file rather than a folder in the export preset structure:

- {shot}
   - nuke
      - script
         - {shot}_comp(_nameindex}_{version}.{ext}
      - renders
         - {shot}_comp(_nameindex}_{version}.####.{ext}

inline1791163574.png

This will generate a directory structure that would look as follows, where the {shot} name in this example will be 'StudioShot001':

- StudioShot001
    - nuke
      - script
         - StudioShot001_comp_v01.nk
      - renders
         - StudioShot001_comp_v01.0001.dpx

Or if you were looking at the directory path on disk (the temp directory is the project directory in this case, so all directories are created here):
/temp/StudioShot001/nuke/script/StudioShot001_comp_v01.nk
/temp/StudioShot001/nuke/renders/StudioShot001_comp_v01.0001.dpx

If you select the Export task, then below the Export Structure panel, you will see a preview of the path:
mceclip0.png
 
Create separate 'render' directories for each comp versions:
 
In order to adapt your export preset so that each comp version render is saved within their own directory, rather than within the same 'render' directory, you can update the preset to the following:

- {shot}
   - nuke
      - script
         - {shot}_comp(_nameindex}_{version}.{ext}
      - renders_{version}
         - {shot}_comp(_nameindex}_{version}.####.{ext}
​
inline865540171.png

This will generate a directory structure that would look as follows:

- StudioShot001
    - nuke
      - script
         - StudioShot001_comp_v01.nk
      - renders_v01
         - StudioShot001_comp_v01.0001.dpx

Or if you were looking at the directory path on disk:
/temp/StudioShot001/nuke/script/StudioShot001_comp_v01.nk
/temp/StudioShot001/nuke/renders_v01/StudioShot001_comp_v01.0001.dpx

This change means that anytime you render a new comp version, a new renders directory will be created in the 'nuke' directory. So for instance if you version up to "v02", your nuke directory would now contain the following:
/temp/StudioShot001/nuke/script/StudioShot001_comp_v01.nk
/temp/StudioShot001/nuke/renders_v01/StudioShot001_comp_v01.0001.dpx
/temp/StudioShot001/nuke/renders_v02/StudioShot001_comp_v02.0001.dpx


By using the principles in the sections above, you can modify any of the default presets to create flexible directory structures that meet your needs.

FURTHER READING

More information about exporting from Nuke Studio can be found in our documentation here:
Exporting from Nuke Studio

    We're sorry to hear that

    Please tell us why