5 hours ago
Since the Roku client 3.0.10 came out, sometimes, after viewing a show to completion; Jellyfin Roku, may not mark the show as viewed.
This happens more often if the playback has been interacted with, {pause, rewind, fast forward, for example.} However, even if playback has been interacted with it may still correctly mark it as viewed.
Conversely, playback has mot been interacted with, it will only sometimes incorrectly mark it as not viewed.
Regardless of if the clip has been interacted with or not, it will pick X:29 or X:59 as the point to resume from. This happens if the playback was allowed to play to completion or if it was interacted with, {pause, rewind, fast forward} with no correlation to when if, any interaction was done or the clip played in its entirety.
Thinking this could be a server issue, a selection of clips were played with the HTML web interface, without generating this issue, so it seems localized to the Roku client. This has been seen on different Roku boxes so it does not appear to be specific to a particular model of Roku.
Has any one else noticed this behavior?
This happens more often if the playback has been interacted with, {pause, rewind, fast forward, for example.} However, even if playback has been interacted with it may still correctly mark it as viewed.
Conversely, playback has mot been interacted with, it will only sometimes incorrectly mark it as not viewed.
Regardless of if the clip has been interacted with or not, it will pick X:29 or X:59 as the point to resume from. This happens if the playback was allowed to play to completion or if it was interacted with, {pause, rewind, fast forward} with no correlation to when if, any interaction was done or the clip played in its entirety.
Thinking this could be a server issue, a selection of clips were played with the HTML web interface, without generating this issue, so it seems localized to the Roku client. This has been seen on different Roku boxes so it does not appear to be specific to a particular model of Roku.
Has any one else noticed this behavior?
