-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix native hls resume #1040
Fix native hls resume #1040
Conversation
This includes mobile Chrome, Android WebView and probably some Apple devices
Also make Safari to resume previous position faster
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed this fixes the resume issue I was seeing on Android.
What else should we look into fixing for an android release? |
We just need to add the GitHub and webhook releases to the CI for a new Android release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aside from this, it's all good.
IMHO this jellyfin/JavascriptSubtitlesOctopus#14 plus new Octopus release plus bumped Octopus release in jf-web so Android gets client-side rendering of SSA back. |
Fix native hls resume (cherry picked from commit 2223a16) Signed-off-by: Joshua M. Boniface <joshua@boniface.me>
Changes
Remove the hack that was used to resume HLS from previous position on Safari (actually it was used to resume everything, even direct plays, so Safari should have played 2.5 seconds of the beginning always) and implement a proper event-driven way to seek the stream only when it's really ready to be sought (should usually be faster than 2.5 seconds, but in reality depends on the bandwidth and the server).
Issues
Fixes the broken resume of non-direct play on mobile Chrome and Android app: