Hello @Nguyen_Canh_Toan thanks for reaching out, I think what stands out here for me is that not all HLS players support LL-HLS and I am not sure about that chrome extension player, but I don’t think it does based on a bog I read:
On the other hand, players that had not been optimized for LL HLS, like the Native HLS Playback Chrome extension, showed latency as high as 26 seconds, which tends to prove that LL HLS is backward compatible on non-LL HLS players, though at normal latency.
There are player that do support LL-HLS and you can see some of those here:
You can test LL-HLS streams by entering the playback URL in the Safari browser on iOS 14, other native apps on devices running iOS 14, or any player that supports LL-HLS. If a player supports HLS but not LL-HLS, it will default to playing LL-HLS streams as standard HLS at a higher latency.
Also make sure you are starting on a keyframe- that’s very important because the video won’t start until it seeks out the keyframe.
Please get a support ticket so we can spare you the trouble of trying to troubleshoot this, we need full access to your configuration and files to accurately diagnose the problem.
For a single stream, we confirmed that the LL-HLS delay time is 5-6 seconds in Safari.
Is this same 5-6 second delay observed with multiple streams (ABR) as well?
I’m currently testing this on my iPhone, but whenever I load it, I experience a delay of 20 seconds, though it drops to 5-6 seconds if I immediately adjust the progress bar.
Hi Jungin,
I was unable to reproduce the behaviour you described. As such, it’s possible that this issue is either limited to your environment or the player you’re using.
I tested playback using the Wowza-Flowplayer demo page and recommend you test with this player too as this should help to narrow down the cause of this problem.
If you’re still having issues with latency of adaptive bitrate streams with the LL-HLS protocol, I recommend that you create a ticket with the Technical Support Team and ensure to provide them with the configuration files, log files created during the reproduction of the issue and a copy of the .smil file used for playback.
If the stream is live and publicly available, the HLS playback URL that’s used would also be helpful for the Technical Support Team to troubleshoot further. Please share this in the ticket (not the public forum).
Regards, Jason Hilton
Senior Technical Support Engineer WOWZA | The solution you start with, the partner you scale with.
