On 2025-12-30 11:08:36 +0000, Barak A. Pearlmutter wrote:
> The underlying problem here is that system components (in this case
> some sound library) should not be playing "Wheel of Fortune" to figure
> out what hardware is available. "Can I have an R? Can I have a B?"
> That's what the config file is doing.
The presence of hardware is often dynamic. So probing the hardware
is useful in practice.
> But if it *does* play that game, "sorry no S" should not be an
> error; at most it should be an info-level log message.
Assuming that PortAudio uses the ALSA library correctly, I agree. But
this should not even be info-level log at all (I certainly do not want
such messages each time I start a PortAudio-based application).
Here, I have only one known sound card:
qaa:~> cat /proc/asound/cards
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x6189290000 irq 218
So I'm wondering why I get all these error messages with PortAudio.
BTW, aplay does not give me any error:
qaa:~> aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC289 Analog [ALC289 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
Is there some ALSA utility that would reproduce the errors as
obtained with PortAudio?
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
