Skip to main content
解決に役立った回答 kev_mon

Hi,

Sorry to all those still experiencing this bug occurring to some editors. Try this: Choose Preferences > Media and disable any Hardware Decoding Options. Reboot the computer. Try exporting once more. Works? Let us know.

Thanks,
Kevin

返信数 18

Inspiring
November 5, 2024

This seems to have something to do with an h.264 file that has flaws. I have a file that I ran through Media Encoder in an attempt to make it work, but PP still generates an error when it hits this file on the timeline during a render. 

Windows 10 Enterprise 22H2 OS build 19045.5011

Dell Precision 3620 i7-7700 3.6 ghz, 64 gig RAM, GTX 1080 (8 gig)

PP 25.2.0 beta build 6 (and earlier builds)

 

I can upload the H.264 file if needed)

Participant
March 23, 2022

I had this error repeatedly but localized it to a specific timeline timeframe. I noticed that the clips that appeared in that timeframe had a differrent frame rate AND pixel aspect ratio. I had a weird 'HD anamorphic 1080' setting on the clips' pixel ratio where the Error Code would come up. Selecting the clip from the project clips preview bin (not assembly line), right-click on that clip...Modify/Interpret Footgage. Set the frame rate to what your project is, AND make sure the Pixel Aspect Ratio matches your project - usally the Square Pixels (1.0) should be good.  Though the frame rate is less problematic, it was the pixel aspcet ratio correction that finally did the trick, and no error code after that!

Participant
December 31, 2021

Well, I had the same issue, disabled hardware acceleration and still didn't work. 

For me, removing a text element from the specified part of the timeline solved the issue. I guess you should try something like that too 🙂

kev_mon解決!
Adobe Employee
April 29, 2021

Hi,

Sorry to all those still experiencing this bug occurring to some editors. Try this: Choose Preferences > Media and disable any Hardware Decoding Options. Reboot the computer. Try exporting once more. Works? Let us know.

Thanks,
Kevin

Participant
May 2, 2024

Thank you!

 

santiagov51046227
Participant
March 19, 2021

In my case, I had multiple FPS footage, and I solved it by exporting the original file into my needed format (size and fps), then replaced the original file in premiere and added back the effects and it worked great.

Participant
November 26, 2020

For someone who have adobe media encoder just add it to queue and problem solved

Kevin-Monahan
Community Manager
Community Manager
June 15, 2020

One Simple Troubleshooting Step For Those Hitting this Common Error

Don't even think about running either Chrome or Spotify while attempting to export. That reduces VRAM, which you often need while exporting. That is, unless you have a GPU with an absurd amount of VRAM - even so....quit these apps, reboot the computer, and then do your export.

 

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
KomfySach
Participant
August 4, 2020

Still doesn't resolve the issue, I don't understand why Adobe, who we pay to update these apps and fix bugs don't resolve the issue.

 

This issue was first raised in 2016, it's now 2020 - so you're saying that it took 4 years but the same issue persists.

 

What are we paying for then? The updates just add more features, but don't fix existing bugs.

 

All the work-arounds mentioned above are clearly based on trial and error and take up more time to "try and fix" what should be fixed by Adobe in the first-place.

 

I've done all these troubleshooting steps, let me know if there's anymore of if you can just resolve this issue with an update since the issue started 4 years ago - assuming Adobe needs more time to resolve the issue, perhaps another 4 years?

richardb29882897
Known Participant
August 4, 2020

Hi KomfySach.

One thing that worked for me (half way down this post) is something you probably don't want to do because it turned a normal 10hour export into a 29 hour export! I posted about it on this thread: https://community.adobe.com/t5/premiere-pro/premiere-pro-crashed-on-nearly-20-export-attempts-over-the-last-fortnight-sos-please/td-p/11298203?page=1

 

Basically, 14.3.1 isn't working for me so I rolled back through prior versions & I got the export to work in 14.0.1 but like I said, it took 29 hours.

 

Initially I:

1. Stopped Windows & Kaspersky (my antivirus) updates,

2. Uninstalled 14.3.1 & installed 14.0.1 after trying multiple prior versions, and

3. File/Project Settings/General - Renderer "Mercury Playback Engine Software Only"

 

Exporting with 14.0.1 resulted in an "Error compiling movie." so Google suggested the changes:

 

1. Edit/Preferences/Memory - Change "Optimize Rendering for" from Performance to Memory, and

2. Edit/Preferences/Memory - Reduce "RAM reserved for other Applications" as low as possible which for me was 3GB.

 

Task Manager showed CPU usage as half the normal levels which more than doubled the processing time but I couldn't export properly for a month so I'm relieved now it's done. I know this is a very unattractive solution but if nothing else works & you are under pressure from a customer you may like to try it. Before trying this I really would thoroughly try Kevin_Monaghan suggestions though.

 

I know the desperate feeling mate, so good luck.

 

My system is:

i7-8700K CPU @ 3.70GHz (12 CPUs), 32GB RAM, Windows, GTX 1060, OS & PP on 970 EVO 250GB, Scratch & footage on 970 EVO 1TB.

Participant
May 14, 2020

I had the same problem. I restarted the programme and ti was fixed.

Hope this helps.

perqocet
Participant
February 4, 2020

A fix that worked for me was if you look at what time the error is at (should say in the box that pops up with the error) and go to that time in the timeline. Click the clip that is there and press delete. Then hit enter or whatever your rendering button is. Then after its done rendering just ctrl+Z to undo the delete and press your render button again. Worked smoothly

Brooks H
Participant
July 29, 2020

Incredibly, this worked for me.

JennHiles
Participant
October 24, 2018

Just updated to CC 2019 and getting this error working on an older version project. If anyone else has this problem while trying to render, nesting the problematic areas worked for me.