Skipping forward or backwards more than once causes infinite buffering

Server Version#: Version 1.18.4.2153
Player Version#: Plex for xbox one 2.45.1.70 (running on xbox one x)
Plex web Version 4.12.3

I’ve been running on the same hardware for years now and only recently started seeing this issue, What happens is if I hit the skip button more than once in quick succession (anything under 5 seconds) the video will get stuck in an infinite buffering cycle, although I haven’t let it sit more than 5 minutes or so.

Taking a look a the logs I can see that one of the temp transcoded chucks can’t be found when requested.

Dec 18, 2019 10:07:23.217 [7156] ERROR - Couldn't find the file to stream: C:\plex_tmp\Transcode\Sessions\plex-transcode-dl6hros8w3pxaw28gje0bh4z-af3a8413-9114-493f-aebb-ab1937bd2aaa\init-stream0.m4s,C:\plex_tmp\Transcode\Sessions\plex-transcode-dl6hros8w3pxaw28gje0bh4z-af3a8413-9114-493f-aebb-ab1937bd2aaa\chunk-stream0-00060.m4s

Going a step further I used process monitor and pointed it to the transcode folder to verify if this was a permissions issue, but noticed something else entirely. The file chunk being requested was never created and in fact it was never even attempted to be created…

I’m attaching the PMS logs with debugging enabled as well as my process monitor output in pms and csv format.

setup information:

  • Server OS: windows server 2016 datacenter edition ver.1607 build 14393.3384
  • Media is hosted on the PMS machine on a drive pool created via stablebit drivepool software
  • All media drives are internal connected via SATA-3 or SAS HBA
  • Server and all clients are hardwired via Ubiquity ER-X at gigabit speeds.
  • This happens across a verity of different formats/codecs
  • In all my testing the file being requested is always 1-4 numbers BEFORE the lowest numbered existing chunk, for example if the lowest chunk number is 30, the error will be looking for one of chunks 26,27,28,29…

buffering issue.zip (1.2 MB)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.