[PR #7338] [MERGED] fix HLS transcoding on android tv -- dont use -noaccurate_seek for hls transcode #11171

New issue

Closed

opened 2025-12-22 08:35:03 +01:00 by backuprepo · 0 comments

backuprepo commented

2025-12-22 08:35:03 +01:00

Owner

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/7338
Author: @mueslimak3r
Created: 2/19/2022
Status: ✅ Merged
Merged: 3/1/2022
Merged by: @crobibero

Base: master ← Head: hls-remove-seek-param

📝 Commits (1)

36cdeaa dont use noaccurate_seek for hls

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 MediaBrowser.Controller/MediaEncoding/EncodingHelper.cs (+1 -0)

📄 Description

Changes

dont use -noaccurate_seek for hls

Issues

exoplayer in the Android TV client would get chunks with video that starts earlier than their timestamps. Typically it would be around 4 seconds behind.

when testing with https://github.com/jellyfin/jellyfin/pull/6600 on Android-TV I found segments were still inaccurate (off by the time difference between two keyframes), even though the requested time was keyframe-aligned. I assume this is because even though the requested timestamp is keyframe aligned, ffmpeg still only goes up until the preceding keyframe.

This issue also occurred in the android (mobile) client using the web player backend

The main resulting issue is that subtitles handled externally can't be synced to the video

Notes

with both hls and progressive encodes excluded, and dash not supported, I'm not sure if this block will ever run

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/7338 **Author:** [@mueslimak3r](https://github.com/mueslimak3r) **Created:** 2/19/2022 **Status:** ✅ Merged **Merged:** 3/1/2022 **Merged by:** [@crobibero](https://github.com/crobibero) **Base:** `master` ← **Head:** `hls-remove-seek-param` --- ### 📝 Commits (1) - [`36cdeaa`](https://github.com/jellyfin/jellyfin/commit/36cdeaa53c0bee8ede6d5ecf66ca629ab55ab3d7) dont use noaccurate_seek for hls ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `MediaBrowser.Controller/MediaEncoding/EncodingHelper.cs` (+1 -0) </details> ### 📄 Description **Changes** * dont use -noaccurate_seek for hls **Issues** * exoplayer in the Android TV client would get chunks with video that starts earlier than their timestamps. Typically it would be around 4 seconds behind. when testing with https://github.com/jellyfin/jellyfin/pull/6600 on Android-TV I found segments were still inaccurate (off by the time difference between two keyframes), even though the requested time was keyframe-aligned. I assume this is because even though the requested timestamp is keyframe aligned, ffmpeg still only goes up until the preceding keyframe. This issue also occurred in the android (mobile) client using the web player backend The main resulting issue is that subtitles handled externally can't be synced to the video **Notes** * with both hls and progressive encodes excluded, and dash not supported, I'm not sure if this block will ever run --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>