Colour mistakes are expensive because they are invisible until the wrong thing renders. Nuke Studio Hub parses the colour settings baked into your .nk and gives you one OCIO & colourspace audit - so a mis-set Read or a Write into a display space gets caught at your desk, not on delivery.
Root colour management & OCIO config
The audit starts at the Root, where a script records its colour management mode and OCIO config. It reads which config the comp expects and reports it up front, so you know the colour context every other node is operating in before you trust a single transform. When a shot lands from another studio, that one line often explains why everything downstream looks wrong.
Every Read and Write colourspace
Then it walks every Read and Write and lists the colourspace each one uses, flagging the smells that bite comps:
- Reads with no input transform - plates pulled in without being brought to working space.
- Plates left on Raw - source footage that never got its correct colourspace assigned.
- Writes into a display space - renders baked to an sRGB or Rec.709 view when finals expect scene-linear or a delivery transform.
- Mixed source colourspaces - plates on different transforms that need a second look before they are composited together.
OCIO nodes, LUTs and CDLs
Colour does not only live on Reads and Writes. The audit inventories the OCIOColorSpace and OCIOFileTransform nodes in the tree, and the LUTs and CDLs they reference, so you can see the full chain of transforms a comp applies. That surfaces the LUT that points at a file only on one machine, the CDL that will not travel, and the redundant or conflicting transforms that quietly shift a shot's look.
Catch it before a re-deliver
A single wrong colourspace can send a whole batch back. The point of the audit is to make the colour pipeline legible in seconds: one consistent view of how the script reads, works in, and writes colour, with the risky spots called out. Supervisors use it as a colour gate before finals; freelancers use it to confirm a delivery matches the client's config; studios use it to keep every artist on the same colour rules. Fold it in with the wider script audit and you have naming, media and colour checked in one pass.
Parsed locally, nothing uploaded
The colour audit reads the settings recorded in the .nk as text, right in your browser - it does not need to load your OCIO config or open Nuke, and nothing about your script is sent anywhere. It runs on Nuke 14 to 16 scripts and starts at A$9/mo with a 14-day free trial.
Frequently asked questions
What does the colour audit check?
The Root OCIO config and colour management, every Read and Write colourspace, OCIOColorSpace and OCIOFileTransform nodes, and LUT/CDL usage - flagging the smells that cause a re-deliver, like Reads with no input transform or Writes into a display space.
Does it need my OCIO config or Nuke installed?
No. It reads the colour settings recorded in the .nk as text, so it audits the script's colour pipeline in your browser without loading a config or opening Nuke.
Which Nuke versions are supported?
Scripts from Nuke 14, 15 and 16. Because it parses the .nk text directly, the colour audit does not need Nuke installed.