mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #984] repeating single track is not possible #472
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#472
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 @eladyn on GitHub (Apr 12, 2022).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/984
This report is primarily coming from https://github.com/Spotifyd/spotifyd/issues/1071, which I noticed, is also an issue with the current dev version as well as with the
new-apibranch.Description
Librespot devices don't support setting the repeat type to
single track, onlyofforall. In the official client (Linux and Android at least), the repeat button, which usually cycles through the three modes, only exposes the two mentioned above. Withspotify-tui, switching the repeat mode totrackworks (as in: it showsRepeat: Trackin the UI), but the text resets itself after a few seconds.I'm not sure wether this is a regression or was always the behaviour, but judging by the two recent reports in https://github.com/Spotifyd/spotifyd/issues/1071 and that I could not yet find any other issue that describes this, it might be a change on the Spotify side, which requires changes in
librespot.Note: This is only an issue with librespot, not with Spotify Connect devices in general, since I seem to be able to set the repeat mode to
trackon an "official" Connect device.Let me know if you need any further details. Thanks!
@roderickvd commented on GitHub (Apr 12, 2022):
Duplicate of #19
@eladyn commented on GitHub (Apr 12, 2022):
Oh, right. I read through that issue, but it seemed different. Should have read more carefully. 😅
@roderickvd commented on GitHub (Apr 12, 2022):
No worries, thanks for your extensive description too.