The 5090 will speed up rendering of any GPU-accelerated effects on your editing timeline, for sure. But most of the work is still largely being done by the CPU.   If you have an unlimited budget, then the AMD Threadripper and Threadripper Pro CPUs will speed up your exports to intermediate codecs such as ProRes and DNxHR, but they are very expensive.   On the other hand, if you're exporting primarily to Long-GOP lossy codecs such as H.264 and HEVC, then the Intel CPUs such as the i9-14900K (and better still the Core Ultra 7 and 9 CPUs) have the advantage.   In other words, it depends on what you are planning to export as. ... View more

I'm afraid that you're stuck with it. It's a hardware limitation. AMD Radeon GPUs do a lousy job of producing quality hardware transcodes compared to Nvidia GPUs and Intel GPUs (and transcoding quality and recording/streaming quality are two completely different animals when it comes to hardware encoding quality). The only workaround is software encoding, in your case. And you must select software encoding manually in the video settings of the export window with each and every timeline that you'd be exporting; otherwise, the encoder selection will default to hardware encoding, which will bring you back to square one (in this case, the mercy of the hardware encoder image quality gremlins). ... View more

It's not Adobe. AMD's encoding quality has always lagged behind that of Nvidia and Intel regardless of which software you're using for encoding. In fact, the encoding quality on even the latest AMD GPUs is only about on a par with an Nvidia GPU from 2016 (the GeForce GTX 10 series). ... View more

Going with a more powerful GPU will not help your export performance much, in this case. Almost all of the performance improvement is from a more powerful CPU. However, the RTX 5090 will speed up your H.264 and HEVC export performance a bit due to the better NVENC encoders on that GPU compared to your current RTX 2060.   And based on your results that you had obtained with the Ryzen 7 3700X and the RTX 2060, I am estimating that exporting using an i9-14900K and an RTX 5090 would take a little less than half, and possibly around one-third, the time it took your 3700X/2060 combo to export to H.264 with most of that improvement coming from a switch to a more powerful CPU. ... View more

Only Metal will be available as of the last two major versions of premiere Pro, in your case. And as of version 25.2, you can no longer select software-only rendering within Premiere Pro or Media Encoder. Software-only rendering is available in Premiere Pro only in troubleshooting mode. OpenCL is no longer available at all on Macs running the newest-supported version of macOS; therefore, your rendering mode is permanently locked to the Metal GPU acceleration mode. ... View more

In this case, then it will not help because all other big-name laptop manufacturers also use their own OEM-customized drivers as well, often installed using legacy non-WDM methods. The only way to circumvent this would be to build your own desktop PC using off-the-shelf components.   Barring that, you can try to go directly to Intel's Web site and manually download the driver for your iGPU for the particular Intel Core CPU that your laptop has, and then try to install that. The driver as suggested by Adobe on that particular page you've posted a page out of is outdated and too old to support your particular iGPU. ... View more

I agree with Ann. Your GTX 780M is obsolete for several years now. It is a mobile Kepler GPU that Nvidia had already completely discontinued driver support for five years ago, with the very last driver being version 425.31 in mid-2019. All recent versions of Premiere Pro now require a driver version higher than 560.xx just to even be supported at all.   In addition, Apple no longer supports CUDA at all beginning with OSX 10.14 (Mojave). And Apple has completely removed OpenCL support in the last couple or so major macOS versions. So, whichever setting that is listed inside the grayed-out selection box will be your default rendering setting (usually Metal, but sometimes software only depending on the GPU) because Adobe has depreciated software-only rendering beginning with version 25.2 of both Premiere Pro and Media Encoder.   In other words, you are at the mercy of Apple. Adobe merely had to comply with the demands of the hardware manufacturers. ... View more

Next thing to check:   Which build of Windows 11 is your system running? First release (21H2), 22H2, 23H2 or 24H2? It is possible, even likely, that your particular feature version of Windows 11 has reached EOS (End Of Service) at Microsoft itself, and that you might need to update your feature build to 23H2 or newer just to remain supported by Adobe? ... View more

Premiere Pro, beginning with version 25.2, has depreciated the MPE software-only mode. You can no longer choose software-only rendering in Media Encoder at all, and you can access software-only rendering in Premiere Pro only when you hold down the Shift key while launching Premiere Pro and then checking the box marked "Use software-only rendering" (this is the troubleshooting menu). Otherwise, if that Quadro RTX 4000 is the only GPU installed, Premiere Pro and Media Encoder are both permanently locked to the CUDA GPU-accelerated rendering mode (and Adobe has permanently disabled the OpenCL mode for all Nvidia GPUs for hardware-accelerated  rendering).   By the way, Turing (which your GPU is based on) is now the oldest GPU architecture that is still receiving CUDA updates. Maxwell, Pascal and Volta GPU architectures have their CUDA support frozen to a previous version beginning with the newest branch 570 of the Nvidia drivers. Under that circumstance, I would not be surprised if the next major version of Premiere Pro would require a Turing or newer Nvidia GPU just to even run at all, or else a warning message would pop up singling out unsupported GPU hardware. ... View more

The problem here is the Windows page file. By itself, it needs at least as much free space on that SSD as the amount of installed RAM that you have in order to function properly. Otherwise, if the SSD runs out of room, the page file cannot expand large enough, resulting in crashes and lock-ups. And trying to disable the Windows page file will not work at all in newer versions of Windows as Windows will always recreate and expand that page file no matter what. ... View more

The problem here is OpenCL. Adobe video programs just do not perform well in OpenCL compared to in CUDA. Unfortunately, AMD Radeon GPUs are stuck on OpenCL in Windows whereas CUDA is restricted to Nvidia GPUs. And AMD has already depreciated not only OpenCL in general (in favor of promoting the HIP API, which no Adobe program currently supports), but also support for all of its pre-RDNA (RX 5000 series) GPUs to a reduced, legacy driver support status. Your RX 580 GPU, unfortunately, predates the RDNA architecture by two full generations. And it has always performed poorly in Adobe video programs no matter what – barely any faster (effectively) than even very recent integrated Intel IGPs to justify the money, space and power usage. ... View more

You need a bigger OS SSD. You simply have too little free space on that 128 GB SSD for the amount of RAM that you have installed. ... View more

That just goes to show the importance of a balanced-performance system – specifically, the balance between the CPU and the GPU. In your case, the GPU is much weaker than the CPU, which can – and does – result in corrupted hardware renders. You really should have had a much more powerful GPU than your current Quadro RTX 4000 (which is, sadly, only equivalent to a GeForce RTX 2060 non-SUPER in overall CUDA performance).   It also proves that your IT department sometimes skimps on the GPU for productivity – too much CPU and not enough GPU. That would be like equipping an AMD Ryzen 9 9950X3D CPU-equipped PC with only a GeForce GTX 1660 SUPER GPU in terms of the relative performance balance. ... View more

Like Warren Heaton stated. Starting with the 2024 version Adobe now absolutely requires a CPU with AVX2 instruction support just to even install any of the Adobe video programs at all. Your Xeon E5 was released during the Sandy Bridge/Ivy Bridge (2011-2012) era, which precedes the introduction of AVX2 instruction support on Intel CPUs beginning with Haswell in 2013 (Intel's HEDT/workstation CPUs had not yet been updated to include AVX2 support at the time of the 2013 Mac Pro's introduction).   And for Mac only the 2024 and 2025 versions are currently available. One 2023 version is available for Windows only. ... View more

Is it possible that selecting "Maximum render quality" might have forced everything – encoding and rendering - into the software-only mode, using the CPU only (no GPU hardware acceleration at all)? ... View more

It falls far short of Adobe's minimum practical requirements, especially if that laptop has only 4 GB of total RAM which will not run Premiere Pro at all. Plus, it is a gimped first-gen Zen APU with only two single-threaded cores with no multithreading capability whatsoever. The screen's resolution is only 1366x768, which does not meet Adobe's official minimum display resolution requirement of 1920x1080. ... View more

The hardware decoding improvements have not changed at all in Premiere Pro since this 2021 thread. AMD restricts all of its GPUs up to and including the RX 7000 (RDNA 3) generation to 4:2:0, and it is highly likely that the video engine in the RX 9000 series remains largely unchanged. It is a hardware engine limitation. And Adobe has not yet updated its hardware decoding support since 2021 at any rate (at least in the official release builds). Yet it is now almost 3.5 years since this thread was started.   I hope this answers this thread directly. ... View more

Thanks for the clarification. ... View more

That's better, if that's all you can afford. Its overall performance would be roughly on par with that of my secondary mini-ITX build that's equipped with a Ryzen 5 7600X and only a Radeon RX 6700XT GPU; however, you do gain AV1 hardware encoding support if you're planning to use software that supports such encoding like DaVinci Resolve. Otherwise, for that amount of money you probably would've ended up with a grossly mismatched setup in terms of the relative component performance balance (either too little CPU or too little GPU). ... View more

That Ryzen 5 5500 is a poor choice for video editing by current standards: It is not a true Ryzen 5000-series CPU per se, but is instead a gimped APU with its integrated GPU disabled, only PCIe 3.0 support (versus PCIe 4.0 on the non-APU Ryzen 5000-series CPUS) and only 16 MB of L3 cache (and again, the non-APU Ryzen 5000 CPUs have four times more L3 cache than the APUs), which will bottleneck the performance of that RTX 4060 which absolutely requires full PCIe 4.0 support to avoid an interface-induced bottleneck as it utilizes only eight of the 16 PCIe lanes. The end result is a system that actually performs worse than a quad-core CPU that's a CPU generation older. As such, it should not have been labeled a Ryzen 5 5500 at all, but a Ryzen 5 5600GF instead as it is essentially a Ryzen 5 5600G with its iGPU disabled.   Unfortunately, the 5500 is also in no-man's land because it requires a relatively expensive higher-end GPU (I'm looking at you, the RTX 4070 SUPER) just to minimize that PCIe-induced GPU bottleneck, and then you'd end up with the exact opposite problem (too much GPU and not enough CPU). As currently configured, that RTX 4060 would utilize only eight PCIe 3.0 lanes on your planned CPU (whereas the RTX 4060 itself is wired for eight PCIe 4.0 lanes), while the 4070 utilizes all 16 PCIe lanes (thus making it much less vulnerable to PCIe clock speed deficiencies).   So, if you get that particular AM4 platform, see if you can get a Ryzen 5 5600 (make sure that the 5600 CPU does not have a "G" anywhere in its model number) instead of that planned 5500 (and remember, the 5600 and the 5500 are of two completely different microarchitectures). And if you do go Ryzen 7, don't pick the plain non-X 5700 as it is like your planned 5500 – a gimped APU rather than a true 5000 series CPU. ... View more

Which exact driver version number are you using? You see, the 57x.xx driver versions have begun to depreciate CUDA support for all older Nvidia GPUs prior to the Turing architecture which came out in 2018. That means that both of the 570-series and newer Studio (and all of the Game Ready drivers in the 570- and newer series) drivers now have broken CUDA support for all GeForce 900 and 10 series GPUs. Nvidia has begun to phase out support for all of the GPUs older than the GeForce 20 and GeForce 16 series GPUS by relegating them to legacy support status. And the next point version of Premiere Pro may begin to warn you that "your GPU will no longer be supported in an upcoming release. Please update to a newer GPU." ... View more

This has been answered in several similar threads:   Beginning with version 25.1, Adobe has changed the priority of hardware H.264 decoding from the integrated GPU to the discrete GPU. This means that the discrete GPU will be utilized first, and then the integrated iGPU will take over only when the discrete GPU's resources allocated to decoding becomes depleted. This creates another problem: That discrete GPU may become depleted on VRAM early, which will force Premiere Pro to default to software-only rendering for the remaining time it takes to render that timeline.   There is a feature that's currently in the beta testing stage which allows the user to change the priority of hardware H.264 decoding from the default dGPU to the iGPU (the latter of which Premiere Pro versions up to and including 25.0 are "permanently" set to). ... View more

True that. But AMD GPUs are slower in RAW codec performance than Nvidia GPUs. They do a bit better than Nvidia in H.264/HEVC performance at some expense of export image quality. ... View more

Guess what? There is absolutely no CUDA GPU acceleration at all in CS4. Mercury Playback Engine wasn't conceived until CS5. The only GPU acceleration, if any, that you'll get in CS4 is OpenGL – and that is only for the interface. All decoding, encoding and rendering in CS4 is entirely software only. And it is extremely sluggish at doing its job because it is limited to under 4 GB total of system RAM (because it is strictly a 32-bit Windows program) while most renders require much more than 4 GB of RAM. ... View more

Actually, Quick Sync never supported 4:2:2 in H.264 at all. It is restricted to 8-bit 4:2:0 like all discrete GPUs prior to the newest Nvidia Blackwell architecture (aka GeForce RTX 50 series). The latest current non-beta version of Premiere Pro (25.1) was released prior to the introduction of the Blackwell architecture, So, no matter what you try to do, and no matter which system that you're using, and no matter what video editing software you're running, all decoding of your 4:2:2 H.264 footage is entirely on the CPU, in software-only mode (and Adobe has no say in this at all whatsoever because the 4:2:0-only hardware decoding for H.264 restriction had been imposed by all of the GPU makers). Even DaVinci Resolve Studio only supports 8-bit 4:2:0 for hardware decoding of H.264 for all Intel and AMD GPUs (discrete or integrated), as well as all Nvidia GPUs up to and including the Ada-generation (GeForce RTX 40 series).   By the way, Nvidia's Pascal and later GPUs support 4:4:4 hardware decoding for H.264 since a few driver versions before the current 572.xx branch. Adobe and most other NLEs currently do not support 4:4:4 hardware decoding of H.264, nor does Adobe support 4:4:4 hardware decoding of anything at all. ... View more

That also depends on the footage that your friend used. If it's H.264, then Nvidia's NVDEC never performed particularly well. In fact, I have an i9-14900K system with an RTX 4070 Ti, and I couldn't believe just how weakly NVDEC performed (at least on the RTX 40-series and earlier GPUs). In fact, software-only decoding with the i9-14900K alone performed better than NVDEC ever did on H.264.   If that footage is in ProRes, then the Apple Silicon Macs except for the base M1 chip offered hardware decoding and encoding acceleration for ProRes. Windows never natively supported ProRes to begin with.   On the other hand, a Mac is not the best choice when deadlines are critical: Every Mac that I had my hands on took much longer at exporting than even a recent-gen PC with an 8-core/16-thread CPU such as a Ryzen 7 9800X3D (which I spent only a couple of hours on). ... View more

And beginning with the 25.2 beta, software-only rendering has been depreciated. A simple launch of Premiere Pro will become permanently locked to the GPU-accelerated rendering mode when a supported GPU is installed, but warn you that Premiere's renderer will fall back to software-only mode only when an old GPU or a GPU equipped with an insufficient amount of VRAM is installed. If you wish to run in software-only mode with a supported GPU is installed, you must hold down the shift key when launching Premiere Pro and select the check box marked "run in software-only mode" or words to that effect.   By the way, Nvidia has begun to twilight support for everything pre-Turing this year, which means that CUDA version will become frozen in all Maxwell, Pascal and Volta GPUs. Only Turing and newer architectures will continue to receive CUDA updates (this means that the only GPUs without hardware ray tracing that will continue in the mainstream support branch will be the Turing-based GTX 16 series). ... View more

Actually, Premiere never supported two completely different discrete GPUs at all simultaneously no matter what. It always supported only the GPU which is selected for rendering. That means that the only way to utilize your discrete Intel GPU would be to select OpenCL instead of CUDA as the hardware renderer (and then, everything gets sent to the Intel GPU while the Nvidia GPU sits idle). Otherwise, only the nvidia GPU is used. ... View more