Making Sense of the Audio Stack on Unix

Re:Making Sense of the Audio Stack on Unix by oilbagz on Monday February 08, 2021 @03:51AM (#26062169)

Use a distro designed to make audio processing a first class service, and you'll never have to reboot again - i.e. kxStudio or Ubuntu Studio.

My Linux DAW easily outperforms my Mac DAW, and I have tens of thousands of buckaroos invested in the latter, but only a couple hundred in the former. Ubuntu Studio is simply the best out-of-the-box DAW user experience around.

>If you're writing audio software the solution is to use WASAPI on windows, CoreAudio on Mac, and tell Linux users to use Windows or MacOS if they want low latency audio.

This is nonsense advice. I'll instead tell Linux users to use a decent distro, and target JACK+Alsa for my Linux builds ...

[ Parent | on HN ]

Re:Making Sense of the Audio Stack on Unix by Papric0re on Monday February 08, 2021 @06:10AM (#26063083)

This! Still I totally understand the OPs point. It's a hassle to start with, especially using a general purpose distro. The interoperability of Jack and Pulse reminds me of Windows ASIO inabaility to utilize shared modes. Yes, there's the PulseAudio-Jack Bridge, but that one's really unstable.

So looking at Pipewire, let's hope for it to make Pro Audio and Consumer Audio interoperable on Linux. Because I really like the flexibility of Jack and the PulseAudio way of user experience.

[ Parent | on HN ]

Re:Making Sense of the Audio Stack on Unix by pjmlp on Monday February 08, 2021 @07:17AM (#26063495)

With the small difference that on Windows the other stacks are available and usually require no user setup to get going.

[ Parent | on HN ]

Re:Making Sense of the Audio Stack on Unix by hctaw on Monday February 08, 2021 @10:00AM (#26065340)

This includes attempting to use ubuntu studio. Still no joy, I have never gotten jack to work properly with relatively vanilla audio gear.

[ Parent | on HN ]