Let me guess...
Your MPE rendering settings for the project may have been set to OpenCL - but Adobe has permanently disabled OpenCL support for NVIDIA GPUs in all Windows versions of Premiere Pro to date. That means that in OpenCL rendering mode, only the Intel and AMD GPUs are used, with the weaker of the two GPUs (the Intel one) receiving a far greater load than the discrete AMD GPU. (Or, if your renderer is set to CUDA, then only the GTX 1060 is used since CUDA is restricted to NVIDIA GPUs; thus, neither the Intel nor the AMD GPU is used.) Plus, your source and/or export videos may have been in the H.264 format, which means that the Intel QuickSync hardware playback and/or encoding was activated since the integrated Intel GPU is enabled (so that the Intel GPU is used even with CUDA enabled for the GTX 1060).
In addition, the nearly maxed out CPU utilization implies that you have only a dual-core i3 CPU. Specifically, an i3-41xx series CPU, which is the only desktop CPU line that uses the Intel HD Graphics 4400 - and judging by the operating clock speed, an i3-4170 in particular. Higher-end Intel Haswell desktop CPUs have the HD Graphics 4600, which has more processing units. That i3-4170 CPU, as it turned out, is simply too weak to utilize even the Radeon RX 570, let alone the even more powerful GTX 1060, for GPGPU processing: Its software-only export time, when downrezzing HD content of a given length to MPEG-2 SD widescreen DVD, would have taken over 1,200 seconds (20 minutes), versus about 820 seconds (13 minutes 40 seconds) with a contemporaneous i5-4590 CPU and about 520 seconds (8 minutes 40 seconds) with a default-Turbo'd i7-4790K CPU. This imbalance is all too common in gaming PCs, which use practically the most powerful (for the total system budget) GPUs but weakling (relatively speaking) CPUs. And remember, for GPGPU work, no higher-end GPU can ever compensate for a weakling CPU (unlike for gaming).
1 Correct answer
3
Replies
AdChoices