Thanks! I was afraid it would involve mucking about in configuration files. This application is sort of for end users - https://github.com/AlgoCompSynth/ChucK- ... m-Setup.md, so I really want the behaviour I had a couple of weeks ago with the latest trixie version of Pi OS: open up raspi-config in a terminal window, go into the "Advanced" menu 'Audio' option, select 'PulseAudio", and reboot. I'm guessing raspi-config did some systemctl commands under the hood; I could supply a bash script to do those as a worst case, but it would be nice if I could get it back in raspi-config.
Also, I'm curious about something else - PipeWire is supposedly emulating the PulseAudio daemon for the benefit of applications like this one - ChucK (https://github.com/ccrma/chuck) that haven't had time to port their code to PipeWire. I've seen a daemon running - why don't ChucK and some other applications see it and use it for their PulseAudio interface? Or am I misreading the PipeWire documentation?
Also, I'm curious about something else - PipeWire is supposedly emulating the PulseAudio daemon for the benefit of applications like this one - ChucK (https://github.com/ccrma/chuck) that haven't had time to port their code to PipeWire. I've seen a daemon running - why don't ChucK and some other applications see it and use it for their PulseAudio interface? Or am I misreading the PipeWire documentation?
Statistics: Posted by znmeb — Tue Nov 18, 2025 9:35 am