Broken Read nodes are the fastest way to lose an afternoon. Nuke Studio Hub reads every Read in your .nk and flags the media problems that turn into red frames and failed renders.
What it flags
- Broken absolute paths. A Read pointing at
/Users/artist/...that only exists on one machine and will not resolve for anyone else or on the farm. - Missing plates and files. Media the script expects that is not where the path says it should be.
- Local-drive references. Plates on a desktop or scratch disk instead of shared storage, so the comp breaks the moment it moves.
- Frame-range mismatches. A Read whose range does not match the media on disk, so frames drop out mid-render.
Catch it at your desk, not at 2am
Because Nuke Studio Hub parses the .nk as text in the browser, it can tell you a plate is missing or mis-pathed without opening the project and without your media being present. That is the difference between finding a broken Read while you still have context and finding it when the overnight render fails and nobody is at the desk.
Portable paths, portable comps
The Read checker is really a portability check: a script full of absolute, local paths will not survive a handoff, no matter how good the comp is. Fixing Reads to resolve against shared storage and a consistent project root is what lets a script open the same way for the next artist. See how to keep Nuke scripts portable for the full approach, and run the Write-node checker for the output side.
Frequently asked questions
Can it find missing media without my plates?
Yes. It reads the paths and frame ranges declared in the .nk, so it flags broken and local-only paths even when the media is not on the machine running the check.
Does it catch absolute paths?
Yes. Absolute and local-drive paths that will not resolve on another machine or the farm are flagged so you can make them portable.
Will it catch frame-range problems?
It flags Read nodes whose declared frame range looks inconsistent, so you can check them before a render drops frames.