This article nails my meeting with #LinuxAudio: "Many existing guides and tutorials still assume PulseAudio or JACK are in use, which can confuse new users trying to follow them.
-
This article nails my meeting with #LinuxAudio: "Many existing guides and tutorials still assume PulseAudio or JACK are in use, which can confuse new users trying to follow them. Some tools haven’t been fully updated with PipeWire in mind, leaving people to dig through forums for answers. While these resources are catching up, the gap can still frustrate less experienced users. It’s part of the growing pains that come with a significant shift in Linux infrastructure."
https://www.xda-developers.com/goodbye-to-linux-audio-headaches-pipewire-simplifies-everything/
-
This article nails my meeting with #LinuxAudio: "Many existing guides and tutorials still assume PulseAudio or JACK are in use, which can confuse new users trying to follow them. Some tools haven’t been fully updated with PipeWire in mind, leaving people to dig through forums for answers. While these resources are catching up, the gap can still frustrate less experienced users. It’s part of the growing pains that come with a significant shift in Linux infrastructure."
https://www.xda-developers.com/goodbye-to-linux-audio-headaches-pipewire-simplifies-everything/
@mosgaard Good point on documentation. That's going to be something going to bite users for a long time - until docs are being updated or clearly marked deprecated/outdated.
And as @PaulDavisTheFirst proved me wrong yesterday, there's a lot of misconceptions and misunderstanding - due to the inherited confused mess from prior days. I owe him an apology and a big thanks for his patience educating me on how Pipewire fits in the stack, in a JACK context. I was clearly wrong. Now I have a better understanding - which helps my further investigations on my latency challenges.
-
J jwcph@helvede.net shared this topic
