Use system loopback as AEC reference depending on settings flag

This makes the AudioService use the `use_loopback_aec_reference` flag in
AudioProcessingSettings to decide if chrome-wide AEC or loopback AEC
should be used. (this flag used to be `needs_loopback_aec_reference`,
this CL renames it to `use_loopback_aec_reference`.

This changes the role of the SystemLoopbackAsAecReference flag. Instead
of forcing the use of loopback AEC (which was the previous behaviour),
it now only decides if LoopbackReferenceManager should be created.

To still allow us to test loopback AEC, we now add an option to force
the use of loopback AEC to the command line. Specifying
`--enable-features=SystemLoopbackAsAecReference:forced_on/true` now uses
loopback AEC whenever chrome-wide AEC would be used.

Note that this CL is intended to be landed after
https://chromium-review.googlesource.com/c/chromium/src/+/6670033

Bug: 415954529

Change-Id: I6dfcf4f8692e8d311998433c5e51ae819618a5cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6668134
Reviewed-by: Colin Blundell <blundell@chromium.org>
Commit-Queue: Fredrik Hernqvist <fhernqvist@google.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1479730}
11 files changed
tree: d3ca9327a3733aebb036b5c77bfdfe5ebb36f5f4
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .cursorignore
  53. .git-blame-ignore-revs
  54. .gitallowed
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. CPPLINT.cfg
  69. CRYPTO_OWNERS
  70. DEPS
  71. DIR_METADATA
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. SECURITY_OWNERS
  80. WATCHLISTS
README.md

Logo Chromium

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.