On Tue, 18 Jan 2022 08:08:56 -0800 (PST)
Len Ovens wrote:
>Pipewire does use all the system bits that puleaudio does, such as dbus
>and of course systemd. I do not think it will run without.
If it *requires* systemd then that is a non-starter for me :(
--
Will J Godfrey
On Tue, 18 Jan 2022, Will Godfrey wrote:
On Tue, 18 Jan 2022 08:08:56 -0800 (PST)
Len Ovens wrote:
Pipewire does use all the system bits that puleaudio does, such as dbus
and of course systemd. I do not think it will run without.
If it *requires* systemd then that is a non-starter for me
On Mon, 17 Jan 2022, Fons Adriaensen wrote:
I'd like to test pipewire as a replacement for Jack (on Arch),
How do I tell pipewire to use e.g. hw:3,0 and make all of
its 64 channels appear as capture/playback ports in qjackctl ?
Note: I do not have anything PulseAudio (like pavucontrol)
Hi Fons,
As a bare minimum you would need pipewire (the daemon) and
pipewire-jack (the libjack.so client implementation). With a custom
config file you can make this work exactly like jack (see below).
The way PipeWire normally works is that when starting the daemon,
nothing is in the graph.
On Mon, 17 Jan 2022 at 16:03, Lorenzo Sutton wrote:
>
> My problem with that set-up is that it seemed that something like Ardour
> would need to be explicitly run via pw-jack so e.g.
>
> pw-jack ardour
>
You distro probably also has a package that puts the pipewire
libjack.so in LD_LIBRARY
On Tue, 18 Jan 2022 19:16:39 +0100
Wim Taymans wrote:
>Hi Fons,
>
>As a bare minimum you would need pipewire (the daemon) and
>pipewire-jack (the libjack.so client implementation). With a custom
>config file you can make this work exactly like jack (see below).
Thanks for this info :)
--
Will
On Tue, 18 Jan 2022 at 17:15, Will Godfrey wrote:
> >and of course systemd. I do not think it will run without.
It does run fine without systemd.
>
> If it *requires* systemd then that is a non-starter for me :(
>
It doesn't require systemd.
You can compile with systemd support and then you
