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

W

wysiwygot

Inspiring

I played with some settings and I don't no why the error disappeared , hopefully for ever

In AME settings I unselected "Import sequences native"

see screenshot

can anyone confirme this

M

Mahmut Ersin5EA5

Participant

Hello all, I also had the same problem and I solved it by changing the render settings from Hardware encoding to Software encoding. I saw a comment in another thread that simply tells that it is related to the hard disk. I was working on a 50 mins project which has a lot of linked after effects compositions and that was the main reason. But this method solved my problem.

W

wysiwygot

Inspiring

Hi
It may solve your problem but....
It is not a solution. Runtimes for rendering take much much longer than using HW coding.
As stated earlier this might not be acceptable for others and me

W

wysiwygot

Inspiring

Question to all having this Problem

1) Is the timecode pointing to the error exactly between 2 clips?
2) Is the timecode pointinh to the start of a transition shipped with PP?

Thanks

R

ronnyroe

Participating Frequently

I just had this error on a brand new computer.

It happens just between 2 raw cuts in the video, no effects or transitions applied.

This is making me desperate, I have a 4K video project at about 60 minutes that with hardware acceleration takes about 5 hours to render out, and my plan is to work on it during the days and let it render during the night, and next morning review and change accordingly.

All my files are local on fast Nvme SSD disks. I am using proxies for all the heavy 4K-files.

But without hardware encoding it will take more than 24 hours to export the project, and my work cycle will be totally destroyed!

Please, Adobe - fix this critical error ASAP!!

Hardware:

AMD 5900X 12-core CPU

GPU Asus TUF RTX 3080

Disks: 2 * Samsung Nvme 870 Evo 1 TB

RAM G.Skill 3600 NHz 32 GB

Software:

Win 10 H2002, 64-Bit
Nvidia: Version 460.89

R

ronnyroe

Participating Frequently

Short update:

I chatted online with Adobe support about this. The agent asked a lot of questions, but had really no suggestion. Got an email an hour later saying:
"Thank you for contacting Adobe Customer Care. Our conversation ended before we were able to reach a resolution. We are following up to let you know we left your case open. Please reply back to this email if you need more help."

I got the feeling that the agent and his/hers colleagues were unaware of this problem. I even gave the agent the link to this thread, but I don't think the Adobe "official" support takes this community-services very seriously.

Anyway , I tried to export this 1 hour 4K video without hardware acceleration and it actually didn't take that extraordinary much more time. I am guessing that a 12 Core CPU overclocked to 4700 MHz per core is good to have in situations like these 🙂

I recommend all customers experiencing this problem to report it to Adobe support, that is the only way that they will actually escalate this internally for their development team to investigate it, maybe in cooperation with the Nvidia people.

knowledgeable_Shimmer0D45

Known Participant

I've been in talks with Adobe Care on Twitter about this exact issue, and they seem quite reluctant about it.

All I got so far, is a few replies telling me to try different settings — all of which do not seem to work in the slightest. I report back to them, conveying my newfound frustration, but they just tell me try other settings, maybe even over the phone.

I get this is how troubleshooting works, but the initial problem remains. Even if we find a way that circumvents the error, Premiere and Media Encoder are still broken, at least from my point of view. An export that once reliable used to work, does not now. Sidestepping might alleviate some problems, but the software in and of itself is faulty.

Feeling how frustating this issue can be, and how Adobe doesn't seem to do anything to fix it (except for telling me to try other settings), I am throwing in an ultimatum. If this issue persists up until Q2 2021, I will be ending my subscription and formally request my money back for the months the problem worsened. I have requested the Adobe Care-team to refer me to any kind of account manager to talk options.

knowledgeable_Shimmer0D45

Known Participant

Short update:

Adobe Care keeps ignoring the request/questions about getting money back after paying for a broken product multiple months in a row, let alone giving an ETA on when this issue will be resolved. At any given chance, they will try to divert the conversation into more suggestions for settings (of which none had any result) and/or referring you to other tech people — although it's pretty clear no one over there has a solid work-around or definitive answer to this issue. I've declined speaking to a senior technician because of this, unless they can guarantee this phone call will annihilate the problem once and for all.

Yesterday I've missed another deadline because of this issue. Even software encoding didn't do the trick this time around, crashing multiple times. I've spent about 3-4 hours (rendering > crashing > cleaning caches > rebooting > rendering > crashing > et cetera) on a render that usually takes no more than 15 minutes. At this point, I just can not guarantee any clients that my work will be delivered in time.

At this point, all I want is for Adobe to just let us know what's going wrong, and what's done about it. Preferably with an ETA on when this shitstorm is over, or when they start compensating us for their flailing. The more they keep prancing around these questions/requests, the more I feel like I should just hop over to DaVinci and be done with this.

knowledgeable_Shimmer0D45

Known Participant

Shorter update:
Adobe asked for my customer ID, which I gave. They then postponed my subscription payment for the upcoming three months, and they acknowledged my frustration about me missing multiple deadlines.

It might sound petty (it probably is), but something like this does make me feel heard. I've told them that I would be happy to further help them fix this problem, should there be anything I could try out for them.

And yeah, I certainly hope they can get around to fully fixing this issue. It might be frustrating, but I'd rather stick with the entire Creative Cloud than figuring out alternatives for all the included software I need on a regular basis.

K

kai5D5E

Participant

I had the same problem with my GTX 1060 - I9 6800k.

In the secuence settings changed from CUDA to Software only, also in the media encoder. work fine.

knowledgeable_Shimmer0D45

Known Participant

So you're just cool with the fact that your GPU isn't utilized at all when rendering? That's a first.

With bigger files, switching from CUDA to software encoding can turn a few minute render into exporting multiple hours on end, as stated above.

It does sidestep this exact error, but the problem remains: Premiere and Media Encoder do not work as promised.

J

Justin-_-

Participant

I have very little to add other than a confirmation of what everyone else is saying. 4k, Appx 45mbps, hardware encoding, random drops. Infuriating. A 4 minute render on great hardware brough to its knees by this.

vepperent

Participant

I am getting the same error.. fails over and over at different parts of the timeline. C'mon adobe, get your house in order. We pay good money for a reliable program and software encoding is NOT a solution!

J

Justin-_-

Participant

I have very little to add other than a confirmation of what everyone else is saying. 4k, Appx 45mbps, hardware encoding, random drops. Infuriating. A 4 minute render on great hardware brough to its knees by this.

knowledgeable_Shimmer0D45

Known Participant

Been experiencing a lot of these errors as well for some time, but they seem to have been ramping up since the last two to three months.

It happens while encoding in Premiere, as well as Media Encoder. I've noticed no difference when trying other settings: it occurs on ~30Hz just as much as 60Hz, and downscaling 4K to 1080p doesn't seem to do anything in its favor either.

The only surefire way to get around it, is opting back to software encoding — but that just seems ridiculous. If you pay top dollar for a proper GPU and professional software, this should not be an issue to begin with.

Is there any way to get the last ~2 months of Creative Cloud refunded/discounted, or anything? If the product doesn't fully deliver (while it did previously), why should we continue to pay the full price?

J

Joe Vegna

Participant

Same thing here. I've tried everything.

Adobe support told me to only use the software render. But a 5min video is estimated to take 22 hours to render.

Ridiculous!

Get it together Adobe. We should not have to struggle with such a simple task as exporting.

E

ENunn

Participant

I've been having this same exact problem since before this thread was made. I've tried everything. It only happens when I render in 4k.

Downscaling is not a solution. Using software encoding is not a solution. Disabling effects is not a solution. This is ridiculous.

B

Brian5CC3

Participating Frequently

I just built a new system with updated Nvidia Drivers on my rtx 2070 and fresh install of Premiere and windows and very first export crashed with Selector 9 error 3.. I cant believe Adobe has not addressed this yet.

P

PhotoEditor45

Participant

Hello same error here. PP 14.7 (build 23)

Media encoder 14.7

No way to encode with hardware acceleration. Always the same erro code 3.

Is there a way to report a bugs ?