commit | bd484e89de8bfda823fbd9101a32c94380be53fc | [log] [tgz] |
---|---|---|
author | Michael Wilson <mjwilson@chromium.org> | Tue Mar 28 20:19:10 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 28 20:19:10 2023 |
tree | 7a39f89d5df5759cf69f856b937669ced7491e68 | |
parent | f086e2a92e942256f4105d80d1b8a0b25ded1c7e [diff] |
Revert "Get sample rate from PulseAudio output device" This reverts commit a0e49851debcbc30e3fed7d1a39ad9e04981d5f9. Reason for revert: This change and its parent change (https://crrev.com/c/4129774) seem to completely break audio on multiple Linux distributions with some soundcard configurations (see https://crbug.com/1427137). Original change's description: > Get sample rate from PulseAudio output device > > This is a follow-up to crrev.com/c/4129774, and completes > output_device_id support in GetPreferredOutputStreamParameters(). > > It also adds the input_mainloop_ lock which was missed in the previous > CL. > > Bug: 1408574 > Change-Id: I81646fa617052a7359437430a53f05f704b33b98 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4181499 > Reviewed-by: Dale Curtis <dalecurtis@chromium.org> > Commit-Queue: Michael Wilson <mjwilson@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1094793} Bug: 1408574 Bug: 1427137 Change-Id: Ifa5375d4dd8b2d5766a800132b944431c1fa33b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4377511 Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Auto-Submit: Michael Wilson <mjwilson@chromium.org> Cr-Commit-Position: refs/heads/main@{#1123241}
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.