|
|
|
|
|
by ofalkaed
164 days ago
|
|
PipeWire seems to solve all the audio stuff for me, zero problems since I made the switch. I had audio fail on resume once when I first installed PipeWire; if memory serves it was that the default settings for PipeWire was to restart the audio server on resume which screwed things up because Jack kept running. Something like that. The fix was simple, just comment out a line and uncomment another. Everything audio has just worked ever since. I have not had any UI issues in at least a decade on Slackware. The few times I tried Mint over the years, it was filled with random annoyances like you mention. Edit: This is not advocating using Slackware for audio work, it works great but it is Slackware and most don't get along with the Slackware way. But there is a DAW module for AlienBob's Slackware Live Edition[0]. It worked alright when I tried it, as well as any other live distro. [0] https://docs.slackware.com/slackware:liveslak |
|
But generally that's my point, 'it works if you go and edit this obscure line in this obscure config file'. Mac has had a stable CoreAudio backend for quarter of a century now (counterpoint - Windows is also a mess). I wish Linux would stabilise their userland a bit more and stop rewriting stuff every few years.
Sometimes I wish there was a commercial company behind 'linux for audio' that will give me a finely tuned Linux distro on a finely tuned desktop machine, based on whatever distro, I don't really care. But have it all released/patched at their own pace, as long as everything 'just works'. I'd be happy to pay for that. The whole 'OS due upgrade, is anything going to work tomorrow, I have a session' is still an unsolved problem on _every_ OS/platform. Most busy studio heads go years without installing/upgrading _anything_ for fear of having a lemon after said upgrade, with clients waiting at the door.