Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Enabling Hardware Acceleration for Rendering

  • Enabling Hardware Acceleration for Rendering

    Posted by Anton Zhuravka on February 7, 2022 at 2:17 pm

    Do I need to have a CPU with Intel Quick Sync feature supported in order to render with Hardware Acceleration enabled?

    I don’t have a CPU with Quick Sync (mine is Intel Core i7 9700KF, without integrated graphics), and the hardware acceleration feature for encoding is enabled to use. But, when I export the video to my computer, the bitrate changes to lower values. For example, if I choose CBR 50 mbps in the Premiere Pro render settings, I will have it rendered at around 4 mbps on my PC.

    Might this issue be connected with the fact that my CPU doesn’t support Intel Quick Sync?


    Anton Zhuravka replied 4 years, 7 months ago 2 Members · 2 Replies
  • 2 Replies
  • Tod Hopkins

    February 7, 2022 at 3:07 pm

    Not unless there is a bug in the software, and I DO see references to such bugs, i.e. output setting not matching actual output for various versions of Premiere.

    I’d still consider other explanations. For instance, the encode “Profile” setting can limit bitrate settings. Premiere does not allow infinite variation. Changing some settings after setting the bitrate can cause Premiere to reset the bitrate. Also make sure you are comparing apples to apples. For example, the CBR setting may limit the entire bitstream, video and audio. (I’ve never checked this in Premiere). I’ve had high-bitrate, multi-channel audio foul my back-of-the-envelope calculations. Also mixing “Mbps” and “MBps” can throw you by a factor of 8. That’s smaller than what you are seeing, but could be part of the explanation.

    Also, “constant bitrate” is not always constant in the absolute sense. We think CBR means that if a frame does not need the full allocation to encode, it gets padded with empty bits up to the limit. In practice, it’s more complicated than that and resulting streams do actually vary from encoder to encoder. If your stream is very simple (lot’s of black or solid color for instance), it would not shock me if the resulting file was not 50mbps over the entire file. The encoder simply determined it did not need that allocation. The stream is still “constant” but the encoder used far fewer bits than you allocated.

  • Anton Zhuravka

    February 7, 2022 at 3:44 pm

    Thank you for your answer. But, the thing is that it only happens when I render with the Hardware Acceleration feature enabled. If I decide to use Software Acceleration, the bitrate matches almost perfectly (I have no complaints to it), however, it takes much more time than using Hardware Acceleration.

    Do you happen to know what can cause the problem?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy