-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roku client appears to NOT update NFO file after video finishes playing through to the very end #1814
Comments
Maybe related to the following issue:- #1567 The app handles the |
@thecodygriffin can you give #1941 a test when you get a chance? |
@cewert Is it fair to assume that I will need to build the Roku app with the #1941 pull request and then side load it to test? If so, I may not be able to do that myself for a few weeks. Otherwise, if there is an existing test build you can point me to, I can side load it sometime this weekend and test. |
Yes, you will need to sideload the app to test but you don't have to build it unless you want to use the debugger and see debugging output. Our CI automatically creates a build zip for all PRs https://github.com/jellyfin/jellyfin-roku/actions/runs/11086513250?pr=1941 |
Unfortunately that doesn't fix my problem of the video player not returning to SDR mode after playing a HDR/DV file to completion. In fact it's still not registering a finished state. |
Here's a video showing the issue:- https://streamable.com/d4wqgk Watching the activity in the Jellyfin server you can see that when stopping media using the back button on the remote the server registers a finished state, however when the media naturally stops at the end with no user interaction no finished state is being sent to the server and the server still thinks the video is active. |
@cewert similar to @roidy findings, the build from https://github.com/jellyfin/jellyfin-roku/actions/runs/11086513250?pr=1941 did not resolve this issue. The NFO file is still not updating upon the "natural" conclusion of a video. |
@thecodygriffin There was a bug in that build. Sorry for not giving you the new link. Can you try this build as well? That's the current build for #1941 |
@cewert Success! The latest build from https://github.com/jellyfin/jellyfin-roku/actions/runs/11087871463?pr=1941 resolves the issue. I confirmed that the NFO file was updated in the following scenarios:
I also verified that the NFO file is still updated when existing it early prior to the conclusion. Thank you for your work on this. I can't wait until the fix makes it into an upcoming release. |
Software Versions
Describe the bug
Upon allowing a video to play through to the very end, the Roku client appears to NOT prompt the update of the corresponding NFO file.
To be very specific, "watched" is NOT updating from "false" to "true" in the corresponding NFO file.
Prerequisites To Reproduce
How To Reproduce
Expected behavior
The NFO file is updated including "playcount" and "watched" among others when applicable
Logs
There are no [ERR] messages in the logs for my testing time range. There was an instance of the following [WRN] message, but it does not appear to correlate with the behavior experienced.
[2024-07-03 10:52:25.892 -04:00] [WRN] WS "10.16.8.1" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
Connection Information
Additional context
If the video is exited by the user prior to conclusion, the NFO file is updated as expected whether that be the "watched", "playcount","lastplayed", or "resume" values.
Furthermore, the behavior is NOT reproducible from the Android or Web clients.
The text was updated successfully, but these errors were encountered: