| commit | c08c191f7d206dc0de945185370d18f29d556931 | [log] [tgz] |
|---|---|---|
| author | philipel <philipel@webrtc.org> | Tue Jan 17 04:03:53 2017 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Tue Jan 17 12:03:53 2017 +0000 |
| tree | a22d9e302b8319e7e4a2ea937ea60e09a9896bee | |
| parent | 6c0fd4341c85e84d78f9b99dc2ab5e4c3e04597d [diff] |
Revert of Make the new jitter buffer the default jitter buffer. (patchset #7 id:120001 of https://codereview.chromium.org/2627463004/ ) Reason for revert: Breaks android bots. Original issue's description: > Make the new jitter buffer the default jitter buffer. > > This CL contains only the changes necessary to make the switch to the new jitter > buffer, clean up will be done in follow up CLs. > > In this CL: > - Removed the WebRTC-NewVideoJitterBuffer experiment and made the > new video jitter buffer the default one. > - Moved WebRTC.Video.KeyFramesReceivedInPermille and > WebRTC.Video.JitterBufferDelayInMs to the ReceiveStatisticsProxy. > > BUG=webrtc:5514 > > Review-Url: https://codereview.webrtc.org/2627463004 > Cr-Commit-Position: refs/heads/master@{#16114} > Committed: https://chromium.googlesource.com/external/webrtc/+/0f0763d86d5d4e7f27e8dece02560e39c6da97d6 TBR=stefan@webrtc.org,terelius@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5514 Review-Url: https://codereview.webrtc.org/2632123005 Cr-Commit-Position: refs/heads/master@{#16117}
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.