Bug: rendering title w/ blur dissolve

There is a bug in Resolve which results in splotchy artefacts on a title sequence when rendered out. Have observed on Win 10 across different render formats. Haven't tested on Linux yet.

How to reproduce: when rendering a title which is not white with a blur dissolve transition and enabling dynamic zoom or any other transition effect under the Text "Video" tab, random circular splotches are generated specifically during the dissolve transition.

vlcsnap-2019-11-19-12h03m12s252.png (274.51 KiB) Viewed 3136 times

I attempted to duplicate this, and was unable. Tried h.264 Native and NVIDIA encoders and DNxHD. What particular codecs failed for you?

This might be small enough that you could zip up the .drp and post it and if not then Dropbox or Google Drive.

Also, which version of DR? There was a similar issue with 16.1 for a particular codec that was solved.

Coincidentally, I tried the same codecs on export (H264 NVIDIA/Native & DNxHR)

Using Resolve 16.1.1

DRP Download: https://gofile.io/?c=cCSo5i

I was able to duplicate this right off. Then I played with it a bit, duplicated the clip on track 1 and stretched the Text effect and then stretch the fade in and fade out. That tended to make the glitches disappear on the fade out but much, much more visible on the fade it.

So to BMD staff. The bug has been duplicated/verified using the project file in the last comment.

I see the problem with the supplied project too.

Using the 16.1.2 update, I just just retried the simple test project provided earlier for this. The bug remains. There are artifacts in the rendered file, whether to h.264 or DNxHR.

Since the test project expired in the original poster's upload to dropbox, I have supplied a copy in my Google Drive (it's rather small at <30kB) https://drive.google.com/open?id=1yUer7 ... 2Rwuv8aCCH

So this bug was identified and verified independently by two other people, but it was missed and fell in a crack. How do we make sure it gets on BMD's bug tracker and fixed before the next release?

With the sheer volume of posts on this sub-forum, I'm not surprised that things get lost. Might be high time to create sub-sections and have separation between topics... like "Beginners Resolve" and "Advanced Resolve"... I think the posts will keep growing exponentially as more and more users jump off the Adobe rental bandwagon.

I've PMed Peter and Rohit to give them visibility of the bug.

Resolve bug report should be a subforum with the possiblity to mark it as confirmed by other users or fixed.

FYI the bug still exists in 16.2

This bug is still manifesting in 16.2.3

*bump*

Still exists on 16.2.4

This appears to have been fixed in beta1 of Resolve 17

This appears to have been fixed in beta1 of Resolve 17

Nope.