Move BitrateAllocation to api/ and rename it VideoBitrateAllocation
Since the webrtc_common build target does not have visibility set, we cannot easily use BitrateAllocation in other parts of Chromium. This is currently blocking parts of chromium:794608, and I know of other usage outside webrtc already, so moving it to api/ should be warranted. Also, since there's some naming confusion and this class is video specific rename it VideoBitrateAllocation. This also fits with the standard interface for producing these: VideoBitrateAllocator. Bug: chromium:794608 Change-Id: I4c0fae40f9365e860c605a76a4f67ecc9b9cf9fe Reviewed-on: https://webrtc-review.googlesource.com/70783 Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Niels Moller <nisse@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22986}
This commit is contained in:
@ -294,8 +294,8 @@ void RtcpTransceiverImpl::HandleTargetBitrate(
|
||||
remote_sender_it->second.observers.empty())
|
||||
return;
|
||||
|
||||
// Convert rtcp::TargetBitrate to BitrateAllocation from common types.
|
||||
BitrateAllocation bitrate_allocation;
|
||||
// Convert rtcp::TargetBitrate to VideoBitrateAllocation.
|
||||
VideoBitrateAllocation bitrate_allocation;
|
||||
for (const rtcp::TargetBitrate::BitrateItem& item :
|
||||
target_bitrate.GetTargetBitrates()) {
|
||||
if (item.spatial_layer >= kMaxSpatialLayers ||
|
||||
|
||||
Reference in New Issue
Block a user