* A2DP sound in ALSA vs PulseAudio
@ 2019-07-24 15:22 Marcel Brouillet
0 siblings, 0 replies; only message in thread
From: Marcel Brouillet @ 2019-07-24 15:22 UTC (permalink / raw)
I have enabled A2DP sinking on my Ubuntu 18.03 computer, and I am able
to stream sound from my phone to my PC. Pavucontrol sees a new device in
"Configuration", a new input in the "Input Devices" tab and a new item
in the "Playback" tab : "Loopback from xyz".
BUT there are no new devices shown in ALSA (result of aplay -l is
unchanged). It seems this is intentional by design, to only register the
new devices in Pulse Audio. I use Mixxx which lists ALSA devices.
Question : What is the best current way to get A2DP sound at ALSA level ?
I found relevant discussions :
referencing a BluezAlsa project.
Has any of the above been integrated in the core bluez (should I
recompile bluez with a config parameter) ?
Is there any advocacy against listing the devices in ALSA ? or any
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-24 15:22 A2DP sound in ALSA vs PulseAudio Marcel Brouillet
Linux-Bluetooth Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox