James Barnsley

Closing this issue; there have been many improvements since 2021 so I trust this issue is now resolved. Please request this issue is reopened if it is still relevant.

@hlgirard what version of Mopidy are you running?

@hlgirard I haven't been able to replicate this issue just yet, but I'll try a few more combinations. I don't have a Raspberry PI 3 to test on (only 1B+...

@hlgirard thanks for that screenshot, it helps explain in more detail what is happening. I suspect there is something funky going on with the Mopidy backend, rather than the Spotmop...

@hlgirard I'm making progress! I have managed to replicate some funky behavior, similar to what you're experiencing. Can you please try disabling _Consume mode_ and seeing if this fixes the...

@hlgirard are you able to try an interface reset for me? Under _Settings_, check _Enable advanced settings_ and click _Reset all settings_. This should have little effect, but worth trying.

@hlgirard Side thought... have you got Echonest enabled?

@hlgirard The latest release of Spotmop revisits the play progress detection (which addresses some issues with inaccurate position data). I'm hoping that this will have some impact on the issue...

Hmm, this is such a weird issue as I have been unable to replicate it across a number of devices. Is there any difference if you toggle consume mode? @fss...

This uses a `PlayerService` model, which you can see here: https://github.com/jaedb/spotmop/blob/master/src/app/player/service.js I'm full swing in development of a revamped version of Spotmop, called [Iris](https://github.com/jaedb/Iris). You could try running Iris to...