3 ms·
I'm curious what you think of PipeWire: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance https://gitlab.freedesktop.org/pipewire/pipewire/-
by uep 6y ago
I'm curious what you think of PipeWire:
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Per...
It claims to get near Jack latency, while implementing a more generic audio graph with better security than PulseAudio.
In regards to Linux scheduler performance, do you have any experience with SCHED_DEADLINE?
- PaulDavisThe1st 6y agoWe don't use SCHED_DEADLINE with audio, because things are driven by hardware interrupts/requirements, which makes SCHED_FIFO more appropriate ("wakeup! time do the work! right now! until it's done!"). macOS doesn't really have SCHED_FIFO, so we end up forced to use something to deadline scheduling there. It works fine. I commented a lot on PipeWire when it started. Thankfully Robin Gareus and others managed to get its developer to change course somewhere along the journey to use a better basic model (notably, pull not push). I no longer follow its development. If it works, it will be good for Linux audio. I don't know if it will, or won't. [for anyone who doesn't know, I'm the original author of JACK]
- afwaller 6y agoHey, thanks for all your work.