How can we improve Premiere Pro?

← Premiere Pro

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

43 votes
Sign in Sign in with: Adobe ID
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

TaranVH shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

21 comments

Sign in Sign in with: Adobe ID
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Martin Klöckener commented  ·   ·  Flag as inappropriate

    @Tyrone Steele
    Switching from Hardware GPU to Software render mode doesn't solve the problem. It's a workaround, but the software render is much slower than GPU render.

  • Tyrone Steele commented  ·   ·  Flag as inappropriate

    SOLVED!!!!
    Set your Media Export to Software, not Hardware GPU (within the Media Export dialogue)
    You may or may choose 1 pass or 2 passes. I've only tested single pass.
    And increase your Windows Paging file to at least 55GB -

    Restart the machine

    I was able to export an entire 6K 30 minute film.
    And PROBLEMS ARE SOLVED.

  • raul velazquez commented  ·   ·  Flag as inappropriate

    I had the same error, I solved it by changing the composition settings from HDTV 1080 25 to HDV 1080. It worked for me

  • Ben Jamin commented  ·   ·  Flag as inappropriate

    I’ve experience this issue for 5 years!!!!!!

    If it can be exported with software only the it should be able to be exported with CUDA!

  • Patrycja Marciniak commented  ·   ·  Flag as inappropriate

    I just spent few hours trying to render a simple, 3-minute sequence, with nothing but a few audio, video and jpg files. Deleted all the Lumetri color filters, still nothing. This is ridiculous.

  • Reto Troxler commented  ·   ·  Flag as inappropriate

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

  • Ben Spear commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

  • TaranVH commented  ·   ·  Flag as inappropriate

    @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  ·   ·  Flag as inappropriate

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

  • Glass Eye commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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!

← Previous 1

Premiere Pro: Stability

Categories

Feedback and Knowledge Base

(thinking…)