Closed
Description
Using both Mopidy-Mobile's "track time" slider and something like mpc seek +1:00
seems to stop Mopidy from generating most events, notably track_playback_ended
/track_playback_started
when switching to a new track. Instead, I see some volume_changed
events in MoMo's log, which clearly don't make sense since volume's been untouched:
websocket:outgoingMessage Object { method: "core.playback.play", params: Object, jsonrpc: "2.0", id: 68 } mopidy-mobile.bundle.min.js:155:8
websocket:incomingMessage Object { jsonrpc: "2.0", id: 68, result: null } mopidy-mobile.bundle.min.js:155:8
websocket:incomingMessage Object { volume: 100, event: "volume_changed" } mopidy-mobile.bundle.min.js:155:8
event:volumeChanged Object { volume: 100 }
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
.
Metadata
Metadata
Assignees
Labels
No labels