Skip to main content
V
verticalcreative
Participant
June 24, 2016
Answered

Premiere Pro CC "Unable to Produce Frame"

  • June 24, 2016
  • 37 replies
  • 240816 views

Hey all, looking for some help for a time sensitive project.

I am trying to export a video project and every time I try and export it, Media Encoder fails and gives me the following information:

"Export Error

Error compiling movie.

Accelerated Renderer Error

Unable to produce frame."

I am dealing with about 22 minutes of footage, almost all of which is 4K within a 1080 project file, with the 4K scaled to different project files. Attempting to export to H.264. Working off of a external hardrive running USB 3.0. Beyond that, I'm not sure what information what may be relevant, so forgive me if I'm leaving out any important details.

Thanks in advance for any advice!

    Correct answer Michał Naplocha

    i've updated my graphic card drivers (Studio Driver for NVIDIA, not the Game Ready one) and it seems like the problem has been solved

    37 replies

    Show previous replies
    olesb17411869
    olesb17411869
    Participating Frequently
    October 21, 2016

    Got the same problem with NVidia Quadro M4000.

    Solution was to change Film Dissolve to Cross Dissolve in 2-3 clips (Clips were really short (Several seconds) and rendered).

    Another solution was to use original (not rendered) clips for Export.

    But it is still annoying.

      Moxtelling
      Moxtelling
      Inspiring
      November 4, 2016

      Has the latest 2017 update solved any of these issues? Mine came back after updating, so be carefull...

      Mine was initially solved by going back to an older driver. But the latest 2017 update does demand latest driver...so I did install latest driver and crossed my fingers, and hoped Adobe had solved this old but very irritatiing issue, but no - the issue came back. Error Compiling, can not redner frames etc....

      What is the oldest driver the new 2017 update wanna play with? The 354 is not enough it seems....

        A
        Anonymous
        November 10, 2016

        Unfortunatelly 2017 update did not solved this issue neither. Been struggling with this error for few days, trying different drivers rendering without CUDA (takes ages! don't have that much time). My system specs are: Dual Xeon with Quadro 4000 (2GB Vram) and 48 GB system memory, latest version of Adobe CC 2017. Not an actual solution, but this is what worked for me so far:

        • Downloaded 372.95 version driver (New Feature Driver (QNF), not the newer one (v375) Optimal Driver For Enterprise (ODE) as this one gave me nothing just errors.
        • Unchecked 3D vision drivers at install.
        • Disabled all Windows 10 x64 animations, aero effects and even icon/mouse shadows.
        • Set Premiere preferences to optimize rendering for Memory.
        • Added the sequence to AME queue and SHUT OFF premiere, to save some GPU ram. Sucessfully rendered 4k sequence via Media Encoder (CUDA - on, Maximum render Quality - off).

        To conclude - never had these issues before 2015.3 Premiere update. Somehow, the newer versions pushes GPU's to 100% and forces it to crash. Upgrading my GPU with more Vram next week, as this issue already wasted too much time.

        Viktor sloth
        Viktor sloth
        Known Participant
        October 16, 2016

        struggling with this as well...

        Only option is to render out without Maximum Render Quality, Maximum Depth and disable CUDA.

        I'm on a GTX970Ti with 4gb ram.

        Honestly I am so sick and tired of this. How hard can it be...
        Why dosn't Adobe give hardware suggestion for hardware that REALLY works, and then make sure that it REALLY works after each update?

        At my company we have 15 different builds, all getting error after error after error and weird bugs all over the line.
        Soon tears will come of out my eyes of desperation, honestly haha

          E
          excited_Genie16B8
          Legend
          October 16, 2016


          Why dosn't Adobe give hardware suggestion for hardware that REALLY works, and then make sure that it REALLY works after each update?

          Too many cards, not enough staff.

          williamg09071959
          williamg09071959
          Participant
          October 3, 2016

          I am on a quite recent iMac and I can't export anything. This is crazy. Tried many of the workarounds above and have got nowhere.

          Need a solution fast.

            E
            excited_Genie16B8
            Legend
            October 3, 2016

            The only solution I've found is to turn off CUDA when that error crops up.

            Drakester347
            Drakester347
            Participant
            September 17, 2016

            Just starting having this issues with a Pascal Titan X.

              avfreedman
              avfreedman
              Participant
              September 5, 2016

              I'm having the same error with my GTX 970 4GB (or 3GB if you know about that whole fiasco). I realize it's not on the list of supported GPUs but it's always worked fine on CUDA before 2015.3. Just wanted to add this data point info to this thread.

              I was able to export this video (Kristen + Rich: "An anchor, a reporter, and a thousand miles of love." on Vimeo ) last night on Software Only with multiple layers, scaling (4K-1080p), Lumetri, warp stab, Neat Video, etc. A six-minute video took three hours on my i7-5820k Overclocked to 4.0Ghz. Three hours of me crying myself to sleep without CUDA haha.

              Hope magic happens for 2015.4!

              smithingham
              smithingham
              Participant
              August 24, 2016

              I am having this problem on an nvidia quadro M6000. Hugely problematic. is there a fix at all? other than transcoding my entire project?

              B
              bclarkified
              Participating Frequently
              August 9, 2016

              This is indeed still a huge problem.  It has various causes, some say it's particular to a file...someone said it is namely mxf's, but in my case it was a proRes file.  There are various remedies I have run across to, all are hysterically round a bout.  BUT I did find if you re-cut in Final Cut X, it works like a charm.

              J
              J_roldan
              Participant
              August 3, 2016

              I too had this issue. It turned out to be an issue with specific files within the project. I used VLC to convert them to essentially the same files and replaced them within the project. This enabled me to export the project successfully. It really didn't solve the problem but was a good work around to get my client his project.

              Jeff

              timw37088702
              timw37088702
              Participant
              July 29, 2016

              For what it's worth, we have two near identical custom rigs, only difference is the gpu.  The rig with the gtx 980 is unable to export anything at all with max quality enabled in export window, no matter what.  Tried every possible solution I can imagine, no luck.  On the other hand the system with the titan x is handling and exporting as it was in 2015.2.  Had nothing but problems after the update with the 980 rig, and it shouldn't be with 4gb vram, no?

              E
              excited_Genie16B8
              Legend
              July 29, 2016

              No, it definitely shouldn't be.  That's why I think everyone getting this error should file a separate bug report for every instance of this error.  Flood the Adobe database with this bug report so that it gets fixed ASAP, because this one really can be a paycheck killer.

              E
              excited_Genie16B8
              Legend
              July 26, 2016

              I just filed a total of 26 bug reports on this issue, the number of times my export has failed with this error.  I know it's a bit of a pain, but I would encourage everyone with this error to do the same.  My thinking is that if Adobe sees just how frequently the error occurs, it will gain importance for an immediate fix.

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