Configuring asoundrc for default bluetooth ignored for Internet Browsers? about bluez-alsa

[borine]

Any other ideas before posting a ton of logs and configuration files?

Bluealsa version 3.1.0 is 3 years old, please try release 4.2.0 before posting any logs because there are many bug fixes that you are missing.

apulse-0.1.13_2

original apulse does not work well with bluealsa. I have a fork borine/apulse with fixes that I used to use with Firefox on ubuntu before canonical spoiled the party by packaging Firefox as a snap. I haven't used it at all for a couple of years now, so I'm not sure if it still works with latest bluealsa.

chromium sort of works, but each tab runs in its own process, so only one tab at a time can open a bluealsa PCM. I would guess that other browsers have the same issue. I think that is why you see "device busy". Because of this I use my own fork of bluealsa with multi-client support borine/bluea-alsa successfully every day with chromium and get excellent results. I do not offer support for that, but you are welcome to try it if you wish. I do not use a ~/.asoundrc for chromium, I just use
chromium --alsa-output-device=bluealsa.

[rogerxxxx]

With chrome and chromium, if I'm not mistaken, seems the browser constantly queries/tests the ALSA playback device upon switching to it's Xorg/wayland window, every time. Long ago, I noticed aplay buffer under/over runs (or the likes) and did not initially notice this only occurring whenever switching to the xorg/wayland window containing chrome/chromium, or upon initially opening the browser. Took a long time to figure-out my problems with aplay staggered music playback! More heavy weight audio players tend to buffer the audio streams (eg. mplayer/mpv) averting the buffer under/over flows.

Some great tips for targeting my troubleshooting, versus just dumping everything at first. Give me a few months, as it's Summer and really busy.

Currently testing with Amazon.com Music/Cloud player, and all three or so Linux popular Internet browsers. Can likely temporarily close for now, or keep open. If I get something working, I will document/follow-up with the steps I took on this bug report.