That tells me nothing. You may need to uninstall and reinstall the program. And older versions of the Adobe programs are not guaranteed to work properly on newly updated operating systems.   So, if you have updated your version of macOS recently, then that may be the issue. You may need to update to a newer version of Premiere Pro just for it to work properly on a newer OS. ... View more

You are wrong about the codec match in "Match source". That preset only matches the resolution, pixel aspect ratio, frame rate and field order. It does not even try to match the video codec at all, but instead will use the program defaults.   And is your installation of Premiere Pro a trial install? If so, then you will have an extremely limited codec selection, which does not include HEVC (H265). In that case, you will need a full paid subscription and activation in order to even see the HEVC codec at all. ... View more

Cette configuration, telle qu’elle est actuellement équipée, n’est pas à la hauteur des normes de performance actuelles pour le montage vidéo, j’en ai bien peur. Vous voyez, ce Ryzen 5 4500 est une version castrée d’un APU basé sur Zen 2 avec son iGPU fusionné. Il souffre également d’une quantité de cache L3 beaucoup plus petite que dans les autres processeurs et ne prend en charge que PCI-e 3.0, de sorte que les dGPU bas de gamme seront goulottés par l’interface PCI-e. Pire encore, le RX 580 est dépassé par les normes dGPU bas de gamme actuelles (il n’est pas suffisamment performant dans le rendu Premiere Pro qu’un iGPU seul pour la puissance consommée par le RX 580). De plus, ce PC a besoin de plus de RAM (32 Go minimum, 64 Go seraient mieux).   Trois mises à niveau ou plus en même temps sont absolument nécessaires pour mettre ses performances à la hauteur. En d’autres termes, une toute nouvelle construction de PC sur une nouvelle plate-forme de processeur telle que AM5 ou Intel LGA 1851 et DDR5 RAM serait plus économiquement réalisable sur la base des performances par rapport coût, que la mise à niveau de tous ces composants de base en une seule fois. ... View more

That first result is about the same score that I got from my i9-14900K system with an RTX 4070 Ti GPU and 64 GB of DDR5-6400 RAM (also running 25.1). However, my system only got 14300-ish to 14500-ish scores with 25.0 in the same PugetBench testing.   This seems to indicate that the i9-14900K is less affected by the 25.1 changes than lesser Intel CPUs are. It also indicates that my PC's performance is more GPU-bound than CPU-bound.   And the i7-4790K that I had from 2014 to 2019 would have choked badly on 25.1, given how poorly (relatively speaking) it would have run on versions 24 to 25.0. ... View more

Actually, the i9-9900K will also be heavily affected by the 25.1 and later versions, as well. Thus, the relative ranking of all Intel CPUs of all generations with iGPU enabled that are running the exact same version of Premiere Pro will remain the same. What's more, the i9-9900K's performance will, if anything, plummet even more from its pre-25.1 performance than an i7-13700K will when both CPUs are running 25.1. ... View more

Thank you for the findings. Adobe has, indeed, switched the decoding priority from the iGPU to the discrete GPU when decoding H.264. Unfortunately, this creates a new problem: Some decoding tasks heavily misuse the dGPU's resources, and by the time the dGPU hands off the decoding task to the iGPU, the Mercury Playback Engine renderer gets automatically and ungracefully locked into the software-only mode (with absolutely no warning whatsoever) for the remainder of the processing/exporting job for that timeline.   And by the way, my secondary mini-ITX system with an AMD Ryzen 5 7600X and an AMD Radeon RX 6700 XT did perform slightly better with version 25.1 than it did with 25.0 and earlier versions. And that's only because the earlier versions had broken support for the AMD iGPU which was fixed in the 25.1 version. ... View more

Too bad it's no longer available new at any price.   In the sub-$190 price range all you can find that can be bought new are 10-year-old Nvidia and AMD GPUs (such as the GeForce GT 710 or 730 and the Radeon HD 5450) that are so obsolete that they are no longer receiving driver updates at all whatsoever, or very-low-end GPUs such as the GeForce GT 1030 or the Radeon RX 6400 or 6500 XT that do not have a hardware encoder at all (and therefore forcing all encoding on the CPU). Nvidia had already discontinued all production of all non-RTX GPUs over a year ago. ... View more

Unfortunatrely, the sub-$200 range of discrete GPUs are now nearly extinct. All you can find in that range are old- or older-generation GPUs that either lack hardware encoding support whatsoever or are obsolete due to the "latest" meaningful driver version update being years old. You'll have to spend closer to $300 just to even find the cheapest relevant discrete GPU at all that can be utilized in Premiere Pro for years to come. ... View more

Yes. Premiere Pro can utilize multiple identical encoders, which can be found inside certain GPUs, simultaneously. However, if the multiple encoders are completely different from one another or are of completely different generations, then only the encoder that's in the GPU that's connected to your primary monitor will be utilized. ... View more

I am also expecting Nvidia to unlock 4:2:2 hardware decoding and encoding support (at least for HEVC) in its Turing and newer-gen GPUs beginning with driver branch 570, which is due to be released whenever the Blackwell GPUs start shipping to distributors.   Adobe users may have to wait longer for this support to be added to its Nvidia codec. ... View more

Like John stated. Nvidia GPUs, particularly later-gen models, work best in Premiere. AMD GPUs, by comparison, are slightly faster for long-GOP (H264/265) processing but slower for RAW codec processing. ... View more

In addition to what Neil stated, it may be that Premiere Pro 25.1 needs something that the GTX 1080 Ti doesn't have (hardware-support-wise) in order to export at a sufficiently fast speed. And with Nvidia pretty much leaving support for pre-Turing GPUs hung out to dry, it would not be surprising at all that a forthcoming version of Premiere Pro would require hardware Ai support in discrete GPUs just to even render or encode with hardware acceleration; in which instance the 1080 Ti would soon be permanently locked to the software-only rendering and encoding modes. ... View more

Here is the problem:   Adobe officially does not support the ARM version of Windows at all. Only the x86-64 version of Windows is supported. The 23.6.8 version of Premiere Pro, however, added ARM Windows support on an experimental basis. ... View more

Further testing with my main system with Premiere Pro 25.1 on Windows 11 24H2 with actual H.264 and actual HEVC footage confirmed my earlier suspicions: With both the iGPU enabled and with a discrete RTX 4070 Ti installed, the iGPU did function with HEVC but not H.264. All H.264 decoding got sent to the dGPU.   And the lack of activity on the "Video decoding" portion of the iGPU graph for HEVC does not mean that the decoding is broken per se, but rather a bug with the reporting in the Windows' Task Manager itself. The "video decoding" part of the graph only works properly when the iGPU processes everything while the dGPU sits idle or is disabled. ... View more

My Intel system's motherboard is equipped with a Z690 chipset (in particular, the motherboard is an Asus TUF Gaming Z690-PLUS WiFi (DDR5)). However, I have updated the motherboard's BIOS twice since I updated to 24H2. ... View more

Another update on my system:   When I ran Puget Systems' decoding test, I discovered that with Premiere Pro 25.1 running on Windows 11 24H2 on my main Intel i9-14900K system with an Nvidia GeForce RTX 4070 Ti, the hardware H.264 (AVC) decoding defaulted to the Nvidia GPU while H.265 (HEVC) decoding defaulted to the Intel iGPU. (This was with the Premiere Pro hardware decoding set to the default of both Intel and Nvidia enabled.) The other GPU, in either instance, showed zero usage.   As for the 24H2 feature update to Windows 11 disabling or wiping out the iGPU selection in the BIOS, it turned out that neither of my two systems had that problem. In other words, some - but not all - Windows 11 24H2 systems suffer from that problem. ... View more

Since this past October, you can no longer buy any MacBook with just 8 GB of RAM. The new base RAM amount for even the cheapest MacBook Air that can be purchased at an Apple Store is now 16 GB. ... View more

For those people running Windows 11 24H2, we will have to wait until the January Cumulative update at the earliest in order to determine if this behavior is fixed. The December cumulative update has no new fixes — only security patches.   We will also have to wait until the next point release of Premiere Pro in order to find out whether the broken auto-hardware-decoder-detection in the current version 25.1 and/or the broken multi-simultaneous-decoder support since at least version 25.0 is fixed. ... View more

The GPU is still important in rendering. In all of my tests the discrete GPU is utilized in rendering where it can, and all of my testing had the GPU set to hardware encode H.264 and HEVC by default. The lower score for decoding (called "Processing" in PugetBench) with the Nvidia hardware decoding enabled versus software-only decoding is likely due to the inherent bottlenecks in the PCIe interface (as well as all other full-duplex interfaces) – in testing, simultaneous transfers through a full 16-lane PCIe bus in both directions create some latencies within, particularly when each of the simultaneous transfers use the entire lane width of the interface. ... View more

That was just running the PugetBench. I will use actual footage later when I perform my re-test.   Although to be exact, my RTX 4070 Ti and all other discrete GPUs will suffer from some lag during decoding while also trying to render because all of the operations must share the exact same PCIe lanes. And all operations in both directions by default utilize all available PCIe lanes. ... View more

At any rate, on my PC software decoding is actually faster on H.264 than the Nvidia hardware decoder on my particular RTX 4070 Ti. Strange. ... View more

Maybe my particular installation of Windows has been doing something that almost nobody else is experiencing? Maybe the expected behavior with 24H2 and any version of Premiere Pro was to disable the iGPU under all circumstances, and that setting the hardware decoding to Intel enabled and Nvidia/AMD disabled would force software-only decoding? ... View more

How did you get Windows 11 (any release, including the very first version) on your PC in the first place? You see, Windows 11 has always officially required a system with TPM 2.0 or higher both present and enabled in order to even install at all. Unfortunately, integrated TPM did not arrive until the 8th-Gen Intel CPUs introduced in late 2017. Your CPU is only a 6th-Gen CPU whose support and servicing was completely terminated by Intel itself at the end of September 2022. And most systems based on such old CPUs had absolutely no TPM support at all of any kind.   And officially, you were not supposed to update to Windows 11 at all on your PC. Windows 10 22H2 was officially the end of the line for your PC's Windows version updates.   As for Windows 11 24H2, both TPM 2.0 and SSE 4.2 support are required. Windows 11 24H2 will not even install at all on a PC whose CPU predates the advent of SSE 4.2 instruction support even if 'hacked" to force-install on a non-TPM-equipped PC. ... View more

I retested my system with version 25.0, and in that version Premiere Pro defaulted to using the Intel iGPU for hardware decoding with the hardware decoding settings are set at their default settings. Version 25.1 changed the hardware decoding default to the discrete GPU with the decoding settings in Premiere Pro set to their defaults.   Thus, I am now concluding that Premiere Pro (in any version since hardware decoding support with a discrete GPU was added) cannot utilize two different hardware decoders simultaneously no matter which version of Windows that the software is running on. Instead, the default hardware decoding settings in Premiere Pro was supposed to automatically select whichever hardware decoder it thinks delivers better performance. Unfortunately, this auto-detection is broken in version 25.1. ... View more

It turned out that at least with Premiere Pro 25.1 running on Windows 11 24H2, only the discrete Nvidia or AMD GPU is being utilized for Long GOP decoding when the decoding settings in Premiere Pro are set to their defaults. ... View more

Unfortunately, this "workaround" only works for H.264. HEVC defaulted to software-only decoding with the above-mentioned settings.   I will try reverting Premiere Pro back to 25.0 to determine if it's a software problem with either Windows 11 24H2 itself or a cumulative update to that feature update, or if it's with the specific Premiere Pro version. ... View more

My i9-14900K system running Windows 11 24H2 is also experiencing the same problem when running Premiere Pro 25.1. It did not experience this problem with version 25.0.   The workaround for this is to clear the checkbox besides Nvidia (or AMD, if you have a discrete AMD GPU) in the hardware decoding settings within Preferences > Media. Only with the hardware decoder set this way (Intel enabled, Nvidia or AMD disabled) would the iGPU be utilized for decoding. ... View more