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

Explorer ,
Oct 31, 2020 Oct 31, 2020

Copy link to clipboard

Copied

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

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

TOPICS
Export or render, Hardware or GPU

Views

39.0K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
replies 189 Replies 189
Explorer ,
Nov 26, 2020 Nov 26, 2020

Copy link to clipboard

Copied

Same Problem here when using Media Encoder

Using PP it seems to work randomly

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 28, 2020 Nov 28, 2020

Copy link to clipboard

Copied

Using Software encoding works.

 

here comes my "last Log"

Log file created: 28.11.2020 09:51:04
---------------------------------------
Ticks = 610 <13248> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 610 <13248> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 610 <13248> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 641 <13248> <Wasapi initialization> <5> Time = 0.0364078second
Ticks = 875 <2364> <AnywhereLocalClient> <5> Local Hub HTTP port retrieved, port: 50454
Ticks = 1157 <13248> <DS> <5> GPUSniffer launching with test mask 62
Ticks = 1938 <13248> <DS> <5> GPU Sniffer Output:
GPUSniffer testing 62
Initializing GPU Tech:
Try CUDA: 1
Try OpenCL: 1
Try Metal: 0
Try Vulkan: 0
KernelLoadAction: 0
UseOpenGLContext: 0000000000000000
UseDeviceContext: 0000000000000000
UseD3D11Context: 0000000000000000
CUDA system device count: 1
Found CUDA device index: 0 Name: GeForce GTX 1660
No capability restrictions detected - adding device to list
OpenCL system device count: 1
Found OpenCL device Name: GeForce GTX 1660 supportsSSG: 0
Skipping nVidia OpenCL device
Finished gpu initialization in 0 ms

--- OpenGL Info ---
Vendor: NVIDIA Corporation
Renderer: GeForce GTX 1660/PCIe/SSE2
OpenGL Version: 2.1.2 NVIDIA 457.30 27.21.14.5730
GLSL Version: 1.20 NVIDIA via Cg compiler
Monitors: 2
Monitor 0 properties -
Size: (0, 0, 1920, 1200)
Max texture size: 32768
Supports non-power of two: 1
Shaders 444: 1
Shaders 422: 1
Shaders 420: 1
Vendor: NVIDIA Corporation
Renderer: GeForce GTX 1660/PCIe/SSE2
OpenGL Version: 2.1.2 NVIDIA 457.30 27.21.14.5730
GLSL Version: 1.20 NVIDIA via Cg compiler
Monitors: 2
Monitor 1 properties -
Size: (-1920, 120, 1920, 1080)
Max texture size: 32768
Supports non-power of two: 1
Shaders 444: 1
Shaders 422: 1
Shaders 420: 1


--- GPU Computation Info ---
Found 1 devices supporting GPU computation.
CUDA Device 0 -
Name: GeForce GTX 1660
Vendor: NVIDIA
Integrated: 0
Capability: 7.5
Driver: 11.1
Total Video Memory: 6144MB
Ticks = 1938 <13248> <DS> <5> GPU Sniffer result: 30
Ticks = 2110 <13248> <GPUFoundation.DirectX> <5> DXGIFactory not found. Debug layer on
Ticks = 3250 <13248> <EACL.HostedLogin> <5> Team Projects login completed successfully, localServerAddress: "http://127.0.0.1:50454", remoteServerAddress: "https://cc-api-teamprojects.adobe.io:443", remoteServerConnected: true, remoteServerAuthorized: true
Ticks = 3313 <13248> <AMEApp> <0> Time taken to load MediaCore plugins: 1065.35 milliseconds.
Ticks = 4422 <13248> <AMEApp> <1> Entering RunEventLoop
Ticks = 4594 <920> <LoadProject> <0> 0.0898622s
Ticks = 4610 <920> <IR.InitIpp> <5> ippInit warning: ippStsNonIntelCpu: The target CPU is not Genuine Intel
Ticks = 6625 <13248> <EACL.HostedLogin> <5> Sending new IMS access token to LocalHub, tokenLength: 1146, truncatedToken: "eyJ4NXUiOiJpbXNfbmExLWtleS0xLm", differentToken: true
Ticks = 7110 <920> <EACL.HostedLogin> <5> Finished sending new access token to LocalHub, result: 0, requestID: "dvanet-d29801bf-a5e0-4dba-b049-7d7a2aaab661-f41b3c7e-db5e-4dd4-a3e8-7e2be2f74866-10", duration: 0.13500000000000001, httpStatusCode: 200, httpLibCode: 0, payload: "[{\"authorized\":true,\"connected\":true,\"forbidden\":{\"error_code\":\"\",\"message\":\"\"},\"lastAuthorizationStatusCode\":200,\"serverURL\":\"https://cc-api-teamprojects.adobe.io:443\",\"serverVersion\":\"\"}]"
Ticks = 15516 <3276> <ExporterMPEG4> <5> Looking for H/W codecs for H.264
Ticks = 15657 <3276> <EncoderStateH264> <5> Found H/W codec for H.264 - nVidia H.264 Codec
Ticks = 38828 <3276> <EncoderStateH264> <1> Encoded using nVidia H.264 Codec (H/W codec) for H.264
Ticks = 38828 <3276> <NvidiaCodec> <5> Encoded 295 Frames Encode FPS = 51.1464 Encode Size 3840 x 2158
Ticks = 38922 <3276> <EncoderStateH264> <1> Time taken for; video =3095 audio=34 mux=0
Ticks = 38922 <3276> <ExporterHost::BeginThreadExport> <5> Exporter finished in : 23.416 seconds. Result code: 3 Destination:C:\Users\Weber\Desktop\REMOVEME\4K 16-9 3840-2160 60fps GoPro Hero 7_2.mp4
Ticks = 38938 <13248> <MF::ErrorReport> <1> Summary:
Ticks = 38938 <13248> <MF::ErrorReport> <1> * errorTitle=Fehler beim Export (Export Error)
Ticks = 38938 <13248> <MF::ErrorReport> <1> * errorDescription=Fehler beim Abschließen des Renderns. (Error completing render.)
Ticks = 38938 <13248> <MF::ErrorReport> <1> * componentName=H.264
Ticks = 38938 <13248> <MF::ErrorReport> <1> * componentSelector=9
Ticks = 38938 <13248> <MF::ErrorReport> <1> * componentType=$$$/ErrorReport/ComponentTypeExporter=Exporter
Ticks = 38938 <13248> <MF::ErrorReport> <1> * errorCode=3
Ticks = 38938 <13248> <MF::ErrorReport> <1> * exporter=H.264
Ticks = 38938 <13248> <MF::ErrorReport> <1> * moduleFilePath=PrExporterModule2.h
Ticks = 38938 <13248> <MF::ErrorReport> <1> * moduleFunction=PrExporterModuleBase::DoExport
Ticks = 38938 <13248> <MF::ErrorReport> <1> * moduleLine=1191
Ticks = 38938 <13248> <MF::ErrorReport> <1> * outputFilePath=4K 16-9 3840-2160 60fps GoPro Hero 7_2.mp4
Ticks = 38938 <13248> <MF::ErrorReport> <1> * outputFileType=H264
Ticks = 38938 <13248> <MF::ErrorReport> <1> * timecode=00:00:04:57
Ticks = 64219 <13248> <AMEApp> <1> Exited RunEventLoop
Ticks = 64547 <13248> <VulcanClientImpl> <4> All clients did not unregister at shutdown, messageClients: 0, notificationClients: 0, responseClients: 1, expression: "!sMessageSubscriptionClientsMap.empty() || !sNotificationSubscriptionClientsMap.empty() || !sResponseMap.empty()"
----------------------------------------
Log file closed: 28.11.2020 09:52:08

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 29, 2020 Nov 29, 2020

Copy link to clipboard

Copied

Things i tried in the meantime

1 - Installed 14.8 Beta Versions without having any success - Same Problem same errors

2 - installed older NVIDIA Driver - No success

3 - deeper investigations

  - Failure always betwin clips

  - changing dissolve from soft to Film sometimes helped - sometimes not

  - error nevver appeared so far in the middle of a clip, aklways between clips

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 24, 2021 Mar 24, 2021

Copy link to clipboard

Copied

Yeah I normally try that among many other different things, sometimes it will work sometimes it won't.

It is so hit and miss, the whole export component of the software makes it near on unusable.

 

Adobe, I have no issue with any of the other functionality of Premiere Pro, I think it is excellent.. but if I've just spent a week on a sequence and then have to spend another 2 weeks trying to export it then what am I bothering for??

 

Maybe you guys need to redesign the whole export functionality, if I can pre render an entire sequence (which I do prior to any export) without issue and it play in preview from start to finish with no issue, then please explain to me why the fudge it has such an issue exporting??? I've even contemplated screen recording the preview because it's honestly better than trying multiple times a day for several

weeks just to have half a chance at a successful export. It's absolutely not good enough, and enough is enough!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 26, 2020 Nov 26, 2020

Copy link to clipboard

Copied

Schermafbeelding 2020-11-26 123528.png

 

 

 

 

 

 

 

 

 

 

 

 

 

I have the same problem over and over again. Yesterday evening I didn't had this problem (I think I have downloaded PP newer version just after that, I doubt.) I am not a computer expert, can somebody explain me this on a easy level? 😉

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 09, 2021 Feb 09, 2021

Copy link to clipboard

Copied

It's likely that this is a workflow issue. It helped me to understand media file types and their compatibilty fwithin a sequence AND having 3 seperate drives. Often I can go in to my CACHE drive and delete all cache files and folders because one is likely corrupt or something. This fixes the issue most often. 

 

Good luck! Almost ave to be a software engineer/computer IT person on top of being an editor now days

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 09, 2021 Feb 09, 2021

Copy link to clipboard

Copied

It's not a workflow issue. I have 3 separate drives for the media, the project/scratch disk, and the export disk. All 3 are SSDs. You should not have to delete cache and it did not fix the issue for me. Downgrading to 14.4 and downgrading my NVIDIA driver resolved the issue. Same disk setup, no deleting of cache or any other stupid suggestions. Any success you're seeing from cache deletion or other trick is by chance. Every 1 in 10 exports would work for me on the latest Premiere+ME+NVIDIA driver regardless of what I changed. The timecode was different for every single failure. It's not one clip, it's not one sequence, it's not any particular setting or drive configuration.

 

This is not a workflow issue; this is 100% a critical driver and application incompatibility.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 28, 2020 Nov 28, 2020

Copy link to clipboard

Copied

Same problem (Selector: 9, Error code: 3) here on Win10 laptop, exporting to internal SSD. Footage sits on external HDD. The problem started after updating the system (Dell update, Win update) and updating Premiere and ME to v14.6 . I reverted to Premiere and ME v 14.5 but encoding with ME still fails.  

 

Screenshot 2020-11-28 162554.jpg

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 29, 2020 Nov 29, 2020

Copy link to clipboard

Copied

Hey everyone, I started having this exact issue 2 weeks ago, so I have to assume the basis for the issue is due to a program update or windows update.. (Selector: 9, Error code: 3)

 

I've tried many different solutions (changing file locations, export file location, changing to ssd instead of hard drive, saving sequence to new file, etc..). The only solution I've found is by removing ALL Lumetri color effects. I had them in an adjustment layer over multiple clips.

 

Once I removed all of the lumetri color effects, it encoded perfectly.

I have not changed any other settings or processes for my weekly videos in months. The only variable I found that allowed the video to fully export/encode is removing lumetri.

 

@adobe.com PLEASE fix this.. it's absolutely rediculous that the issue is so widespread and obviously linked to a program update (PP or ME) or even just lumetri color itself.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

Reverted ME and PR to 14.4 solved the issue, encoding works again.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 30, 2020 Nov 30, 2020

Copy link to clipboard

Copied

Unbenannt.JPG

 

I am having the same problem... updated PR and ME and sind then I can't even render in ME anymore just in premiere and then this happens... ADOBE pleade fix this!!!! Every bloody update there are issues!

1.JPG

Premiere: on NVME SSD C://

Cache: on NVME SSD D://

Project & Previews: on SSD E://

 

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 01, 2020 Dec 01, 2020

Copy link to clipboard

Copied

I am having just the same problem, tried everything in this thread. The only way I could get anything to export was to export my 4k footage in 1080p, which is a shame as I specifically upgraded my phone so I can vlog fully in 4k! Please help us adobe!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

To make a long story short. (see my posts above)

1. I reverted back to 14.4 (PP and ME) and everything worked as expected.

2. I openend a case with adobe, the support guy played 2 hours on my PC without coming to a result. On the end all my ME presets were lost.
3. reading this thread it seems it is a common problem. I wonder why no Adobe official has resonded yet. Do they seriously take care the problems in this forum?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 03, 2020 Dec 03, 2020

Copy link to clipboard

Copied

Reverting back to 14.4 (ME) worked for me too

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 27, 2021 Jan 27, 2021

Copy link to clipboard

Copied

i5-4460 8GB RTX2060

Hardware encoding used to work like charm. At some point yesterday started crashing EVERYTIME,
with "Selector: 9 Error code: 3", different timecode everytime, no relation to any particular object on timeline.

The following did NOT work:
- all source files in one folder,
- switching H.264/H.265, VBR/CBR, various bitrates and quality settings,
- changing output desination to same or different HD/SSD,

I began loosing hope. Rolled back ME to 14.4. PP stayed 14.8. Closed all background stuff.
Finally, it worked! Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 27, 2021 Jan 27, 2021

Copy link to clipboard

Copied

Thanks Anna, that's good to know. I have been running this solution since 31 October and have not had any problems at all. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

I moved my RAW media files to SSD too (along with Cache/DB/Previews etc to separate SSDS) and I've not had any problems since on PP 14.6 & ME 14.6

 

I did also, however, update my Nvidia driver to the latest November Studio update for my GTX 1070

 

Previously the workarounds I had for those still having issues are:

  • Export using Software only encoding.
  • or export a master big Apple ProRes 422 file then convert that file to H.264 or H.265 using media encoder.

 

Regards Gary

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

Hi Gary,
My System is completely SSD based with the latest Drivers. All files are distributed. I tried everything you did without success.
Software Only is not an option. Producing 2hours 4K video it takes more than a day to render on a 12 Core 4Ghz System.
For me only the fallback to 14.4 worked.
Are you working wtth 4K footage and Lumetri color grading?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

Hi, yes I use a mixture of HD and 4K and lumetri LUTs on an adjustment layer.

 

Try exporting to Apple ProRess (with all your 4K and Lumtri on) then convert the file to H.264/265 with ME (hardware encoding on) to see how long it takes overall.

 

Regards Gary

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

there seems to be an issue when using Media Encoder, by dragging and dropping sequences directly from PR zu ME. I can export in Premiere with not tooo many issues, usually I have to restart PR (this software is sooo bad!!!) and then try a few times. But dropping into ME an clicking on Preset to make adjustments it just won't load 100% and never open the window. Now I tried exporting in PR and saying "add to renderque" it opens ME and then it actually works. I can open the preset and even click on export and it will start rendering process... lets see how far it gets or if it crashes too...

I updated my NVIDIA drivers, no change...

Safest for me export in PR directly, sucks because you can't work in PR whilst exporting... but that's my workaround. @Adobe PLEASE FIX THIS ISSUE! I have had this problems sooo many times in the past... how can the most important step not work?!?!?!? Sometimes I wonder if they even really use their software!!!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 03, 2020 Dec 03, 2020

Copy link to clipboard

Copied

I am having exactly the same problem.  I'm running a brand new Puget Systems machine with an i7-10700K, RTX 3080, and Samsung 970 EVO Plus NVME SSDs.  Source clips are H.264 from GoPro Hero 5's and Sony a7iii in muticam timelines.

 

Initially, nearly every encode was failing.  After updating to the latest Studio Ready Nvidia driver and the latest Premiere and Adobe Media Encoder, it only fails occasionally.  Usually, the first encode fails, and I can reset the item in Adobe Media Encoder and press start again, and it works.

 

I just had one fail, reset it and it succeeded.  I then duplicated ten copies and started them, and it's almost done with number 7 with no errors.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 03, 2020 Dec 03, 2020

Copy link to clipboard

Copied

Almost forgot:  I'm using the YouTube 1080p default preset for export.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 03, 2020 Dec 03, 2020

Copy link to clipboard

Copied

And...I'm running Lumetri to color grade everything.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 06, 2020 Dec 06, 2020

Copy link to clipboard

Copied

I'm having the exact same issue. Hope it's just a bug they can fix in the next update cause it's really causing me problems as I use this program for my work  Tried everything in this thread with no luck. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

I am getting the same issue with a similar error message, tried rendering in ME and PP and get same results.

Im running 14.6 ME and PP

 

I was running stable studio drivers from nvidia v456 I have now upgraded to latest driver 457 gamers version just in case, this has not resolved the issue. 

I have made several videos over the last month and this is the first time this has happened so I can assume it is to do with latest version 14.6

I am running a gtx 1070 8gb GPU

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines