It works sometimes and sometimes it doesn't (until I make it somehow as mentioned above) Although it is not perfect and isn't a clean way to go about it. This is done as an effort to force Davinci Resolve to put more bits into rendering those frames where the issue shows itself.

I've tried to eradicate this up-to some extent with the help of an image layer on top(with suitable composite mode and opacity) - Like these ones The only thing that I've found to be constant and that is the fact that it usually happens when sudden changes are made within the video which shouldn't really occur since this is a very resolve specific issue and other workstations seem to not have this glitch. The glitch is very unpredictable and can show itself at any random edit. I am still not entirely sure why this issue exists or how to fix this. I have been getting the same issue even now in Resolve 16.2.2. So far the only thing that helps is lowering the render speed, but it's still not eliminating all glitches, and it makes rendering take forever (slowing down not only the complex layered parts, but even pure black and credits).Ĭould it be that Resolve has bugs rendering out footage that is H.264 in the timeline, no matter what it's rendered too? Seems like this could be the problem. However I'm seeing just as many glitches with other codecs. I've read you shouldn't render to H.264 because it specifically has issues, and that rendering to DNx or anything else should work. For the project I'm currently working on none of this helps. I've read comments advocating turning on 'force debayer to highest quality', 'force sizing to highest quality', turning off 'network optimization', changing the render color space to something different than the project's color space, setting the timeline resolution to match the render resolution, and more. I don't think this issue is necessarily due to rendering to H.264.

Glitch effect davinci resolve 17