How to make Resolve run 75% FASTER

Dude, $20,000 machine and I can't get streaming. If you've ever used After Effects Maya or Cinema 4D, then you're no stranger to a slow experience. Mac PC, $500 computer, $20,000 workstation, it doesn't matter, in this video I go. to show you how to

make

your system run 75%

faster

and

resolve

with simple techniques and if you want to follow along you can download the footage from my Discord channel. The link will be in the description. All I ask in return is that you subscribe. Channel hits the like button and let's move on to the intro before moving on to the question of the week: who rated Oppenheimer and how would you describe the look?

The winner will receive recognition in the next video. The solution has three main ways to optimize your footage. Timeline Proxy Resolver generates proxy media and renders cache, so let's start with the most common type, which is Timeline Proxy Resolver. You're probably familiar with it in Premier Pro Final Cut 10 or Avid, they all have that thing where you can reduce the resolution of the timeline in half. or a quarter so that the reproduction is smooth, it is perfect for editing, it is not ideal for color grading and you will know what I mean, so now we are on our color page and if I do a reproduction I will get about six or seven the frames are correct, okay, if I go to the playback menu and the timeline proxy resolution, I can take it from Full to Medium and this footage is 4K, you can see it right here, UHD and the timeline is also UHD, okay, so let's come back here.

I can go to my playback timeline proxy resolution let's lower it to 1080p, which will be half. We got 7 frames per second. Let's see where we are now. We're getting between 14 and 15 frames. It's a 100% increase, so the performance increase is out of control. Okay, what happens if I go to playback and lower the resolution of the timeline proxy? Leave it in a room. Let's try again. Okay, now we're getting closer to real time, so we get 20 frames. We went from seven frames, six to seven frames. 20 frames per second, which is more than doable if you're editing well, but here's the problem if I key in and we're here, just look at the jagged edges and what happened to the grain pattern.

Now keep your eyes on this section, let me. go back to the playback timeline proxy, set it to maximum and just watch what happens, you'll see how much the texture of our footage was affected, which is why it's absolutely a big no when it comes to grading to use this technique. perfect for editing, we recently did a survey. Most of you, regardless of your skill set, struggle with matching skin tones, balancing, and working with 8-bit images, so I created a free 1 hour long training that covers all of that plus we'll wrap up the training . with an extensive Q&A session and you will also get a link to download the power ratings from the practice footage and some of my personal LS links to the training are in the description below.

Let's go back to the video, so now let's look at the second popular one. The option which is to generate proxy media is perfect for this situation here, so I have a clip here that is shot in Raw on a red Gemini 5K clip and if I do a playback after a bit of grading, it drowns out and we get about 14 . frames, well, you can see it right here Gemini 5K, so what can we do? What can we do? We can proxy to get much smoother playback, so when I click on my project settings in the master settings, this is the section we need to look at.

Right now the resolution is set to choose automatically, we can force it if we just want to

make

sure that the resolution stays intact because we already discussed that when you lower the resolution, it affects your texture if you're applying. stuff like that, but the resolution is so smart that depending on your system it will make that decision, in my case I'm pretty sure it won't mess with my resolution, so I'll just let you choose. automatically and then for the 422 HQ proxy media format is almost lossless. This is the default for streaming and Netflix and all those platforms, so that's the default standard and I'll leave it as it is now.

Generating proxies takes time, so you want it. to make sure you choose the fastest drive you should download those things to, so now the drive I chose is around 8000 megabytes as read and right, so the whole process will be much

faster

, the same will be true for the cache. files okay so what we want to do is we want to come here in our media pool and this is our r3d file so I'm going to right click here and I'm going to say generate proxy media okay so as soon as you click here it will continue and it will transcode the clip to 422 HQ on the surface nothing actually happens like the file still says r3d play it and let's see what happens wow so we'll get real time playback. something actually changed but the quality is exactly the same and it still says r3d even if I hover over and if I go here it says r3d right here the only thing that changed is the icon here just look at it so instead of liking what Before we had a camera behind it and then a small clip in front, which means it's not the original camera, it's a proxy clip.

Another way to know that it is a proxy clip. You can right click on this area and go down. here activate the proxy media path and then also the online status and if I exit suddenly we can see the resolution of the proxy, it left it as expected and then for the online status, it is not original, now it is proxy and if go up to here, it's going to give me my location where the proxy media is stored and this is what's happening right now here, if I go to my color page, one thing you want to make sure of is that in your play below the proxy handling is configured to prefer proxies because if it's configured to disable all proxies now, if we do a replay, nothing happens, so you might be confused because you're generating proxies there and then you come here and say, dude, why?

It's not working, what's happening, so just go here in your playback and make sure that in proxy handling it's set to proxies. Now the ideal scenario for using proxies is this when you're grading, click play and go to proxy management and just configure it. prefer the original camera so that when you're grading you have the highest quality image, so even if it's choppy, who cares that you're grading? continue when the customer comes in, you can leave, okay, let me do this and you can leave. Prefer proxies as the quality is not very low resolution, the client will be very happy and will appreciate that the playback is in real time and then once you are done with the client, go back to the original camera in the way you want to organize . is that you go to lunch, you generate proxies and then when you come back, everything is ready to go at that point, you just flip the switch and that's it, you go to Third and my favorite option, render cache, and this is the method where you

resolve

will come in and render your clips when your system is in idle state. resolve has three different types of render cache options and before we get into that, let's click on our settings again and what you can see here in your render cache will be set to pros. 422 HQ, which is exactly what we need, so let's start with the Fusion render cache.

You see these three little stars here, that means it's a fusion clip, so I just removed all the corrections I made to this clip and if I play it. It's not playing in real time, it's suffocating. Why is prores 444 UHD? It should play fine. This happens because a fusion effect is applied to it and it is suffocating it in order to fix it. I can right click here. I can go to the Fusion Output render cache. I can set it to Nothing really changes here because you have to go to the playback render cache and then set it to user as soon as I do that, you'll see that line.

Now you'll see like it's starting to turn blue so check it now we're getting real time playback so we went from six and seven frames to real time playback so that's the first problem on the L hand why did I do this first? the resolution works from Upstream to Downstream when you make a change here then you go to your color page and if I take all of these and turn them on that blue line stays intact it doesn't need to be rendered and if I do a render it's still choking much better than before, but there are certain effects applied here that are quite heavy and that's what's causing the couple of throttling options we have here to fix this issue are playback under cash render and what if we set to Smart it's an automatic option and if we go to Smart now the resolution goes and looks at each node that it thinks needs render cache.

This is my least favorite type of rendering cash because you're not in control, it's just taking control. and it's overkill everything, what if I go and take you to this project right here and now we have a red raw project with hundreds of clips on a timeline and imagine if I go here in playback and change this to Smart, just look what's going to happen? The first thing that happened was this red line appeared all over my timeline and look what's about to happen with my Clips boom, suddenly they all turn red and I don't know if you can hear my computer right now, it's working so damn. with a lot of effort and just look at how many different nodes it will go and select the ones that need to be rendered, it will take up so much storage on your system that it will choke your machine for so long, that's why this is not my preferred method and a more advanced method would be this , so let's buy some real status.

All I'm going to do is play, go here and then change it to user. Let's do a playback like it didn't do anything, so the changes we had made. our Fusion render that took us from six frames to 14 frames was a big jump, but nothing really changed here because now you're in manual mode and you have to decide which node you want to render cash. It is very easy to do this. Let's say I'm going to start right here, I'm going to turn off these three effects and I'm going to do a playback, so we go from 14 frames to almost real time, so that's pretty ridiculous, what if you take this off and now play it right, that's even better now that we're literally at almost 24 frames per second.

What happens if I turn this off and play it now that we're getting real-time playback? What happens if we reverse it? What happens if I turn on? all this turned on and now we do a playback, we are almost in real time and then it tells me that the real culprit was the noise reduction as it always will be so what I'm going to do is this: I'm going to turn this on I'm going to right click and I'll say node cache enabled and just look what happens, this is the only node that turned red because we're manually controlling it, it's going to render it a lot faster and now if you go do a playback like once it's done rendering the cache as you're going to see we're going to have a crazy boost 12 frames wait for it to explode so now we're at 21 frames this is more than doable whether you're showing it to the client or when you're working on your own grading your Projects.

The beautiful thing about this is that if you're working with a fixed tree, even if you have 400 shots, we can make that change and then select Ripple. and that will apply throughout the project, the order of the nodes is important when using node caching, so if I were to detach this by pressing e, I would bring it up here and drop it, it would take a second and everything would change. red, so it's going to go away and re-render, so let's wait, okay, and now if I render it, we'll get the same amount of performance. The problem now is that if I go and create a new node, look what it did, it threw the You can't just put anything anywhere without thinking, so if I were to take this offline again and put it in Upstream like we did before, now I go to set it up here, wait until everything renders well, so there we are.

We're there again right now, if I go here Downstream and I go, I want to change this and do it like crazy, so I want to do that, look at this, I'm turning it on and off, it doesn't affect anything. no need to re-render it because the Noe cache happened upstream and that's how you make the resolution run 75% faster on your machine. If you enjoyed the video, hit the like button. See you at the next one.