Revert "MediaStreamAudioSource: Organize audio processing layout calculations" This reverts commit d19b62789ed2f2ade012b822b3ed0bb117b27113. Reason for revert: Bug: 422611724 Bug: 405165917 Original change's description: > MediaStreamAudioSource: Organize audio processing layout calculations > > Introduces MediaStreamAudioProcessingLayout, which, > based on the requested AudioProcessingProperties and available device > effects, determines what processing should be done in WebRTC and what > should be delegated to the platform, as well as configures necessary > AudioProcessingSettings for WebRTC processing. > > A variety of decisions which used to be made in MediaStreamAudioProcessor::WouldModifyAudio() > ProcessedLocalAudioSource::EnsureSourceIsStarted() > AudioProcessingProperties::ToAudioProcessingSettings() > > are now combined under one roof. > No behavioral changes. > > Bug: 405165917 > Change-Id: Ib3dccc74a47cfede090bab539615175853543028 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6554248 > Commit-Queue: Olga Sharonova <olka@chromium.org> > Reviewed-by: Sam Zackrisson <saza@chromium.org> > Reviewed-by: Per Ã…hgren <peah@chromium.org> > Auto-Submit: Olga Sharonova <olka@chromium.org> > Reviewed-by: Dave Tapuska <dtapuska@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1463890} Bug: 405165917 Change-Id: I15cb27f17e4cdd81bfe472007172d53ca3871623 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6624364 Reviewed-by: Sam Zackrisson <saza@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/main@{#1471680}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.