Yes, it’s basically the same but more sophisticated. You have several choices in Resolve: there’s a universal setting (i.e., applies to all clips) where you can choose no render cache, smart render cache, or user render cache, and you can also manually set specific clips to be render-cached using the render cache clip output or Fusion output.
The smart render cache acts like FCPX’s background rendering: all processor-intensive effects (Fusion effects, titles, transitions, etc.) are rendered automatically. The user render cache allows you to choose (in the Master Settings section of the Project Settings) which types of processor-intensive effects you want to render-cache. The choices there are transitions, composites, and Fusion effects; you can turn off any one of them if you know you don’t want transitions (for example) to ever be render-cached.
The clip-based output cache provides the most control; you pick and choose which clips will be render-cached.
All of this will help in terms of real-time playback, but I saw in another thread that you’re thinking of buying an older MacBook Air, and I’m pretty sure Resolve 16 will be unusable on that machine, at least for anything beyond basic editing. My test machine is a 2014 Mac Mini with i5 and 8 gigs of RAM, and while Resolve will run on it, it’s not practical for real work even with 1080p footage. You can definitely forget about using Fusion, and while you can accomplish basic primary and secondary color grades it won’t handle GPU-heavy tasks like noise reduction, deflicker, etc.
What’s Render Cache? Does it use hardware differently or does it render some things and not others? I have an 2017 MB Air that runs Resolve 15 but you have to use the highest screen resolution, which makes the interface very small on 13″ screen. Not all buttons appear even so.
Independent/personal/avant-garde cinema, New York City
The render cache is simply designed to speed playback, that’s all. It renders certain processor-intensive effects (e.g., Fusion animations, noise reduction, titles, transitions, etc.) in the background so you can play back your timeline without it stuttering and dropping frames. Without render caching, some of the clips in my 23.98 fps timeline play back at 1 frame per second, especially if I’ve applied noise reduction.
Think of it this way: with the render cache turned off, your GPU (or in your case the integrated Intel graphics) has to do all the work of processing effects every single time you play through clips on your timeline. When you turn on the render cache, those effects are baked in and the GPU doesn’t have to go through all that work each time.
The MacBook Air’s graphics processor isn’t going to be robust enough to even accomplish some tasks, especially in Fusion, but also on the Color page. It should be fine for editing and maybe some basic color correction on HD or proxy footage.
Hi Brad, a question for you (or everyone) from Paris, because you seem to be an expert : Is there a way to keep working in fusion, edit, color etc while Resolve is processing an export (creating a file) ?
That’s one of the very pleasant FinalCutPro’s feature, you can keep on working instead of waiting for ages the files to be processed… especially when you have to export something like a one hour documentary for instance.
Thank you for your answer
(and a little last one : I’m searching for a way to delete locked keyframes in fusion (keyframes with a lock icon (don’t know why some have a lock icon))… If you have the answer, I would be the happiest man on earth.