first of all, thank you a ton for the 1.5 release. It’s great !!
I have a question regarding the implementation of Spotify and maybe I missed something but why does the Volumio player not show up in the Spotify device list like any other device logged in to the Spotify account and on the same network ? Sure, Spotify appears in the Library of the Volumio GUI but wouldn’t it be much more elegant to have it appear in Spotify’s device list ?
That way, it would be possible to continue to use the Spotify GUI for Spotify and not have to revert to the web GUI of Volumio.
That functionality is called Spotify Connect, which unfortunately is only available to commercial partners currently. You can help upvote the suggestion to make this a publicly available API, so we can integrate with Volumio!
Is there a possibility to develop the spotify connect capability on the volumio without knowing the "Spotify Connect Wireless speaker API " ?
Spotify connect is so handy and easy to use. The interface is perfect and complete. The spotify integration in Volumio is still very litlle, we can only search tracks. It’s a still a very good start
NB : maybe you can edit the topic “SPOTIFY CONNECT - VOLUMIO PLAYER IN SPOTIFY DEVICE LIST”
Anyone interested by this feature ?
Meanwhile, as ning-yu said, anyone interested by this should give some kudos for the release of this API on the spotify forum : LINK
Edit :
-I’ve done some research on the web. Apparently, this feature is based on the open audio streaming platform “qualcomm allplay” . The link to the sdk
According to this blog post), there is a Raspberry Pi API for this technology magicplay.com/
-I inform you also that Qobuz is announcing Qobuz Connect (hi-res) based on Qualcomm Allplay also. on-mag.fr/index.php/topaudio … -longtemps
I have no knowledge in coding, but I thing if this technology is develop on Volumio, a large panel of audio solution will be open. No need for further programming for the Spotify feature on the Volumio, that is currently limited.
Edited : I have done some research on the web. I have tried to understand how Spotify Connect is working.
Spotify connect is a protocol, like Dial for chromecast, like airplay by apple, like allplay by qualcomm.
I’ve found some very good explanations on this forum github.com/mopidy/mopidy-spotify/issues/14 :
-The playing device (e.g. Mopidy) streams music directly from Spotify’s servers. The controlling device (Spotify app on your phone) may be removed and the music will continue playing.
-Spotify Connect is entirely custom. It has nothing to do with UPnP/DLNA, Qualcomm Allplay, Chromecast’s DIAL, or similar.
-Control is done through Spotify’s servers, not directly over your local network.
-There is no special hardware required.
-Eventually there will be a public SDK for Connect functionality. Currently this SDK is only being distributed to Spotify Partners.
-Reverse engineering the protocol is supposedly quite hard, so we’re recommended to sit tight waiting for the SDK.
Some are trying to reverse the protocol (divideoverflow.com/2014/08/rever … y-connect/)
It’s released that Qualcomm Allplay is compatible with spotify connect and now qobuz connect (flac), but there is no img for raspberry pi. They have only published the SDK for iOS and android.
If allplay or spotify connect is implemented as a feature on Volumio, a large panel of solutions will be open. Because streaming may be the future of cloud music. It will let for example people create small diy wireless connected speaker based on raspberry.
hi, thank’s for your research. It is much more complicated than I thought but this would be a killer feature to implement. Once the public SDK is out it would be up to Michelangelo to evaluate if it is worth the effort or for other developers to step in to help this get off. Cool stuff !
Great !
Meanwhile, michelangelo, is it possible to implement on the spotify’s streams on volumio a way to get the albums, artists and tracks saved on spotify ? Because now, it’s just possible to read the playlists saved on spotify.
Thank you in advance !
michaelangelo and ning-yu, we’re currently working on reversing Connect, as Spotify are taking way too long to produce a Public API, and even when they do, it will still be proprietary, so we’re remedying that now:
any help would be great, as it’s quite a task to fully reverse engineer and implement, but we’ve worked out the API for playback control, and we’re nearly there on the audio, so if you or anyone else is capable, and wants to provide a helping hand, head on over to the Gitter chatroom (where all the action takes place), or have a look at the work done so far at:
I followed the link to give Kudos to the idea on the spotify forum, and noticed a link in the right hand side bar of the page, that had a link to register in some kind of program to test the connect api. I don’t know for how long it has been there, and I assume that such a beta program would be announced either on the blog or in the appropriate developer channel and would be noticed by the people interested in reverse engineering the protocol, but just wanted to mention it, just in case.
