Remove SendPacer from ViEEncoder and make sure SendPacer starts at a valid bitrate
This reverts commit e30c27205148b34ba421184efe65f6a0780b436d (https://codereview.webrtc.org/1958053002/) Original reverted cl is in patch set #1. Changes in following patch sets. The cl now also make sure SendPacer starts with the configured bitrate provided in a call to CongestionController::SetBweBitrates)() It turns out that the failing tests in 609816 is due to a bug in the current code that runs the proper at 300kbit regardless of configured start bitrate. Original cl description: Remove SendPacer from ViEEncoder This CL moves the logic where the ViEEncoder pause if the pacer is full to the BitrateController. If the queue is full, the controller reports a bitrate of zero to Call (and BitrateAllocator) BUG=chromium:609816, webrtc:5687 TBR=mflodman@webrtc.org NOTRY=True // Due to bug in android_x86 cq builder.... Review-Url: https://codereview.webrtc.org/1958113003 Cr-Commit-Position: refs/heads/master@{#12688}
This commit is contained in:
@ -14,11 +14,16 @@
|
||||
#include "testing/gtest/include/gtest/gtest.h"
|
||||
|
||||
#include "webrtc/modules/bitrate_controller/include/bitrate_controller.h"
|
||||
#include "webrtc/modules/pacing/mock/mock_paced_sender.h"
|
||||
#include "webrtc/modules/rtp_rtcp/include/rtp_rtcp_defines.h"
|
||||
|
||||
using webrtc::RtcpBandwidthObserver;
|
||||
using webrtc::BitrateObserver;
|
||||
using ::testing::Exactly;
|
||||
using ::testing::Return;
|
||||
|
||||
using webrtc::BitrateController;
|
||||
using webrtc::BitrateObserver;
|
||||
using webrtc::PacedSender;
|
||||
using webrtc::RtcpBandwidthObserver;
|
||||
|
||||
uint8_t WeightedLoss(int num_packets1, uint8_t fraction_loss1,
|
||||
int num_packets2, uint8_t fraction_loss2) {
|
||||
|
||||
Reference in New Issue
Block a user