File Naming Convention
Workspace & Preferences
Workspace & Preferences Location:
Timeline Disk Caching
Comp Disk Caching
Comp Disk Cache Size: 100 GB
Undo History Size: 250 MB
Maximum Undo Events: 25
New Merge nodes connect A input: Disable
Autokey roto shapes: Enable
Startup workspace: HansMain
Show splash screen at startup: Disable
Reopen acts like new panel: Enable
Expand/collapse panels in Properties bin to match selection: Enable
Postage stamp mode: Static frame
Arrow Up: Color Red
Used to stand out re-directions in script streams.
Size of dots: 1.5
Clear input window on successful script execution: Disable
GL buffer depth: half-float (Defaults to byte)
byte is an 8-bit process, so with 10-bit monitor, not fully used, hence, need to use half-float or float.
Use GPU for viewer when possible: Enable
Use GPU for inputs when possible: Enable
3D control type: Maya
Enable to prevent new import data nodes from overwriting specified project frame range.
Node Class Names
Note that references to nodes should be confirmed with its class name, and not necessarily the node name in the UI. In the following example, the
Tracker1 node has a class of
Tracker4, while an older version of the Tracker node labeled
Tracker2 has a class name of
Tracker3. The number notes the different versions of the same node as they are updated.
Older nodes can be accessed and created with the
X key and typing in the name of the class.
Information for the nodes is accessed and displayed with the
Nuke Directory Locations
Q100048: Nuke Directory Locations
On macOS: Pressing CMD+Shift+Period will display the hidden files/folders in the Finder. NOTE: On Windows, the .nuke folder can be found under the directory pointed to by the HOME environment variable.
Notes - Process Management
B Pipe Structure
- B inputs parallel the script stream.
- A inputs branch from left.
- Masks branch from right.
- Naturally preserves metadata
- Branch streams can retain metadata with Merge from parent tree spine and linking metadata from A (parent tree spine) to B (new branch).
- Quick disable of nodes to visualize updates.
- Visual clarity.
- Include script description and outline in comment within script. (Similar to G sheets)
- Define goals.
- Best workflows.
- Anticipate potential issues, revisions, and challenges.
Deconstruct v. Consolidate
Deconstruct processes into nodes rather than consolidate processes into solitary nodes to visualize branches, relationships, and factors. A consolidated Roto may hold many processes within it, but a Roto branching from an operation (i.e. Merge) node can isolate separate sub-processes for clarity.
- Compartmentalize processes with sub-processes that isolate single tasks.
- Branch compartments so that they can be enabled/disabled from parent tree spine without major disruption.
- Note compartments that can achieve repetitive, common tasks for modular use in script or other scripts.
- Use color-coded backdrops with labels and descriptions.
Additional Key Considerations & Notes
X: Mix value for node is somewhere between 0 and 1, but not an integer.
- Pass Through
- Reformat downstream, but balance load optimization if possible.
- Preserve original format to allow for edits and potential revisions.
- Reformat at joint between branch and main tree spine.
Bounding Box Management
- Goal is optimizing performance and efficient workflow.
- Manage bbox at individual node level by removing extraneous pixels.
- With Merge node, set foreground assets to A input and specify
set bbox toto replace default
union, which assumes the bbox of only the relevant data based on A and B inputs.
- Add crop nodes at key points in stream.
- Utilize autocrop() Python function.
- Select node to be cropped.
Xfor command line.
nukescripts.autocrop()and set to Python.
- Allow script to process crop and to create an
- Profile node & panel
- Analyses data usage per node to track performance bottlenecks.
- Read with
- Connect a
Postage Stampnode to a
Readnode and enable
- This allows the
Postage Stampto be reused through script and still reference the original
Readnode data without importing the data in separate
- Utilize toolsets for adding preset nodes/blocks to scripts.
- Investigate incoming data for opportunities to pack channels for optimization.
- Key opportunities:
- B/W images using all RGB channels
- Duplicate data
Layer Contact Sheetto view layers in incoming data.
Copynodes to reroute channels for packing.
Removenodes to remove extraneous channels and layers.
- Only work with the channels you need.
- Noted when software manipulates pixels in about every node operation and leads to data loss.
- Inevitable part of workflow, but minimize data loss as much as possible to retain original data value.
- Note the nodes that concatenate to reduce filtering.
- Transform that scales up followed by a Transform that scales down, then followed by a Grade node.
- The 2 transform operations are performed together via concatenation and therefore act as a single transformation operation, after which the grade operation is performed.
- However, if a Grade node is between the 2 aforementioned Transforms, then the first transform operation is performed followed by a Grade, which performs a filtering operation, After this, the second transform operation is performed as a separate operation, but on filtered data.
Concatenation of transforms in Nuke
Concatenation of transforms in Nuke - Written Tutorials A fairly common question among Nuke users is whether transformation nodes concatenate in Nuke, which nodes do and don't, and how can one tell. The subject can be particularly confusing for artists wh
- If camera data is unavailable, check metadata of incoming data.
Notes - Asset Management
Define project global frame range and format size.
Format Incoming Movie Files
Read: Identify frame range needed.
Reformat: If applicable, reformat to project format size.
Write: Output movie file to .exr image sequence, which can then be read back into Nuke.
Use TIFF image file format.
Troubleshooting & Resolutions
Viewer doesn't refresh.
This issue might be sourced from either the recent use of a Roto or RotoPaint. A good first step would be to clear all caches and restart Nuke, which has been a suitable solution in a few instances.
On This Page
- File Naming Convention
- Workspace & Preferences
- Project Settings
- Node Class Names
- Nuke Directory Locations
- Notes - Process Management
- B Pipe Structure
- Script Management
- Deconstruct v. Consolidate
- Additional Key Considerations & Notes
- Node Indicators
- Format Preservation
- Bounding Box Management
- Workflow Optimization
- Channel Packing
- Camera Reference
- Notes - Asset Management
- Incoming Data
- Troubleshooting & Resolutions
- Viewer doesn't refresh.