Merge of Enforcing a stream delay of 0 to be assumed in the AEC on Chrome OS This CL forces the AEC2 to assume a stream delay of 0, thereby avoiding that the incorrect stream delays reported on Chrome OS causes echo issues. TBR=henrik.lundin@webrtc.org (cherry picked from commit 11556464a62ea14db9eee5e6c2a79a40aa1700ab) Bug: chromium:797274, chromium:797272 Change-Id: I10f295c9f1d735622c55fc56be99a14c6cdd88a2 Reviewed-on: https://webrtc-review.googlesource.com/36081 Reviewed-by: Per Åhgren <peah@webrtc.org> Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> Commit-Queue: Per Åhgren <peah@webrtc.org> Cr-Original-Commit-Position: refs/heads/master@{#21432} Reviewed-on: https://webrtc-review.googlesource.com/36220 Cr-Commit-Position: refs/branch-heads/63@{#14} Cr-Branched-From: bef8a5d2ca5413c680995584b8c0976852ba5f25-refs/heads/master@{#20237}
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.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.