Skip to main content
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

AWMAust40857378
Participant
June 11, 2025

This error will appear if a linked media issue occurs. If you're working with files in the cloud and perhaps the file location remains exactly the same, but the file is synced to the cloud for some reason is no longer available offline, whereas it was before, you may find this error appearing. One thing worth checking is your linked media.

Participant
January 28, 2024

Export Error
Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: QuickTime
Writing to file: G:\Business\Business Projects\Projects\Video Productions\My Channel\Benofi\Channel Videos\Accident VIDEO\Proxies\PXL_20231219_113645894_Proxy.mov
Around timecode: 00:00:00:14
Rendering at offset: 0.000 seconds
Component: QuickTime of type Exporter
Selector: 17
Error code: -1609629695

Participant
June 18, 2021

For me, there was a clip that had time mapping, was split, and had an effect. Nesting it first helped.

Participant
May 16, 2021

I had the same issue, was working with a 10 seconds clip, the text was scaled 2000px which scales down to 700px, font used is Crewniverse.

 

Everytime I rendered, the same issue was encountered. I restarted my PC changed the font (Couture), reduced the scale, then it rendered smoothly. But when I changed the font back to Crewniverse the same issue happened all over again.

 

PC specs :

AMD Ryzen 5 2500u

AMD Radeon Vega 8 1GB

8GB RAM

 

Not in a position to afford new tech, please help me with what steps to follow.

 

P.S. I read all answers in the thread, will follow all the guidelines mentioned but the failed render happened for too long and I'm a bit scared.

 

 

Participating Frequently
April 22, 2021

You also need to switch to software rendering in After Effects if you are using it too.

Participant
April 21, 2021

I found a very simple solution to your issue, which I also had. It does not involve changing settings or buying equipment and takes 2 seconds. Simply select-all (clips) and nest them together (Clip/Nest). I have found this solution also fixes other encoding isses by simply nesting certain clips together that have a problem. At least it worked for me. Good luck.

giliminimice
Participant
February 14, 2021

Here are a couple of possible solutions.

 

1. Try to pre-render you files in the timeline, that made the difference for me. The actual encoding is using the pre-rendered files if your sequence settings are right. You can patch the shortcut to render from in to out in the Keyboard shortcut panel. For long timeline, try rendering at least the part where you have a lot of effects (lumetri, scaling, ae linked comps, etc.) 

2. Make sure you close all others apps (Especially Aftereffects) when rendering. 

3. Render from Media Encoder, but close your premiere project before you start the cue

4. Render in a less compressive Codec than H264, DNx or proRes, than re-encode into H264. It is not ideal but you shouldn't lose to much quality in the end. 

 

Hope that makes it for you! 

Participating Frequently
January 1, 2021

Hi here is what helped me. My camera is producing .mov files (nikon Z50). I use to work with a default sequence setting which was DSLR (editing mode) which is using I-frame only MPEG. then I was exporting my project to h264. So it seem like input file was in one code, sequnce and preview set to another and exported to H264.

 

All I did is I went to Sequence/Sequence settings and changed:

 

Editing mode: CUSTOM

Preview file format: Quicktime

Codec: I personaly use Apple proress 422 Proxy OR proress 422

 

Doing this also gives me smooth renders and much faster exports (SMART RENDERING) if you plan on exporting in the same codec as we setup for the sequnce. PRORESS 422. (I couldnt use smart rendering before as it was going to error all the time)

 

If you are working in proress 422 and you want to export in h246 that will work from now on without any problem but you can not use smart rendering, it will only work as i mentioned before you work and export in the same codec. So it sorted all my problems. 
My current workflow is using apple prores 422, using smart rendering, exporting in 422 and then I use media encoder to convert to h264 (super fast) if needed.

Participant
January 2, 2021

Hey TomasK86,

Your solution resolved ALL of my rendering problems and now I export with no frustrations. Having the sequence and preview files in the same codec as your export makes sense. Less processing for the computer to do to avoid errors and confusion. Thank you so much for sharing this and I hope other people will see this, too. I just want you to know that you have just saved me A LOT of time and money as I started considering buying a 6800XT thinking that would solve my problem. Thank you, again!

Participating Frequently
January 2, 2021

You are very welcome. Since the beginning, I had a feeling that this is not that much fault of  Premiere Pro rather some settings. I hope more people will see 🙂

 

Happy editing.

Participant
August 20, 2020

I may have found the solution...
I tried all the fixes I found online: restarted Premiere Pro, restarted my PC, updated GPU drivers, updated/reinstalled Premiere Pro, cleared my cache, turned off CUDA, only CPU, exported project to the fastest drive (m.2 SSD), replaced heavily edited video clips with lower resolution files, even upgraded my PC to Ryzen 3800X, RTX 2070, which should work wonderfully because of the Nvidia graphics card, and 32GB 3000mhz RAM... still no luck. I work with 6K 8:1 BRAW footage, by the way. 

 

What fixed my problem is I created a new project, copied the whole timeline from the original project, and pasted it to the new project. From there, I exported and ta-da! I was able to export without any errors.

 

I hope this helps anyone who's having the same frustration as me. Please Adobe and Nvidia, fix this bug. You have loyal customers who pay a premium but still come across errors like this, no matter how much processing power their computers have.

Participant
January 2, 2021

EDIT: Please follow @TomasK86 's solution! Mine doesn't work all the time but his WORKS 100%.

Participant
August 4, 2020

In 2020 I'm still having the issue, it only started happening when I got the latest version of premiere.  I went back 3 versions and it worked with no problems.  Didn't do anything else to effects or settings.  Seems like a new version issue for me.