New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
python3 -m sounddevice not listing pcms #446
Comments
Maybe. I don't know. The list of devices comes directly from the underlying PortAudio library, which currently doesn't have a proper PulseAudio backend yet (PortAudio/portaudio#336), so I guess it uses the ALSA emulation of PulseAudio. You could ask at the PortAudio project (http://portaudio.com/contacts.html) or at the PulseAudio project? As an alternative, you could try using JACK or PipeWire, maybe those support your device from |
I think there must be a limit maybe its the standard 32 of the kernel and some how we lose one and it ends as 30 :) I thought it was just hardware but maybe its pcms also and they are lost at the end of the list. If the alsa pulseaudio emulation it makes quite a hash of things as these are not pcm's they are plugins that could be used in pcm's and have often wondered why they are listed.
The above is a whole lot of pointless as they can not be used alone as they need to be part of a PCM. So prob you are right and there is a limit to the alsa pulseaudio device return which is strangely 32 -1 and the alsa pulseaudio returns pulse devices 1st but if you look it states everyone of those devices are alsa not pulseaudio? I think I will just have to find an alternative to sounddevice/portaudio |
Is there a method to list asound.conf pcms?
It will list everything else but the pcm I want to use (rate change)
Maybe it has something to do with Pulseaudio or there is a limit on devices returned?
Just tried a lite version on a pi3 that doesn't have pulseaudio running
All those are alsa pcms that just don't show on my x86 machine with pulseaudio / desktop install, but list fine on the pi
The text was updated successfully, but these errors were encountered: