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
In general, multiple running PortAudio applications should be able to list available devices. There is no known limitation to doing this on Linux with ALSA.
To Reproduce
Replace device("CODEC") with device(<identifiable part of your sound card's name>) in the following code. Then compile it and run it twice in different shells. The second shell lists no devices. But I think basically you can run any application that uses portaudio in one shell and then another application that uses portaudio in a second shell to reproduce this issue.
I tried to reproduce this. I booted an RPi4 running
Linux neuhaus98 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
entered:
cd portaudio
./configure && make
bin/pa_devs
bin/paex_sine
While paex_sine was running, I entered "bin/pa_devs" is a second window.
When paex_sine is running I get all the same devices except the dmix device!
I also noticed dmix "unable to open slave" right before the PortAudio version was printed.
That was not printed when paex_sine was not running.
Pa_GetDeviceCount()
returns 0 (zero) when another application that uses PortAudio is running.[Originally reported by @nodemand during #870, when written in first person the description below is quoted from @nodemand in #870]
Expected behavior
In general, multiple running PortAudio applications should be able to list available devices. There is no known limitation to doing this on Linux with ALSA.
To Reproduce
Replace device("CODEC") with device(<identifiable part of your sound card's name>) in the following code. Then compile it and run it twice in different shells. The second shell lists no devices. But I think basically you can run any application that uses portaudio in one shell and then another application that uses portaudio in a second shell to reproduce this issue.
Code:
Actual behavior
The second shell lists no devices.
Additional context
I checked #804 and adding
arm_64bit=0
to/boot/config.txt
on Bullseye and rebooting does not give me any devices. Still 0.At one stage, prior to realising that it is an issue with multiple concurrent PortAudio apps, @nodemand wrote:
The text was updated successfully, but these errors were encountered: