I thought PipeWire was supposed to be an implementation of the PulseAudio and JACK APIs, requiring no new public API. Disappointing.
noddy@beehaw.org
on 24 Aug 2023 13:19
nextcollapse
The qemu pulseaudio support wasn’t very good though. Very finicky to set up, and a lot of stuttering issues. Maybe this was an opportunity to implement something better with pipewire.
BautAufWasEuchAufbaut@lemmy.blahaj.zone
on 24 Aug 2023 14:44
nextcollapse
Pipewire offers different ways of interacting with it. There are compatibility layers for example for pulseaudio and Jack.
This is a good thing imo. That way you have compatibility, but aren’t held back by legacy interfaces.
LeFantome@programming.dev
on 24 Aug 2023 20:48
collapse
Not requiring and not offering are two different things.
threaded - newest
facepalm
xkcd.com/927/
I thought PipeWire was supposed to be an implementation of the PulseAudio and JACK APIs, requiring no new public API. Disappointing.
The qemu pulseaudio support wasn’t very good though. Very finicky to set up, and a lot of stuttering issues. Maybe this was an opportunity to implement something better with pipewire.
Pipewire offers different ways of interacting with it. There are compatibility layers for example for pulseaudio and Jack.
This is a good thing imo. That way you have compatibility, but aren’t held back by legacy interfaces.
Not requiring and not offering are two different things.