18.1 not updating on the color page

Hi there
Is anyone else having this issue using the new 18.1 release on a PC:
I'm finding that after a while when tweaking a reasonably complex grade on the color page .. Resolves stops updating the output, whatever you do the current output remains. It seems to have rendered cache and is sticking with it not realising that updates have been made. My current workaround is to set the timeline to 'none' on the render cache dropdown - not ideal, but hopefully it will be an easy fix. It would also be great if the render panic internal setting could amended on the timeline - so I often grab a clip and drag & drop it earlier in the sequence but Davinci says that the whole timeline area that you have dragged over must need a fresh render, rather just where you drop the clip. Doing a copy and paste does avoid this issue, but drag and drop is so handy and hopefully an easy tweak to the code?

Robin

I also have this issue. The grades are not overly complex - 16 nodes in a fixed node tree. Noise reduction on 1st node.

I have had this issue for a long time now and I was hoping today's update (18.1.3) would solve it, but unfortunately it hasn't.

It's very frustrating in a session as suddenly my adjustments are not shown and I have to disable and re-enable cache. I experience this on both my studio system and my system at home, which are different hardware and system builds. Has anyone else had this issue?

Windows 10
AMD TR 32-core 3970X
RTX 3090
128MB RAM

Media storage is over 10GbE network or on local drives.
Cache is set to local NVME

+ 1 I am only experiencing this issue with automatic caching and not user mode.

I am sad to report that I'm still getting this issue frequently in the latest update.

Logs on the link - https://we.tl/t-mfO9s5UOcK. They were too large to upload here.

I would love to know if this can be reproduced and looked into sometimes as it's a a real problem for us here.

Current system:
Windows 11
AMD TR 32-core 3970X
RTX 3090
128MB RAM

Using DNxHR 4444 Cache onto an M2 internal drive. The codec never makes any difference.

what are you caching? the output?

One thing to check is a broken node link. I've chased around why a certain clip won't update and the scopes seem dead. I found the answer was the small input link between a node in the chain of nodes was disconnected. Stupid me. Hours lost searching the sub menus on scopes, manual, this forum.

Just my screw up when using a parallel node and changing the node link from a serial node into a parallel node but forgetting to reconnect the serial node.

I'm just using Smart Cache. I never had a single problem with it until version 18.

I can try caching nodes manually and see what happens, but surely Smart Cache should behave. In my current project I can turn cache on and off and see that the cache has just not refreshed since my last action. This happens with just a simple few nodes.

+1 seeing this issue daily on multiple systems.
smart caching to prores4444XQ or uncompressed 16bit - usually happens when there are multiple nodes that are cached and grade changes happen upstream...but its hard to figure out for certain as it occurs seemingly randomly.

I am having the same issue. The software still works and you can make changes in the nodes and or disable them and no update to the node or output. Usually a restart does the trick but it will come back. The program is not frozen. It just stops updating. I am working with 4k or 6k footage and 10ish nodes. I have not been able to narrow anything down, but it is frustrating. I still absolutely love Davinci Resolve though.

[Dwaine Maggart]

Next time that happens, select the Resolve Help menu: "Create Diagnostics Log on Desktop" and send us a link to the file.

Hi Dwaine,

This happened just now so I have attached logs.

I was playing around with the Sky Replacement effect and adjusting a key and mask that feeds into it. Suddenly it stopped updating, switching the node on/off and moving the mask around didn't trigger a cache update. Last few actions were switching the smart cache off and toggling nodes on/off to check it was responding again.

Thanks for looking into this.

[Dwaine Maggart]

Can you send a project export .drp of the project you were working with?

Looks like there were issues with the DeckLink SDI config. I don't know if that was a cause or an effect.

In Project Settings - Master Settings - Video Monitoring, Resolve defaults to SDI configuration - Dual link. Your Studio 4K card does not support dual link, so make sure that's set to Single link.

If it is set to Single link, make sure there is not some other app running that would access the Decklink card.

Thanks Dwaine! Interesting about the Video settings, not sure how that happened. I've not actually had any video output issues. I do sometimes have to run Premiere at the same time which also uses the Decklink. I switch between the two without issues generally, although sometimes they can conflict if I don't fully minimise one app properly first, which is to be expected.

The cache problem is also the same on my GUI as it is externally, so I can't imagine this is directly related.

Here's the project - https://we.tl/t-ZWvZJ6GbEX

It's quite a big one but hopefully it helps.

Cheers!

Hi Dwaine,

Quick follow up on this as it happened again on a much simpler project.

Turning some of my nodes on/off or making changes didn't update cache. If I bypass all colour then I see the change. Weirdly I can disable my colour transform at the end of the chain and that updates the picture, but the nodes upstream don't show a change until I disable cache. It works normally for about 90% of the time... but when it fails it fails repeatedly.

New logs and simpler proj here - https://we.tl/t-T8qcHNFfDg

We're running projects from a shared network Database. Could that be related? Current projects are only in Single User mode.

We have literally 100s machine (linix) in shared databases…. i dont think that is the issue….

[Dwaine Maggart]

I'm still seeing DeckLink config errors, but I doubt those are directly related to the issue you are describing. But, if you have Premiere running at the same time as Resolve, perhaps there are resource issues due to that. Would it be possible to make sure no other heavy apps are running, and see if the Resolve issues still happen?

You are also using a pretty heavy cache format, and your default cache path is your C: drive. That's not filling up, is it? Cache for the project you sent is around 69 GB.

That's definitely not right. My cache is set to a local 4TB M2 on both of those projects. Occasionally it can be set to C: by accident when it gets set incorrectly by someone sharing a project, but these seem to be set correctly.

Decklink is set to single link in this latest project I sent over. I'm very confused if you're still seeing it set to Dual.

I also ran into the same issues without Prem or other apps running earlier today.

[Dwaine Maggart]

I can't tell from a project what it's cache path is actually set to. All I can see is that in the preferences, the default cache path is the C: drive. If you are then setting the project to cache in a different location, great.

All I see are DeckLink SDI config errors. I see that your project is set to single link, therefore it seems the errors are likely coming from something else controlling the DeckLink and preventing Resolve from setting it was desired.

How about this as a test, just to totally eliminate the DeckLink from consideration. In Resolve Preferences - System - Video and Audio I/O, set Monitor Device to None, save the prefs and restart Resolve.

Again, this is only a test. I realize you can't run that way normally. But do the other issues persist with the DeckLink out of the picture?

Ahh, gotcha. I have a project template that's set up correctly for cache but I'll check my defaults too. I appreciate that checking absolutely everything is setup correctly is a good troubleshooting plan.

I'll try that test out today hopefully. Really appreciate the help.