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

sethcshort

Participating Frequently

UPDATE With v15.0 - This is broken in 15.0

I had no problems until I was forced to uninstall and reinstall AfterEffects and Media Encoder due to an error in the connection between them. I installed the new version, 15.0, of Media Encoder (AKA 2021, along with a new AE 2021). This version IS having the problem described.

Per the tips here I installed the previous version. The only one available is 14.9. I also had to install the previous version of AfterEffects to match, so they're both "2020" versions.

This has fixed the issue.

Specs:

AMD Ryzen 9 3900X

96GB RAM

Nvidia RTX 3080 (seems unused during rendering)

Project files on HDD

Cache files on separate SSD

sethcshort

Participating Frequently

Note: I didn't uninstall the latest (15.0) version before installing 14.9. They're both currently installed. 14.9 works.

V

vcno1

Participant

I use PP for many years, first time ever to write something on this forum.

Please fix this, I am back to the old version of Media Encoder and error 3 is gone.

@

@mat.vds

Participant

Same problem.

Now I don't even try to render full video. I've chosen to chop it to 3 minute clips, and than I put together pre-rendered videos

@

@mat.vds

Participant

But now it doesn't work either

D

defaulterlbqq913byl

Participant

Hi guys ! I struggled with this issue all day and I finnally found a solution. It's not perfect but it works fine for me.
The issue occurs when I try to export my video in 4k. I have a nvidia GTX 1080 and a 12 thread CPU with 32Go of ram.

the solution was just to export the video in HEVC h.265 codec. You will not be able to open it with every video player but it works for youtube upload. You can also try to reimport the HVEC exported video in a new premiere pro project to try to re-export to h.264. It's not perfect solution but it saved me hours of investigations on my hardware.

The error seems to be caused by SSD that cannot handle a such writing stream or the GPU VRAM that is overloaded during process.

Sorry for my english i'm from france 🙂

TyreReviews

Participating Frequently

I've been having this issue on a relative new build with two internal NVE SSDs which are blazingly fast, so I don't think it's that 😞

Plus it also started happening on my laptop randomly too.

Zotac RTX3090 with latest NVIDIA Studio drivers.

48gb ram

5800x

Windows 10 pro

It started on my laptop months ago, this is aa joke now

A

andys14629770

Known Participant

Hello Adobe ... solution??? New version ??

R

Rammeh

Participant

For anyone still having this issue:

I had this exact problem. Rendering a 25 minute video, lots of cuts, lots of footage, lumatri, graphics, the lot... Randomly it would give me the Error code 3 failure during the rende, this was both direclty in Premier and Queued to the Meda Encoder.

I resolved it but going into the Creative Cloud app, uninstalled Media Encoder v14.9. Then under other versions I installed v14.4.

I then dragged the Premier project into the Media Encoder window, setup exactly as before and it rendered... and quickly too.

I hope this helps anyone that is experiencing this problem because I know first hand how annoying it is after spending a couple of days editing...

mynameJeff

Participant

I can confirm this. I usually don't write on forums but after spending hours losing hair, it would seem a simple fix to this propblem was to go back to Media Encoder 14.4. I've been suffering from this problem for quite some time now and I've only been able to render out smaller projects (1080p, 3-5 minute videos) vs my longer 4k projects since updating my Media Encoder a few months back. You're a life saver thanks. hope this workaround works for the rest of you guys, cheers!

5neaky C

Participating Frequently

Hello Adobe Video Editors,

Wanted to add my frustrations here to this thread in hopes that we all get noticed and get a new updates that fixes this H.264 exporter Selector:9 Error Code:3 conundrum.. Its angering me and wating my time, and money, seeing how we all bought rigs to use the hardware encoding to speed our workflow. Only fix I have found is to use the software rendering only-- which exports super slow.

Here is my rig - see if ther is anything similair here worth noting:

AMD Ryzen 9 3900 12 Core Processor | MOBO ASUS Tuf Gaming x570-plus

Windows 10 pro 19041.804 - on (C:) Samsung SSD NVMe 970 EVO 1 TB

Adobe Media Encoder 14.9 | Premiere Pro 14.9.0 Build (52)

Nvidia GeForce RTX 2070 SUPER Driver 461.40 Studio

32GB Ram

Exporting To: (D:) Samsung SSD NVMe 970 EVO 1 TB

Footage on: (I:) Seagate Expansion Desk SCSI Disk Device - 10TB

Project files and Scratch Files on : (I:) Seagate Expansion Desk SCSI Disk Device - 10TB

Footage description h.264 | 4K | 24fps | From Sony A7iii.

V

Viktor5EBF

Participant

Hi my Encoder did keep crashing when exporting. ( new version 14.9 )
I did Export directly from PP, it worked for me.

Hope it helps someone.

WilliamKBergman

Participant

I just had this issue too. but the error code: -1

I solved my issue by making the name of the exported file very short (since it was quite long before) - and then renaming it once the file had been exported.

W

wysiwygot

Inspiring

Due to this issue I reverted back to 14.4 late 2020.
Now I installed the latest PP and AME Versions (14.9) an I immediatly run into the Error again.
Selektor: 9
Fehlercode: 3
I was surprised, because after changing the following settings in AME I was able to export without any error. (see attached screenshot) "import sequences natively" = unchecked
After reverting the settings "import sequences natively = active" the error apperared again every time i tried to export.

After unselecting "import sequences natively" again i had no further Problems, the error was gone again

It appears however th export seems to be a little bit slower when using "import sequences natively = unchecked"

Nevertheless I am disappointed because no Adobe official has responded in this thread yet.

attached a screenshot of the settings I'm talking about.

And no there is no hardware problem neither is there a slow system. My system is an absolute highend machine.
Only M2 drives and 12Core 24Thread CPU+ NVidia
All running with the latest patches and drivers.

S

stephenb51767573

Participant

I have had this same issue over and over since updating (currently on 14.9) PP/ME

It is not the drive space, it is not some corrupt section of timeline, it is not hardware acceleration. The only thing that solves the problem has been to choose the generic "High Quality 1080 at 5.1"

dennisg5831719

Participating Frequently

Switching to NVIDIA Studio Driver 457.30 solved all the Problem for me. Current Version of ME,AE and PR running well, no more errors

G

Gary5F9EAuthor

Participating Frequently

OK thats interesting I might have to try that too, but at the moment I've only just updated to ME 14.8 and PR 14.8 plus the latest Jan 2021 Nvida Studio Driver plus the latest Intel graphics drivers too, so lets see what happens.

I will aslo try the switching on/off of Intel and Nvidia decode options to see what happends plus the ignore decode errorss option independently.

Regards Gary

K

KarlRock

Participating Frequently

Same error. Dell XPS 7590 (2019) with 32GB RAM GTX 1650 with Studio Drivers. Using Software Encoding only fixes it. But that's not feasible when I'm using effects.

M

MattiLad

Participant

SOLUTION

Hi everyone, just want to jump on to share my experience with this awful issue and my fix.

Rig:

i5-10400

GeForce GTX 1050

3x8GB LPX Coasair Vengeance

B460M Aorus Pro MoBo

TLDR;

-install fresh version of Windows 10

-get all your drivers updated

-make sure onboard graphics are enabled in BIOS

-make sure your onboard driver is actualy the correct version using this https://www.intel.co.uk/content/www/uk/en/support/intel-driver-support-assistant.html

Issues I was getting: error 3 sector 9, RAM at 99% and crashing, general crashes, freezes, computer restarts, BSODs, importer 37/38/39 errors while scrubbing, other general error codes and freezes.

All these problems are now fixed following my fix.

Little bit of background:

Upgraded rig as I was getting error 3 sector 9 along with other issues, assumed it was compatibility issues with my current i7 4770k so went and upgraded to an actual compatible CPU.

After upgrade I still had the same issues, after tons of research and troubleshooting I narrowed it down to the on board graphics driver still having the old driver installed so I completey uninstalled it and reinstalled and this also the unlocked the OpenCL export option on project settings, so naturally I thought great it's fixed. NOT. So I still had issues but what I had done did mate a massive difference, I was getting further in the export each time and the system was utilizing the CPU much more efficiently, but now instead of getting error codes it would either just crash, stop or more frequently the RAM would hit 99% and tank. So, stumped and having ventured all other paths, I dedicded to do one last test and that was to install a fresh version of windows, get all the drivers updated and try again. Wow, what can I say. I was overjoyed, I've not had any issues since, the only issue I've had is when I attempted to export on CUDA instead of OpenCL, which threw out the error 3 sector 9 again, but I just started it straight back up switched back to OpenCL and all was good once again, so although this was clearly a local issue, I highly reccommend trying to export a project on a fresh install of windows, if, like me, you are completely out of options. Also I noticed that adobe has a list of reccommended GPU's here https://helpx.adobe.com/uk/premiere-pro/system-requirements/2019.html and it seems that most people's rig doesn't include one from their list, not sure if this makes a difference but would help explain why they reccommend these GPUs in particular. So there, we have it.

Good luck everyone and I hope you can resolve your issues like I did. I've been on loads of adobe forums and all the advice from the technical 'experts' really are garbage and all the same old generic trash, clear media cache, disable this disable that. also FYI, I have H264 encoding and decoding enabled and checked the boxes of nvidia and intel, still works like a charm with no issues.

C

Clough42

Participating Frequently

I can confirm that disabling the Nvidia hardware decode in Preferences->Media seems to help. I disabled only the Nvidia decode and left the Intel hardware decode enabled. It's now decoding using the GPU in my i7-10700K and applying effects and encoding with the RTX 3080, and all appears well.

It's also pretty fast, at least for my use case. I just encoded a 20-minute 1080p30 piece (3-camera multi-cam edit with Lumetri color correction on every clip) in 2 minutes 17.

shanet95106976

Participant

Hey Everyone,

I was having this exact same issue as everyone else as of Jan 20, 2021 and it has been very frustrating. I got it to work (could be chance), but here is what I did:

I went to the exact frame where it said the export failed and analyzed it. Turns out there were two clips overlapping each other on different tracks (very common for my editing method). So I basically flattened the timeline right there where the issue was happening. I began an export in Premiere and changed the export to another drive. I was originally rendering from one m.2 internal drive to another m.2 internal drive. This time I tried rendering to the same m.2 that the project files are on.

While it was exporting I read someone said to try ME 14.5. So I installed 14.5 ME while the render was going. Never had to use Media Encoder, because the render completed with zero errors. I'm not sure which of these things, if any, fixed the issue. I'll keep ME 14.5 for now in case it happens again.

I was working with Sony A7SIII footage XVAC-HS 4K 120p (and 60P) 4:2:0 10 Bit as well as a little XAVCS-I 4K 60p at 600mbps. Final export was to a h.264 .mp4 file with a 1 VBR of 100mpbs and Hardware Accleration.

PC Specs:

Intel i7-8700k overclocked at 4.8ghz

32gb of 3200mhz Ripjaw RAM

Gigabyte RTX-2070 8GB GPU

1TB WD Black SN750 NVMe SSD (Contains Footage as well as Scratch/Cache)

500GB Samsung 970 EVO NVMe M.2 SSD (C: Drive with programs and project files)

Originally tried exporting to the C: Drive. When the export worked, I rendered to the 1TB m.2 that has the footage and scratch/Cache.

Hope this helps someone somehow meet a deadline, haha!

C

Clough42

Participating Frequently

This whole situation is very complicated, and there is some intermittent
factor affecting it. I have "fixed" it several times, only to have it
reappear later, so I think there are a lot of solutions being reported here
(including by me) that didn't really fix the problem; the problem just
didn't happen on the next export after the change.

The best way to prove that something actually fixed the issue is with an
A-B-A test:

1. Test scenario A and observe the failure.
2. Make your change, test scenario B and see it succeed.
3. Un-do your change and test scenario A again, and see it fail.

Because this is intermittent, I have never been able to un-do a "fix" and
see the failure again.

My hunch right now is that disabling the Nvidia hardware decode is the one
real fix right now, but I can't prove it. That could end up being
coincidence as well.

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