borine

As you have already found, you can get a list of sound card names by typing: $ cat /proc/asound/cards The first digit is the index of the card, the name...

The values entered in mpd,conf against "device" and "mixer_device" are just meaningless strings as far as MPD is concerned - as Max says, MPD just passes them on the the...

@crocket alsa documentation is notoriously sparse, ambiguous and incomplete. Often reading the source code is the only way to make sense of a feature. In this case, start reading here:...

You must not insert a backslash into the given control name. If `amixer` gives: ``` amixer scontrols ... Simple mixer control 'MISSION USB Audio 2.0 ',0 ... ``` Then your...

> probably trimmed by some internal routine. No, MPD does not "trim" or otherwise modilfy the given string in any way. The string you put in `mpd.conf` is the string...

closing due to lack of activity

closing due to lack of activity

I've just updated the wiki page https://github.com/arkq/bluez-alsa/wiki/PulseAudio-integration with information on how to disable pipewire bluetooth support. I still have not found any way to get the pipewire loopback module to...

The wiki page [Pipewire or PulseAudio Integration](https://github.com/arkq/bluez-alsa/wiki/PulseAudio-integration) is now complete, documenting the working setup that I now have with Ubuntu 24.04LTS (pipewire 1.0.5, wireplumber 0.14.17, bluealsa 4.2.0). I think there...

Assuming you are using ALSA applications, then you can avoid the need to use `bluealsa-cli` after every connection by defining a PCM with the desired codec configuration in ~/.asoundrc, for...