admin/webrtc_m130
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Make sure updated pacing factor is applied immediately.

Browse Source 
Bug: chromium:771346
Change-Id: I2d7116f0278a053b97944eccdb2d5f33ad9a5d84
Reviewed-on: https://webrtc-review.googlesource.com/6281
Reviewed-by: Philip Eliasson <philipel@webrtc.org>
Commit-Queue: Erik Språng <sprang@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#20323}
This commit is contained in:
Erik Språng 2017-10-04 09:42:53 +02:00 committed by Commit Bot
parent 6bf70d20da
commit 5fc130b065
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
modules/pacing/paced_sender.cc
View File

@ -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) {