- Posts: 453
- Joined: Wed Feb 21, 2024 11:53 pm
- Location: Planet Earth
- Real Name: Sebastian Alvarez
Fri May 30, 2025 10:02 pm
As much as I hate to say it, Resolve's caching system is still a mess. This manifests at least in two ways:
1) Not all changes to footage delete the previous cache to build a new one. This can be changes in effect parameters, changes made in the Fusion page, going between proxy and non-proxy, and probably many others.
For example, I had created a proxy for an EXR sequence and chose Proxy from the drop down list in the timeline monitor. It started caching automatically about 5 seconds. I went into the Fusion page because the layer that was showing was AO, and I needed Combined. I went back to the edit page. Still showed as AO. I realized that when I created the proxy, it created it from the AO layer, so I clicked on the proxy drop-down and selected "Disable All Proxies". This should have deleted the cache for that timeline, since that was the only clip. But it didn't, it just kept caching where it left off, so now if I play the timeline, I have a few seconds where it's AO, and the rest combined. I had to delete the project's cache (something that because of how bad the caching system is I have to do very often and I setup a shortcut for it), for it to build with the combined layer.
This is just one example, but I find myself using that shortcut all the time because these kinds of situations where I make changes and the previously cached area doesn't get deleted and cached again are very common.
2) Because Fusion Studio beta 4 broke the output for my Decklink Mini Monitor 4K (which the final release didn't fix), and I wanted to watch on my TV set a render I did from Blender in Rec.2020, I imported the EXR sequence into Resolve Studio and created a new sequence from it. This is a 24 fps 2048x858 sequence, and the closest resolution that the Decklink card offers is 2048x1080, which looks perfectly fine to me. This is a multilayer EXR sequence with each frame taking up 103 MB of space, give or take. Which is a lot, but it is on an NVMe drive that benchmarks at 7000 MB per second. So it's fast enough. But, that doesn't really matter because I tried different things, like creating an optimized version, a proxy version, with the optimized version set to Prores 422 and the proxy to Prores 422 Proxy.
And yet, that sequence of about ten seconds cannot play at 24 fps. Granted, it has to render from a Fusion comp because the multilayer sequence loads the AO layer first, so I have to go into the Fusion page to set it to Combined. And when I go back to the edit page, whether I choose to view it as an optimized clip or a proxy one, it will go down to around 9 fps. I think when it's the proxy is slightly higher, like 15.
So I just don't understand why this sequence can't play at 24 fps smoothly after creating an optimized version and even a proxy version, because it doesn't matter if the files are 103 MB each. If Resolve renders any kind of file from that, call it proxy, optimized or its own cache (which also doesn't play smoothly), it should play just fine. And it doesn't. And we're not even talking about 4K footage here. It's 2048x848. It's less than plain old HD 1920x1080. So why wouldn't it play a very simple sequence, the only thing in the timeline, with only one FX which is the OCIO colorspace?
To me it seems that this released was rushed out the door, same for Fusion Studio breaking output from the Decklink card, which was perfectly fine up to Fusion Studio 20 beta 3. What's the big rush? Why not take care of bugs before final release? It seems to me that these days we're all permanent beta testers. Companies release things even without proper testing, so we have to constantly install updates every week or so.
The only software company that doesn't do that in my experience is Steinberg. I have used Cubase Pro since version 12. Most stable software I ever used on Mac and PC. And I don't have to download and install new updates every two weeks. They are every few months. And it just works. They don't have public beta releases, but when they release the first build of a major version, it just works. When it doesn't, it's usually some bug in a plugin and it works fine again as soon as you remove it.
Why can't companies take more time for development and release things when they're ready instead of participating in a non-existent race?
1) Not all changes to footage delete the previous cache to build a new one. This can be changes in effect parameters, changes made in the Fusion page, going between proxy and non-proxy, and probably many others.
For example, I had created a proxy for an EXR sequence and chose Proxy from the drop down list in the timeline monitor. It started caching automatically about 5 seconds. I went into the Fusion page because the layer that was showing was AO, and I needed Combined. I went back to the edit page. Still showed as AO. I realized that when I created the proxy, it created it from the AO layer, so I clicked on the proxy drop-down and selected "Disable All Proxies". This should have deleted the cache for that timeline, since that was the only clip. But it didn't, it just kept caching where it left off, so now if I play the timeline, I have a few seconds where it's AO, and the rest combined. I had to delete the project's cache (something that because of how bad the caching system is I have to do very often and I setup a shortcut for it), for it to build with the combined layer.
This is just one example, but I find myself using that shortcut all the time because these kinds of situations where I make changes and the previously cached area doesn't get deleted and cached again are very common.
2) Because Fusion Studio beta 4 broke the output for my Decklink Mini Monitor 4K (which the final release didn't fix), and I wanted to watch on my TV set a render I did from Blender in Rec.2020, I imported the EXR sequence into Resolve Studio and created a new sequence from it. This is a 24 fps 2048x858 sequence, and the closest resolution that the Decklink card offers is 2048x1080, which looks perfectly fine to me. This is a multilayer EXR sequence with each frame taking up 103 MB of space, give or take. Which is a lot, but it is on an NVMe drive that benchmarks at 7000 MB per second. So it's fast enough. But, that doesn't really matter because I tried different things, like creating an optimized version, a proxy version, with the optimized version set to Prores 422 and the proxy to Prores 422 Proxy.
And yet, that sequence of about ten seconds cannot play at 24 fps. Granted, it has to render from a Fusion comp because the multilayer sequence loads the AO layer first, so I have to go into the Fusion page to set it to Combined. And when I go back to the edit page, whether I choose to view it as an optimized clip or a proxy one, it will go down to around 9 fps. I think when it's the proxy is slightly higher, like 15.
So I just don't understand why this sequence can't play at 24 fps smoothly after creating an optimized version and even a proxy version, because it doesn't matter if the files are 103 MB each. If Resolve renders any kind of file from that, call it proxy, optimized or its own cache (which also doesn't play smoothly), it should play just fine. And it doesn't. And we're not even talking about 4K footage here. It's 2048x848. It's less than plain old HD 1920x1080. So why wouldn't it play a very simple sequence, the only thing in the timeline, with only one FX which is the OCIO colorspace?
To me it seems that this released was rushed out the door, same for Fusion Studio breaking output from the Decklink card, which was perfectly fine up to Fusion Studio 20 beta 3. What's the big rush? Why not take care of bugs before final release? It seems to me that these days we're all permanent beta testers. Companies release things even without proper testing, so we have to constantly install updates every week or so.
The only software company that doesn't do that in my experience is Steinberg. I have used Cubase Pro since version 12. Most stable software I ever used on Mac and PC. And I don't have to download and install new updates every two weeks. They are every few months. And it just works. They don't have public beta releases, but when they release the first build of a major version, it just works. When it doesn't, it's usually some bug in a plugin and it works fine again as soon as you remove it.
Why can't companies take more time for development and release things when they're ready instead of participating in a non-existent race?