Hello fellow Debian users,I wish I had better news for you but at this point in time PipeWire is not a replacement for JACK when it comes to pro-audio. Neither in terms of reliability, performance or features. It is certainly not something to use in a studio with paying customers, or live on stage.
There are still regular issues [1] coming up, configuration is still not easily accessible [2], freewheeling does not always work, and performance when using many clients is not yet equal to how JACK handles context-switches.
JACK is mature and reliable, musicians can trust it live on stage, pipewire is still under heavy development and sadly not yet ready for prime-time.
On the upside JACK and pipewire can co-exist. When jackd requests a device via d-bus, pipewire does (or should) release it.
At this point it is even unclear if JACK will be ever be discontinued. A recent discussion at [3] investigates the possibility to run pipewire on top of JACK, but that is a different story.
-- robinPS. I have been involved with development of both JACK, design of PipeWire and am developing pro-audio software such as Ardour (I am also a Debian user since Potato).
[1] https://discourse.ardour.org/t/ardour-inputs-with-pipewire/108489[2] https://discourse.ardour.org/t/how-does-pipewire-perform-with-ardour/107381/12 [3] https://lists.linuxaudio.org/hyperkitty/list/linux-audio-...@lists.linuxaudio.org/thread/I3BSVFO6DU7S2L7ATA7WOSDS7BTS4BPH/
On Sat, 15 Jan 2022 17:14:16 +0000 =?utf-8?Q?Cr=C3=A1udio?= <claudio...@protonmail.com> wrote:
Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attentioHi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention!Hi Chris, do you think Pipewire is stable enough for professional audio production? I've seen some reports that it fails at important moments... Thank you for your attention! Cláudio. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Em quinta-feira, 30 de dezembro de 2021 às 14:03, chris <inkbottle...@gmail.com> escreveu: > `pipewire` is providing its own replacement for `jack`, so if you are using `pipewire` maybe you should not have `jackd2` installed at all. > > I think I've done exactly the following: > > ``` > > aptitude --schedule-only install libspa-0.2-jack qsynth rosegarden; aptitude --schedule-only full-upgrade; aptitude install > > aptitude purge pulseaudio pulseaudio-module-bluetooth pulseaudio-module-gsettings > > aptitude purge qjackctl jackd jackd2 > ``` > > Then, to start an app needing `jack`, I did: > > `pw-jack qsynth` (don't forget to add a soundfont in `settups/soudfounts`) > > then: > > `rosegarden 28316.mid` (you must go in `studio/manage midi devices` and select a mdi output) > > And it worked. > > I'm using unstable. > > Right after switching to pipewire, I did: > > ``` > > aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries > aptitude purge pipewire-media-session > aptitude reinstall wireplumber > ``` > > Maybe as a user you should do: > > ``` > > systemctl --user --now disable pulseaudio.service pulseaudio.socket > > systemctl --user mask pulseaudio > > systemctl --user restart pipewire > ``` > > Maybe there should be a dependency conflict between `pipewire `and `jackd`? > > Also, concerning > > <q cite="https://wiki.debian.org/PipeWire#For_JACK";> >
OpenPGP_signature
Description: OpenPGP digital signature
