Bugs, instability, crashing, latency .. compatibility issues, difficult to configure at first .. bluetooth audio is lower quality than it could be (AptX and LDAC codes unsupported) .. performance is not that great compared to pulseaudio and jack ..
> Therefore, I naturally omit the use and configuration of additional audio layers in the form of a Jack server, PulseAudio or the unfortunate PipeWire from RedHat.
I cannot understand this sentiment. I have used all three for years each. If I had to qualify one as "unfortunate", it would certainly not be PipeWire (nor would it be Jack for that matter).
> performance is not that great compared to pulseaudio and jack ..
Jack makes different trade-offs by default, so for some definition of performance, yes, one could see it as superior to PipeWire. But in my experience PipeWire is better than PulseAudio on all axes (at least: latency, CPU usage, resampling quality).
Not sure what you mean by this, aptX and aptX HD work flawlessly for my Bluetooth headphones with pipewire
I'm aware that performance is not quite as good as Jack (but not by significant margins AFAIK), but how is performance worse than PulseAudio? That cuts against every datum I've ever heard about the two.
Edit: pactl info | grep "Server Name"
Server Name: PulseAudio (on PipeWire 0.3.65)