![]() ![]() In fact, none of the throttling or other flag type indications in HWINFO change during the event. The former may be mildly overclocked, the latter is not at all, just the default configuration from the motherboard. I also always see the "Current limit throttling" on two workstations with Skylake-X CPUs, one 7820X, another 7960X. Even buying an entirely new PC might have the exact same results, and would be a massive waste given that every bit of hardware is running perfectly.Thank you for escalating the issue. Cannot even suspect the Nvidia/AMD interaction since disabling hardware acceleration only leaves it working with AMD tech. Definitely not something that can be justified as insufficient hardware power.Īll that is left is a bug in Adobe or it's interaction with some piece of hardware. Again this is with 2 tracks of 1080p footage at any display quality (1, 1/2, 1/4, 1/8) and some simple transitions. I noticed that disabling hardware acceleration results in slightly better performance (because of the relatively heftier CPU) but still throttles out (this time at 50% CPU) weirdly. I tried footage that works fine on my other PC, and I reset the PC again for good measure. I've tried a 3080 card, different drivers, and older versions of Premiere. I have had the PC hardware professionally tested (down to the motherboard slots for everything) and every part works perfectly. So maybe if rjl pops in, he can give some specifics. All the working drives being SSDs, or coming from a massive RAID that has the internals and connections to sustained read/write well above 6Gbps. Even with a couple Nvme drives involved, it's better to have programs/OS on one drive, another drive totally dedicated to cache/preview files, and a third to projects/media. One drive is simply not going to work as well as multiple drives. But you only list one drive, and if that's all you're using, right there is a bottleneck in working with Premiere. ![]() In your computer, your CPU looks pretty decent, as is the GPU. Of course, GPU vRAM counts, and that card is pretty good.īut another massive area, is drive utilization. Karl Soule suggests a minimum of 2GB per CPU core, I've seen others suggest 4GB/RAM per CPU core. It's not one or the other, it's a balancing act. What I do know is enough to say your assumptions of how Premiere "views" the hardware are not actually correct. I can give decently solid but general comments. I'm not the best one around here to explain the intricacies of Premiere's hardware issues. Can I tell Premiere to only use 20% of the CPU thus creating an effective equality? Can I weight Premiere more heavily towards CPU? I've tried a number of similarly powerful GPU's to the same effect. I would take ANY solution to this nonsense. It is simply 2 overlapping video files, both at full size (no editing has been done yet). The other tracks at that point in the attached picture are empty. Premiere even continues to play audio after the timeline has been paused, and it continues to do so until the GPU has stopped having a heart attack (5 seconds after finishing all of the edited parts). ![]() Adding a second layer, or any transition, or any editing causes the playback to stutter and lag, with a framerate approaching 0fps. In practice this looks like Premiere struggling to play a timeline of a completely unedited piece of footage. So because the PC's power is heavily weighted towards CPU (an intentional choice given editing typically uses far more CPU than GPU), the GPU is unable to keep up with Premiere's demands and thus throttles the whole process. What I've gathered is that Premiere Pro scales the drain on the GPU by the power (and threads) of the CPU. It runs perfectly smoothly in every respect, but Premiere Pro is nearly impossible to use. I built a new Windows 10 PC with one of the goals being that it be capable of editing video. ![]()
0 Comments
Leave a Reply. |