I don't think it's explained in the article, but why was spotifyd chosen instead of cast or airplay "middleware"? Surely cast and airplay work with Spotify while delivering equal sound? Either way, amazing work and looks fantastic in wood.
Not the author, and I'm also not sure I fully understand your question, but am assuming 'cast or airplay' refers to the method used by mobile devices to redirect AV streams to different devices. Both those solutions still require a spotify client somewhere to interact with the spotify api. The spotify client is still ultimately responsible for determining what to play, where to play from, and what stream URL then nee…
Yes, thank you for phrasing it better.
I don't think what you said is 100% true. I have an old chromecast that is capable of playing Spotify without the "spotify client" (i assume you mean spodifyd).
From what I understand about chromecast is that it uses a "cast protocol" (?) and therefore doesn't require "clients" (xyzd) for each media service integration.
Unsure about airplay though.
I imagine the reason they chose to use this spotifyd approach might be
- There is no "cast client" or "airplay client" available
- Audio properties of the Spotifyd client are superior to the alternatives
- They only use spotify
- just because they wanted to
Yup, i understand the idea behind these clients and why they're superior to bluetooth.