3 ms·
Another problem with PulseAudio is with latency and routing, which is why a lot of professional audio programs on Linux use JACK instead of PulseAudio. It's som
by oakwhiz 13y ago
Another problem with PulseAudio is with latency and routing, which is why a lot of professional audio programs on Linux use JACK instead of PulseAudio. It's sometimes very hard to get JACK to play nice with PulseAudio, and this is exacerbated by the fact that ALSA only allows one program to use one audio device at a time. So it doesn't always "just work"...
- marshray 13y agoIsn't it kinda the kernel's job to allow multiple processes to access shared resources? Imagine if only one process at a time were allowed to access the disk.
- Daishiman 13y agoResources that require low-latency low-level access cannot be multiplexes easily
- Shish2k 13y agoSo have multiplexing desktop mode by default, and give pros a "reduce my latency" button?
- marshray 13y agoWhy couldn't the kernel perform simple mixing of the audio streams with just as low latency as something like JACK?
- oakwhiz 13y agoI've heard that you can get PulseAudio to connect to JACK, which in turn connects to ALSA. The idea here is that latency-sensitive applications that use routing will connect to JACK, while applications that connect to PulseAudio (like Skype, Firefox, etc.) don't care about latency. However I haven't been able to get this to work properly (why isn't this set up as the default on any of the distros I've tried this on?)