Skip to main content
NCrum2
NCrum2
Participating Frequently
June 25, 2019
Answered

Error Code: -1609629690 Accelerated Renderer Error

  • June 25, 2019
  • 18 replies
  • 148836 views

So I'm working on a big project with tons of 4k footage and every time I try to render or export I get this error (file name changed for client privacy):

"Export Error

Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264

Writing to file: \\?\C:\Users\User\Desktop\video file.mp4

Writing file type: H264

Around timecode: 00:00:44:09 - 00:00:45:01

Rendering at offset: 44.375 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629690"

I tried multiple solutions that others have found useful, namely exporting to a different location, turning off CUDA (see below), and editing things at the time codes that the errors are referenced to be in (changes nothing).
I've updated my NVIDIA graphics card drivers (both to game ready and studio ready drivers), updated premiere CC, all the normal things to look out for as far as I know.
Still get it. Also, when rendering without cuda it gives me blocks of weird checkered graphics throughout the video:
Never ever seen that before. But obviously eliminates that option.

As far as I can tell, removing my color grade with Lumetri is the only thing that lets it render and export as normal, but that's obviously an issue because this is a lot of v-log footage that I can't just export without a grade.

I would transcode all the footage, but this is a BIG session, so I'd be doing that with just so many files that I don't want to do that if I can help it, and I am already using proxies so I'd have to go through that again too.

I can export on my other system at home just fine (I'll post those specs too if need be) but I don't think it's as powerful CPU or GPU wise as this system, so I don't know what's happening.

System Specs:
Windows 10 Home 64-bit
Intel i7-4790K 4. GHz (8CPUs)
16 GB RAM
NVIDIA GeForce GTX 1080

Premiere CC 2019 (current version up to date)


Any help would be greatly appreciated. Thank you for your time.

    Correct answer SugnaShane

    Here's how I fixed this issue. Uncheck the boxes circled in red. I had no issues rendering a 4k sequence.

    18 replies

    Show previous replies
    S
    SugnaShaneCorrect answer
    Inspiring
    November 17, 2020

    Here's how I fixed this issue. Uncheck the boxes circled in red. I had no issues rendering a 4k sequence.

      Kevin-Monahan
      Community Manager
      Kevin-MonahanCommunity Manager
      Community Manager
      November 17, 2020

      Hi Shane,

      What kind of hardware are you running?

       

      Thanks,
      Kevin

      Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
      S
      SugnaShane
      Inspiring
      November 17, 2020

      Hey Kevin,  Surface Book 2 and the following

        eigenartfilmproduktion
        eigenartfilmproduktion
        Known Participant
        November 11, 2020

        Hi Kevin,

         

        thanks for your reply. This is hilarious and inaccetable. It worked flawless in earlier versions of premiere. Adobe needs to fix this - it happens even with a gtx 2070 super, which is not known for low performance. I think Adobe is pushing their users every time for new hardware - but they never do anything to make their software work with the existing hardware users have. It´s a huuuuge joke in my eyes. Don´t buy Adobe products, don´t use them and if so, send them your invoice for lost life and working hours!!!! PLEASE FIX THOSE INACCEPTABLE AND UNCONTROLLED ERRORS ONCE AND FOREVER, THIS IS NOT PROFESSIONAL!!!


          Kevin-Monahan
          Community Manager
          Kevin-MonahanCommunity Manager
          Community Manager
          November 17, 2020

          Eigenart,

          Have you tried updating your GPU drivers? Let me know.

           

          Thanks,
          Kevin

          Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
          W
          woijegoiaerg
          Participating Frequently
          December 24, 2020

          I'm experiencing the same issue and symptoms as the OP with a 1660 Ti and up to date drivers.  We're at a loss of what to do now.

            Kevin-Monahan
            Community Manager
            Kevin-MonahanCommunity Manager
            Community Manager
            June 9, 2020

            If this error is hitting you, I've found that it is triggered under these conditions:

            On PC, the error is often related to Hardware Encoding in Premiere Pro 14.5 and later. A bottleneck is created with certain settings enabled with certain hardware components. The following steps may help:

            1. Choose Preferences > Media
            2. Deselect GPU options for hardware decoding of H.264 and HEVC media.
              (see screenshot from user SugnaShane)
            3. Reboot the computer.



            If this is not the case than one of the following may be the root cause.

             

            1. A single GPU accelerated effect (usually Lumetri) applied to too many clips.
            2. Multiple GPU accelerated effects applied to too many clips.
            3. Frame size is 4K or above
            4. Sequence size is 1080 but has 4K clips and is therefore scaled (which triggers Mercury Playback Engine, and therefore, the GPU).
            5. Sequence Frame Rate is one frame rate, say, 23.98, and your clips are another "slightly different" frame rate, like 24, 24.01, 29.97, 30. This also taxes the GPU via the Mercury Playback Engine.
            6. Sequence is quite lengthy in duration.
            7. The sequence has a specific issue at the Timecode mentioned in the error dialog box, usually a GPU accelerated effect, and often a Lumetri Color effect.
            8. A combination of all these things.


            What is going on here?

            The installed GPU is not powerful enough for the task of "effects processing" (like Lumetri) and scaling, frame rates, etc. at the same time the file is to be encoded. 

             

            The only bullet proof solutions in my experience:

             

            • Buy a new GPU that has more VRAM: 
              • Buy a much more powerful GPU for your system (and make sure it is balanced with your other components) to suit your GPU hungry workflow.
            • Use smart rendering to incrmentally process your video for export.
              • Offload the GPU hungry tasks at ingest and or while rendering previews by using smart rendering.
                • Use the previews to harness a render which does not tax the GPU at all in a process called "smart rendering."
                • All you need to do is set your render previews to something like ProRes, with settings that align with your preview files.
                • Export as ProRes with "Using Previews" checked off and you will export without errors as the GPU has already done its work by rendering previews (which you are in control of).
                • You can also ingest as ProRes with LUTs attached, so certain grading can be baked in, offloading GPU cycles. If no other effects are added, you could use this file in the smart rendering workflow, as well.
            • Use "Software Only" mode for the Mercury Playback Engine in Project Settings, or remove GPU accelerated effects.
              • Choose File > Project Settings > General and set the renderer to Mercury Playback Engine Software Only.
            • Hopefully, you already know how to remove GPU acclerated effects. Click them in the Effect Controls panel and press Delete.

             

            Hope this helps some people struggling with this error.

             

            Thanks.
            Kevin

            Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
              S
              sheas51226003
              Participant
              April 13, 2020

              I had this problem, It was so late at night that I just said what the hell and rendered it with software only. the next day it hit me that one of my frames has two transitions overlapping eachother and thats why when i previously tried it would get stuck at that same time (46%) over and over. Hope this helps someone.

                J
                jerr.addison
                Participant
                June 8, 2020

                I got this error too. For me I was adding transitions between images in a 4K sequence. The images were 5184x3456 each and the transitions were scaling and rotating the images, as soon as I disabled the transition I was able to render it only in the project as a preview but still not able to export it using GPU rendering. It was a 3rd party transition and also I have a GTX 950 so my GPU is already pretty weak. 

                 

                Hope we can get this resolved, am I suppose to never scale 4K video ever again? I need to call adobe.

                 

                 

                Edit: This solution has worked for me so far

                Just nest the clips you wanna export on the timeline then open a new project (assuming you are using cc2019) drag or copy the nested sequence to the new project timeline

                  P
                  projekt2501
                  Participant
                  July 11, 2019

                  I am having the same issue. I have an 80 minute long documentary with mostly 4k footage. A lot of the footage has LUTs on it and some are being scaled. I understand that this would be very taxing on a GPU when using CUDA for rendering, however I am doing this on a new PC with an RTX 1080ti in it. Literally the (currently) fastest GPU you can get. If this GPU can't handle it, then what can? Also it's pretty disheartening to see that this issue was being complained about on this forum way back in PP 2015.

                  So now I'll try exporting with software-only rendering. Glad I spent all that money on that graphics card.

                    NCrum2
                    NCrum2Author
                    Participating Frequently
                    July 11, 2019

                    Yep. Good luck. I never found an answer and it’s depressing that no one from adobe directly has commented to try to help. I even tried going to reddit and posted about it too, where I got some potential solutions but nothing resolved it for me. I ended up just using my other computer.

                    Heres the link to the reddit post though in case something someone else said can help you:

                    https://www.reddit.com/r/premiere/comments/c7l9of/this_error_1609629690_is_eating_a_paycheck_and/?utm_source=share&utm_m…

                    P
                    projekt2501
                    Participant
                    July 12, 2019

                    Thanks. I'll check it out. Yeah I'm in hour 6 of exporting in 10 minute

                    chunks. Kill me.

                      NCrum2
                      NCrum2Author
                      Participating Frequently
                      July 2, 2019

                      I'm still dealing with this issue It's starting to eat my paycheck at this point

                        robertd43652856
                        robertd43652856
                        Known Participant
                        December 26, 2019

                         I know how u feel, I got the same issue 😞
                        feels bad

                          josephtothe
                          josephtothe
                          Participant
                          June 26, 2019

                          So I just successfully exported a project with this error message and here's what I had going on:

                          I realized that I had copy and pasted files into the sequence from another sequence. So what I did was delete those clips and reimport the the raw files from Finder. Usually, I place clips onto my timeline through Media Browser, but because I was working a little sloppy I just dragged and dropped the clips in from Finder. Not sure if any of this will be a solution, but that was mine.

                            NCrum2
                            NCrum2Author
                            Participating Frequently
                            July 2, 2019

                            I generally always import via drag and drop, log, and then start editing sequences. And again, I can export just fine on another computer in the same project. I did go through and replace anything that I might have copied and pasted from another sequence, and that hasn't helped.

                            Ann Bens
                            Community Expert
                            Ann BensCommunity Expert
                            Community Expert
                            June 25, 2019

                            Its a Lumetri issue.

                            Remove the effect and apply again.

                            Troubleshooting errors related to clips displayed as red and white checkerboard with old projects that use Lumetri effec…

                            NCrum2
                            NCrum2Author
                            Participating Frequently
                            June 25, 2019

                            Did just that and I wish I could say that it worked, but it didn't :/

                            Doing that and then trying again without CUDA gives this error code now too:

                            NCrum2
                            NCrum2Author
                            Participating Frequently
                            June 25, 2019

                            You mean you have gaps in your timeline?


                            I mean yeah, if I disable all the footage except the ones I've never had issues with it will say there are problems where no footage is even visible. Just to test if it's even the clips that are the problem.

                              Terms & ConditionsAccessibility statement
                              Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices