You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On latest mpd git (b1677bf), I can no longer properly control the volume of the alsa output (USB device)
If it is at zero, no sound as expected.
But as soon as I increase it to 5%, the alsa output is set to max volume. I can double check that in alsamixer where I can see the volume at 100% for that output.
So the volume is either null or at full volume, while mpd reports a volume at whatever percent it think it is. In my example, it reports it at 5%.
This is happening with mpc or mympd client, the same way.
This was working perfectly fine on 0.23.15
# part of my mpd.conf
audio_output {
type "alsa"
name "ALSA output"
device "hw:1,0" # optional
mixer_type "hardware"
mixer_device "hw:1"
mixer_control "Speaker"
mixer_index "0"
buffer_time "200000"
period_time "5084"
}
mpd is running on a rpi3b (armv7), 32bit, with archlinuxARM, linux 6.12.5, alsa-lib 1.2.13, alsa-plugins 1.2.12, and a USB card (Unitek Y-247A)
The text was updated successfully, but these errors were encountered:
On latest mpd git (b1677bf), I can no longer properly control the volume of the alsa output (USB device)
If it is at zero, no sound as expected.
But as soon as I increase it to 5%, the alsa output is set to max volume. I can double check that in alsamixer where I can see the volume at 100% for that output.
So the volume is either null or at full volume, while mpd reports a volume at whatever percent it think it is. In my example, it reports it at 5%.
This is happening with mpc or mympd client, the same way.
This was working perfectly fine on 0.23.15
mpd is running on a rpi3b (armv7), 32bit, with archlinuxARM, linux 6.12.5, alsa-lib 1.2.13, alsa-plugins 1.2.12, and a USB card (Unitek Y-247A)
The text was updated successfully, but these errors were encountered: