Most delivery problems trace back to a Write node. Nuke Studio Hub parses every Write in your .nk and checks its output path and file name against the rules your studio actually uses.
The problems it catches
- Wrong output folder. A Write pointing at a scratch folder, a local drive, or the wrong shot - not the delivery path.
- Missing version tokens. A hard-coded
v01that never increments, so two renders overwrite each other or the version does not match the script. - Inconsistent render names. Some Writes follow the convention and some do not, so the delivery is a mix of naming styles.
- Client handoff errors. File names that will not match what finals or the client expect, causing a re-deliver.
Before and after
A Write that will bite you:
/Users/me/Desktop/renders/comp.####.exr
The same Write, convention-clean, with a shot, version and padded frames on the delivery path:
$JOB/renders/SHOT010_comp_v012.####.exr
The checker flags the first and shows you exactly which rule it breaks, so fixing it is a decision, not a hunt.
Check them all at once
Nuke scripts can have dozens of Write nodes across a comp. Eyeballing each one is slow and easy to get wrong. Nuke Studio Hub lists every Write, its path, and any naming or version issue in a single report you can export to CSV or PDF and hand to the next artist. Pair it with the Read-media checker and the handoff checklist for a full pre-delivery pass.
Frequently asked questions
Can it enforce our studio naming convention?
Yes. The checker compares each Write node against a naming convention so it flags exactly which nodes and rules are out of line.
Does it catch missing version tokens?
Yes. It flags Write nodes with no version token or a hard-coded version that will not increment between renders.
Do I need Nuke open to check Write nodes?
No. It parses the .nk script text in your browser, so you can audit Write nodes without launching Nuke.