Reland Refactor reporting of VideoBitrateAllocation
Original description Move reporting of target bitrate to just after the encoder has been updated. Originall submitted as refs/heads/master@{#32275} Patch 1 contains the original cl ,patch 2 the fix to send rtcp even if BWE does not change. Bug: webrtc:12000 Change-Id: I16766e08229fe1f6f65f449e0e074bed03338693 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/186948 Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Per Kjellander <perkj@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32340}
This commit is contained in:

committed by
Commit Bot

parent
d9603b276b
commit
d0a8f51ef7
@ -267,6 +267,9 @@ class RTC_EXPORT VideoEncoder {
|
||||
|
||||
// Target bitrate, per spatial/temporal layer.
|
||||
// A target bitrate of 0bps indicates a layer should not be encoded at all.
|
||||
VideoBitrateAllocation target_bitrate;
|
||||
// Adjusted target bitrate, per spatial/temporal layer. May be lower or
|
||||
// higher than the target depending on encoder behaviour.
|
||||
VideoBitrateAllocation bitrate;
|
||||
// Target framerate, in fps. A value <= 0.0 is invalid and should be
|
||||
// interpreted as framerate target not available. In this case the encoder
|
||||
|
Reference in New Issue
Block a user