-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AV1 CBR padding function #11
Comments
#5 is maybe my mistaking it for a bug, because the lack of CBR padding in AV1. So, I think that the change of the default buffer size to 'TargetBitrate / 8' in 1.1.0.0_dev2 may not need. And, it is possible that (Target bitrate/fps) x (LookAheadDepth - 1) = 'minimal buffersize' |
Thanks for the Issue. I am aware of this problem, all the conditions for CBR Padding to work with AV1 were met on my part, but it did not work, so a week ago I contacted Intel and gave them all the information, at the moment I am waiting for feedback from Intel |
@ma3uk |
@ma3uk |
Yes, I know this method, but if you look at the content of the PR that you threw off, you can see that it is designed for a new generation of GPUs starting with integrated Lunar Lake GPUs and discrete Battlemage GPUs. |
@ma3uk |
CBR Padding feature is seemed to fill the remaining bitrate with meaningless information
so, bitrate on static screens doesn't drop much, so bitrate spikes are less
and as a result, even if the buffer size is large (target bitrate X 2), can achieve almost constant bitrate.
On H264 and HEVC, the CBR Padding feature is works (probably)
so bitrate spikes are very uncommon.
In AV1, the bitrate is reduced during static scenes
this cause more bitrate spikes than H264 and HEVC.
In the current state, for strict CBR in AV1, the buffer size must be extremely lowered
This means that there are losses in many places, such as lookahead quality and video quality.
The text was updated successfully, but these errors were encountered: