if the volume device is "alsa", force using ALSA PulseAudio emulation #29
Conversation
| @@ -447,6 +447,8 @@ default is used. If the device string is missing or is set to "default", | |||
| PulseAudio will be tried if detected and will fallback to ALSA (Linux) | |||
| or OSS (FreeBSD/OpenBSD). | |||
|
|
|||
| To force PulseAudio using ALSA emulation, use "alsa" as the device name. | |||
There was a problem hiding this comment.
I don’t understand this sentence. Which API will be used when specifying “alsa” and why is it necessary to have this special case?
There was a problem hiding this comment.
You could already force using the ALSA API by using any device name other than "pulse", "default" or missing value. The problem is that the ALSA device name for the PulseAudio backend is also "pulse", so there's no way to force using it. This is one way to address this problem.
There was a problem hiding this comment.
Okay, but why would you want to enforce using ALSA when you’re using PulseAudio via ALSA’s PulseAudio backend anyway? I don’t see the point in that.
There was a problem hiding this comment.
I suppose to mimic the old behaviour, without the thread wakes, etc. A vague reason, admittedly.
There was a problem hiding this comment.
The reason I suggested it was to mimic the old behaviour since I never had problems with muted volume then. #28 however fixed that problem.
There was a problem hiding this comment.
OK, closing pull request.
The ability to force using the "pulse" ALSA device (using PulseAudio through ALSA emulation) was missing. This patch makes that possible by specifying the device "alsa".