4 ms·
Not the parent post, but I've been thinking about unifying all devices in my home by sending all audio streams into a single, unified "sound server" from which
by jeroenhd 5y ago
Not the parent post, but I've been thinking about unifying all devices in my home by sending all audio streams into a single, unified "sound server" from which I can easily switch between TV audio, Bluetooth, headphones, etc.
The idea is to be able to take a call on my phone and receive notifications on my laptop while developing on my PC. It'd also be nice for streaming stuff in general.
As many people who have also looked into this stuff probably already know, interactive audio is really sensitive to latency. I've given it a quick shot by running pulse over the network, but honestly I wasn't impressed. I've given up for now, but some suggested software here might be good enough for a second shot, based on pipewire and its JACK backend this time.
- getcrunk 5y agoHear hear. I was just thinking about a putting all my music and a mpd on my pi then running clients on tv/computers/phones. But ur idea is the next step!
- Shared404 5y ago> I was just thinking about a putting all my music and a mpd on my pi then running clients on tv/computers/phones I actually do something similar to this to run music for an online D&D campaign I'm in, except I use the http output so none of the other players have to install a client. I do like the idea of the home audio server use case, I think it'll go on my back burner!
- smaudet 5y agoThat sounds too connected - I like the idea of some sort pulseaudio network services but with better latency. I'd like to see pulseaudio with a better cross platform UI and a set of decentralized services versus introducing a single point of failure like you are proposing. Maybe a solution with dns-sd with stun support and a slick UI for desktop/mobile?
- iostream23 5y agoOr AVB as I note above, depending upon your lan and hardware