+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Media always restarts after segment 92 during transcoding (/t-media-always-restarts-after-segment-92-during-transcoding)
Media always restarts after segment 92 during transcoding - dfgfbhfhfgdsgfrsejikgfrfikg - 2025-07-26
This issue only occurs when playing media with the Android client. The Web client seems to work fine. My server is running in Kubernetes using the image lscr.io/linuxserver/jellyfin:latest. I pulled the latest release before running these tests. Jellyfin version is 10.10.7.
Playback starts as normal but then suddenly the video starts over from the beginning. Then it restarts the video again and again and again ... The player will continue doing this until I kill it and its delete cache in Android. App version is 2.6.3.
After enabling debug logging, this is what I see. In the log file last_500_lines.log (which won't attach to this thread for whatever reason - idk why or what to do about it because this forum doesn't even provide any error about that), on this line, segment 92 was requested:
[2025-07-26 10:19:13.525 -04:00] [INF] [8] Microsoft.AspNetCore.Hosting.Diagnostics: Request starting "HTTP/1.1" "GET" "http"://"jellyfin.jealwh.local""""/videos/757f8f68-a3f1-19c7-73df-12652e6f8b0e/hls1/main/92.mp4""?DeviceId=8f3b92422c3b3c5a&MediaSourceId=757f8f68a3f119c773df12652e6f8b0e&VideoCodec=h264,vp9&AudioCodec=copy&AudioStreamIndex=1&VideoBitrate=14874412&AudioBitrate=125588&AudioSampleRate=44100&MaxFramerate=23.976025&PlaySessionId=cbf4018c568946f4b9ab524837fe6b34&api_key=a6b2ceaf8faa4bf8b94bc52d45bcfd52&TranscodingMaxAudioChannels=2&RequireAvc=false&EnableAudioVbrEncoding=true&Tag=97f169c76f2a144b1df8f30a853ebdf7&SegmentContainer=mp4&MinSegments=1&BreakOnNonKeyFrames=False&h264-level=41&h264-videobitdepth=8&h264-profile=high&h264-audiochannels=2&aac-profile=lc&TranscodeReasons=ContainerNotSupported&runtimeTicks=5602260000&actualSegmentLengthTicks=104270000" - null null
After that, segment 0 was requested - a restart:
[2025-07-26 10:19:13.736 -04:00] [INF] [8] Microsoft.AspNetCore.Hosting.Diagnostics: Request starting "HTTP/1.1" "GET" "http"://"jellyfin.jealwh.local""""/videos/757f8f68-a3f1-19c7-73df-12652e6f8b0e/hls1/main/0.mp4""?DeviceId=8f3b92422c3b3c5a&MediaSourceId=757f8f68a3f119c773df12652e6f8b0e&VideoCodec=h264,vp9&AudioCodec=copy&AudioStreamIndex=1&VideoBitrate=14874412&AudioBitrate=125588&AudioSampleRate=44100&MaxFramerate=23.976025&PlaySessionId=cbf4018c568946f4b9ab524837fe6b34&api_key=a6b2ceaf8faa4bf8b94bc52d45bcfd52&TranscodingMaxAudioChannels=2&RequireAvc=false&EnableAudioVbrEncoding=true&Tag=97f169c76f2a144b1df8f30a853ebdf7&SegmentContainer=mp4&MinSegments=1&BreakOnNonKeyFrames=False&h264-level=41&h264-videobitdepth=8&h264-profile=high&h264-audiochannels=2&aac-profile=lc&TranscodeReasons=ContainerNotSupported&runtimeTicks=0&actualSegmentLengthTicks=104270000" - null null
I then restarted Jellyfin and tried again with the same file. In log file last_500_again.log, on this line, segment 92 was requested:
[2025-07-26 11:11:15.303 -04:00] [INF] [13] Microsoft.AspNetCore.Hosting.Diagnostics: Request starting "HTTP/1.1" "GET" "http"://"jellyfin.jealwh.local""""/videos/757f8f68-a3f1-19c7-73df-12652e6f8b0e/hls1/main/92.mp4""?DeviceId=8f3b92422c3b3c5a&MediaSourceId=757f8f68a3f119c773df12652e6f8b0e&VideoCodec=h264,vp9&AudioCodec=copy&AudioStreamIndex=1&VideoBitrate=14874412&AudioBitrate=125588&AudioSampleRate=44100&MaxFramerate=23.976025&PlaySessionId=5516da09b583426f8e3800e59d50727c&api_key=a6b2ceaf8faa4bf8b94bc52d45bcfd52&SubtitleMethod=Encode&TranscodingMaxAudioChannels=2&RequireAvc=false&EnableAudioVbrEncoding=true&Tag=97f169c76f2a144b1df8f30a853ebdf7&SegmentContainer=mp4&MinSegments=1&BreakOnNonKeyFrames=False&h264-level=41&h264-videobitdepth=8&h264-profile=high&h264-audiochannels=2&aac-profile=lc&TranscodeReasons=ContainerNotSupported&runtimeTicks=5602260000&actualSegmentLengthTicks=104270000" - null null
Then, AGAIN, it restarted:
[2025-07-26 11:11:15.665 -04:00] [INF] [16] Microsoft.AspNetCore.Hosting.Diagnostics: Request starting "HTTP/1.1" "GET" "http"://"jellyfin.jealwh.local""""/videos/757f8f68-a3f1-19c7-73df-12652e6f8b0e/hls1/main/0.mp4""?DeviceId=8f3b92422c3b3c5a&MediaSourceId=757f8f68a3f119c773df12652e6f8b0e&VideoCodec=h264,vp9&AudioCodec=copy&AudioStreamIndex=1&VideoBitrate=14874412&AudioBitrate=125588&AudioSampleRate=44100&MaxFramerate=23.976025&PlaySessionId=5516da09b583426f8e3800e59d50727c&api_key=a6b2ceaf8faa4bf8b94bc52d45bcfd52&SubtitleMethod=Encode&TranscodingMaxAudioChannels=2&RequireAvc=false&EnableAudioVbrEncoding=true&Tag=97f169c76f2a144b1df8f30a853ebdf7&SegmentContainer=mp4&MinSegments=1&BreakOnNonKeyFrames=False&h264-level=41&h264-videobitdepth=8&h264-profile=high&h264-audiochannels=2&aac-profile=lc&TranscodeReasons=ContainerNotSupported&runtimeTicks=0&actualSegmentLengthTicks=104270000" - null null
362ms later. WTF is Jellyfin doing?
There are no errors or problems in the log that I can see. There are no errors or any problems at all in the FFmpeg log. This problem happens with many media files, not just this one.
Settings like "Throttle Transcodes" and "Delete segments" are already disabled.
My /config/cache/transcodes folder is a RAMdisk so it is certainly fast enough for the transcoder process.
This failure happens long before playback actually reaches this point. 92 segments is about 9 minutes 20 seconds. The media failed/restarted only a of couple minutes into playback - not at the 9:20 mark.
So ... WTF is Jellyfin doing?
last_500_again.log.txt (Size: 198.05 KB / Downloads: 4)
RE: Media always restarts after segment 92 during transcoding - dfgfbhfhfgdsgfrsejikgfrfikg - 2025-07-27
This issue does not always occur at segment 92 but when it does occur it does seem to always occur at a specific segment with whatever media is being played. Today I started another video and it began restarting immediately. Here are the timestamps from that (i.e. log entries for "Request starting" for 0.mp4):
[2025-07-27 08:08:01.930
[2025-07-27 08:08:02.232
[2025-07-27 08:08:05.701
[2025-07-27 08:08:08.246
[2025-07-27 08:08:10.626
[2025-07-27 08:08:13.349
[2025-07-27 08:08:15.426
[2025-07-27 08:08:17.383
[2025-07-27 08:08:19.385
[2025-07-27 08:08:21.500
[2025-07-27 08:08:23.423
[2025-07-27 08:08:25.408
[2025-07-27 08:08:27.283
[2025-07-27 08:08:29.364
[2025-07-27 08:08:31.354
[2025-07-27 08:08:33.247
[2025-07-27 08:08:35.064
[2025-07-27 08:08:37.003
[2025-07-27 08:08:38.830
[2025-07-27 08:08:40.712
[2025-07-27 08:08:42.548
[2025-07-27 08:08:44.422
[2025-07-27 08:08:46.287
[2025-07-27 08:08:48.145
[2025-07-27 08:08:49.936
[2025-07-27 08:08:51.849
[2025-07-27 08:08:53.677
[2025-07-27 08:08:55.579
[2025-07-27 08:08:57.499
[2025-07-27 08:08:59.348
[2025-07-27 08:09:01.278
[2025-07-27 08:09:03.212
[2025-07-27 08:09:05.067
[2025-07-27 08:09:07.018
[2025-07-27 08:09:08.941
[2025-07-27 08:09:10.772
[2025-07-27 08:09:12.617
[2025-07-27 08:09:14.823
[2025-07-27 08:09:17.307
[2025-07-27 08:09:19.461
[2025-07-27 08:09:21.451
[2025-07-27 08:09:22.966
[2025-07-27 08:09:24.722
[2025-07-27 08:09:26.626
[2025-07-27 08:09:28.069
[2025-07-27 08:09:30.416
[2025-07-27 08:09:30.538
[2025-07-27 08:09:41.775
[2025-07-27 08:09:43.083
[2025-07-27 08:09:45.774
[2025-07-27 08:09:45.914
[2025-07-27 08:09:57.449
[2025-07-27 08:09:58.768
After letting Jellyfin fail over and over it eventually showed "A fatal error was encountered in the HLS stream" in the Android client.
Also, this problem only occurs when "Video player type" is set to "web player". Using "Integrated player" allowed the problem video the play - but the integrated player option is trash and is unusable for other reasons, as is the external player.
ALSO, I discovered that killing the app, clearing its cache, then opening the app will sometimes - completely randomly - cause the app to claim it cannot connect to the server next time I open the app. When this happens, the app will then NEVER connect to the server ever again. It just claims it can't connect. Meanwhile, the Web UI and other apps like Findroid can connect just fine - so the server is clearly working without a problem. Again, WTF is Jellyfin doing? The app just gets stuck in a weird state where it thinks the server it unreachable and refuses to attempt to try again even though there is a $%^%%$^ connect button! Clicking it makes it claim it still can't connect. To fix it, I AGAIN have to kill the app and clear its cache.
Jellyfin is horrible software.