What's the current problem with Pipewire? Pulse (for simple audio stuff) and Jack (for low latency stuff) integrations both work fine for me, so I'm wondering what problems you've run into recently are.
Though honestly, on Linux I just use ALSA for everything and don't think about it after that. By definition neither Jack nor Pipewire can be faster than the ALSA they are talking to.
> By definition neither Jack nor Pipewire can be faster than the ALSA they are talking to.
Sure, but that's like saying that you don't need an operating system when you can compile to baremetal. Both Jack and Pipewire are slower, but offer pretty substantial routing options on top of that. Furthermore, I believe both protocols support ALSA connections too.
I use Bitwig on NixOS and it's not too bad with PipeWire. Latency and routability generally rivals CoreAudio, which is good enough for me.
And I don't want to sound like I'm dumping on Pipewire; I think the work Wim has been doing is absolutely awesome and (unlike a lot of what FDo puts out) actually solves existing problems rather than hypothetical ones. It's just not quite (yet) what I need as a DJ and looper.