4 ms·
Pipewire allows any app to be an element on a patchbay: https://gitlab.freedesktop.org/ryuukyu/helvum https://gitlab.freedesktop.org/ryuukyu/helvum
by marcodiego 5y ago
Pipewire allows any app to be an element on a patchbay: https://gitlab.freedesktop.org/ryuukyu/helvum https://gitlab.freedesktop.org/ryuukyu/helvum
- PaulDavisThe1st 5y agoI know what Pipewire does ... I wrote JACK :) I was describing what macOS does not not allow, and that's routing audio between applications. When I say that, I don't mean that it is impossible - there are numerous tools (including JACK) that will allow it - but it doesn't come with just CoreAudio itself.
- marcodiego 5y agoThanks for writing Jack! I love the fact that I can play something in vmpk, render using qsynth, process in rackarrack and record directly in audacity. The routing feature alone sets Linux apart from the competition and I'm happy it influenced pipewire to implement it. Linux is already deployed in some commercial daws and it will soon be an RTOS. Hope music production will have more and better options because of this.
- PaulDavisThe1st 5y agoThere have been "RTOS" versions of Linux for more than 20 years. The current mainstream kernel already includes almost all of the RT_PREEMPT patch set that makes it more or less an RTOS if you want it to be.
- loxias 5y agoEchoing the parallel comment, if you're willing to get your hands into the guts, you can get amazing "RTOS-like" audio performance out of linux. I love pushing the limit of how low latency can get. Start with the PREEMPT_RT patches, be sure your irqs for audio are prioritized right, then experiment with pinning individual processes to specific cores, as well as locking their address space in memory.
- loxias 5y agoThanks for writing JACK! I'm curious what you think of PipeWire, feel free to be opinionated. I'm also a low level audio/midi dev (tho far less prolific, and less public) and having seen how you architect things, and your code, I'd value your opinion.