Skip to main content
Participant
February 1, 2025
Answered

Hardware Encoding suddenly doesn't work

  • February 1, 2025
  • 2 replies
  • 546 views

Hey everybody,

 

Posted this in the Media Encoder-subforum as well, but no results.. This one is way more active, so I'll have a crack here..

 

I've been exporting video's in H.264 with NVENC Hardware Encoding for a couple years now, and it always has been working fine. But since today it suddenly doesn't work anymore. I've tried everything, I've updated my Nvidia-drivers to both the Game Ready and Studio Drivers, I've installed an earlier version of Premiere Pro and Media Encoder etc. etc. but nothing works.

 

My hardware is:

AMD Ryzen 9 5900X

Nvidia GeForce RTX 2080 Super

32GB DDR4 RAM

Samsung 990 Pro SSD

 

And my encoder settings are:

H.264

3840x2160p 25fps

Progressive

VBR 1-Pass (35 Mbps target with 45Mbps max)

 

Look, It's never been an issue, and now when I wanna export a video with the exact same settings it suddenly doesn't work anymore, and I've also tried on other videos which I previously rendered. Now they suddenly don't.

 

Even more curiously. For some reason, when I wanna export an After Effects-project with those settings in After Effects it does work, but than when I wanna use Media Encoder it suddenly doesn't. So the problem is limited to Premiere Pro & Media Encoder. And yes, I've tried every solution I've seen on the forum, and nothing works, so hopefully you guys have some new ideas.. A video which used to take 50 minutes to render, would now take over 15 hours.. I have also tried using BETA-versions, but again, to no avail..

 

UPDATE 1: I did try on MacBook with the exact same settings, but there 'Hardware Encoding' still works, but I don't want to use my MacBook for exporting.

 

UPDATE 2: Since then, a new Nvidia Studio-Driver has been released, which unfortunately doesn't help..

 

 

Correct answer Ann Bens

Reset preferences - Premiere Help

2 replies

Participant
February 1, 2025

Omg, thanks.. Something that actually worked.. When I reset the settings it also disbaled Plug-Ins for one time, and than it suddenly worked again.. Than be removing plug-in's one by one, I found out it was the .WebM-plugin that caused all of this.. Thank you so much ❤️

Ann Bens
Community Expert
Ann BensCommunity ExpertCorrect answer
Community Expert
February 1, 2025