| commit | b0ab2ce256e1421d747f372f8bf1b15870c58683 | [log] [tgz] |
|---|---|---|
| author | Sam Zackrisson <saza@webrtc.org> | Tue Oct 16 10:48:40 2018 +0200 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Oct 23 07:44:09 2018 +0000 |
| tree | 19a71749b268b8b8f84fb4c7a2e3cd71de2eae07 | |
| parent | c9f9b8711fb2a1afb6f9789b4188e6a1474711bb [diff] |
Reland "Remove the HighPassFilter interface" Downstream Chromium dependencies fixed here: https://chromium-review.googlesource.com/c/chromium/src/+/1286449 This is a reland of e2405c1a823f3baf90a9c72f2e058f91eb659c20 Original change's description: > Remove the HighPassFilter interface > > The functionality remains unaffected. > Filter toggling is still available via webrtc::AudioProcessing::Config. > Example: > webrtc::AudioProcessing::Config config = apm.GetConfig(); > // Read settings > if (config.high_pass_filter.enabled) { ... } > // Apply setting > config.high_pass_filter.enabled = true; > apm.ApplyConfig(); > > Bug: webrtc:9535 > Change-Id: Ib4c4b04078bbb490ebdab9721b8c7811d73777a8 > Reviewed-on: https://webrtc-review.googlesource.com/c/102541 > Commit-Queue: Sam Zackrisson <saza@webrtc.org> > Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> > Reviewed-by: Per Åhgren <peah@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#25198} Bug: webrtc:9535 Change-Id: I0017193ad3ca1762e186f3ad79f29d33ef468202 Reviewed-on: https://webrtc-review.googlesource.com/c/106681 Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> Commit-Queue: Sam Zackrisson <saza@webrtc.org> Cr-Commit-Position: refs/heads/master@{#25300}
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.
Authoritative list of directories that contain the native API header files.