I’ve been dabbling in Nuke after a few years on Flame, and have found Nuke’s playback to be much much slower.
I’m reading 4K exrs, from an internal NVME RAID. Flame scrubs through and plays the files effortlessly, whereas Nuke’s read node is only getting 7fps while it caches into RAM.
Nuke/Flame artists, do you think I’m missing something obvious here? Or is this just the difference between Flame’s GPU acceleration vs Nuke’s CPU playback?
this is just how nuke is, its always been like this.
Nuke studio has more advanced ram caching and its a bit better but nuke scrubbing and interactivity is nowhere near flame if you sre just reading a file/sequence
For play down/shot review in Nuke there are a few options I like to set as default in the Viewer for max performance.
always on:
[half-float] gl buffer depth
use GPU for viewer when possible
use GPU for inputs when possible
disable GPU viewer dithering
on for review only:
enable full frame processing
With the above options set, and full frame processing on, it caches playback much faster that the defaults, and I can loop playback and pan+zoom around the image, plus use the gain+gamma viewer tools and it stays locked at the playback fps.
This is with Nuke 14.0v2, Rocky 8.5, NVidia A5000, NVMe raid, UHD, DWAA half-float exr frames.
Also, if you have ARRIRAW or R3D footage, enable ‘Use GPU if available’ on the read nodes and I like to disable the postage stamps on those as well.