Closed sellibitze closed 2 years ago
Found the culprit in Jellyfin Web. Since the web client thinks we're transcoding, it adds the transcoding offset to the current time, which is wrong, as External player direct plays. Fixing the External player profiles should fix this bug.
Still seems to be an issue, according to #602. Needs more investigation.
I'm able to reproduce the issue in the new version but only when there are subtitles for the video. The player profile lacks the supported subtitle formats so the server still thinks the video needs to be transcoded. Seems like adding them fixes the issue.
Please describe your bug
Steps to reproduce:
I'm not sure which side is to blame here. The server side or the client side. So, I'm opening the issue here.
According to the attached jellyfin logs, the wrong time stamps also appear as reported by the client:
The second time stamp should be around 360000 ms (6:00). So, if that is really what the client was reporting, the client is at fault, I guess. But it might also be a value (wrongly) adjusted by the server -- maybe because the server thinks the client's "epoch" (0:00) starts at 5:00 (last resume point).
Jellyfin Version
10.7.7
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct