Current broadcast contains DVR chunks of the previous broadcast
Possible cause: The broadcast is over, but the stream has not been stopped.Suggested solution: This is a normal behavior. To avoid this situation:
- Stop the stream when the broadcast is finished.
- Delete the DVR archive before starting a new broadcast.
Low-latency streaming is buffering
Possible cause: Perhaps end-user’s public internet speed and quality aren’t sufficient to download data in a timely manner. Suggested solution: For such users, provide an alternative viewing experience: display /master_mpegts.m3u8 link (HLS non-low-latency manifest URL from UI) in your player or add an attribute?no_low_latency to our built-in player.
Read more:
Manifest is empty and stream is not working
The stream is sent to ingester normally, ffmpeg or OBS show correct info. But the manifest .m3u8 is empty and the stream is not shown. Possible cause: The master stream is being sent with network problems, or the encoder settings are set incorrectly. Suggested solution: Our low latency solution has a latency of 4-5 seconds. If the delay is more than 5 seconds: Check the graphs for the relevant stream in your personal account under “Monitoring.” Frames per second, Interval between key frames, and Bitrate should be stable. If you see breaks in the graph, this means your stream is being sent from your encoder with issues. Check your encoder’s latency and settings. See the relevant sections in the documentation:- Input parameters of your live streams and videos
- Use RTMP protocol
- Use SRT protocol
- Use broadcasting software (ffmpeg, OBS, Streamlabs, etc)
Picture is falling apart
When you see this picture, it means there is packet loss in the network from your encoder to our ingester.