From ea8c0f6fcbd79fd3933cf2f2511a8900c1a9344a Mon Sep 17 00:00:00 2001 From: Stefan Holmer Date: Wed, 13 Jan 2016 08:58:38 +0100 Subject: Fix capture ntp time issue introduced with r11187. 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} --- webrtc/call/call_perf_tests.cc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/webrtc/call/call_perf_tests.cc b/webrtc/call/call_perf_tests.cc index 86cd9ae072..3adcb10b09 100644 --- a/webrtc/call/call_perf_tests.cc +++ b/webrtc/call/call_perf_tests.cc @@ -405,6 +405,11 @@ void CallPerfTest::TestCaptureNtpTime(const FakeNetworkPipe::Config& 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, int time_to_render_ms) override { rtc::CritScope lock(&crit_); -- cgit v1.2.3