commit | a421ddd60eb15a19b675ceaa4e241bd15cc86f8e | [log] [tgz] |
---|---|---|
author | peah <peah@webrtc.org> | Mon Sep 12 18:27:14 2016 |
committer | Commit bot <commit-bot@chromium.org> | Mon Sep 12 18:27:20 2016 |
tree | da7f444afba9641271147e41623008eb12339dd8 | |
parent | b3f7876a95d266db68011e47994772a95d6ac97c [diff] |
The buffering of the farend signal is refactored in this CL. The former buffering scheme was overly complicated and complex as. -It buffered twice as many data points as needed. -It used the ring_buffer C functionality directly inside the delay adjustment functionality which makes that functionality very hard to read. In order to overcome these problems this CL does -Change the buffering to buffer only the amount of samples needed. -Wrap the ring_buffer C functionality in a wrapper class with methods that are more descriptive in what they do to affect the AEC delay. Additional notes: -Some minor other name changes/code changes were also introduced. -The ringbuffer C functionality should be removed, but now is not the time to do it as the rest of the code is very adapted to the wrapping behavior of the ringbuffer. It is better to simplify the surrounding code before doing that. The changes have been tested to be bitexact. This CL is chained to the CL https://codereview.webrtc.org/2321483002/ and will be followed by another CL. BUG=webrtc:5298, webrtc:6018 Review-Url: https://codereview.webrtc.org/2319693003 Cr-Commit-Position: refs/heads/master@{#14188}
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.