Spatial render issue (v17.2)

After upgrading DR with project to 17.2 I get multiple random artefacts in same frame when using Spatial Threshold. Tried removing and adding the node but that does not solve the issue.

Test render: https://danielsenphoto.com/davinci/Render_test.mp4

Anyone with similar issue or fix?

Setup: MacPro(Late 2013), D700, 64 GBRAM. BigSur 11.3.1.

[Shrinivas Ramani]

Hi

Could you post an example DRA (project archive) with a small clip that we can observe?

Please feel free to dupe the project, clear out other timelines/clips if the project is sensitive.

Along with the logs from help menu, please upload the DRA to a file share website and provide the link.
Thanks
Shrinivas

Thanks for a quick reply.

At my home office this did not occur with the same project. So it might be specific for the MacPro(2013) or D700 GPUs?

Home office setup: MacBook Pro (15-inch, 2017 Radeon Pro 560 4 GB), 16GBRAM, eGPU with AMD Radeon RX 5500 XT. BigSur 11.3.1.

If you still would like a project file insight, let me know.

Thank you and thanks for your great work on DR++.

Hi

Could you post an example DRA (project archive) with a small clip that we can observe?

Please feel free to dupe the project, clear out other timelines/clips if the project is sensitive.

Along with the logs from help menu, please upload the DRA to a file share website and provide the link.
Thanks
Shrinivas

https://danielsenphoto.com/davinci/DR_test.zip

I have same issue in
setup :
macpro2017
macos bigsur 11.3.1

other mac
setup
iMac 2018 4k
macos bigsur 11.3.1
not appear this issue

Issue persists in v17.2.1.

[Shrinivas Ramani]

Hi Arild

Unfortunately, this is an issue introduced in Big Sur, specific to the D700 GPU. There is nothing we can do to work around the bug in Resolve.

If this a critical issue, you may wish to consider using Mac OS Catalina for the short term as a workaround.

Thanks
Shrinivas

Hi Arild

Unfortunately, this is an issue introduced in Big Sur, specific to the D700 GPU. There is nothing we can do to work around the bug in Resolve.

If this a critical issue, you may wish to consider using Mac OS Catalina for the short term as a workaround.

Thanks
Shrinivas

Thank you, that is great to know, fortunately I can render on a separate work station the very rare times I need the Spatial Threshold tool. Meanwhile, Apple hopefully fixes this in the future as I still enjoy working on my good ol' "trash can" machine.

Thanks for your great work and help.

Best, Arild.

Update: It seems to be working again in OSX v.11.5.2/Resolve Studio v.17.3.

Update 2: However, now there is an introduction of other artefacts on render output (see attached screenshot).

Thanks,
Arild.