Moving pulseaudio-qt to Frameworks

[Nicolas Fella]

Am 18.12.24 um 08:53 schrieb Sune Vuorela:
> On 2024-12-17, Nicolas Fella <nicolas.fella at gmx.de> wrote:
>> a few years ago I extracted parts of plasma-pa into a library to be able
>> to reuse them in KDE Connect. The result is the pulseaudio-qt library.
>> It has been independently released ever since.
> This might just be me not following fully along on the newest linux
> desktop audio trends but isn't pipewire the thing to use now?
>
> Or is pipewire providing and suggesting to use pulseaudio api instead of
> pipewire api?
>
> Or how is it nowadays?
>
> (I was stuck in jack-land for 4 years until recently-ish, so all of this
> might be obvious for everyone else)
>
> I do think that a <thing> that has a future, 3 or more users and are
> commiting to a stable api/abi does belong in frameworks.
>
> /Sune

Pipewire recommends using the PulseAudio API to interact with the audio
server, see
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ#what-audio-api-do-you-recommend-to-use

That means even if everyone is using Pipewire as the audio server the
Pulseaudio API is going to be relevant for the forseeable future.