commit | 1c392cc5cf83630eaaa0401954b66149c1760ebc | [log] [tgz] |
---|---|---|
author | skvlad <skvlad@webrtc.org> | Fri Apr 01 21:46:44 2016 |
committer | Commit bot <commit-bot@chromium.org> | Fri Apr 01 21:46:54 2016 |
tree | 3d3e11565b9d4ad9f950f1e27d3cd78c53574ab5 | |
parent | 2d66cf9d8d5326029aaac1863acb8ccb9ae91db0 [diff] |
Avoid rescheduling the next RTCP packet if the RTCP sender status doesn't change. The change made in https://codereview.webrtc.org/1757683002 introduced an extra call to RTCPSender::SetRTCPStatus after the video receive stream is created. The SetRTCPStatus call results in no state change, as the RTCP sender is already enabled, however, it reschedules the next RTCP packet to be RTCP_INTERVAL_VIDEO_MS/2 (500) ms in the future. Before the change, the next packet time was only set by the previous call to RTCPSender::SetSSRC, which placed it 100 ms in the future. The change, therefore, changed the timing of multiple performance tests - as it now takes a different length of time to ramp up to the same bandwidth. BUG=chromium:597332 Review URL: https://codereview.webrtc.org/1826093004 Cr-Commit-Position: refs/heads/master@{#12203}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.