The infamous GPU render Error -1609629695

2020 and its still happening...

Same here, Lumetri generates that error in my projects!
also the "Offset Effect" makes my render fail...

I'm being thwarted by this error at the moment. I only started experiencing it when I updated not long ago to Nvidia driver R390 U9 (392.37) (February 22, 2019) for Quadro K620 graphics card and updated to CC 2020.

I am now on nVidia driver R450 U1 (451.48) (Release Date: 2020.6.24) and getting CUDA errors on the timeline too.

Hi guys, I literally tried everything... and the only thing that worked was removing the adjustment layer, exporting it, and then importing this exported file, and then doing the intial adjustment of lumetri color on it....

Its still stupid PP2020 has to be buggy like this... what are we paying for?

Disabled Color effects when rendering a .png image sequence to a h.264 file fixed this issue. Workaround will be to do color grading on rendered h.264 along with normal editing.

This GPU render Error -1609629695 issue has not been resolved in Adobe Premiere Pro 2020. This occurs when using the Metal renderer, and in my case when using the Warp Stabilizer effect.

However, switching my project renderer from Metal to Software Only before export allowed the export to finish properly in my case.

I am a "many editor" and it is a bane, yes. You have settled on a work-around that is actually useful and not some random shot-in-dark solution that does not address the rendering bug that is a part of PP.

Frankly, I'm a little upset that I didn't think about it.

By rendering your previews in the same output format, then using "smart render," you can make sure all is rendered properly BEFORE output, and not fret that the output encoding will implode.

The way I'm applying plug-ins and opacity to my work, it's a 95% chance that the encoding fails on output, and I don't normally have the time to do the "software" encoding thing.

Got the same error recently, didn't happen before

@Amédée
I know this is no help to you, but I actually haven't encountered this bug in over a year. so I think they've been making progress in fixing it.

We're in April 2019 and this ******* error is still there. No clue, no fix, only ****!!! ******* Adobe, Jesus Christ...!!!