The last two upgrades have broken my audio setup.
First the options for Network Server and Network Access in paprefs were greyed out and my sinks disappeared after upgrading to bookworm. I just had to create a link to an existing file and it was working again but, it's weird that it was needed in the first place. Pretty sure it has something to do with the change from pulseaudio to pipewire but I'm not very up to date on that subject and I just want to have my current setup to continue working.
Then yesterday I just launch a simple apt-get upgrade and after rebooting my sinks disappeared again. The network options in paprefs were still available, but changing them did nothing. I had to create the file ~/.config/pipewire/pipewire-pulse.conf.d/10-gsettings.conf and stuff it with "pulse.cmd = [ { cmd = "load-module" args = "module-gsettings" flags = [ "nofail" ] } ]" in order to have my sinks back.
I know it's not only a Debian thing, as I can see this happening to people on Arch forums, but as Debian is supposed to be the "stable" one, I find it amusing that a simple upgrade can break your sound.
Mainly because of bluetooth headphones with multiple computers. That way they are paired to only one computer and I can use them with other computers at the same time. Just right click on paprefs system tray icon, change the sink and the audio is sent somewhere else. I know it's now possible to have bluetooth headphones that have multiple connections but it wasn't the case a few years ago and I still find it much more useful this way.
But it's also useful when I have my laptop near my main computer and want to use its much better speakers instead of the crappy ones on the laptop. Right click, select another sink, and that's it.
It's just nice to have the option to send the audio from one computer to another. It's a shame that it's apparently a niche thing.
I've also used pulseaudio for this sort of things in the past, it's very flexible and works rather well!
When it works (!), it's one of the reasons I brag to my tech friends about Linux, and why I switched to Linux many many years ago. In fact, it was when Esound was a thing. But once in a while it stops working after an upgrade or a dist-upgrade, and I have to spend time trying to fix it.
I like to joke around with tech minded friends that Windows keeps breaking with every updates, but then I have to spend an hour finding out why my sinks disappeared after an upgrade, and I'm forced to realize that... sigh... these things happen with Linux too.
You could maybe look into using SnapCast, it would be independent from pulse and should work even through apt updates ;)
I haven't been using pluseaudio for an eternity, since the Linux machines I use are mostly headless,.yet I was a pluseaudio fanboy when it was.just replacing ALSA. Yet, the hours and hours pulseaudio cost me to fix some upmix that had stopped working or some other weird shit... IDK if I'd still preach it's upsides would I be in the same situation now.
I tend to like it. I use it even on some headless machines (for example for streaming audio). I'm gonna have to learn more about using Pipewire sadly.
I’ve never heard of someone doing something like this before, but it sounds like it could have some pretty cool downstream applications (thinking Bluetooth speakers)
With your setup would it be possible to pair your headphones to your phone (iPhone in my case) and be able to pass audio from different computers to a central one that my phone could then relay to my headphones?
I often walk around my house/yard while listening to something playing on my laptop/desktop. And if I get too far from the source, it breaks the Bluetooth connection. So I usually end up having to drag my laptop around the yard with me. A much nicer solution would be to have my phone on my person, and use the wifi to keep connected to my “audio source” without needing proximity to the actual pc playing the sound.
Audio over the network is a feature of pulseaudio/pipewire from a module aptly named "module-simple-protocol", and as simple as it is to make it work on Linux (when it works), it's unfortunately not as easy on other platforms. Technically speaking, it's possible to do that on Android with an app called "Simple Protocol Player" but it's apparently very glitchy and you're going to need some patience for the setup. It's from someone that wanted to stream audio from an HTPC with Ubuntu to an Android phone, but the author states that it's pretty buggy. Here's the link to their blog: https://kaytat.com/blog/?page_id=301
So the short answer is unfortunately "no", unless you want to practice your patience on a project.
Thanks for this. I guess I should have expected that answer. Bluetooth in general already tests my patience, so I’m not sure a new project revolving around things that already piss me off would be a smart move for my already rising blood pressure.
I’ll stay tuned to that protocol though, as it could probably help me in some other less complicated projects I’d like to tackle.
Does this give network latency on top of Bluetooth latency or does the network somehow "handshake" it with the Bluetooth on the devices you're listening to?
I never noticed any latency when I'm not using bluetooth. And no, the devices do not speak to each other. For PA/pipewire, this is just an audio sink as any other.
There is latency when using bluetooth but this is pretty standard. It just doesn't increase (or not noticeably) when streamed to another computer.
@pedz
I'm on the same point. Until i had my multi connection bluetooth I worked the same way. The problem now. It does not work that nice.
I try currently to switch back. But my goal currently is using my #Kodi Mediacenter. But Kodi sems still using alsa. It was a hack to get simultaniousl y output with a bluetooth speaker. (For Radio in other rooms)
I gave up this network audio setup for Kodi.
@MrWafflesNBacon
AFAIK Kodi can use pulseaudio and probably pipewire. I use Kodi too on those computers and I just leave it to use the default PA device that I've set. I switch the default devices with pasystray.
What's usually breaking for me is paprefs. Every so often after an upgrade, the options are greyed out and I can't share or access my devices over the network.
I never tried to setup simultaneous output before because I just switch from device one to another, but I just enabled it in paprefs and it's working too.
That's a cool use case