• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Premiere ignores my bitrate settings

New Here ,
Dec 11, 2024 Dec 11, 2024

Copy link to clipboard

Copied

I always rendered my videos in Full HD, H.264 using VBR 1 (pass) at around  20-25 Mb and everything seemed to be okay, but at some point Premiere just started to ignore my export settings. Even when I set the max 50 Mb for Full HD, the outcome wouldn't get higher than 5-7 Mb, no mater what codec I chose. The size of my videos also didn't match the estimated size that Premiere suggested because of that. 

 

I also noticed that it never happened when I'd worked with simple and small projects with little to no effects/transitions/etc.; Premiere "ignored" the bitrate setting of much bigger, heavier and complex projects. 


I tried a lot of stuff and finally fixed it - I had to turn off the Hardware acceleration and use CBR instead of VBR (switching to CBR while still using HA didn't help, as well as using Software Acceleration with VBR; it only worked when I did both things at once). Now Premiere renders my videos with the bitrate I need, though it's much slower.

And though everything works more or less fine now, still. Can someone explain me why that possibly could happen?

TOPICS
Export , Hardware or GPU

Views

106

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Dec 11, 2024 Dec 11, 2024

Based on your description, this issue likely stems from the interaction between hardware acceleration and memory management during video encoding.

Here's what's probably happening:

When using Hardware Acceleration with VBR, The GPU handles both video processing and encoding.
Complex projects with many effects require more GPU memory and when memory becomes constrained, the encoder may automatically reduce bitrate to maintain stability, maybe this explains why simple projects worked fine while com

...

Votes

Translate

Translate

correct answers 1 Pinned Reply

Adobe Employee , Dec 11, 2024 Dec 11, 2024

Was your question answered by our expert, @Fifan_Ebusto0374? Please let us know.

 

Thanks,
Kevin

Votes

Translate

Translate
Community Expert ,
Dec 11, 2024 Dec 11, 2024

Copy link to clipboard

Copied

Based on your description, this issue likely stems from the interaction between hardware acceleration and memory management during video encoding.

Here's what's probably happening:

When using Hardware Acceleration with VBR, The GPU handles both video processing and encoding.
Complex projects with many effects require more GPU memory and when memory becomes constrained, the encoder may automatically reduce bitrate to maintain stability, maybe this explains why simple projects worked fine while complex ones had issues

Why switching to Software encoding with CBR fixed it?
Moving to CPU encoding removes GPU memory constraints, CBR provides more predictable memory usage patterns.
The CPU can access the full system memory, preventing bottlenecks
Though slower, it maintains the specified bitrate consistently

The reason both changes were needed is that Hardware acceleration alone would still hit memory limits even with CBR
Software VBR could still cause memory spikes that affect encoding
The combination ensures stable memory usage and consistent bitrate

The estimated size discrepancy occurred because Premiere's size estimation assumes ideal encoding conditions, not accounting for potential hardware limitations during actual export.

Possible solutions I would try->
1. Reduce project complexity by pre-rendering complex sequences
2. Increase your GPU's memory allocation for Premiere if possible
3. Split very complex projects into smaller segments for export

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 12, 2024 Dec 12, 2024

Copy link to clipboard

Copied

LATEST

That's a great explanation! I'm kind of okay with a bit slower render process, so I guess I won't change the setting for now, but it seems like things you described are indeed the root of my problem. I hope this thread will help somebody facing the same problem out there as well

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 11, 2024 Dec 11, 2024

Copy link to clipboard

Copied

Was your question answered by our expert, @Fifan_Ebusto0374? Please let us know.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines