I've tried to embrace some of these new #linux technologies, such as #wayland and #pipewire

With #piprewire, there is sound glitching across all DEs and all common distros. Even if I tweak the out-of-the-box settings, such as default.clock.min-quantum as recommended in numerous forum posts/wiki articles, it only marginally improves it, and I still get random audio playback issues in various music players such as #rhythmbox and #audacious, although I will concede #kodi seems perfectly fine.

With #wayland, there are a couple of apps I use, such as #avidemux, that don't really work with it, even under #xwayland
I can 'force' around that with things like using --platform xcb on the command line, but it's less than ideal.

So for me, whether I'm using my normal setup of #debian #trixie with #xfce, or use #gnome or #kde on the same base, or indeed try the same on #fedora or arch-based distros such as #cachyos or #EndeavourOSArch, it is the same outcome.

Newer isn't always best. #X11 with the right conf file to sort out screen tearing, works with everything I ever use on any DE or distro.
#pulseaudio just works everywhere.

So I'm going to stay in the past with the tried-and-tested X11 and Pulseaudio, until these 'new' technologies have matured and fixed all the edge-case issues they have.

Pipewire/Pulseaudio and avahi are driving me crazy

I've got my sound server on my local network that publishes the sink. Clients are configured to detect it via zeroconf

The service appears on the client when I look with avahi-browser

Yet, the sink will only appear in pulse audio clients when I restart avahi-daemon on the server.

Any idea why ?

#Pulseaudio #Piprewire #avahi