commit | 92594a30ce02aed75f8a2a9f21e5b8c5c4e5f199 | [log] [tgz] |
---|---|---|
author | minyue <minyue@webrtc.org> | Fri Dec 18 23:31:14 2015 |
committer | Commit bot <commit-bot@chromium.org> | Fri Dec 18 23:31:19 2015 |
tree | 1ea821ec482c80f290c1afe5666b9792fae0f7b5 | |
parent | 4ff818e61467f716340a43d30a970bcb5ec31ebf [diff] |
Moving FFT on farend signal to where it is used in AEC (bit exact). Currently, FFT is performance when AEC buffers farend signal. This has some drawbacks 1. memory inefficiency: two ring buffers are needed; 2. computation inefficiency: if ringbuffer gets wrapped around, some FFT computation will be wasted; 3. accessibility: the main AEC function looses accessibility to the time-domain signal. Therefore, this CL tries to buffer time domain data, which is buffered any way if a debugging macro is defined, and calculate the FFTs where they are actually used. BUG= Review URL: https://codereview.webrtc.org/1512573003 Cr-Commit-Position: refs/heads/master@{#11091}
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.