Forum Discussion
Stream Live Event has a 50 second delay
MicrosoftWhen you were playing back the live event and got the 50 second delay what OS and browser where you on?
My understanding was that we typically had a delay of about 20-30 seconds so 50 seconds seems higher than my understanding. I'm checking with some folks on our engineering team that own this layer to understand if 50 seconds is normal or not. But they wanted to know the above.
Windows 10 Pro - Teams Desktop Application/IE/Chrome (Teams)/Chrome (Stream Site)
Mac OS 10.13.6 - Teams Desktop Application/Chrome (Teams)/Chrome (Stream Site)
iPhone Xs Max 12.1.1 - Teams iOS App/Safari (Stream Site)
I attached a screenshot where you can see OBS on the right streaming an http://www.clocktab.com/. Top Left view is Teams and bottom is Stream. You can see the delay in the broadcast equalling around 50 seconds. I loaded the Teams Live Event on Teams on my iPhone and it was the same delay.
Here is a link to a desktop recording of the delay.
https://youtu.be/rINXmPJ96-s
- Marc Mroz
Thanks for the extra info. I'm passing it on to our engineering team that knows this layer to find out if 50 seconds is within expectations or if it's higher than we'd expect.
Marc Mroz Is there any update on the latency? We're trying to use an external encoder as well for our company presentations and we're having the same issues with 30-40 seconds of delay between the encoder and the livestream. It makes it really hard for our work from home staff to engage in the presentation.
I have found that when encoding for HLS that 30-40 second delay is normal. We get around this by prompting for local questions/interaction until the content reaches our remote audience, not ideal but it works. Hope this helps.
From http://www.wowza.com/blog/hls-latency-sucks-but-heres-how-to-fix-it
"When changing an adaptive stream in HLS, it demands a new buffer to be built. At the time of this article, Apple defaults to 10-second content chunks and a certain number of packets to create a meaningful playback buffer. This results in about 30 seconds of glass-to-glass delay seconds from capture to final packet assembly. But, when you introduce CDNs for greater scalability, you inject another 15-30 seconds of latency so the servers can cache the content in-flight – not to mention any last-mile congestion that might slow down a stream."
More about HLS from Encoding.com
https://www.encoding.com/http-live-streaming-hls/
