Run PipeWire on top of native JACK
Code: Select all
PipeWire can also run as a JACK client on top of the native JACK daemon if desired.
See JACK and PipeWire for more information.
Haven't tied this, but they state it's possible...
So this would fix a lot of scenarios/fears debated in this thread...
Also, Pipewire is still SO young, we are still at Version 0.3.x , far away from 1.0....
https://gitlab.freedesktop.org/pipewire ... ses/0.3.68
Code: Select all
The ALSA plugin has experimental support for IRQ based scheduling. This
should decrease latency for some (mostly USB) drivers. This should bring
latency within JACK latency. More work on this will be done before the
1.0 release later this year
They are working hard on it, give them some more time. Pulseaudio also had not the best reputation because of "too-early-release-desaster", alas that's how you are gonna find those nasty bugs in such a complex application without having a billion dollar company behind your back (as coreaudio had with Apple). And opposed to Pulseaudio it also does MIDI (and also Video)...
Pipewire for sure needs to mature a lot, it's in it's childhood.. But I am quite optimistic that it will be successful, it even seems we could have a 1.0 release that year I really like the comment where it was called an equivalent of coreaudio userspace part - if it can surpass that one on feature- and performance-level (and that's the goal), it could make a lot of people happy, if not, you apparently can still plug it into JACK
more fresh food on the topic: https://discourse.ardour.org/t/why-not- ... /108377/12
robin garaeus of ardour fame is currently less optimistic:
The actual problem that pipewire will fix is:
- to easily aggregate multiple soundcards
- provide seamless support when hotplugging devices
- have persistent names for sound-devices and ports (no more random order when using multiple audio or MIDI devices)
- support multiple buffer queues with different quality of service (allow to run low-latency Ardour and a high-latency Desktop sound app simultaneously)
That being said, I’m currently no longer convinced that the pipewire ecosystem will be the future. It became too complex, and ambitious with conflicting goals and repeated the mistakes pulseaudio made. It currently also does not scale as well as JACK, and as opposed to JACK also enforces policy.