Pipewire output could use some love

[birdie-github]

Source

[jlindgren90]

@radioactiveman considering this and #1401, do you think it would be better to just use the PulseAudio plugin on systems with PipeWire? If I recall correctly, one of the goals of PipeWire was that applications could do exactly that -- continue to use the PulseAudio API without changes. Are there any downsides that you know of, to doing this?

The PipeWire API itself seems to have quite a learning curve* and I don't understand it well enough to address the concern/bug that wtaymans mentioned.

• To be fair, so do ALSA and PulseAudio, but that code is already written and pretty well-tested at this point.

[radioactiveman]

According to the issue reported by @birdie-github, the crackling also occurs with PulseAudio and mpv. So this is not specific to Audacious (and the PipeWire output plugin). #1401 is for me also not that critical so I would prefer it to "just" address the issues instead.

I will try to get in touch with the developers of PipeWire and Qmmp to fix it together.