For some time now I have not been able to resume watching movies in Plex. If I can’t watch a movie in one session and try to come back the following day, when I try to resume from my last position I just get an endless spinner.
This happens with:
- Plex client app on Nvidia Shield TV
- Plex client app on Apple TV 4
- Plex web app
I am currently running the linux PMS v1.3.0.3059 for Plex-pass users, but this has been happening for some time with various older versions of the server.
Movies play fine if I watch from the start, but as soon as I try to resume a movie, or fast-worward I get the endless spinner.
Resume should be a core feature for a media playback system surely.
Is anyone looking into this? I know I’m not the only one affected after looking through these forums, but I have not seen a definitive fix, or even a response from a developer yet.
Resume should be working, and is working for me. Please provide logs from the Shield and from PMS after recreating this issue.
Hi, I just turned on the verbose network logging on the Apple TV 4 and reproduced the issue.
I gather Plex devs can see these logs on a server somewhere. Time was approx 23:40 GMT on 5th Dec 2016, I left it spinning for a few minutes. Movie was Battleship (2012).
I also have PMS logs from the same time, where can I send them?
I will check if I can get those logs from the devs but they are busy ad it may take a while. It would be faster if you could recreate the problem and grab the local app logs. Please post any logs here or you can PM them to me.
PM sent with PMS logs attached.
I’m looking at the time you indicated and it looks like it is resuming properly.
Here is the command requesting the start if playback. offset=1647 is to start at 1647s into the video.
Dec 05, 2016 23:41:56.082 [0x7eff5ebfe700] DEBUG - Completed: [192.168.0.41:58623] 200 GET /video/:/transcode/universal/start.m3u8?audioBoost=100&directPlay=1&directStream=1&fastSeek=1&includeKeyframePlaylist=1&location=lan&maxVideoBitrate=200000&offset=1647&partIndex=0&path=%2Flibrary%2Fmetadata%2F12696&protocol=hls&session=F9FEB024-41F3-4E1B-B942-18758CF36EFD&subtitleSize=100&videoQuality=100&videoResolution=1920x1080 (8 live) TLS GZIP 23ms 620 bytes
Here is the transcoder line stating it is starting at segment 164, where each segment is 10s, so 1640s, which is the resume point.
Dec 05, 2016 23:41:56.111 [0x7eff4dbff700] DEBUG - Job running: FFMPEG_EXTERNAL_LIBS=‘/var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Codecs/4b2f00a-1141-linux-ubuntu-x86_64/’ XDG_CACHE_HOME=‘/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache/’ XDG_DATA_HOME=‘/usr/lib/plexmediaserver/Resources/’ X_PLEX_TOKEN=‘xxxxxxxxxxxxxxxxxxxx’ ‘/usr/lib/plexmediaserver/Plex Transcoder’ ‘… segment_time’ ‘10’ ‘-segment_start_number’ ‘164’
Here is the client asking for segment 164.
Dec 05, 2016 23:42:08.924 [0x7eff5e3fd700] DEBUG - Request: [192.168.0.41:58628 (Subnet)] GET /video/:/transcode/universal/session/F9FEB024-41F3-4E1B-B942-18758CF36EFD/base/00164.ts (10 live) TLS Signed-in
So I’m not seeing a problem.
Ok thanks for checking.
I have tried the last 2 nights to recreate the problem using the Nvidia Shield TV and of course it has worked perfectly both times!
If I can reproduce it again I will post more logs, but for now it seems to be behaving again.
I have recently replaced a network switch, so that might have resolved some underlying network issue between the client-server or server-NAS.
Thanks for your help.
Also, note that the preplay screen doesn’t change if you watch more than 1 episode through post-play. So if you pause and just back out, it takes you to the pre-play of the first episode you watched (not the last) so it may appear that it wants to start from the beginning. If you click > to get to the correct episode, it should show you the correct progress and allow you to resume.
