Sat Apr 11, 2020 10:02 pm
Note: I was not able to reproduce this problem after restarting my Mac.
Note 2: It does appear that when highlighting is enabled (not A/B mode) that TNR becomes disabled. I'm not sure I understand the logic of that.
I have just observed another oddity with trying to highlight TNR effects. I have a project that contains mostly R3D media. When I select a clip that uses the Project's default settings and then attempt to examine the TNR node in Highlight A/B mode, I get nothing but straight black. When I change the Decode Quality setting for the clip from Use Project to any other setting (from Full Res Premium to 1/16th Good), then I can see the pixels that differ due to TNR. When I switch back to Use Project, the decode setting is correctly restored to what my project is using, AND the TNR node shows the noise-reduced pixels according to that decoding setting. As I step through the clip, I can see the pixels dance. When I select another clip, then return to that one, the TNR mode again shows no pixel differences in the Highlight A/B mode until I change the decode options and change them back.
But more seriously than just the display using Highlight A/B mode, Resolve doesn't apply TNR to my clips unless I do this manual dance. Which only works for a single clip (not even all clips in single-clip mode). So it's really broken for me using R3D files.
It would be great if Resolve did not need this back-and-forth intervention to get TNR working with R3D media.
MacOS Catalina Version 10.15.7
iMac Pro (2017)
3 GHz Intel Xeon W
64GB 2666 MHz DDR4
Radeon Pro Vega 64 16 GB
RED Rocket-X
Decklink 8K Pro card feeding FSI XM310K Monitor