Redrum wrote: > I edited my previous post regarding this. > > I do believe you are right with regard to what's happening. I think my > issues have been with pause/time elapses/resume of a podcast currently > in the playlist. If the time is a few minutes - fine, longer, say 1/2 > hour+ maybe not. From memory, I got in the habit of noting the time > before pause, and if resume failed, I would either ffwd to my remembered > timestamp, or, go back to recently played, choose it again, then resume > from last to recover. > > The HTTP dropping after some time makes sense, but, the recently > played-resume from last position works regardless of time. I went into > my recents from weeks ago and resumed just fine. > > Maybe if there was a "save spot" option instead of pause/resume it would > help my use case? Say like '+' -> menu-> save spot or resume from saved > spot. > > But like I said, I am trained how to recover and it's not an issue, just > trying to "what if" to help the op. > > Jim
I was wrong, there is everything in place to resume to the paused position, if the stream is seekable which should be the case, so there is likely a bug somewhere. Could you set "(player.streaming.remote) - Player Remote Streaming Logging" to debug and capture a case where it fails? LMS 7.9 on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5, Riva 1 & 3 ------------------------------------------------------------------------ philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=112587 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
