What the script audit checks
Nuke Write node naming checker
Write nodes are where a comp meets the pipeline, and where handoffs break. Nuke Studio Hub parses every Write node in your .nk and checks the output path and file name against your studio's naming convention.
It flags the problems that cost a render night: output paths pointing at the wrong folder or a local drive, missing version tokens (a hard-coded v01 that never increments), inconsistent render names across a project, and file names that will not match what finals or the client expect. Instead of eyeballing dozens of Write nodes by hand, you get a single report of exactly which nodes break the rules and why. More on the Write-node naming checker →
Nuke Read node missing media checker
A comp that opens with red frames is a comp that stops work. Nuke Studio Hub reads every Read node in the script and catches broken media before you open Nuke: absolute paths that only exist on one artist's machine, plates on a local drive that will not resolve on the farm, missing files, and frame-range mismatches between the node and the media on disk.
Because the whole thing runs by parsing the .nk as text in your browser, it can tell you a plate is missing or mis-pathed without ever opening the project or touching your media. That is the difference between finding a broken Read at your desk and finding it when the render fails at 2am. More on the Read-media checker →
Nuke gizmo and ToolSet dependency audit
Scripts travel between artists and machines, and gizmos do not always travel with them. Nuke Studio Hub inventories the gizmos, ToolSets and plugins a script depends on and flags anything that will not open cleanly somewhere else: unknown or missing gizmos, deprecated nodes, and tools installed on your box but not on the farm or a collaborator's machine.
The result is a portability report, so you know a script will open the same way for the next artist before you hand it over, not after they call you about a node that turned into an error. More on keeping scripts portable →
Nuke project folder structure validator
Clean handoffs start with a clean folder tree. Nuke Studio Hub checks your project against a standard structure - comp, renders, elements, scripts, in and out - so caches, plates and outputs land where the next person expects them.
When your folders, your Write paths and your Read paths all agree, a comp hands off to finals or another studio without a scavenger hunt. Pair the structure check with the Write and Read audits and you have a full comp handoff checklist in one pass. See the folder-structure template →
Nuke node graph viewer
Because the .nk stores each node's position, Nuke Studio Hub rebuilds the comp's node graph in your browser at its real xpos/ypos, reconstructs the edges from Nuke's stack model, and lets you pan, zoom and export an SVG - with flagged nodes ringed so you can see where a problem lives. Read the whole tree without opening Nuke, and hand a reviewer or client the layout with no install required. More on the node graph viewer →
Nuke collect files & dependency manifest
One manifest of every external file the script needs - Read/Write media, LUTs, CDLs, vector fields, fonts and geo - each graded for portability and, when you scan the folder, checked for whether it resolves on disk. The result is a real collect-files list to gather everything before a vendor or farm handoff, so a script that opens on your box opens on theirs too. More on the dependency manifest →
Compare two versions of a Nuke script
Diff two .nk versions node-by-node and see exactly what was added, removed or changed - Write paths, colorspaces, disabled nodes - between v012 and v013. It answers "what changed in this turnover?" in a click, catches what a v-up note glosses over, and needs no Nuke seat to review. More on the version compare →
Nuke OCIO & colourspace audit
Read the Root colour management and OCIO config, every Read/Write colourspace, the OCIOColorSpace and OCIOFileTransform nodes and their LUTs/CDLs - and flag the smells that cause a re-deliver: Reads with no input transform, plates left on Raw, Writes into a display space, and mixed source colourspaces. A colour gate before finals, all in the browser. More on the OCIO & colour audit →
