Pausing a song ends up restarting a song

[jbouter]

When a song is paused, regardless of MPD frontend, and resumed at a later point, it will resume playing the song until it has run out of buffer. After which it'll restart the same song without resetting the time it has been playing. Resulting, for example, in "14:36 / 9:57" time played by the end of the song.

[Prior99]

I am not sure if you are searching at the correct place. Correct me if I am wrong, but mopidy works in a way where the Backends just give a playable URI to mopidy which then plays it. The actual playing/pausing/resuming/skipping is not handled by this project.

[Prior99]

Is this still relevant @kyentei ?

[jbouter]

It still is. I just don't know whether it's a mopidy or subidy issue. If Subidy is feeding the music stream to mopidy and gets paused, perhaps it'll restart feeding the stream? I have only reported my finding, and not taken a look at the code.

If you consider this issue not relevant to the subidy project, but to mopidy instead, I'll re-post the issue there. Though I do doubt whether mopidy would have the same issue with, say, playing local MP3 files.

[Prior99]

As I said, subidy is not streaming anything, it is just giving mopidy a URL on which it can then stream the music.

[hhm0]

It could be that the subsonic server being used does not support range requests. See spl0k/supysonic#57 for a similar case.

In my experience with supysonic and mopidy/subidy, the behavior was a bit different: although the song wouldn't restart from the beginning, it would take a while to seek, especially near the end of the track (presumably since it had to redownload the track from the beginning until the seekpoint).