Server Version#: 1.30.0.6486
Player Version#: 5.51.1
Ok big brain people… Shed light on this and prove it is not a player bug!
Bottom line up front: Console output displayed on Vizio TV reports, “WARN Reporting timeline but position is greater than duration, defaulting to duration!”
4K UHD Blu-ray remuxed to .mkv files end randomly, but repeatably at the same point for each file. The player marks them as “Watched” and not as ended at a certain point. 1080p files do not seem to exhibit the same behavior (not extensively tested due to lack of content). Files play normally on other players (web and Roku) and directly (via computer). Files have previously played flawlessly on Plex for Vizio player. Behavior was first noticed in late September or early October of 2022. Last flawless experience with the player was most likely July 2022. It is likely that a change in between this time period introduced this error. I have previously posted concerning this error, but with new information, felt it best to start a new thread.
Previous post: Vizio Plex client ends 4K movies after a few minutes, marks as watched
The server logs show no errors with playback. However, I recently had the Plex for Vizio player output the console to the TV and noticed the following warning: “WARN Reporting timeline but position is greater than duration, defaulting to duration!” This warning fits with the server log which shows updates on the play status and timeline until the time stamp where the console reports the WARN notice. After the WARN notice, the server reports that the movie reached the full duration and shows normal entries which you would expect after a file completed streaming. In short, from the server’s perspective, the file played normally, reached the end, and was terminated properly.
Now, there is the possibility that Plex for Vizio has started to require a piece of metadata that was previously optional in the .mkv format. If this is the case, I would love to know so I may incorporate that newly required info into my work flow and prevent this problem.
Anyone care to shine light on this issue?
(Additionally, I have also tried multiple servers, one ARM, one Intel, both running Debian Linux, and both wired and wireless connection to the TV… in all scenarios, the results were identical, exhibiting the same described behavior.)
