![]() ![]() When this occurs, DaVinci is using your scratch disk as an output drive. Keep in mind that cache rendering is triggered whenever it is needed after 5 seconds of inactivity – this value can be changed in the project settings – General Options / Enable background caching after X seconds: Background Caching delay Source Cache works similar to Proxy files, and it has to be re-rendered whenever a source clip has changed, which in most cases will be when we apply any change to the Camera RAW settings of the RAW footage.Adding a serial node after doesn’t affect it and the cache is still valid. Node Cache is broken whenever a change is made before this node.so it has to be re-rendered whenever a change is made to the clip. Output Cache is rendered after all the color corrections, node plugins, etc.Broken CacheĬache is broken as soon as the change is made before the caching point. It works only in Smart mode and renders clips in the timeline that use composite modes other than Normal and any clips with opacity or speed effects. Sequence CacheĪccording to the Resolve’s manual there’s no way to trigger Sequence Cache in User mode. So in case we have some 4K footage in the project, and the timeline is set to 1080p, the footage will be downscaled during the caching process. – it just plays back the cached ProRes file.Īdditionally, caching at the source level scales the video to the timeline resolution. After applying Camera RAW settings, I enable Source Cache and the playback is not affected by RAW processing/debayering/etc. In my case, I use it every time I have RAW footage in my project. Works really well with formats that are heavy and require a lot of CPU/GPU processing. Source cache can be treated as on the fly proxy generation. The only exception is Camera RAW module – any change in there will break the cache. Source cache, as opposed to Output Cache, is rendered before all the color correction adjustments. The situation changes when we try to change anything that is before the cached node, and, in this case, the node has to be re-rendered:Ī good practice is to use Node Cache for 3rd party OpenFX plugins as they usually take a lot of CPU/GPU time and the real-time playback is most likely lost after applying them. All the changes are applied on top of the rendered ProRes File. After adding a serial node after, we can apply all the built-in color corrections, and the cache is still valid. Let’s say we apply OpenFX plugin in the first node and then cache the node. This is the most useful caching type in my opinion and allows to build on top of the cache without breaking it. Node CacheĪll the changes made within one node can be cached on the node level using Node Cache: Enable Node Cache Fortunately, there are other types of caching allowing us to build on top of them without the need of re-rendering each time we apply any color correction. The above picture shows that the render cache is not valid anymore and has to be re-rendered (red color). The only problem with Output Cache is that it gets broken always when there’s any correction made to the clip. Output cache is designed to improve the editing within Resolve for playback and trimming. The output cache is the last caching point in the processing chain, and it happens just before the frame is sent to playback. Now we can trigger any type of caching at any level. To enable User Render Cache select the option in the Playback menu: Enable User Render Cache ![]() ![]() To have a full control over the caching process we need to change its mode to User (there’s also a smart mode which manages caching automatically the default one is none though). The below diagram shows how the processing flows within DaVinci: There are 4 caching levels in DaVinci Resolve: Caching in DaVinci resolve was mentioned in my recent article about its performance, and today I decided to write a bit more just about this feature. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |