More bugs I found so far... NR and Tabs display

Hey guys!
I have noticed the Spatial Noise Reduction is not as reliable as until v14. It is giving me jagged edges/pixelated edges with the "Fast" setting and starting from 5 in threshold in color option only. I had to use the "Enhanced" setting and maxed it to 100 threshold in color option only to give me a nice result. And it slowed things waaay down. Didnt try the lumna option. I used to go by using "Fast" before but not now I cant.
Also, something I go through since v14 is that when I come back to the Edit Tab often it doesnt remember tracks sizes and positioning in the screen. Im using a dual screen for UI, Win10 Creators edition and a GTX 970 Strix.

Hope it helps developers. So anxious to be able to composite within Resolve with Fusion integration! But for now Fusion is not reliable enough for me to even try minor things. But we'll get there. Thanks, guys!

Hi, Rohit! Sorry the late.

I've done these on beta 3, so it still persists. I found it when doing a chroma-key job and the edges gotten aliased/jagged and I had to go back to Resolve to see whats happening. At first I thought it was a render problem but then I realised it was a NR issue. I'm attatching some screen grabs to illustrate the issue:

Here is the original image:

01.JPG (201.12 KiB) Viewed 1397 times

Here it is zoomed. You can see some color noise and that's what I usually like to get rid off every edit.

02.JPG (164.28 KiB) Viewed 1397 times

Here it is with threshold 15 on chroma value only and you already can see the jagged edges:

03.JPG (159.18 KiB) Viewed 1397 times

Value 50 and it gets more proeminent:

04.JPG (161.41 KiB) Viewed 1397 times

And here it is changed from "fast" to "enhanced" and threshold set to 100. It gets where I want but at the cost of it becoming very slow due to settings. I used to get that same result until v14 with the "Fast"setting.

05.JPG (156.18 KiB) Viewed 1397 times

It looks like it's processing the noise reduction first and then doing the chroma keying, while in practice you want it to be the other way around.

I used to get that same result until v14 with the "Fast"setting.

and how fast was playback compared to using the fast setting now?

I used to get that same result until v14 with the "Fast"setting.

and how fast was playback compared to using the fast setting now?

Playback seems to be as usual. Only the result on the screen (and rendered video) are like affected. Realtime with "fast", before and now, and very slow with "Enhanced", as would be expected.

It looks like it's processing the noise reduction first and then doing the chroma keying, while in practice you want it to be the other way around.

In fact, it has nothing to do with the chroma-keying itself. In that step, I only do a rough grade to optimize it for chroma-keying in After Effects. I always did that and hope I can do it all inside Resolve soon when Fusion integration becames stable. I only noticed it because I was getting jagged edges in my keyed plates inside AE and I never got that before. Then I nailed the issue. It happens with other "edges" between other colors too, but its hard to see. That combination of colors made it more pronounced. Its like something with the math behind NR is not ok, its like it tries to take the chroma noise out but just a few threshold steps up and it messes everything mixing colors from one area to the other.

Yesterday I dived into NR myself and discovered that Temporal NR doesn't give any effect on the footage.
Do you have the same issue?

Yesterday I dived into NR myself and discovered that Temporal NR doesn't give any effect on the footage.
Do you have the same issue?

Im not used to use Temporal NR as I usually get what I want without much trade off. At least I used to. I only used Temporal with some really bad footage but its slow (as expected). Havent tried it with v15 yet.

Yesterday I dived into NR myself and discovered that Temporal NR doesn't give any effect on the footage.
Do you have the same issue?

depends on the footage and the settings you use. Also, if you can't see any difference by eye then check the scopes to see whether there is any difference with it on

It looks like it's processing the noise reduction first and then doing the chroma keying, while in practice you want it to be the other way around.

In fact, it has nothing to do with the chroma-keying itself. In that step, I only do a rough grade to optimize it for chroma-keying in After Effects. I always did that and hope I can do it all inside Resolve soon when Fusion integration becames stable. I only noticed it because I was getting jagged edges in my keyed plates inside AE and I never got that before. Then I nailed the issue. It happens with other "edges" between other colors too, but its hard to see. That combination of colors made it more pronounced. Its like something with the math behind NR is not ok, its like it tries to take the chroma noise out but just a few threshold steps up and it messes everything mixing colors from one area to the other.

is your footage log then? what happens if you set the node gamma to Linear? (if it isn't log then I expect doing this will make it look terrible, not that I'm sure it will solve the issue in any case)

is your footage log then? what happens if you set the node gamma to Linear? (if it isn't log then I expect doing this will make it look terrible, not that I'm sure it will solve the issue in any case)

Well, in this case it was a BMCC footage, flat/film (log?). DNxHD. Didnt test other formats. Might have something to do... or not. Even if it has, certainly NR has something off.