Jellyfin Forum
Playback Time Hack and Fast-Forward Issues a/w 10.9.7 - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Playback Time Hack and Fast-Forward Issues a/w 10.9.7 (/t-playback-time-hack-and-fast-forward-issues-a-w-10-9-7)



Playback Time Hack and Fast-Forward Issues a/w 10.9.7 - Brian - 2024-07-14

Since upgrading to 10.9.7 time hacks a/w television recordings are broken and fast-forward functions are not working normally; Transcoding operation appears to have changed.

Previously, when I paused playback or used fast-forward, the bottom left corner displayed how far you had progressed through the recording and in the bottom right corner displayed time remaining (hr:min:second format).

Currently, playback time hacks are off - One hour shows are said to be over five hours long (or sometimes something like "596523:1...") and when you fast forward you may advance somewhat, but the time hacks which are displayed, simply don't reflect reality.

Related or not, transcoding behavior has changed as well. Rather than dozens of .ts transcoding files being generated in the /var/lib/jellyfin/transcodes in response to a playback request, I'm seeing no files... or I'm seeing two very large and growing .ts files... or at this moment I'm seeing numerous .mp4 files.

On-screen behavior described is via Roku app. Strangely, playback via Firefox browser hangs on new and older recordings - just displaying spinning circle.

Apologies if these descriptions seem imprecise but behavior seems erratic and difficult to characterize.


RE: Playback Time Hack and Fast-Forward Issues a/w 10.9.7 - Brian - 2024-08-25

Further to earlier post and through v10.9.10...

Prior to these issues emerging, I could monitor integrated GPU activity with sudo intel_gpu_top as numerous relatively small .ts files were generated and written to /var/lib/jellyfin/transcodes whenever a recording was selected for playback. Once the entire show was processed, GPU activity would zero-out as playback continued.

Complicating matters, I've seen instances where a recording which generally exhibits the time hack issue will suddenly and for no apparent reason show correct time hacks! Thinking here particularly of a recent SNL recording which showed the expected 1:30:00 recording duration, and could be fast-forwarded and rewound normally. That said, prior and subsequent playback of this same recording suffered the time hack issue. I cannot detect a pattern to explain this intermittent behavior.

I appreciate that I'm a noob, but this time-hack issue has persisted through several Jellyfin upgrades and I'm at a loss. Any suggestions would be appreciated.