-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call to get_current_track returns outdated information #2024
Comments
Debug log please. |
Here is the relevant part as far as I can tell. Just added two tunein stations to the tracklist and called next (2021-10-26 20:10:10,943) and get_current_track (2021-10-26 20:10:12,654) from my speaker (SPEAKER_IP_ADDRESS). Seems to be a race condition, as the new tunein station is not yet playing when I call get_current_track. What do you think? Here is the log
|
This is my experience. In order to let the user know which track is playing, after a |
Commands like this in Mopidy are async. The track change is not guaranteed to have finished by the time |
Situation
I want to use a physical button to move through the mopidy playlist. I implemented this by having the button trigger a call to core.playback.next. Now, I want to let the user know what the new track is and call core.playback.get_current_track.
Expected behavior
core.playback.get_current_track returns the track I just switched to.
Actual behavior
The call does not reflect the latest change and returns the previous track. This seems to only be the case when tracks are streamed from the internet (seen with tunein and youtube extensions) but not with local files.
The text was updated successfully, but these errors were encountered: