zqz/platform-external-webrtc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix capture ntp time issue introduced with r11187.

Browse Source 
I think the problem was that I only introduced delay in one direction, and the estimation assumes that the RTT is evenly divided between the send direction and the receive direction, which was true for the old test.

BUG=chromium:576246
R=pbos@webrtc.org

Review URL: https://codereview.webrtc.org/1577853005 .

Cr-Commit-Position: refs/heads/master@{#11233}
This commit is contained in:
Stefan Holmer
2016-01-13 08:58:38 +01:00
parent 365543d0e7
commit ea8c0f6fcb
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
webrtc/call/call_perf_tests.cc
View File

@ -405,6 +405,11 @@ void CallPerfTest::TestCaptureNtpTime(const FakeNetworkPipe::Config& net_config,
sender_call, this, test::PacketTransport::kSender, net_config_); sender_call, this, test::PacketTransport::kSender, net_config_);
} }
test::PacketTransport* CreateReceiveTransport() override {
return new test::PacketTransport(
nullptr, this, test::PacketTransport::kReceiver, net_config_);
}
void RenderFrame(const VideoFrame& video_frame, void RenderFrame(const VideoFrame& video_frame,
int time_to_render_ms) override { int time_to_render_ms) override {
rtc::CritScope lock(&crit_); rtc::CritScope lock(&crit_);