>There's a lot of painful voodoo, competing control systems and legions of mostly out-dated forum threads of dead-ends, anecdotal advice, misinformation. I'm ho

>There's a lot of painful voodoo, competing control systems and legions of mostly out-dated forum threads of dead-ends, anecdotal advice, misinformation. I'm hoping that the next Ubuntu Studio will Just Work on the laptop that I have put aside for it and that I won't have to waste more time in the Pulse/Alsa/Jack soup. I've had a lot of success using kxstudio https://kx.studio/ https://kx.studio/ Along with cadence to manage Jack and alsa and Catia/Claudia for managing studios and ladish sessions. It can be installed on top of an existing Ubuntu based system without much trouble and after setting it up it works flawlessly for me. I've been using this setup for a few years now. >legions of mostly out-dated forum threads of dead-ends, anecdotal advice, misinformation I completely agree with this. Any guide that still recommends qjackctl or manually fucking around with alsa and midi bridges should be completely disregarded. There's zero reason to need to do this any more and there hasn't been for at least half a decade now. It's really too bad, honestly the flexibility offered by Jack and the huge range of audio software on linux allows for workflows I'd never been able to do on windows. It's pretty much the entire modular linux philosophy applied to making music and it's closest i've come to the same kind of workflow you get with hardware equipment. Just fiddling around with different plugin routings can give you some pretty cool sounds that can be patched into any Jack aware software you have.