You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Playback media that is contained in a transport stream "ts" file in Direct Play mode (not transcoded) and observe that the duration is wildly inaccurate, and that seek back/forwards is impossible. Try the same media on a web browser or Android client and see that is works correctly.
How To Reproduce
Create two 10 second test files (a "ts" and a "mkv") with keyframes as follows:
The app only supports USB and DLNA IIRC so whichever is easier for you. Feel free to test any and all files you think may be bugged using the roku client
I just did a local play with these test files on USB in Roku Media Player and observed:
test_01 (h264 in a ts) plays, but there's now no controls available at all.
test_02 (h264 in a mkv) plays, with full controls working (e.g., pause, rewind).
So the difference with the "ts" file locally is the Roku now presents no controls at all!
Interestingly, with remote play of these on the Jellyfin backend there's no "FFmpeg.DirectStream" log created, unlike with Android or Firefox, which I guess is wrapping it in a HLS stream for them, but not for Roku clients?
I encountered this same issue (Direct Play of .ts files resulting in bad time hacks and disabled forward/rewind navigation) and my workaround was modifying app Settings-->Playback-->Video Codec Support and disabling "Support Direct Play" for both MPEG-2 and MPEG-4.
Software Versions
Describe the bug
Playback media that is contained in a transport stream "ts" file in Direct Play mode (not transcoded) and observe that the duration is wildly inaccurate, and that seek back/forwards is impossible. Try the same media on a web browser or Android client and see that is works correctly.
How To Reproduce
Create two 10 second test files (a "ts" and a "mkv") with keyframes as follows:
Then play them back via Firefox, Android, and Roku clients:
Expected behavior
Ability to seek back / forwards as per other clients.
Logs
n/a
Screenshots
See jellyfin/jellyfin#12244 (comment)
Connection Information
Additional context
I also filed jellyfin/jellyfin#12244 should this be a backend issue, however other clients don't suffer this issue.
The text was updated successfully, but these errors were encountered: