5 ms·
>I remember in the days of kernel 2.2 that even XMMS would stop playing any music if I started using more than one or two applications. Back then the sound sub
by digi_owl 12y ago
>I remember in the days of kernel 2.2 that even XMMS would stop playing any music if I started using more than one or two applications.
Back then the sound subsystem didn't do any mixing or similar, so if some program grabbed /dev/snd, everyone else had to wait.
As for low latency sound work on Linux today, Jack is what you want rather than pulseaudio. Frankly Pulseaudio is a massive detour when it comes to Linux audio.
- rglullis 12y agoYeah, I mentioned aRTs but I was actually thinking of Jack (too late to change it). The annoying thing with these different sound systems is that it turns a general purpose workstation into an either/or proposition. - The applications that depend on pulseaudio were really not happy when jack was the sink. - Skype wouldn't work. - Because of the real-time requirements of the sound applications, everything else felt absolutely sluggish. - The volume control stopped working. All in all, I'd have to setup a separate system just to run jack-dependent applications.
- digi_owl 12y agoWell at least having Skype go Pulseaudio only prompted the creation of https://github.com/i-rinat/apulse https://github.com/i-rinat/apulse.
- BFay 12y agoPulseaudio has gotten a really bad rep, and I think there was at time where it was legitimately awful, but I think it's better than it was. On mainstream distros with pulseaudio like Fedora or Ubuntu, audio just works, when you don't have low-latency requirements. When you do have low-latency requirements, things are a bit tricky. You do pretty much need to get a low-latency or realtime kernel, and you definitely want to use Jack or ALSA. Maybe this setup is a little more frustrating than Windows, where you may just need to install one driver like ASIO4ALL. But it's flexible, and you can actually get Pulseaudio and Jack working pretty well together after installing the pulseaudio-module-jack. You can turn on jack when you need it, turn it off when you don't, and all of the pulseaudio stuff will get routed through it so that you don't lose sound from your other applications. If you want, you can route audio from pulseaudio into whatever other audio applications you're using - sometimes I like taking Youtube videos and routing the audio through weird effects in Pure Data. I toggle jack on and off with this little script, works pretty well for me right now: https://gist.github.com/YottaSecond/f0a1b515f95b2e791755 https://gist.github.com/YottaSecond/f0a1b515f95b2e791755
- aidenn0 12y agoUbuntu is the reason PA got a bad rap, and PA is an example of why I don't use Ubuntu. When Ubuntu adopted PA, the readme file still described it as "the sound server that breaks your audio" It was the most mature thing that had the features that Ubuntu wanted, so they adopted it despite the fact that it was clearly not yet ready for prime-time. That all being said, PA is not the choice if you want to do DAW style stuff; it tends to prefer lower cpu utilization to lower-latency.
- anon4 12y agoYou can actually layer pulseaudio on top of jack and have per-application volume controls, plus letting some applications output to your usb headset and whatnot; and also allowing pro-grade applications use jack directly, not bothering with any of the pulse nonsense at all.