borine

> I found that opening the PCM channel can establish the SCO connection When using BlueALSA, that is in fact the **only** way to establish the SCO connection. There is...

> What do you think about renaming bluealsa.conf to org.bluealsa.conf? I think that is the "correct" name. The only backwards compatibility issue I can see with changing the name is...

A BlueALSA PCM can be opened by only one process at a time. So you cannot use `arecord -D bluealsa` or `ffmpeg -i bluealsa` when also running `bluealsa-aplay` because `bluealsa-aplay`...

The [troubleshooting guide](https://github.com/arkq/bluez-alsa/blob/master/TROUBLESHOOTING.md#4-couldnt-open-pcm-device-or-resource-busy) has now been updated to clarify this limitation

> pass BT audio from ba-aplay to the default sink in ALSA so `ba-aplay` is the application !! > some phones won't let you adjust the volume. I guess that...

It really depends on what `hw:0,1` is. For most soundcards, the playback stream for a device is on a different physical port to the capture stream of the same device....

> is it any other way ... to achieve this requirement ? Well, the simple answer is to use an audio server like pipewire or pulseaudio. If you are unable...

Sure, there are some notes on using the `snd-aloop` Loopback device with BlueALSA in the wiki here: https://github.com/arkq/bluez-alsa/wiki/Using-BlueALSA-with-dmix But, if I was building a system with the specific requirement to...

> why pipewire will be your choice than bluealsa Because the main issue discussed here is moving a running audio stream, uninterrupted, from one output device to another. This is...

> Do we have any audio player in pulseaudio like bluealsa-aplay ? I guess the nearest equivalent is the pulse module-loopback module or the pipewire libpipewire-module-loopback module. See the pulseaudio/pipewire/wireplumber...