Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
RjL190365
LEGEND
RjL190365
LEGEND
Activity
‎Dec 29, 2024
10:32 AM
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
‎Dec 25, 2024
10:47 AM
1 Upvote
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
‎Dec 24, 2024
07:38 AM
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
‎Dec 18, 2024
09:40 PM
1 Upvote
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
‎Dec 15, 2024
01:14 PM
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
‎Dec 14, 2024
04:32 PM
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
‎Dec 12, 2024
02:10 PM
1 Upvote
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
‎Dec 12, 2024
07:54 AM
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
‎Dec 10, 2024
04:51 PM
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
‎Dec 10, 2024
11:16 AM
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
‎Dec 10, 2024
09:49 AM
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
‎Dec 10, 2024
08:17 AM
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
‎Dec 08, 2024
02:48 PM
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
‎Dec 07, 2024
01:12 PM
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
‎Dec 07, 2024
10:18 AM
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
‎Dec 07, 2024
08:59 AM
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
‎Dec 06, 2024
02:59 PM
1 Upvote
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
‎Dec 05, 2024
08:22 PM
...on my main Intel i9-14900K system. The specs are: Intel i9-14900K 64 GB DDR5-6400 RAM GeForce RTX 4070 Ti 1 TB Samsung 980 PRO SSD (C: drive) 2 TB Samsung 980 PRO (D: drive) Windows 11 Pro 24H2 Premiere Pro 25.1 The integrated Intel UHD Graphics 770 is enabled on this system. I turned on and off hardware decoding and hardware encoding, and I also set the hardware decoder to Intel (Quick Sync) only or Nvidia (NVDEC) only. The hardware encoding is locked to Nvidia (NVENC) only or software only (Intel Quick Sync hardware encoding is not possible with a discrete non-Intel GPU installed). The overall results, in order from slowest to fastest (based on my PugetBench for Premiere Pro scores using the Standard preset): Nvidia hardware decoding enabled, hardware encoding disabled Nvidia hardware decoding enabled, hardware encoding enabled Both hardware decoding and hardware encoding disabled Intel hardware decoding enabled, hardware encoding disabled Hardware decoding disabled, hardware encoding enabled Intel hardware decoding enabled, hardware encoding enabled The result with Premiere Pro set to the default decoder and encoder settings was equal to that achieved with the Nvidia decoder enabled and hardware encoding enabled due to the default decoder setting, which was supposed to utilize both the Intel and Nvidia decoders, was broken in Premiere Pro 25.1. Please note that my findings are for my particular system only. If your system has a weaker CPU, then the hardware decoding performance will always beat software-only decoding. It just so happens that my i9-14900K is more than powerful enough to handle software decoding. If you have the chance to play around with the decoding and encoding settings, please share your findings in this discussion. Randall
... View more
‎Nov 24, 2024
07:02 AM
1 Upvote
I never neglected my mini-ITX system even though I have just recently updated my main PC from an Intel i7-12700K to an i9-14900K. Yesterday I decided to upgrade that mini-ITX system as well: Before, it had an AMD Ryzen 7 3700X, and updating it to a newer 5000-series CPU on a now-dead socket is proving to be economically unfeasible despite the reduced prices on the outgoing parts. So, I did an entire CPU platform upgrade to a B650 motherboard and a Ryzen 5 7600X CPU with 64 GB of DDR5-5600 RAM that had been pulled from my previous i7-12700K system (I upgraded to DDR5-6400 RAM when I did the i9-14900K update). The 7600X showed a nice improvement over the old 3700X.
... View more
‎Nov 20, 2024
11:29 AM
In case anybody is wondering, my current system (i9-14900K, RTX 4070 Ti) did not get exactly downgraded to an older driver per se, but Windows Update still kept attempting to download an older driver (in the past couple weeks, version 560.94, whereas previously it was version 528.24 when I first received the card) which would then fail to install. The only way to stop those multiple failed download attempts would be to already have a driver successfully installed via that Windows Update site before any newer Nvidia-direct driver gets installed on top of it (and not completely uninstalled as it would have with a clean install). Over time, those failed download attempts will eat up the boot drive's storage space, to the point that the boot drive becomes so full that Windows would fail to even start at all due to depleted disk space.
... View more
‎Nov 17, 2024
05:01 PM
In case you're wondering, you will need to update your system's Intel GPU driver to a newer version than the one that you have currently installed. Unfortunately, big-name OEMs such as HP have customized GPU drivers installed that will likely complicate the proper installation of a newer generic Intel graphics driver. Also, please note that Intel had depreciated all 7th- through 10th-Generation Intel CPUs (such as your laptop's 8th-Gen i5 or i7 Whiskey Lake CPU) to legacy graphics driver support, which means that there won't be any new features or compatibility fixes for newer versions of software while only critical security fixes will continue.
... View more
‎Nov 09, 2024
02:59 PM
I hear you. The CPU and GPU should be in relative performance balance for the best possible performance in workstation workloads. In my case, I waited until today (when that i9-14900K dropped to below $450 before sales taxes) to upgrade my PC from a 12th-Gen i7 to that aforementioned 14th-Gen i9. Everything else in my current build remains the same, including my now-trusty non-SUPER RTX 4070 Ti.
... View more
‎Oct 30, 2024
11:31 PM
2 Upvotes
I'm afraid that Peru Bob is correct in this case. That entire laptop is too weak by modern standards. And its Quadro P520 (there is no P250 at all) is so weak that it bottlenecks even the weakling CPU. Worse, the P520 has no hardware NVDEC decoder or NVENC encoder at all while the 10th-Gen Comet Lake U's integrated graphics is a gimped version of the integrated graphics that's inside most 10th-Gen desktop Comet Lake CPUs (with fewer render units and lower clock speeds to boot). Thus, all H.264 and HEVC decoding must go almost entirely to a CPU that is already struggling to keep up at all (plus, the integrated UHD Graphics 620 isn't of much help here). Worst of all, practically none of the internal components (CPU and GPU) is user-upgradable at all. As a result of these shortcomings, the only fix is a completely new system (desktop or laptop).
... View more
‎Oct 22, 2024
04:05 PM
It is a Windows issue. Newer builds of Windows 10, as well as all builds of Windows 11, no longer natively supports MPEG-2 video; third-party software and/or hardware or an optional Microsoft MPEG-2 codec plugin download from the Microsoft Store is now required for the OS to even recognize MPEG-2 files at all.
... View more
‎Oct 09, 2024
08:45 PM
What is the exact GPU with 16 GB of VRAM did you choose? You see, there are some graphics cards with 16 GB of VRAM that actually have lower-spec (and therefore less powerful) GPUs on them than some 8 GB oir 12 GB cards.
... View more
‎Oct 08, 2024
04:39 PM
2 Upvotes
Actually, the RTX 30 series supports only hardware decoding for AV1. The RTX 40 series introduced AV1 hardware encoding. AMD's RX 6000 series (except for the RX 6400 and RX 6500 XT) introduced that company's hardware AV1 decoding support. AMD's AV1 hardware encoding support is only available in the discrete RX 7000 series GPUs plus the enthusiast-level mobile Phoenix APUs.
... View more
‎Oct 08, 2024
09:53 AM
1 Upvote
For me, Resolve introduced a completely different set of issues. For one, its free version neither has a software H.264 or HEVC encoder at all nor can one be added in (unless one pays for the Studio version), and since it does not have a GPU hardware encoder at all the Windows version must rely solely on whatever encoder Windows itself natively has access to (which may be none at all and therefore cannot export to H.264 or HEVC on its own on such a system), depending on the system's software configuration. Secondly, Resolve (at least in its free version) does not support several older but still commonly used video and audio codecs at all, and therefore such media must be converted to another format using external third-party software before it can be imported into Resolve.
... View more
‎Oct 05, 2024
09:51 AM
At that price point you might be able to get a now-out-of-production GeForce GTX 1650, which is now just about the absolute bottom-performing GPU that is still supported by NVIDIA with new driver updates. With both NVIDIA and AMD now pretty much abandoning the low-end GPU market and only making higher-end GPUs which now start out at around Rs 25.000 or higher, the entry level is now completely left out in the cold.
... View more
‎Oct 04, 2024
09:27 AM
Unfortunately, you will not find one that's priced that low that is supported any longer by its manufacturer. Those GPUs (such as the GT 710 or GT 730) will be completely incompatible with any recent version of Premiere Pro because such cheapies are completely obsolete. That will result in Premiere Pro either running in a crippled software-only rendering mode (no GPU acceleration whatsoever) or refusing to run at all. The cheapest supported GPU will cost you at least quadruple (4 times) your stated budget.
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices