27a457d172
This is a reland of https://webrtc-review.googlesource.com/34380 The main problem with that CL was that we used frame timestamps as basis for frame dropping, but those might not be continuous or even populated in some circumstances. Additionally, I found that the bitrate was off since the encoder does not not take the dropped frames into account, so if we drop every other frame continiusoly, the bitrate sent will be around half of the target. Patch set 1 is the original CL, subsequent patch sets cotains fixes. Bug: webrtc:4172 Change-Id: I8ec8dddcebf4ce44f28dd9055cf9c46bbd68e4a6 Reviewed-on: https://webrtc-review.googlesource.com/39201 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21601}
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.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct