TNR bug (existed before 17)

Resolve's built-in temporal noise reduction is great, but there's one big pain point when using a scene-cut-detection workflow: it seems that often the temporal NR algorithm tries to use frames from the previous/next clips, which results in nasty artifacts on just the first and last frame of the noise-reduced clip. It makes sense in a way, since the previous and next clips are part of the same piece of media, but Resolve should be smart enough to understand that if a frame is radically different (enough that the "neural engine" already was able to determine that it is a different shot during scene cut detection) it should not be considered when doing temporal noise reduction.

Workaround (in 17) is to do a Render and Replace on the clip on the Edit page, then apply TNR.

I don't think the Neural Engine is used in NR, so...your work around may be 'the' way.

Thanks for explaining why I'm having these artefacts!

It would be great if Resolve had an option to start and end temporal NR at the boundaries of the clip.

Thanks for explaining why I'm having these artefacts!

It would be great if Resolve had an option to start and end temporal NR at the boundaries of the clip.

+1