Closed bchah closed 2 months ago
For a long time, when playing directly in Safari, there has been an intermittent problem where playback starts in legacy HLS due to a slow network or unknown reasons, but in that case, if you move the seek bar below to the latest, playback starts in LLHLS again. There seems to be a condition where Safari starts playing LLHLS in legacy mode under certain conditions. I don't think this has anything to do with OME 16.4.
The LLHLS native player included in Safari appears to be in beta. In my opinion it is more unstable than any player like hls.js or shakea. One thing I've experienced is really surprising: until iOS 17.1, LLHLS forced the bitrate with the lowest ABR to be selected. This was fixed just recently in 17.2.
In any case, it is unlikely that this is a regression bug in OME since there have been very few LLHLS-related patches recently, but I will look into this again when I have time in the near future.
On my Iphone, the problem with low LLHLS bitrate in safari is not reproduced on 17.2 beta 2, but it is reproduced on the 17.2 release, and also not reproduced on the 17.3 release. Based on this, I think that they finally released it in 17.3 :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug Apple devices which do not support HLS.js are falling back to regular HLS instead of native LL-HLS playback.
To Reproduce Start an LL-HLS stream and view it from an iPhone or another device which does not use HLS.js for LL-HLS - it will not have the same low latency as HLS.js / OvenPlayer.
Expected behavior In the past, native playback of LL-HLS worked well with 2-3s latency but now it seems to fall back to regular HLS with 15-20s latency instead
Server (please complete the following information): OME 0.16.4 on Ubuntu Docker
Player (please complete the following information):
Additional context I'm not sure whether this is an issue with the latest Apple OS or OME 0.16.4. Is anybody else able to reproduce the issue?