Skip to content
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

Erratic behavior of next/previous in "paused" state #1177

Closed
tkem opened this issue May 11, 2015 · 3 comments
Closed

Erratic behavior of next/previous in "paused" state #1177

tkem opened this issue May 11, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@tkem
Copy link
Member

@tkem tkem commented May 11, 2015

Given the following sequence of mpc commands

$ mpc load "Beatles - One"
loading: Beatles - One
$ mpc play
Love Me Do
[playing] #1/27   0:00/2:20 (0%)
volume:100%   repeat: off   random: off   single: off   consume: off
$ mpc pause
Love Me Do
[paused]  #1/27   0:06/2:20 (4%)
volume:100%   repeat: off   random: off   single: off   consume: off
$ mpc next
From Me to You
[paused]  #2/27   0:06/1:56 (5%)
volume:100%   repeat: off   random: off   single: off   consume: off
$ mpc play
From Me to You
[playing] #2/27   0:00/1:56 (0%)
volume:100%   repeat: off   random: off   single: off   consume: off
$ mpc status
From Me to You
[playing] #2/27   0:06/1:56 (5%)
volume:100%   repeat: off   random: off   single: off   consume: off

one would assume that the track that's getting played is "From Me to You". Curiously, however, it still is "Love Me Do", though mpc status claims otherwise.
This seems to occur only when changing tracks using next/prev in "paused" mode, and is also reproducible with Mopidy-Mobile/Mopidy.js, so it does not seem to be an mpd issue.
When calling mpc stop instead of mpc pause, this does not seem to occur, i.e. tracks are changed an played as expected, although mpd status will not report the current/next track when paused.

Mopidy v1.0.4 verbose log for above command sequence: https://gist.github.com/tkem/393e2f5c103b9eb238d5

@jodal
Copy link
Member

@jodal jodal commented May 11, 2015

I'm guessing this might have the same root cause as #1172.

@jodal jodal added the C-bug label May 11, 2015
@jodal jodal added this to the v1.0.5 milestone May 11, 2015
@adamcik
Copy link
Member

@adamcik adamcik commented May 12, 2015

#939 comes to mind, but that was for seek but likely due to the same set of assumptions in the existing code.

@jodal
Copy link
Member

@jodal jodal commented Jun 24, 2015

Fixed with the merge of #1185.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants