This way you can send any audio from laptop/phone to the stereo over lan.
Not sure why you would want to limit yourself to the service of a single provider. (What value does Spotify Connect add, if any?)
The primary benefit for me is that a Connect client is actually connecting to spotify itself - it's less output sink and more headless client. So if I start spotify playing, and then close my laptop, it can sleep properly without interrupting my Connect device.
The source for the app used in the video is here: https://github.com/ford-prefect/pa-output-switcher
That repo links to a page about building an AOSP firmware image which uses pulseaudio: https://www.freedesktop.org/wiki/Software/PulseAudio/Ports/A...
I don't want to use a custom firmware image. I like the firmware provided by Google, and the monthly security updates. If I were to switch to a custom build of AOSP, I'd need to sideload Google Play Services (by downloading it from a source I trust less than I trust Google) and would also no longer get security updates.
I glanced at the readme, but it looks like it's written for someone who already knows why they wanted an open source Spotify client.
Regardless of all the above, good work!
That said, AFAIK it's not technically legal to use regular Spotify in a public space. Spotify Business seems to use a separate client, no idea whether that's instead of or in addition to the consumer ones.
Is there a way to trick Spotify into streaming AAC like on the Chromecast?
Sad to say it, but Spotify's AAC streams sound much more atmospheric than their Vorbis. Could be different low pass filters.