mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #290] Switching tracks no longer working correctly #194
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#194
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 @IsaacWoods on GitHub (Feb 21, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/290
I've recompiled an application using librespot after a while (it used to work perfectly).
Most of it still works (can still successfully connect, load tracks and stream audio), but switching tracks no longer works correctly. Instead, something like this happens:
PlayerCommand::Loadis receivedPlayerCommand::Loadis received, but for the previous track (the one already playing, not the one just selected).@thusly commented on GitHub (Feb 21, 2019):
I'm having the same issue, although I actually assumed it was because I hadn't recompiled in ages. This problem started occurring for me yesterday, with a librespot binary that was compiled months ago and had been working fine, otherwise.
I just recompiled to see if the issue would be resolved, and it's still occurring (and here I am). I'm assuming something changed on Spotify's end.
@devgianlu commented on GitHub (Feb 21, 2019):
librespot-javaworks fine with Spotify1.1.0.237.g378f6f25, I can't really tell what's happening.@forslund commented on GitHub (Feb 21, 2019):
Think this is the same issue as I reported in #288
@IsaacWoods commented on GitHub (Feb 22, 2019):
This is indeed connected to #288 (I didn't realise at first it was to do with the URI stuff).
This is fixed by changing this line to (credit to @worleydl):
I have no idea why this stopped working (maybe API v2 was deprecated internally and so they moved the endpoint?), but this seems to fix it, so closing.
@AxelNilsson commented on GitHub (Feb 22, 2019):
This should be reopened, since the master isn't fixed.
@dtcooper commented on GitHub (Feb 22, 2019):
Getting a lot of reports of this re: raspotify#183, but unobserved myself
@kingosticks commented on GitHub (Feb 22, 2019):
If #288 also fixes this then we don't need two open issues for what is essentially the same thing.
@sashahilton00 commented on GitHub (Feb 22, 2019):
as @kingosticks said, this is a duplicate. continue discussion in #288.