The state of libspotify in 2017

I know that libspotify will no longer receive any support and is being replaced by webapis. I have no problem with this because libspotify usability is just bad and there are a lot of errors without errors, as well as many missing features. However, there is no way to get the stream URL or have a small library to decode the streams.

We were promised that a new small replacement library will be available "soon" for more than 4 years, and parts of libspotify have already been completed. In addition to this, from some time there is a note that libspotify will be disabled in 2017.

I don't care what the web API is provided, which is clearly superior to libspotify in almost every way. All I care about is the simple player API in which I can enter the Spotify track URI and get the original PCM frames (which can be output to speakers, broadcast to unsupported devices, etc.).

You already have this type of library inside the android SDK that provides everything we need. What is the reason for not providing a standard c library for non-android platforms (win32, Linux, mac)?

Or provide a way to get the RTMP or HTTP stream URL, as was done in the Spotify webplayer, which would be even better.

I really like Spotify and hope to continue developing applications that use it.

+6
source share

Source: https://habr.com/ru/post/1013860/


All Articles