Resolve 11: Taking Advantage of the Improved Render Cache

This article was originally published on Premiumbeat’s blog here.

If you’re regularly experiencing dropped frames and sluggish performance, Resolve has a Render Cache feature that renders corrections for smoother playback.

For most Resolve systems utilizing modern graphics cards, real-time playback should be attainable (aside from intensive exceptions like playing Red footage at a high debayer).  However, in previous versions of Resolve, the Render Cache has never fully worked. It was the software’s glaringly broken feature, an anomaly in a package that worked so well otherwise. I found myself frustrated mid-session, quitting and re-opening the program to get the Cache to kick in. I assigned offending clips to the Cache manually, only to have the renders clear out, “get stuck” and not regenerate. Rendering was also often slow, with percentages ticking up at a crawl. When dealing with clients that expected a fast session, and at the least real-time playback, it wasn’t optimal.

Updated Render Cache in Resolve 11

That’s why I’m so happy to report that the Render Cache has been revamped for version 11. As with many of the software’s evolving features, Render Cache has been streamlined, simplified. We used to have Cache options for None, All, User, Dissolves, and User and Dissolves. Now, we have only three: None, User, and Smart. The Resolve team must have seen rendering dissolves as not very processor-intensive, and I’d seldom found a use for it in my work, usually opting to work in Unmix mode when on the Color page.

I’ve found the Smart setting to be most useful when utilizing noise reduction, one of the most processor-intensive tasks in the grading process. The Temporal Noise Reduction offered in Resolve has saved more than a few projects I’ve worked on, and the third-party OFX plugin Neat Video for Resolve is one of the best noise reduction tools out there. However, due to the intense processing involved, noise reduction is a memory hog that slows playback to a crawl. This is where the Cache comes in.

Read more on Premiumbeat’s blog.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s