-
Resolve 17.2: mask piped to next node does not show up as expected
What has worked a thousand times now seems consistently not to work well.
We have all used power windows a thousand times, piping a power window into the next node, in addition to the RGB video pipe. One could then, for example, brighten a face power window in the next node using the piped power window. Or, we might use, for example, an HSL or 3D keyer to create a matte which is then piped to the next node in addition to the RGB pipe.
Piped power windows and mattes have worked as expected a thousand times. Until recently.
Perhaps starting with the newest releases of Resolve 17 there are baffling behaviors in the piped node.
Most frustrating is that the power window or key selection matte may not appear at all in the receiving node. Or a solid color field may appear instead of a mask/matte selection. Or the expected mask may suddenly appear if one disables the piped node and re-enables it. Or perhaps disconnects and reconnects the mask/matte pipe. But no behavior is consistent.
This tool which has worked a thousand times before but now doesn’t seem to work most of the time. The node highlight feature, always helpful when dealing with masks and mattes, likewise shows this baffling behavior.
Tried all sorts of variations to identify the steps that lead to this behavior. No joy.
And, FWIW, another unexpected behavior is that the matte view window in the key options window no longer seems to show the entire mask/matte but seems to be zoomed in, showing only a portion of the mask/matte frame. Unusable.
Has something changed??? What am I missing???
(Hardware shouldn’t be the problem: happily used this PC for Resolve for a couple of years: 12 Xeon cores, 48 gig ram, two or three SSDs, perhaps 40-50 TB of storage.)
Thanks, guys (and girls!)
Mike
-
2 Replies
-
Just took a look at this, and had no issue pipping a window into different nodes…serial, layer, no issues at all.
-
Thanks, Glenn. Glad an expert had a quick look at this. And also that you did not seem to recognize this issue otherwise: That is, when a guy has a problem he is rarely the first one if it is a genuine app issue.
I did some of the usual re-install and re-start and, happily, it is much better, perhaps fixed.
In the background, I wonder about how, exactly, Resolve handles alphas, masks and mattes in the Resolve node area. We all know that blending those can be done in a million ways. But since Black Magic supports also Fusion stand-alone Studio and Resolve/Fusion, I am happy to think that, at bottom, they really do have it handled.
Must be very tricky for them, though, to cram all that nuance and subtlety into a user-friendly app.
Thanks again, Glenn.
Mike
Reply to this Discussion! Login or Sign Up