It's definitely a totally untested usecase, it has not been supported at all, or well, in the past, and there are most likely some issue that would require to go into the SC code. When Hanno back then inspected the question it actually looked like there might even be issues with ALSA itself (pulseaudio also builds on alsa). Try listing devices and setting the server to them via server options. I think you'll find that some don't work. This is quite definitely not something trivial to work with, and I'd ask: what is your/our goal when dealing with this? Among old users there is no interest in using portaudio/pulseaudio, it's simply considered non-pro with respect to latency. So not much support to expect from that side. When the Sonic Pi people came the interest was obvious: ease of use had a higher priority than low latency. Hanno went quite a few ways to understand the problems better, enquiring among portaudio people and, and at some point facing the view that there actually might be a ALSA issue portaudio can't get around. Maybe that was why he dropped out, or maybe he just lost interest in Sonic Pi.