Somebody said on GitHub that "Pipewire is the soon to be successor to
Jack/Pulseaudio".
I ran a quick search in this ML and couldn't find any mentions of it in
the last few years.
Is Pipewire viewed like this by the wider community? Does anybody have
experience using it?
https://pipewire.org/
Thanks,
Yuri
Hello all,
updates on <http://kokkinizita.linuxaudio.org/linuxaudio/downloads/index.html>
zita-jacktools-1.5.2
Fixed some bugs that made the class destructors segfault.
jconvolver-1.1.0
jmatconvol-0.4.2
Added -T option to fconvolver and fmatconvol, truncates
output file to input file size.
Ciao,
--
FA
Could someone please do a simple test on any Pipewire installation
set up to use/replace Jack (or shed any light on this).
If I run 'pw-record crontest.wav' it works fine, as expected.
If I run 'pw-cat 2> errrrr.txt' ditto, of course.
If I setup a user cronjob with 'crontab -e' to run the commands
(at the start of the next minute or so) the first does nothing,
while the second works.
Cron writes to /var/log/syslog like:
CRON[7694]: (john) CMD (pw-record crontest.wav)
rtkit-daemon[1277]: Supervising 7 threads of 4 processes of 1 users
(second line repeated)
--
John (older than 95.6% of the population).
> Maybe pipewire is not run by the same user than the cron job.
This was my initial idea, however what I think is more likely is that there
is no dbus session for the process to connect to.
Are you running PW as a user or system-wide?
On Tue, Jul 06, 2021 at 12:05:00PM +0200, Wim Taymans wrote:
> The pipewire daemon is meant to be small and modular. You could run
> a custom version of that with only what you want. It could possibly be
> smaller than jack.
Systemd started off like that as well... and now it has its tentacles
everywhere, and has become a nightmare to configure and for security.
Some questions:
* Will PW run without systemd, polkit, dbus ?
* Will it have a configuration that is fully controlled by the
end user, centralised in one place, and that is protected from
modification by just dropping files in some ***.d ?
> Is it more complicated? probably.. mostly the memory management and
> abstractions of the processing nodes.
> All of the desktop stuff (pulse-server) and autoconnect things
> (session-manager) are in separate processes that you don't need to run
> if you don't want to.
If this is going the work the same way as systemd I fear it will be
glorious pain to for the end used to remain in control.
--
FA