# Nuke vs Flame Playback

**URL:** <https://forum.logik.tv/t/nuke-vs-flame-playback/7725>\
**Category:** Tools and Tech\
**Tags:** nuke\
**Created:** [February 15, 2023, 6:22am UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725 "2023-02-15T06:22:20Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![PatrickC](https://avatars.discourse-cdn.com/v4/letter/p/c67d28/32.png) [@PatrickC](https://forum.logik.tv/u/PatrickC)\
**Post date:** [February 15, 2023, 6:22am UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/1 "2023-02-15T06:22:20Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\
**Post date:** [February 15, 2023, 7:10am UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/2 "2023-02-15T07:10:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![TimC](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/timc/32/11881_2.png) [@TimC](https://forum.logik.tv/u/TimC)\
**Post date:** [February 15, 2023, 5:00pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/3 "2023-02-15T17:00:34Z")

</div>

is this the scanline rendering vs how Flame displays footage? or more ram-caching vs playback off a high speed array

---

<div class="post-metadata">

**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\
**Post date:** [February 15, 2023, 5:07pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/4 "2023-02-15T17:07:15Z")

</div>

you can actually disable the scanline rendering now still doesnt make a difference.

I cant say what the technicla  
reason is for this and how flame manages to do it so well, as does resolve, nuke is just craazh slow

---

<div class="post-metadata">

**Author:** ![PatrickC](https://avatars.discourse-cdn.com/v4/letter/p/c67d28/32.png) [@PatrickC](https://forum.logik.tv/u/PatrickC)\
**Post date:** [February 15, 2023, 10:24pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/5 "2023-02-15T22:24:20Z")

</div>

Yeah I posted this same question on a Nuke forum and got the same response ¯\_(ツ)\_/¯

No wonder so many Flame artists I’ve spoken to struggled with Nuke

---

<div class="post-metadata">

**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\
**Post date:** [February 16, 2023, 8:17am UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/6 "2023-02-16T08:17:50Z")

</div>

for some reason even though everyone says _use exr its faster_ its not, you can playback a prores just fine in nuke usually… which is interesting.

i think nuke is very I/O prohibited, its know also that nuke is VERY slow writing to network storage which is insane.

What I do is I mapped shift+r to open RV on a read node to playback precomps in realtime.

so I send my precomp to the farm, pull back the render and play it in RV , its pretty fast.

---

<div class="post-metadata">

**Author:** ![milanesa](https://avatars.discourse-cdn.com/v4/letter/m/b77776/32.png) [@milanesa](https://forum.logik.tv/u/milanesa)\
**Post date:** [February 16, 2023, 2:09pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/7 "2023-02-16T14:09:33Z")

</div>

If you are pulling from the network, you can also use the Localization options to cache on your fast drive… still wont be real time.

---

<div class="post-metadata">

**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\
**Post date:** [February 16, 2023, 6:31pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/8 "2023-02-16T18:31:53Z")

</div>

nuke 14 is even worse -.-

---

<div class="post-metadata">

**Author:** ![milanesa](https://avatars.discourse-cdn.com/v4/letter/m/b77776/32.png) [@milanesa](https://forum.logik.tv/u/milanesa)\
**Post date:** [February 16, 2023, 6:34pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/9 "2023-02-16T18:34:04Z")

</div>

I was alway expecting a “What does Flame has that Nuke does not” Thread…. playback would be the first item in the list.

---

<div class="post-metadata">

**Author:** ![mybikeislost](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/mybikeislost/32/12217_2.png) [@mybikeislost](https://forum.logik.tv/u/mybikeislost)\
**Post date:** [February 16, 2023, 7:34pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/10 "2023-02-16T19:34:15Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![PatrickC](https://avatars.discourse-cdn.com/v4/letter/p/c67d28/32.png) [@PatrickC](https://forum.logik.tv/u/PatrickC)\
**Post date:** [February 17, 2023, 1:04am UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/11 "2023-02-17T01:04:58Z")

</div>

Thanks, I have similar hardware so I’ll give these settings a shot

---

<div class="post-metadata">

**Author:** ![george](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/george/32/384_2.png) [@george](https://forum.logik.tv/u/george)\
**Post date:** [December 28, 2024, 9:41pm UTC](https://forum.logik.tv/t/nuke-vs-flame-playback/7725/12 "2024-12-28T21:41:27Z")

</div>

I know its old thread but a good practice would be to add a crop and a remove node and keep rgb only  
one is to get rid of the excess information out of the format and the other to remove channels you dont care about . Cache disc : nvme  
gpu on the viewer is helping for not have to redo the cache if you like to do an exposure up or down .  
nuke : workhorse for shots  
flame : finishing station  
but yeah nuke is meeeh in this regard.
