Applications

Site created with Notion, Super & Cluster

← Back

File Naming Convention

MyCGDoc Production Protocol

DNS: Denoised

UND: Undistorted

Workspace & Preferences

Workspace & Preferences Location:

C:\Users\<USERNAME>\.nuke

Windows

Scopes

• Histogram
• Waveform
• Vectorscope

Source: https://learn.foundry.com/nuke/content/comp_environment/color_correction/using_scopes.html

Resource: https://www.youtube.com/watch?v=JtlJAeJENgM&t=599s&ab_channel=Foundry%2Cimaginationengineered

Preferences

Performance

Behaviors

Panels

Source: https://learn.foundry.com/course/4683/play/2-set-up

Project Settings

Root

Variables

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 I key.

Sources

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.

support.foundry.com

Notes - Process Management

Source: https://www.youtube.com/watch?v=-Em0Wvm8O-I&ab_channel=Foundry%2Cimaginationengineered

B Pipe Structure

Logic

• B inputs parallel the script stream.
• A inputs branch from left.
• Masks branch from right.

Benefits

• 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.

Script Management

Planning

• Include script description and outline in comment within script. (Similar to G sheets)
• Outline
• 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.

Modularisation

• 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

Node Indicators

• A: Animated
• C: Clones
• E: Indicator
• X: Mix value for node is somewhere between 0 and 1, but not an integer.
• Channels
• Utilized
• Pass Through

Format Preservation

• 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.
• Strategies
• With Merge node, set foreground assets to A input and specify set bbox to to 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.
1. Select node to be cropped.
2. Key X for command line.
3. Enter nukescripts.autocrop() and set to Python.
4. Allow script to process crop and to create an AutoCrop node.

Workflow Optimization

• Profile node & panel
• Analyses data usage per node to track performance bottlenecks.
• Read with Postage Stamp node
• Connect a Postage Stamp node to a Read node and enable hide input.
• This allows the Postage Stamp to be reused through script and still reference the original Read node data without importing the data in separate Read node.
• Utilize toolsets for adding preset nodes/blocks to scripts.

Channel Packing

• Investigate incoming data for opportunities to pack channels for optimization.
• Key opportunities:
• B/W images using all RGB channels
• Duplicate data
• Use Layer Contact Sheet to view layers in incoming data.
• Use Shuffle and Copy nodes to reroute channels for packing.
• Use Remove nodes to remove extraneous channels and layers.
• Only work with the channels you need.

Filtering

• 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.

Concatenation

• Note the nodes that concatenate to reduce filtering.
• Example
• 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.
• Reference:

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



www.nukepedia.com

Camera Reference

• If camera data is unavailable, check metadata of incoming data.

Notes - Asset Management

Incoming Data

Define project global frame range and format size.

Graphics

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.

Source: https://community.foundry.com/discuss/topic/135309/nuke-stops-refreshing

On This Page

• File Naming Convention
• Workspace & Preferences
• Windows
• Scopes
• Preferences
• Performance
• Behaviors
• Panels
• Project Settings
• Root
• Variables
• Node Class Names
• Sources
• Nuke Directory Locations
• Notes - Process Management
• B Pipe Structure
• Logic
• Benefits
• Script Management
• Planning
• Deconstruct v. Consolidate
• Modularisation
• Additional Key Considerations & Notes
• Node Indicators
• Format Preservation
• Bounding Box Management
• Workflow Optimization
• Channel Packing
• Filtering
• Camera Reference
• Notes - Asset Management
• Incoming Data
• Graphics
• Troubleshooting & Resolutions
• Viewer doesn't refresh.