mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #121] Volume management bug: manipulating volume switches Repeat state #67
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#67
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 @kataklasm on GitHub (Oct 29, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/121
Just encountered this little non-urgent bug: Manipulating the volume controls through + or - switches 'Repeat: Track' to 'Repeat: All'. No change was observed when manipulating volume when in neither 'Repeat: Off' nor 'Repeat: All', in both cases the state is constant.
@sputnick1124 commented on GitHub (Oct 30, 2019):
What device are you using to play it when this happens. I just noticed a similar behavior using
spotifydas my device, but playing audio through the web player works fine.Actually, using the web player as the client and
spotifydas the player, I am unable to even selectRepeat: Track. It just cycles betweenAllandNone. Curious...@kataklasm commented on GitHub (Oct 30, 2019):
I'm not quite sure what you mean by device in this regard. In any case, I am using a XMG a507 running popOS 19.04, using spotifyd as the server and spotify-tui as the CLI.
@sputnick1124 commented on GitHub (Nov 1, 2019):
Sorry for the lack of clarity. By device I meant what Spotify calls a device when it says "Devices available". In this case, the
spotifydserver using the Spotify Connect API would be the device.I suspected that may be the case. The issue actually lies within spotifyd (actually librespot), but has been addressed with a recent update (see https://github.com/Spotifyd/spotifyd/issues/381). I have tested this on my local machine by updating spotifyd to current master and building, but the issue has not resolved itself yet for some reason.
That said, I don't think there is any bug within spotify-tui to address here.
@kataklasm commented on GitHub (Nov 1, 2019):
Thanks for the update, I'll close this then. See spotifyd #381 for a possible fix.