Copy link to clipboard
Copied
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
Hi all,
Thanks to everyone who contributed to this thread and thanks to those people we’ve spoken to via video call.
I’d like to summarize the changes we made in v25.1, the impact, and possible changes in the future.
As @mayjain has mentioned, in v25.1, we changed GPU priority so that an Nvidia GPU will be given priority over an Intel GPU when decoding H.264 in 8-bit 4:2:0. Note that in more complex sequences, Premiere Pro uses both GPUs, splitting the load between them.
Based on our tes
...Hi All,
Apologies for the inconvenience caused. We have addressed a major issue discussed in this post, where HEVC files in non-English folder paths may not be decoded via Hardware.
We truly appreciate your support and collaboration in investigating this issue. While beta builds are not recommended for production, they
...Copy link to clipboard
Copied
Hi all,
We've identified the source of the problem and have a fix for it. I'll post another update here when the fix is in our public beta. @AndrewTheGreat we'll be very excited to get your feedback on the fix!
Thanks,
Fergus
Copy link to clipboard
Copied
Thanks y'all for the clarification on my prior post.
Copy link to clipboard
Copied
Good day. Since we're talking about problems with other languages, there's been a problem with finding effects in Cyrillic for a long time. If you type the effect name in lowercase letters, it won't be found, but if you start typing it with a capital letter (just like it's written in the list of effects), it will be found. There are no problems with effect names in Latin - you can type them with either a capital or lowercase letter. It would be great to fix this.
Copy link to clipboard
Copied
I'm a bit late on this as only just returned home. I see the problem has already been identified which is good.
For the sake of checking I did try it out and results attached.
iGPU happily decoding at about 49%. 13900K CPU at 20%. NVidia 4080 Super at 59%.
Intel iGPU driver on latest one, 32.0.101.6987.
NVidia Driver 576.80
Copy link to clipboard
Copied
Well, it might be a little stupid question,
Not only the rendering (Export), but also the timeline preview is affected by that, right?
If you use a premier version of 25.1 or higher, except in special circumstances
Intel QuickSync Does Not Work Properly Under Normal Conditions
Can I see this information as something I need to know?
Copy link to clipboard
Copied
Rendering is the last thing you should consider. It normally is as fast as your system can provide. The problem we are dealing with here mainly affects the playback speed and smoothness.
Copy link to clipboard
Copied
Thank you for your kind information
Thanks to you, I think my thoughts are organized well !
Copy link to clipboard
Copied
Hi All,
Apologies for the inconvenience caused. We have addressed a major issue discussed in this post, where HEVC files in non-English folder paths may not be decoded via Hardware.
We truly appreciate your support and collaboration in investigating this issue. While beta builds are not recommended for production, they install separately from release versions and can be used for testing the fix. Please let us know your feedback after testing.
Thank you for your patience and continued support.
Best regards,
Mayjain
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more