mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Playback issue since the 10.7.0 update #2772
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fabieng83 on GitHub (Mar 11, 2021).
I had no issues with Jellyfin before the update , everything was working perfectly , localy and remotely
i run jellyfin on a raspberry pi 4 , and i updated jellyfin using apt-get upgrade
When i direct play the file , it's working fine , but when the file is remuxed or transcoded , the stream never start.
Media Info of the file
Input #0, matroska,webm, from '/media/disk/film/2020/365.Dni.2020.mkv':
Stream #0:0: Video: h264 (Main), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 24 fps, 24 tbr, 1k tbn, 48 tbc (default)
Stream #0:1(fre): Audio: aac (LC), 48000 Hz, 6 channels, fltp (default)
Stream #0:2(fre): Subtitle: subrip (default)
Logs
In the logs , everything look normal , but i pasted the logs here https://pastebin.com/raw/2GC0Ceva
reading the logs , jellyfin think that the client has started playing the movie
FFmpeg Logs
https://pastebin.com/raw/bbnUDjTu
nothing suspect in here for me
Server System :
Client System :
n: APP: v2.2.3 Chrome: 89.0.4389.86
i've joined a .ts file to the ticket
5035405f707c6d86cb384ff805d1abdf24.ts.zip
@fabieng83 commented on GitHub (Mar 16, 2021):
hello ,
i can provide access to the server via ssh and http if some of you are curious about the issue.
@fabieng83 commented on GitHub (Mar 17, 2021):
Somebody on reddit had the idea to delete all the addons ,
i just did that , and it doesnt fix the issue.
when i look at my android client who tries to play a film , I see him going to 8sec then back to 0sec in a loop
@fabieng83 commented on GitHub (Mar 22, 2021):
update 10.7.1 doesn't fix the issue
@fabieng83 commented on GitHub (Mar 29, 2021):
downgraded today to 10.6.3 (the 10.6.4 deb was not available)
the issue is now fixed...