mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #92] Like or Dislike unavailable when connecting to Spotify Connect #81
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#81
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/92
Wednesday Sep 27, 2017 at 06:02 GMT
Originally opened as https://github.com/plietar/librespot/issues/254
The Like or Dislike commands disappear from the player as soon as the Spotify Connect (using librespot/raspotify) device is chosen to play audio. Instead the Random / Repeat commands appear.
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Sep 27, 2017 at 13:36 GMT
Yes this is the default behaviour. If you want Like/dislike feature, you are free to write some lines in the evening hours and post a Pull request. xD
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Sep 27, 2017 at 17:06 GMT
Default behavior of other Spotify player (PC App, Spotify Web Player, Chromecast, etc) is to put the thumb up/thumb down commands for radio playing when you can discover new artists and to put the Random/Repeat commands when you play a chosen artist.
Ahah, yeah it will need me quite a few evening hours to wrote this particular lines ;)
@ComlOnline commented on GitHub (Jan 29, 2018):
I've just checked and this bug still exists
@sashahilton00 commented on GitHub (Jan 29, 2018):
Not a bug afaik, it requires implementation, it think it falls back to shuffle/repeat. Possibly linked to #57 as it came in with spotify radio?
@sashahilton00 commented on GitHub (Feb 25, 2018):
This behaviour no longer occurs.
@IiroP commented on GitHub (Oct 27, 2019):
This issue is there again, build with latest commits. Exactly the same behaviour as in first post.