Premiere Pro 25.1 - iGPU stopped decoding my footage

[AndrewTheGreat]

Ok, just updated to v 25.1 opened my projects in progress to find out that none of them uses my iGPU to decode.

Went on checking it with different formats that are decoded (h264 8-bit 4:2:0, h265 8-bit 4:2:0, h265 10-bit 4:2:0, h265 10-bit 4:2:2) by the iGPU - all of them show 0% load.

What is going on, guys? Why is it "new version - new bugs" thing every time? My CPU immediately started being loaded more, like by 60% all the time, even though my GPU does the decoding, whereas on the previous versions the average CPU load was 20-30% with the iGPU doing all the decoding job.

Yes, I tried reinstalling both Premiere Pro (as well as resetting its cache, preferences and plugins via the start+shift menu) and all the drivers. 

Steps to reproduce? Open a project or create one, import a knowingly decoded video, put it on your timeline, press Play. Watch the the Windows Task manager - Performance graphs.

i7 14700K, RTX 4080, 64 Gb ram, SSDs, Win 11 24h2

[MyerPj]

I was rendering a 1-hour multi-cam (edited with Proxies) but of course rendering with the full media, which was almost all h.264. 2 - 1080p cameras and one UHD 3840x2160, in a 1080p timeline. Had some nice numbers going:

12th Gen 12900k, RTX 4070, basically I'm only using the beta these days PP 25.4.0 b68

[Dmitriy36779285gov2]

Hi!
It's been a long time, but I still have to stay on version 25.0. Because all the versions released after that DON'T support hardware decoding of some video formats. I took screenshots while working on one video file.

 

Screenshots shows that in Premiere 25.0 this format (HEVC 10 bit 420) is successfully decoded by the integrated graphics card.

 

And there is NO DECODING in newer versions. There is also no hardware decoding on the RTX 5080, which claims to support this format.

In davinci resolve, hardware decoding is supported on the rtx 5080. 

 

Will this issue really be resolved? Or is it time to switch to davinci? I don't want that. I know premiere very well, and love it. But it has become difficult to work in it due to various bugs.

I understand that not everyone has this problem. But it is available. And it's clearly programmatic. And it's clearly about Premiere.

I've tried installing different versions of the graphics card drivers, but the result is always the same.

My system:

14900K, RTX 5080, windows 11 24h2 (same results on windows 10)

[Dmitriy36779285gov2]

Test file
https://drive.google.com/file/d/1Y7pyZjdrC_CVZe2Y28sJDQl7RHgHCoK8/view?usp=drive_link

[MyerPj]

Hey @Dmitriy36779285gov2 

I gave it a try with my RTX-4070, and 12th gen I-9, Intel UHD 770, and it works well. I think NVidia has dropped the ball on this one, they should be getting the signal by now, and we have an nvidia person on this thread which is good news. I hope an acknowledgement and the fix comes soon.

FWIW: Here's two screenshots

[Dmitriy36779285gov2]

Hey, MyerPj

Thanks for the reply.

As I said before, not everyone has the problem. Rather, on the contrary, only a minority of users have a problem. And that's why developers are paying less attention to this problem.

I must say that some new video formats, which are supported only by the new 50xx graphics cards, are perfectly decoded in premiere beta versions. The stated support has appeared. That's good! But some old formats that should be decoded by ANY video card (integrated or discrete) stopped being decoded after version 25.0. So now I'm doing one project in version 25.0 and the other in beta.

The test file is just one of the broken formats on my computer.

I'm glad that everything is working fine for you. You're lucky to be able to enjoy premiere working properly.

I hope there are those who have a similar problem.

[Dmitriy36779285gov2]

Interesting behavior. Decoding the same file in different projects opened at the same time
https://youtu.be/fDB4cN8QVig

Test files:
https://drive.google.com/drive/folders/1igksF4C2t_IUqYwv1aUhsITRNjNSdQ9t?usp=sharing

Premiere 25.2.3 (Build4)

[Dmitriy36779285gov2]

Possibly useful information. The same project, the same file, opened in different versions of premiere, shows different information tabs (Importer MPEG / Importer MP4)

 

 

[Fergus H]

@Dmitriy36779285gov2 We are definitely following this thread but, at this time, don't have advice for you. Our testing is showing that the GPU is being used correctly for decoding your 10-bit 4:2:0 sample file and this should not have changed between versions. The ImporterMPEG / ImporterMP4 change you noticed is expected but should not be related to this issue. 

I'm discussing this problem with my colleagues and will come back to you when I have more information. 

Regards,

Fergus

P.S. The enclosed screen capture is what I see on my system. Of course, I recognize that this doesn't help you at all and I'm eager to get to the bottom of what you are seeing. 

[Dmitriy36779285gov2]

Thank you for your attention to this topic, Fergus.

This is my personal pain. I know that most users don't have this problem. Only some of my colleagues have it. Apparently, it consists of some combination of hardware and software.

What I've tried:

I've changed versions of premiere many times. I check every new version.

Reinstalled Windows.

I replaced the rtx 3080 graphics card with a rtx 5080.

I have installed different versions of the drivers. Including full removal of nvidia drivers via DDU.

Updated the BIOS. Resetting the BIOS.

I turned on and off the built-in video core in the BIOS.

Enabled and disabled intel/nvidia decoding in premiere settings.

I repeated all the tests in Windows 10 (to exclude windows 11 from the list of suspects)

I thought the problem was in the hardware, but everything works fine in version 25.0. And in davinci resolve.

Processor - Intel(R) Core(TM) i9-14900K

MB - Asus rog strix Z790-a gaming WiFi D4

RAM - 128 GB DDR4 3600 MHz

Video card - RTX 5080

[AndrewTheGreat]

I suggest that everyone interested test out this file in Premiere Pro: https://disk.yandex.ru/i/kHkJfArIgaAfGQ

The file info: 

Why this file? Because it's an iGPU decoded one:

The expected behavior is this:

The reality in Premiere Pro 25.3.0 build 84 is this (see the CPU and the iGPU load):

Should anyone have their iGPU rolling, their PC should be investigated and taken for a reference.

[RjL190365]

This is what I get on my system:

Anything else besides what I am showing you may be caused by improper iGPU driver installation. Specifically, a totally clean install of a generic iGPU driver without first letting Windows Update install an "OEM-optimized" version of the iGPU driver. That will cause everything to default to fail-safe driver settings.

[AndrewTheGreat]

Can you post your full specs? Because never has this file been able to be played back by the iGPU unless 1) it's Premiere Pro 25.0 or older , 2) It's Win 10 or Win 11 23h2. 3) It's Davinci Resolve

It's nonsense that there's some driver misinstall issue - believe me, I have tested every possible variant or combination of software  or scenario on the planet. It's been almost a year already

[RjL190365]

CPU: Intel Core i9-14900K

Motherboard: ASUS TUF Gaming Z690-PLUS WIFI

RAM: 2x32 GB (64 GB total) DDR5-6400

GPU: GeForce RTX 4070 Ti

Operating System: Windows 11 24H2 (updated from an earlier version of Windows 11)

Premiere Pro version 25.3

[AndrewTheGreat]

I don't believe you 🙂 can you show it in a video?

If so, Adobe should study your PC under the microscope 

[RjL190365]

Maybe it's my particular installation of Windows, which has seen a couple of annual feature updates and various other updates. Perhaps I could try wiping my PC and start over from scratch?

On the other hand, you may be one of the few people who have the particular problem that you described. Perhaps Adobe should put your PC and a few others who have that same problem under a microscope?

[JonesVid]

@RjL190365 

Are you using the Intel Support assistant for driver updates and option to do a 'clean install'?

I always use this to update and clean install Intel iGPU driver.

I'll try this test when I'm back home end this week on my 13000k based system and post result.

@AndrewTheGreat - thx for posting this. 

[RjL190365]

I downloaded the driver directly from the Intel Web site, and then run the setup program after I allowed Windows Update to install an iGPU driver because I had (mistakenly) believed that the Setup Assistant download supported only overwrite (in-place) driver upgrades.

And with the iGPU driver that's currently on my system, I did use the 'clean install' option in the setup program. Previously, I simply overwrote the older driver.

[AndrewTheGreat]

I would like Adobe staff explain this, @Fergus H @mayjain @jamieclarke  

How come that if a 100% iGPU-decoded video is not decoded if the file comes from a folder with the name written in russian or chinese (didn't check other languages) and IS decoded if the name is written in english? What type of linguistic discrimination is that?

Here's a proof. A copy of one and the same file was put into folders with a russian, english and chinese name. 

[RjL190365]

Simple. The alphabets of the program and the file names must match. Otherwise, the program will default to fail-safe parameters. No wonder why the English-language version of Premiere Pro works for hardware acceleration with Latin letter script but not with Cyrillic or Chinese script.

[Moderator: this is incorrect. There is no requirement for the application to be using the same language as path names and Premiere Pro has no fail-safe mode that it defaults to. The issue discovered by @AndrewTheGreat is a bug that we will fix. We are actively working on it.]

[andreik18371608]

What do you mean not surprising? So if you are from a non-English speaking country you should use limited functionality?

[R Neil Haugen]

I think what he means is the computer system must be set to the same language as Premiere Pro. That's all. If I read that correctly.

[AndrewTheGreat]

It would be true if every software worked that way. It's a non-compliance with expected rights, because I paid for a multi-language license so the languages I use should not limit in any way my personal experience. Working with multiple laguages for all my life I've never had any cases like this with any other software. Premiere Pro surprised me once again.

[andreik18371608]

Do I understand correctly that this is a solution to the problem that we have been talking about here for almost a year? I have noticed for quite some time that people on different forums complaining about this problem are attaching screenshots with Cyrillic. By the way, this explains why no one can reproduce this problem.

[Fergus H]

@AndrewTheGreat thanks very much for reporting this! It is definitely not expected behavior and, as @andreik18371608 points out, could be the explanation for why we've been unable to reproduce some of the performance problems that have been reported on this thread. 

We're looking into this issue now and we'll update this post when we have more information. Again, thanks very much. 

Regards,

Fergus

[Dmitriy36779285gov2]

I'll add a few words. Maybe my observations will help you a little.

1. Decoding stops if any characters other than the Latin alphabet are used. I tested Cyrillic, Hindi and Hebrew.

2. If you try h264 decoding, it works fine with any characters in the name. The problem concerns only HEVC.