Hardware decoding not working - AMD Ryzen 2600

[Mesut Or]

Hello everyone,

I was using the same configuration last 2 years. Same hardware same video footage same cameras. But now somehow gpu acceleration while playback not working. Usually my gpu maxes out %100 but now my CPU maxes out and Gpu encoding is not in use. Is something changed or is this a bug?

My project is unusable now 

Project:  4 camera multicam 

Footage Xavc s 1080p50 50/Mbits 

Camera Sony Nx200

Windows 11 22h2

Premiere pro 23.0.0 build 63

Amd ryzen 2600

Gtx 1070

16 GB 3200 mhz ram

1 TB NVME ssd (970 evo plus)

i know my pc is old but with that gpu decoding i was handling good 

Note: I am not talking about gpu encoding. Its works fine but gpu Decoding doesnt work.

[Kevin-Monahan]

Hi Mesut,

Thanks for the info. I formatted the info for you: 

• Issue - Hardware decoding is not working in a Multicam project (with four video streams). 
• Adobe Premiere Pro version number: Premiere Pro 23.0
• Operating system - Windows 11 22h2
• System Info: CPU, GPU, RAM, HD:

  • AMD Ryzen 2600

  • GTX 1070

  • 16 GB 3200 MHz ram

  • 1 TB NVME SSD (970 Evo plus)

• Footage: XAVC S 1080p50 50/Mbits 
• Steps to reproduce -
  • Load the footage.
  • See if GPU is decoding the footage.
• Expected result: 
  • The GPU is decoding the footage. 
  • Usually, my GPU maxes out at 100%, but now my CPU maxes out, and the GPU encoding is not in use. 
• Actual result: The GPU is not decoding the footage.

[Fergus H]

Mesut, 

Would you please share a sample video file with us? 

Thanks,

Fergus

[Mesut Or]

Hello,

Thank you for your answer. I tested the newest beta version and the problem still occurs. I also tested the previous version 22.5 and the problem still continued but it was working before. So the problem could be Win11 22h2 update or Nvdia driver update 

Here is some sample footage. Windows 11 media player uses GPU for decoding but premiere pro uses only CPU

https://drive.google.com/file/d/1jrAzWC1luee4IHlOgkyJQFCSTeL12Kik/view?usp=sharing

I appreciate if you can try and reproduce the issue 

Thank you 

Mesut

[Fergus H]

Hi Mesut, 

Thanks for sending me the file. I was not able to duplicate the problem: this file did playback using the GPU on my computer. What has changed since this was working for you? 

Regards,

Fergus

[Mesut Or]

Sorry for the late reply. I was trying to find and solve problems on my end. But unfortunately I was not successful. The last things changed on my computer are Win 11 22h2 update and new Bios update.
On my other laptop with win 11 22h2, Gpu decoding is working (Intel XE Graphics). I also downgraded the bios to the old version, but it's still not resolved.
I tried both nvdia studio and gaming drivers, the result did not change.

Somehow on my computer, premiere pro is not communicating with the nvdia drivers, but I can't find the reason. If there is a test you want me to do, I can do it, and I'm open to any suggestions for a solution.

Thank You

[Johan5FB9]

Decoding recently stop working for me too. It worked fine before. I open the same project that worked before. It's h.264 4:2:0. Color grading seems to be gpu accelerated though. I got the GeForce 1660 ti. Using the latest studio driver.

[Mesut Or]

Yesterday i tested another pc that has 12700K and 3060. Hardware decoding was working. Can it be problem with amd based pcs ? Do you have Amd or Intel cpu Johan 5fb9?

[Johan5FB9]

Thank you for writing. It´s Intel (Core i5-9400F). I just tryied to export as well: The encoding is around 4 % and decoding is 0 % (cpu 100%). During playback encoding and decoding is 0% (cpu 100%).

[RjL190365 · Accepted solution]

Here's the problem:

With newer Nvidia drivers, NVDEC is not working properly. And the PCs that have playback issues all have a common hardware issue: They absolutely require a discrete GPU just to even run anything at all. That includes all F-series Intel CPUs whose integrated UHD Graphics - which is required to be both present and enabled just to even enable its Quick Sync hardware decoder and encoder at all - has been permanently disabled by the chip manufacturer.

What happened with my lower playback scores in PugetBench for Premiere Pro in the H.264 tests when using a pre-516 driver version was that NVDEC literally stole much of the decoding power from the Intel Quick Sync, thereby preventing Quick Sync from doing its job properly. However, once again, the systems that have the issues do not have integrated Intel graphics at all, forcing everything onto the CPU while the NVDEC in post-516.xx drivers is crippled immensely.

[Johan5FB9]

Thank you for letting us know!

I downgraded to this driver and now it works like before.

NVIDIA Studio Driver - WHQL

Driver Version: 516.94 - Release Date: 2022 August 9

So if I understand what you are writing correctly, Nvidia's new drivers are better than before for computera with both Intel Quick sync and a Nvidia card? But accelerated video editing pretty much stopped working for computers with dGPU only? If that would be the case for all non Quick Sync computers out there the update is pretty bad, isn't it? Can it be fixed in a future update?

[Johan5FB9]

Mesut Or,

Ah, it was working on that setup. So it might not be a problem for alla Intel K cpu:s then.

[Johan5FB9]

Ahh 12700K supports quick sync.

[Kevin-Monahan]

Hello @Mesut Or,

Thanks for the message. It’s been a long time since you filed this bug. Are you still having this issue? If so, let us know.

I'll move your post to the Discussions board while we await your information.

Thanks,


Kevin

[Mesut Or]

Hello @Kevin-Monahan ,

Thank you for your question, Yes its been a while. I tried the answer this thread couple of times then but i couldn't do it somehow. My Answers wasn't showing up. 

No I don't have this issue anymore. @RjL190365 gave the right answer.  And i upgraded my system to Intel i7 12700k and RTX 3070ti. Since then i havent got any issues. Last Year was pretty stable for multicam editing workflow. No Hardware decoding or playback start stop issues anymore for me.

Thanks,

Mesut

[Kevin-Monahan]

Thanks for reporting on that, @Mesut Or! I appreciate you, @RjL190365! You are always a real help to our community with hardware issues. I really value the input there, thank you!

Cheers,
Kevin