> On 26/01/2022 17:08, Wim Taymans wrote:
First, let me give kudos to Wim for coming on the list and interacting
about this with the community! Much appreciated ;-)
[...]
Running PipeWire on top of JACK was something that was requested early
on because firewire audio support was broken in the
kernel and there was no other way to run that hardware otherwise. Now
that this is largely fixed, running PipeWire on JACK is
pretty pointless, confusing and no longer supported. I think I'm going
to remove it in some future version...
Speaking of PipeWire as a potential JACK replacement, what's the status
of JACK Transport? there are hints in the FAQ [1] and an old version of
the Wiki [2]
Am I the only one thinking that coupled with the more 'obvious'
inter-connect-ability of any (jack-enabled) application, JACK transport
is still a _really_ cool feature and one of the reasons I (maybe also
other people) really like doing music/audio with Linux, i.e. using 'any'
application you prefer to do a certain part of the job in both more
traditional and experimental creative set-ups?
Lorenzo
[1] https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ
[2]
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/JACK?version_id=003ca265e1dca550ed29e32245ce3c9230cde630
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
https://lists.linuxaudio.org/listinfo/linux-audio-user
