Server Version#: 1.32.8.7639
Player Version#: 10.9.1
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Server is running Plex on bare metal Ubuntu Linux 22.04.3, with a 4x4TB RAID 5 array with disk spindown time at 10 minutes for power saving.
Player is Android TV and the issue is going on forever (years).
Every time that one TV episode ends, and the disk are in a spindown state, the next episode is 99% of the time 2:00:00 (2 hours) long. This episode plays fine, and then when it is over, Plex will reproduce black screen until the 2 hours mark. And if I exit and select another one, that episode will remain as not completely watched.
Reanalyze doesn’t solve, as plex detects perfectly its duration and it is not a library issue. It is possible to see that when the next episode starts reproducing and enters the player (leaving the countdown between episodes), if I press the up button on my remote, I can see from the bottom bar that the episode has the correct duration, while I hear the disks starting up.
But, as soon as the image start displaying, the end counter goes directly to 2 hours.
This issue was reported multiple times on multiple platforms, and it seems to be related to an idle state or a delay in reproduction
Interestingly, this is not happening with the first episode that I play from the menu, even though the disks are in the same spun down/idle state. This only happens after the first episode. And, it doesn’t happen
This is rather annoying as every 2 episodes I have to exit and select the episode as played, and move to the next one, all manually with the remote.
Hi, my post is the 2nd one you linked to in your post, and I haven’t had this issue for nearly 2 years now. And no one has reported it to me either. I can’t say for sure how or when it stopped. For me it was only in the web player and the work around I came up with while it was happening was to just force transcode it with the setting at automatic, or original quality.
The transcoder would sit quietly in its room and think about what it had done and would then come back with the correct duration. So short of a proper diagnosis (you might want to post logs when it is happening) just making it transcode while you watch will help. It did for me.
The first think I checked on your post was which server you use… I had this issue when I using the Windows server and it had long gone before I moved to a linux server… I never did check if it was happening to files of a specific codec or it just happened to any of them.
