You got things wrong there. Your GPU is being slammed by simply rendering the Gausian blur effect, which along with whatever GPU-accelerated effects you might not have been aware of that totaled 84% GPU utilization (as indicated by the 3D load). By contrast, the RX 580 does not do much to process the Gausian Blur effect, and thus the 3D utilization is very low there, resulting in very poor GPU effects performance.   The NVENC encoder is stuck below 10% because H.264 doesn't demand much if any hardware encoding capability. Your old GPU showed far greater encoding utilization because the RX 580's encoder is far less advanced than the RTX 4060's.   However, the CPU utilization being below 20% in this workflow is indicative of a bottleneck somewhere in your system. Usually in the form of misbehaving background processes interfering with your new system's performance that didn't occur with your old PC.   What's worse, big-name computer brands tend to load the system with bloatware that steals performance from your new system and often cannot be easily uninstalled without destroying its existing OS installation. ... View more

I think I found the problem:   Your timeline is in HLG, not PQ. That breaks your PQ workflow from the start.   Unfortunately, there is no factory preset with a PQ timeline. The only default presets with HDR in their name all use HLG. The conversion from PQ to HLG during rendering and then back to PQ during exporting will ruin your HDR exports. ... View more

It's OK as long as you don't do 3D work or use any 3D effects in After Effects (which works far better with CUDA, which supports only recent-gen NVIDIA GPUs, than in OpenCL, which all non-NVIDIA GPUs are permanently stuck on in Windows). ... View more

Fair enough. I currently don't have the Studio version of Resolve (only the Free version, which lacks many of the hardware-accelerated features that are included in the paid Studio version), and it does not support AC3 audio at all (AC3 must be transcoded to another audio format before one can import to Resolve). ... View more

That goes to show you the differences in rendering/processing priority choices between Premiere and Resolve. You see, your i9-10920X CPU is a weakling by current standards (but was a decent CPU for its 2018-2019 vintage). Adobe, for the most part, prioritizes raw CPU power over GPU performance but still doesn't take full advantage of multithreading, while Resolve is quite heavily GPU-dependent as long as the CPU used in the Resolve system is just powerful enough not to heavily bottleneck a given GPU. And the lightly-threaded performance of your i9-10920X CPU (which, by the way, is significantly lower than any current- or recent-gen CPU) is what's causing Premiere Pro to stutter and choke under rendering.   No wonder why the RTX 5080 didn't make any tangible performance difference with Premiere Pro in your system: It is significantly hamstrung by the CPU. ... View more

En realidad, es todo lo contrario:   Está bloqueado para el renderizado acelerado por GPU solo CUDA a partir de la versión 25.2. Ya no puede seleccionar el renderizado solo por software en la página de configuración. ... View more

You've got things a bit mixed up. As another poster stated, beginning with version 25.2 of Premiere Pro, you can no longer access software-only rendering within the Premiere Pro or Media Encoder settings. And if that GTX 1660 is the only GPU installed in your system, and you have not enabled the Integrated Intel UHD Graphics 630 that's on your i7-9700 CPU, then you're permanently locked to CUDA "accelerated" rendering, while with the integrated GPU enabled you can only choose CUDA or OpenCL for rendering (and OpenCL will utilize only the UHD Graphics 630 for rendering).   The only way that you can access software-only rendering at all would be to hold down the Shift key and then check the box marked "Use software only rendering" (this choice is one of the five choices in Premiere Pro's troubleshooting mode). ... View more

My opinion on that build still stands as of right now, but for a somewhat different reason:   What I stated above for the Ryzen 5 5500 is especially true due not only to the PCIe 3.0 connection between the CPU and the GPU, but also due to the relatively low amount of VRAM on the RTX 4060. The lower the throughput between the CPU and GPU, the more VRAM you'll need on the discrete GPU in order to minimize that bottleneck. But with only 8 GB on that RTX 4060, depending on your project you may get depleted of discrete GPU VRAM relatively early in your renders, forcing the rendering onto that slower PCIe 3.0 bus. The Ryzen 7 5700X, on the other hand, uses a PCIe 4.0 connection between the CPU and GPU, so the performance degradation is reduced. ... View more

Actually, the Intel CPU in that laptop does support Quick Sync. It's the Nvidia GPU that supports neither NVDEC nor NVENC, and that the way current (recent) versions of Premiere Pro operate, Premiere's GPU detector currently gives up once it detects a driver for the GPU that it prioritizes.   Because of this, the OP has no hardware encoding at all, and he has no hardware decoding for H.264. And assuming that HP did not disable the integrated Intel UHD Graphics in that laptop, only HEVC will be hardware-decoded, and only in 4:2:0 color space. ... View more

For that budget go with the RTX 5060 Ti 16 GB card, especially if you're going to also work with 10-bit 4:2:2 H.264 or HEVC video footage and/or run After Effects on a frequent basis. Here's why:   Radeon GPUs are restricted in hardware to 4:2:0 hardware decoding/encoding no matter what. No 4:2:2 or 4:4:4 hardware support at all. After Effects performs relatively poorly in OpenCL compared to in CUDA.   That narrows your choices down significantly.   Alternatively, if you can live with only 12 GB of VRAM, then the RTX 5070 is a good alternative. (The RTX 5070 Ti is even better, but its current price is outrageously high for what it is.) ... View more

Your desktop plans are on the right track, especially since your current laptop's GeForce MX 150 has absolutely no hardware H.264 or HEVC decoding or encoding capability whatsoever (it is, after all, based on a low-end GT 1030 with hardware decoding permanently disabled at manufacturing level while the hardware encoder is completely absent in the GP108 chip that it uses). This forces all decoding and encoding back onto the CPU – straight to the main cores of your 8th-Gen Intel CPU proper.   Under the above circumstances, Premiere Pro 25.1 and later are not suitable for use with that laptop because of the decoding and encoding priority of these newer versions of Premiere Pro: In your case, everything will be sent entirely to the CPU, in software-only decoding and encoding mode because Premiere Pro prioritizes discrete GPUs over integrated ones. And if it detects an installed driver for the GPU which lacks hardware decoding and encoding support, your system would become permanently locked to software-only decoding and encoding for H.264 and HEVC.   And Intel has placed all driver support for all pre-11th-Gen CPUs into legacy support three years ago, which means that there will be no new feature support for these older iGPUs while only critical security fixes will continue. ... View more

Your post is completely off topic. Your Quadro 4000 is not the same GPU as the Quadro RTX 4000 at all. In fact, the Quadro 4000 is about eight years older than the Quadro RTX 4000.   And the Quadro 4000 is now long obsolete. Driver version 377.83 dates from all the way back in 2018 and is a security patched variant of a driver that came out in early 2017. Nvidia had completely discontinued all driver updates for all Fermi-architecture GPUs back in March 2018, with security updates lasting only until January 2019.  ... View more

An update:   The official release version 25.3 is now available. Currently, only Blackwell-architecture Nvidia GPUs support hardware 10-bit 4:2:0 and 10-bit 4:2:2 H.264 decoding, while hardware 10-bit 4:2:2 HEVC decoding is a first for Nvidia (Intel and Apple GPUs already support hardware 10-bit 4:2:2 decoding for HEVC). ... View more

Almost nine years too late for that response, I'm afraid. The GTX 1050 Ti was mediocre back in 2016, and is seriously outdated if not obsolete today. Newer versions of Premiere Pro hardware accelerate certain rendering features that older GPUs do not support, causing serious degradation of performance. ... View more

Ann is correct. Microsoft's support for Windows 10 will officially end (sunset) this coming October, and the Creative Cloud desktop frontend now requires or will soon require Windows 11 23H2 or later just to even install at all. In the meantime, the Creative Cloud desktop frontend app will remain installed, but will be permanently frozen to an older version which will not permit you to update your Creative Cloud apps to a version that's any newer than the version which was the latest at the time of that older app version's release. And if you uninstall the Creative Cloud desktop app, you will no longer be able to perform a clean installation of even the Creative Cloud desktop app, let alone the latest versions of the Creative Cloud programs.   In other words, you're stuck with older versions of the Adobe programs until you update your PC to Windows 11 or buy a new PC with Windows 11 pre-installed. ... View more

That would be a huge improvement for your PC. ... View more

Which exact Radeon GPU do you have? I cannot see the exact model in that screenshot.   And if that GPU is at 100% utilization, but you have only a 6-core 12-thread CPU, this may mean that you either cheaped out on the GPU model or are trying to decode heavily compressed hi-res footage that severely taxed the GPU's decoding capability. ... View more

The biggest problem with that workstation is simple: Its installed GPU is outdated. That Quadro M4000 is now almost a whopping 10 years old (and based on an architecture that's almost 11 years old) at this point, and it has been depreciated for CUDA support in newer drivers. Specifically, although CUDA is still supported in newer drivers for that GPU Nvidia is now concentrating on the RTX GPUs (initially sold as Quadro RTX, then just plain RTX and now RTX PRO) from this point going forward. That means the Quadro RTX (and the related T-series) GPUs are now the oldest generation to continue receiving CUDA updates. And all pre-RTX GPUs will soon fall into legacy driver support status.   What happened in your workstation was that renders in both After Effects and Premiere Pro called for hardware acceleration of certain features that older GPUs did not support at all, which resulted in the rendering of those features falling back onto the CPU in software-only mode or not rendered at all, which in turn negatively affected the overall performance score of that workstation. Worse, most of the effects that got sent to the CPU instead of the GPU are only single-threaded when software-rendered. In other words, both After Effects and Premiere Pro expected a CUDA Compute Capability version of 7.5 or higher, but that M4000's CUDA Compute Capability version was only 5.2 (and the compute capability version is completely separate from the CUDA driver version number). And you cannot change that at all in software; the version is permanently baked into the GPU hardware.   As a result, you really need a newer-generation GPU just to keep that Methuselah of a workstation competitive in performance, although that 11-year-old CPU platform will not come anywhere close to matching a recent-generation CPU platform in overall performance. ... View more

The problem with what you are wishing for is that it is impossible no matter what. Every single MP4 (H.264 and HEVC) encoder in existence always re-compresses video no matter what. The only feasible solution is in one of the replies: Set the bitrate as high as you comfortably can (this means higher than the bitrate of the source video) in order to minimize quality loss. ... View more

That's exactly what I meant. ... View more

The problem, in your case, is an OEM-customized Intel driver whose latest available version is several months old. And your laptop's OEM failed to update its drivers to a newer version (in all likelihood, the only available driver from Lenovo is a hardware launch-day driver). Worse, attempting to install a generic Intel graphics driver (available directly from the Intel Web site) results in either a warning message or an install error. ... View more

The excessive number of crashes indicate that your GPU may be failing. That degradation of your GPU may have been caused by continued use of a low-quality power supply unit (PSU), whose DC quality is so shoddy that it ends up being a PC component killer. And I would not trust, nor even purchase, a GameMax or GamePower branded PSU at all due to that brand being a scam. The strikes against GamePower/GameMax PSUs include review sample manipulation, paid positive reviews and downgrades in component quality during a given model's production run with absolutely no indication whatsoever. In other words, that so-called "1050W" PSU of yours might very well have been only a 450W unit - and then, your i7-14700K will draw more than 253W by itself off of that PSU! Coupled with the 290W power draw from your RTX 3070 Ti, and you might have very well exceeded the maximum realistic power capacity of that PSU!   That is a very common problem with building a higher-end PC such as yours. Go whole hog on the components but cheap out on the PSU. That's just plain foolish, IMHO.   Therefore, I would replace that PSU right away before you purchase a new GPU or continue using your PC. If you don't, more of your PC's components will die an ungraceful death. ... View more

You're officially out of luck. With the release of version 25.2 of Premiere Pro, the last remaining build of version 23, 23.6.8, became unavailable. ... View more

I am sorry to tell you this, but your Pentium Silver-branded CPU is of an older generation which is based on an architecture which has absolutely no AVX2 instruction support whatsoever. Those CPUs remained in production well into 2021.   What's more, the very last version of Premiere Pro that was compatible with a non-AVX2 CPU was version 23.x, which is now no longer available although version 23.6.8 remained available until the release of version 25.2, when it was finally dropped.   In this case, then, the only solution is an entire new PC. ... View more

Thread count is only indirectly proportional to the performance in the Adobe Creative Cloud apps. You also have to factor in the performance per thread, as well. And CPUs from different generations may have vastly different performance-per-clock and performance-per-thread results. ... View more