Participating Frequently

Answered

Encoding Failed Component: H.264 of type Exporter Selector: 9 Error code: 3

Forum|Forum|5 years ago
October 31, 2020
79 replies
203351 views

Hi, I have an encoding failer (see log below) which when I repeat/reset status on the same sequence will happen/fail at different times during the same export with no changes to the project/setting etc?:

Basic setup; Windows 10, Premiere 14.5, ME 14.5 Geforce GTX 1070 with latest Oct 2020 studio driver

------------------------------------------------------------
- Encoding Time: 00:03:15
10/31/2020 02:56:00 PM : Encoding Failed
------------------------------------------------------------
Export Error
Error compiling movie.

Export Error

Error completing render.

Writing with exporter: H.264
Writing to file: \\?\D:\Premier Pro Exports\20201012-wed-gib-wedding-MA.mp4
Writing file type: H264
Around timecode: 00:12:40:14 - 00:12:40:15
Component: H.264 of type Exporter
Selector: 9
Error code: 3

------------------------------------------------------------
- Encoding Time: 00:03:28
10/31/2020 03:00:29 PM : Encoding Failed
------------------------------------------------------------
Export Error
Error compiling movie.

Export Error

Error completing render.

Writing with exporter: H.264
Writing to file: \\?\D:\Premier Pro Exports\20201012-wed-gib-wedding-MA.mp4
Writing file type: H264
Around timecode: 00:13:20:16 - 00:13:20:17
Component: H.264 of type Exporter
Selector: 9
Error code: 3

------------------------------------------------------------

Correct answer kazdave

Here is a fix

Change hardware Encoding to Software Encoding.

https://youtu.be/EJ9dClm7XZQ

Show previous replies

K

kai5D5E

Participant

I find another solution.

First, clean all the cache files, first from the preferences/media chade/delete all. Then in the scratch disk for premiere pro, i have all my files in documents/ premiere pro docs. Each one i diferent but make sure you have absolute control over the location of that folders.

Restart the computer, then in Media encoder/preferences de select the box "stop current item if decode errors are detected" and working with Cuda is fine again.

dennisg5831719

Participating Frequently

i had the same problem, after updating Premiere, After Effects, Photoshop and Media Encoder.

The current NVIDIA Drivers are realy buggy since weeks!

Switching to Studio Driver 457.30 will solve all the Problems mit Adobe products, but the driver is 12% slower then the newer one.

A

Anonymous

I downgraded my Premiere down to 14.4.0 and I can finally render my final video without errors or crashes in H.264. I did the same thing with the media encoder (14.4) with no luck though. Doens't crash anymore, but won't render any further then 1% either. I will update if something weird happens again.

J

JamesAllenUK

Participating Frequently

Wow so the suggestion by Majlo_PL above to disable the option:

"H264/HEVC hardware accelerated decoding (requires restart)" on the 'Media' preferences panel as totally resolved this issue!!

I can now render my 12 minute 4k project without a single error. GPU acceleration is still enabled for encoding so it completes very quickly. Just to add, this project has no Lumetri adjustments or anything other than basic clip assembly so far, though it was failing every time on render at different time indexes on each attempt.

As an aside, by doing this it's also fixed a weird glitch I had on a small part of a sequence where a previous clip 'bled' into a subsequent clip, even on render. With the above option disabled that part of the sequence is perfect now.

A

andys14629770

Known Participant

Is the problem with the new update fix?

J

JamesAllenUK

Participating Frequently

No this has beeen going on since October apparentely.

T

tac425

Participating Frequently

This has started happening to me. Just built a $2500 PC because I was sick of dealing with Mac. Computer is less than a week old. Super happy that Adobe is ignoring this issue.

blumooon

Inspiring

I feel you, it's not like we have to pay for this program or anything. (insert eye rolling emoti here)

Just bought a 3600 dollar rig, and not looking forward to see what Adobe has in store for me when I transfer all my programs over to it.

FYI. I have everything 100% upto date excet my encoder, that is still at 14.5. It works, and works very very well. Only takes me 15 minutes to render a 1080p 60fps 20 minute video. Not sure it will work for everyone, but it works for me.

C

Clough42

Participating Frequently

I just had yet another failure. The symptoms are the same as everyone else. I can confirm that it occurred at a cut, on the first frame of the new clip.

In my case, it's a multicam timeline, with Lumetri color grading applied on adjustment layers in nested sequences.

As usual, I just right-clicked on the failed entry in Media Encoder, reset it, and started again. Everything worked the second time through. It's definitely an intermittent issue.

J

Justin-_-

Participant

I've found some success in exporting to a master file (Like a ProRes 422 Quicktime file) and then transcoding that to my h265 file using AME. It still effectively doubles the time, but that's faster than software encoding and it's at least reliable (so far...)

R

Ralph_Edits

Participating Frequently

Same problem here, would love a comment or acknowledgement of the problem from adobe.

M

Majlo_PL

Participant

I I solved the problem partially. I turned off the hardware decode and it helped. The encoding of the mie still gos through the graphics card. I checked it out at several large weddings and it all went smoothly.

M

Majlo_PL

Participant

I solved the problem partially. I turned off the hardware decode and it helped. The encoding of the movie still goes through the graphics card. I checked it out at a couple of big weddings and rednering went smoothly. Premeire Pro version 14.7.0. Check with you and let me know if it helped.

vepperent

Participant

Wanted to check in and lambast Adobe for their poor customer support. This thread has been open since OCTOBER of 2020 and still no reply or fix from adobe.

M

Majlo_PL

Participant

HI, i have same problem and still no solution 😞

Lee Imae

Participant

Same problem here, with both H.264 and H.265 at totally random places/times. Other codecs perform just fine. Have tried all the suggestions in this thread, none of 'm work to solve the problem on my (high-end, fully up to date) system.

The workaround mentioned before - however - does work (but more than triples your total rendering time). As all of the other codecs work fine, just export using the one with the highest quality (like Apple ProRes) and import that export back to a new timeline in a new project and - then - export it using H.264 and H.265, which will then work fine as a mere transcoder.

The problem - thus - seems to lie somewhere in the newly upgraded hardware accelerated encoding part, as software encoding seems to work fine (though takes forever). Amazing such a mega-bug in such a mega-essential part of Premiere can go untackled (or even ignored) for so long by Adobe! I mean, it is not like we are nitpicking here, are we? The very least you'd expect from any video editor is that it is able to produce a ... video.

A

andys14629770

Known Participant

And no comment from Adobe ... bad bad bad !!!!

vepperent

Participant

Still having the same problem... still no solution.

SOFTWARE ENCODING IS NOT A SOLUTION.

G

Gary5F9EAuthor

Participating Frequently

Hi all,

Unfortunately, some of the recommendations to fix the problems didn't work, they did, however, improve the frequency I could encode but not 100% i.e I would just get this dreaded error less often.

My current workaround is PR at v14.7 (as I don't get any working editing errors, only during export non-queued) but downgraded ME to v14.4 (i.e the version that didn't give me this error which was introduced from v14.5 i.e the version with NVENC) and then queue from PR v14.7

Also, software encoding works on ME & PR 14.7 (obviously but not the solution) but also encoding a "master" Apple Pro-Res version and then encoding to H.264/5 with that master file with ME 14.7 (with hardware encoding on).

I will also follow up the pause of my monthly payment with and to Adobe as mentioned in this thread.

Regards

Gary

R

ronnyroe

Participating Frequently

I got an automatic reply from Adobe that they will close my case reported to them about this, "because they haven't heard anything more from me". Hard to say anythiong more than what I have already described to them about this.

One thing I would like to ask you in this thread though: I guess you are like me using the Nvidia Studio Driver, version 460.89. I noticed that Nvidia released version 461.09 of the "Game Ready Driver" on 7th January. Has anyone tried that, to see if the issue has been addressed? I know that the "Studio version" is to be used when not gaming, but maybe some of the fixes in the latest driver also addresses this bug?

I don't know if this is an Nvidia issue or if it is an Adobe issue. Since it only happens to me when I use hardware acceleration, I guess at least Nvidia is involved, right? Or does the issue also happen for those that uses AMD GPU? Or Mac users?

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded