You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The resulting bitrate corresponds to the indicated in the settings.
Current Behavior
The resulting bitrate does not even closely correspond to the indicated in the settings. For example, I set 6 Mbps. In simple scenes bitrate will be ~20 Mbps, in complex ~140 Mbps. This is displayed both in the Stats window and in the properties of the resulting file.
Steps to Reproduce
Output Mode - Advanced
On Recording tab:
Video Encoder - AMD HW H.264 (AVC)
Rate Control - HQCBR or HQVBR
Bitrate - 6000 Kbps
It seems the rest of the settings does not affect this.
Start Recording
Anything else we should know?
AMD Adrenalin version 24.5.1
The problem is present only with AVC. HEVC and AV1 work as expected.
This behavior is very similar to CQP ~20. Clarification: CQP value displayed in the log is not related to this problem.
The text was updated successfully, but these errors were encountered:
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/pEvB87fs4SfOBF33
OBS Studio Crash Log URL
No response
Expected Behavior
The resulting bitrate corresponds to the indicated in the settings.
Current Behavior
The resulting bitrate does not even closely correspond to the indicated in the settings. For example, I set 6 Mbps. In simple scenes bitrate will be ~20 Mbps, in complex ~140 Mbps. This is displayed both in the Stats window and in the properties of the resulting file.
Steps to Reproduce
Video Encoder - AMD HW H.264 (AVC)
Rate Control - HQCBR or HQVBR
Bitrate - 6000 Kbps
It seems the rest of the settings does not affect this.
Anything else we should know?
AMD Adrenalin version 24.5.1
The problem is present only with AVC. HEVC and AV1 work as expected.
This behavior is very similar to CQP ~20. Clarification: CQP value displayed in the log is not related to this problem.
The text was updated successfully, but these errors were encountered: