Resolve is crashing on a certain clip in the color page when I rearrange some of the connections. In general, I have had much more complicated node trees than this one without this problem, but this is one of the first times I've been using multiple mediaOut nodes from Fusion to have separate inputs on the color page. Not certain that's related, but seems far from impossible. This is my current node tree:
Screenshot 2021-12-03 224144.png (59.45 KiB) Viewed 892 times
I'm on a 2017 Razer Blade with Resolve 17.2.2. Windows 10 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz 2.59 GHz 16GB RAM NVIDIA GeForce GTX 1060, DCH driver (Studio as opposed to Game Ready), version 471.96
Uli Plank wrote:If this is 4K, you may still hit a limit.
And I'm probably hitting that limit with a simpler color node tree because two images are still coming out of Fusion first? That would make sense, but I still kind of don't understand why it would only crash on the color page and not also the edit page. Wouldn't it have to render the Fusion output under the hood before having an image to send to the color page to begin with? That implies that a normal render from Fusion would also crash even on the edit page without doing anything in color. And if it's crashing at the color page level, wouldn't that also happen with clips that aren't using Fusion, especially if they have more complex node trees?
A matte. I wasn't done configuring it the I wanted it when I ran into the crash and then took the screenshot, but it's supposed to be the full original image, the new sky (also a full image), and a matte to use as the alpha input to separate the two. I was thinking I might want to have the option to play with the matte itself in the color page if I need to slightly adjust my edges so I don't have to go back and forth with the Fusion page as much.