Using an Nvidia Shield Pro as the main Plex player, and it consistently is marking the next episode as watched. This is driving me crazy as keep having to remember which episode I last watched.
What is the fix please?
Plex Media Server version?
Plex AndroidTV client version?
Both available in list of Authorized Devices: https://app.plex.tv/desktop/#!/settings/devices/all
Both needed to try and replicate the problem.
Plex Server Version 1.22.3.4392
Plex Player SHIELD Android TV Model P2897 Version 9
Android TV Client Version 8.16.0.24423 (04921805)
Hi @FordGuy61 are you able to replicate?
Thanks for pinging me.
If I understand correctly, when you watch, for example, episode 2 of a TV show, Plex also marks episode 3 as played. Is that correct?
If so, I cannot reproduce.
If I play a TV episode to the end, Plex marks it as played. It does not mark the next episode (or any other) as played.
I marked all seasons / episodes of a show as unwatched.
Using Plex 8.17.0.24942 on my Shield, I watched s01e01 to the end, and Plex queued up episode 2. I backed out to the season view. Plex marked e01 as played, but not e02. The same thing happened when I played e02 and e03.
I then played episode 6, in the middle of the season, with both e05 & e07 unplayed. Plex played e06 normally, marked it as played when finished, and queued up e07, but did not mark e07 as played.
I made a similar run through season 2 using Plex 8.16.1.24597 on my Amazon FireTV 4K with the same results.
Am I correctly understanding what you are seeing on your end?
If so, Iâm not sure what would cause that to happen. I looked through library and client settings and did not see anything.
Does this happen only with the Shield - i.e. what happens if you use Plex Web?
If it also happens on other clients that would point towards the server.
If only on the Shield, you might see if there is a Plex client update available in the Google Play store app. 8.16.2 was released yesterday, and 8.17.0 is available if youâre on the beta release.
2015 Shield Pro: v8.17.0.24942
AFTV4K: v8.16.1.24597
PMS 1.23.0.4459 on Synology DS918+.
1 Like
Hello @FordGuy61 thanks for trying to help me.
You are correct in what is happening for me, very odd that it isnât happening for you, maybe (hopefully) I just need to change a setting.
I am just running an episode through to the end on the Shield and I will report back a screenshot of the behaviour that I am seeing that seems to be causing the problem.
It does not happen on other devices, just the Shield. I also have an Amazon FireTV stick, HTPCâs, a Vero 4K+, it also doesnât happen on the Shield if I use Kodi with the Plex plug-in, but I prefer the GUI and functionality of the Plex app.
Here is the issue. I just played through s03e12 and allowed it to play to the end, and didnât touch anything once it had finished.
It is now showing this at the server side - the Shield has jumped to the end of the next episode, and is holding it there, saying âbufferingâ. Very odd!
I repeated the exact same thing, on the same device but using Kodi and the Plex for Kodi add-on, the issue was not present. The episode just stopped, and playback stopped on the server side as you would expect.
I have auto updates enabled and the Plex app has been updated to version 8.16.2
Also, look at the timestamps: 43:30/41:30.
It shows you have played two more minutes than the length of the episode.
The progress bar is seemingly wrong as well, as it looks like youâre about halfway through the episode.
Iâve never seen this before. It is interesting that the FireStick does not exhibit the same behavior, as it uses the same Android TV client as the Shield.
Not sure exactly how to proceed. Hereâs some ideas:
- The log files on the server or client might pick up something.
- Set server for debug, not verbose, logs (Reporting issues with Plex Media Server).
- Enable logging in the Plex app on the Shield (in the app Settings)
- Play the last minute or so of episode 12, let it jump to episode 13, stay in buffering, etc for ~30 seconds, then stop playback. Do not exit the Plex app (or you canât get to the log file).
- Wait 1 minute for everything to get logged & the server to settle.
- Pull server logs
- Pull client logs. http://shield_ip_address:32500/logging. Save the web page as a text file. Note connection is http, not https & port number is 32500, not32400.
Not sure what to look for in the log files, except something out of the ordinary, which I know is incredibly vague.
You could post the log files to the thread and somebody might be able to find something.
- Remux Episode 13.
The file container, mkv or mp4, could be damaged and causing issues for the Shield. Remux the file using MKVToolNix or similar apps.
Remuxing with MKVToolNix will not alter the video or audio tracks. It will copy them to a new file (sorta like performing a âsave asâ). MKVToolNix supports saving files as MKVs. It will take mp4 and other containers as input.
After you remux episode 13 and place it in the directory, manually scan the show so Plex will pick up the new file. Also manually analyze the episode.
- Transcode the video using Handbrake, XMedia Recode, or similar tools.
The video track could somehow be damaged in a way causing issues for the Shield. Transcoding it should clear up any problems. Not sure how just the Shield would be sensitive to video track issues, but I suppose it could happen.
- Make a copy of the original as a backup.
- Transcode the episode.
- Remove the original from the library. If necessary, manually scan the library so Plex knows it has been removed.
- Place the new version in the library. Manual scan if necessary.
- Analyze the episode.
Then play episode 12, etc and see what happens.
Hi, thatâs a lot!
I am not really wanting to dedicate that much time to the issue.
It happens with multiple files / series, all of different file types, so I donât think it is a muxing issue.
For now, I have switched on the auto play next episode option, to see if that is easier to live with. Having it secretly marking unwatched episodes as watched has been quite problematic. At least if it autoplays it will force us to stop it, so we will be alerted.
I donât think I am alone, I have found other reports of the issue here:
Completely understand about the time involved.
I had not seen those other posts.
Hopefully this gets resolved.
Cheers.
1 Like
Bump.
Can anyone else replicate the issue in the screen shot above?
Can I bump this please - any plex employees able to assist?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
