The infamous GPU render Error -1609629695
The bane of many an editor. I encounter this bug at least once a day. If this happens in the middle of a render, the entire thing fails. (Thank Adobe for smart rendering, at least!)
The best workaround I've been able to come up with, is to ALWAYS render timeline previews. I use cineform, and so the final, smart render, is very fast.
Here is a long forum thread about it. This bug has been a problem for many years: https://forums.adobe.com/thread/2171535
This is Unique ID 160 on my Premiere problems spreadsheet: https://docs.google.com/spreadsheets/d/1dVJb7kI_ZETLavrplfARgn9gL8HUpvkq6A0jCPxqA3w/edit#gid=1133868629


-
Reto Troxler commented
Same here, Lumetri generates that error in my projects!
also the "Offset Effect" makes my render fail... -
Ben Spear commented
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.
-
Primero Ang commented
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?
-
Rahbert Blake commented
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.
-
Pat Lee commented
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.
-
MHN commented
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.
-
Anonymous commented
Got the same error recently, didn't happen before
-
TaranVH commented
@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. -
Amédée Boulette commented
We're in April 2019 and this ******* error is still there. No clue, no fix, only ****!!! ******* Adobe, Jesus Christ...!!!
-
Glass Eye commented
April 2019 - this error has been plaguing me and several Adobe technicians on my 32gb MSI laptop gtx 980m, trying (and failing) to render the last bit of a motion graphics template from Envato
-
Tom Kaliamos commented
Issue fixed in latest version (Adobe Premiere Pro 2019 13.0.1).
I'm using a 5 year old iMac running macOS Sierra.
Renderer is set to (Metal).
Had this issue for a couple years and I'm now experiencing fast and reliable renders and exports. -
Tom Kaliamos commented
Issue fixed in latest version (Adobe Premiere Pro 2019 13.0.1).
I'm using a 5 year old iMac running macOS Sierra.
Renderer is set to (Metal).
Had this issue for a couple years and I'm now experiencing fast and reliable renders and exports. -
Bolik Seb commented
I have this issue with LUMETRI COLOR! Just put it at the bottom of the effects and will work!
It's worked for me al least! -
Fede commented
Also have that error code. I found it's GPU related, and in my case with Colorista IV plug-in. I have a preset for a transition effect with many Premiere's internal filters, and if i put Colorista at top it fails. If I put it at bottom, it works. Have also experienced same issue with Lumetri