commit | eb648bf0e5a9bae185bcd6b4b3be371e1da3507d | [log] [tgz] |
---|---|---|
author | kjellander <kjellander@webrtc.org> | Mon Mar 07 17:56:26 2016 |
committer | Commit bot <commit-bot@chromium.org> | Mon Mar 07 17:56:34 2016 |
tree | 032feccddeba2d9d2d065b5329cd1f3daee11507 | |
parent | 96150a63224001c773bb62e7bba38ace02176827 [diff] |
Revert of Implement the NackModule as part of the new jitter buffer. (patchset #19 id:360001 of https://codereview.webrtc.org/1715673002/ ) Reason for revert: Unfortunately this breaks in the main waterfall: https://build.chromium.org/p/client.webrtc/builders/Android32%20Builder/builds/6362 I think it's related to dcheck_always_on=1 which is set in GYP_DEFINES only on the trybots, but not on the bots in the main waterfall. Original issue's description: > Implement the NackModule as part of the new jitter buffer. > > Things done/implemented in this CL: > - An interface that can send Nack (VCMNackSender). > - An interface that can request KeyFrames (VCMKeyFrameRequestSender). > - The nack module (NackModule). > - A set of convenience functions for modular numbers (mod_ops.h). > > BUG=webrtc:5514 > > Committed: https://crrev.com/f472c5b6722dfb221f929fc4d3a2b4ca54647701 > Cr-Commit-Position: refs/heads/master@{#11882} TBR=sprang@webrtc.org,stefan@webrtc.org,terelius@webrtc.org,torbjorng@webrtc.org,perkj@webrtc.org,tommi@webrtc.org,philipel@webrtc.org BUG=webrtc:5514 NOTRY=True Review URL: https://codereview.webrtc.org/1771883002 Cr-Commit-Position: refs/heads/master@{#11887}
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.