If the main selling point is that it's a lightweight alternative, it would be good to include some details in the readme (e.g. RAM usage, CPU, etc).
And then detail how packaging it as a Snap undoes all their hard work.
Spotify-Qt
31–40 of 45 posts
Re: Spotify-Qt
#32Spotify web client with Adblock works best imo. No shuffle playing of albums. Or “shuffled” radio playlists. Don’t even need premium.
Walmart with reused bags and a getaway car works best IMO. Don't even need to pay.
While that is a very funny sentence, the half a cent I'm withholding from the artist by blocking the ad is hardly a robbery.
Just buy a CD once in a while if the guilt is too much to handle.
Re: Spotify-Qt
#33Using the Spotify Rest API it is already possible to build nice feature rich Spotify clients for remote players. I don't think there is a supported native playback library? I'm not sure how local playback is implemented in this project.
The main problem I have with the Spotify API is that its remote playback management API is limited/incompatible with some players (Sonos).
Re: Spotify-Qt
#34Earlier quoted context omitted.
Walmart with reused bags and a getaway car works best IMO. Don't even need to pay.
While that is a very funny sentence, the half a cent I'm withholding from the artist by blocking the ad is hardly a robbery. Just buy a CD once in a while if the guilt is too much to handle.
Indeed, over half of all musicians make their primary income from live performances because streaming pays so little to most!
Re: Spotify-Qt
#35Earlier quoted context omitted.
Read the source, Luke.
isn't it just an interface to a proprietary binary which has no source to be read?
No, it uses librespot which is a open re-implementation of libspotify, which was Spotify's old, but now pulled, SDK. The risk however is that when Spotify thinks it's no longer worth supporting older harder devices that rely on the original libspotify, they'll pull the endpoints and remove functionality (already happened to search, for example, but they could use the newer APIs for that - it's going to be hard when they do it with playback, as the new APIs require DRM).
Re: Spotify-Qt
#36Re: Spotify-Qt
#37If the main selling point is that it's a lightweight alternative, it would be good to include some details in the readme (e.g. RAM usage, CPU, etc). And then detail how packaging it as a Snap undoes all their hard work.
The snap is mostly a leftover from before AppImage builds were available, as that was the easiest way for me to package binaries at first. AppImage is now the preferred way to run the application on distros that don't have packages from their native package manager. I'll make sure to update the readme!
Re: Spotify-Qt
#38Using the Spotify Rest API it is already possible to build nice feature rich Spotify clients for remote players. I don't think there is a supported native playback library? I'm not sure how local playback is implemented in this project. The main problem I have with the Spotify API is that its remote playback management API is limited/incompatible with some players (Sonos).
It relies on a separate client for playback, which can be an open source client like librespot/spotifyd, or an official client. It's also mostly older systems using the older, deprecated, playback client that aren't compatible with the Web API afaik.
Re: Spotify-Qt
#39Gave it a quick spin on Windows and it's incredibly slow to drag the window around, no idea why but I'd guess it's redrawing for every frame. Interesting though, could be good if it offers better playlist management, for instance I'd like to see all artists who's songs I've liked.
Haven't noticed any issues like that under Windows, so please open an issue with more details. You can also try either enabling a native window handle from "Settings > Interface > General > Use native window", or enable a native window frame from "Settings > Interface > Title bar > Disable Application title bar".
I'll also see if I can implement something like that!
Re: Spotify-Qt
#40Gave it a quick spin on Windows and it's incredibly slow to drag the window around, no idea why but I'd guess it's redrawing for every frame. Interesting though, could be good if it offers better playlist management, for instance I'd like to see all artists who's songs I've liked.
Unfortunately, it also cannot find my audio device (I have several connected), so it failed at the the one job it really had.
Only devices exposing to the Web API, and logged in with the same account, are currently supported. If you know that a device you're trying to use is exposed, please open an issue with more details.