From 5fc130b0656fa54cc0c3e87875e2f57e649f7032 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Erik=20Spr=C3=A5ng?= Date: Wed, 4 Oct 2017 09:42:53 +0200 Subject: [PATCH] Make sure updated pacing factor is applied immediately. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bug: chromium:771346 Change-Id: I2d7116f0278a053b97944eccdb2d5f33ad9a5d84 Reviewed-on: https://webrtc-review.googlesource.com/6281 Reviewed-by: Philip Eliasson Commit-Queue: Erik Språng Cr-Commit-Position: refs/heads/master@{#20323} --- modules/pacing/paced_sender.cc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/modules/pacing/paced_sender.cc b/modules/pacing/paced_sender.cc index 96355b30c0..fc6a9f0f9b 100644 --- a/modules/pacing/paced_sender.cc +++ b/modules/pacing/paced_sender.cc @@ -359,6 +359,9 @@ void PacedSender::UpdateBudgetWithBytesSent(size_t bytes_sent) { void PacedSender::SetPacingFactor(float pacing_factor) { rtc::CritScope cs(&critsect_); pacing_factor_ = pacing_factor; + // Make sure new padding factor is applied immediately, otherwise we need to + // wait for the send bitrate estimate to be updated before this takes effect. + SetEstimatedBitrate(estimated_bitrate_bps_); } void PacedSender::SetQueueTimeLimit(int limit_ms) {