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
PlaybackController.seek() stops generating events #1505
Comments
Sorry, we're talking 'bout Mopidy v2.0.0, of course. |
For reference, this is what switching to a new track looks like before running
For some reason, the |
AFAICS, this is also reproducible with the latest Mopidy |
Same situation after running Mopidy for a couple of days unattended - no more events delivered to MoMo. Restarting Mopidy fixed that. Sorry, not too much information in this (except it may not only be related to seek)... |
For the record I've experienced the same behavour (on Mopidy 2.0 release) but only when using dleyna / podcast backends and after some time. I couldn't reproduce it using mopidy-spotify. I couldn't find a totally reproducible set of steps, so finally I didn't fill an issue. |
@ismailof: Thanks for your input! The difference may be that dleyna/podcast rely on the |
I've been able to test this issue a little bit more, and seems pretty reproductable. What I'm getting after a
So it seems it has to do with some Currently I'm using Mopidy release 2.0.0. I'll try to reproduce it with |
Thanks, @ismailof for taking the time to investigate this further! |
5b6632e might be relevant for this, I'll undo the fix to see if I can reproduce. |
Or 3ee9124 |
Well, I could do a bit more testing on this, and it led me to the same problem that #1462. If the That said, I could finally test it on a up-to-date I'm attaching the log of a
|
Closing as fixed by #1496 |
Using both Mopidy-Mobile's "track time" slider and something like
mpc seek +1:00
seems to stop Mopidy from generating most events, notablytrack_playback_ended
/track_playback_started
when switching to a new track. Instead, I see somevolume_changed
events in MoMo's log, which clearly don't make sense since volume's been untouched:This seems to affect Mopidy operation until Mopidy gets restarted. I haven't used MoMo's track time control that much, recently, so I can't say when this was introduced. However, being able to reproduce this with an
mpc
command seems to indicate a bug in Mopidy, and not the client.Edit: fixed expected events for sending
playback.play
.The text was updated successfully, but these errors were encountered: