On 2021-02-08 09:14, Max wrote:
Interesting thread. Out of curiosity: How does pipewire relate here? Since it claims to be a replacement for jack and pulseaudio but jack1 and jack2 coexist, does it replace jack1 or 2?
Pipewire implements the JACK API, similar to jackd v1 implements JACK API and jackd v2 also implements JACK API. Ideally any implementation of the JACK API should be interchangeable, with the choice based on what specific features each implementation provides. Pipewire also implements the pulseaudio API, which should help with people that would like to run normal system applications like a music player or web browser at the same time as applications which use jack (as well as implementing something similar for video applications). Note that pipewire is still in development, so is not yet considered ready for use in critical situations.
You should only run one JACK audio server at a time, so pipewire, OR jackd v1, OR jackd v2. Thinking of either of the three as specifically replacing one or both of the other JACK API implementations isn't quite accurate, although at one time some people thought jackd v2 would end up replacing jackd v1. For various reasons both continued in parallel, and that will likely be the same with pipewire, some distributions will switch to pipewire when it is mature, some will not, and some will provide ways to choose which implementation you want to use.
-- Chris Caudle _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx https://lists.linuxaudio.org/listinfo/linux-audio-user
