On Mon, 15 May 2023, Michael Jarosch wrote:
Am 15.05.23 um 04:11 schrieb Len Ovens:
Pipewire has gotten around it because they don't use device interupts. They
can give jack clients whatever buffer size they like so long as the entire
buffer is big enough. That is probably not an entirely correct assesment.
All I know is that jack with ffado is rock solid.
What do you think: Will pipewire finally support ffado?
The last I heard, there are no plans to implement any Jackd backends in
PipeWire. That includes net, FFado etc. There is already an auto dummy
device in Pipewire, but I do not think it is as flexable as the jackd
dummy backend.
In theory, Pipewire should be able to use a running Jackd as a device.
There are some problems with this. Libjack must be one of jackd1, jackd2
or pipewire. If Pipewire is set up to act as jack, then starting
jackd(bus) will not work as planed because jackd will try to load
pipewire's libjack and fail. So jackd must be run from a script that first
resets the environment libpath to point at jackd's libjack before running.
I have not heard anyone who has said they have done this.
--
Len Ovens
www.ovenwerks.net
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx
