In a research that was conducted to see the correlation between video stream lag and user retention, it was discovered that between 15-20% of the viewers could wait for more than nine minutes if there were an issue with a video’s content. This means that it is easy to lose 80% of your audience if the video experience is bad. If you have bad content, 25% of your viewers will leave before the video runs for 4 minutes. 

If you want time to develop troubleshooting tools, then you need to go for conventional broadcasting as it will allow you to undertake rapid detection of delivery chain issues. In this complex process, you will work with broadcast operation centers. When an issue arises, an operator can spot it quickly and identify the stage that has the problem. Although this process works, it is not good for broadcasters. 

When we look at the chain of video stream monitoring, you will see that there are a lot of elements being combined. And it will be essential to understanding the area of the problem. We are going to look at an example of a streamer, without the end viewers and the platform which cannot be monitored because the output originates from the platform side. 

When we start looking at multistreaming, we get into a more complicated environment because the chain has more elements. Each extra platform has its network path where stability and quality are dependent on other factors. 

How can we identify and resolve an issue? 

Firstly, we need to look at the video stream. This will allow you to know the network connection and the devices causing the problem. This will help you to see the elements in the chain that are causing problems. Ideally, it is the corrupt or missing data from video stream that should be reported by the delivery chain devices. This specific data will have to be provided in real time, making the problem easy to detect as soon as it happens. 

Which information is important? 

You need to ensure that you get as much information as needed, starting from your first chain link. Part of the data that you will collect will start because it is the metadata that describes the settings that the encoder provides. Some of the feedback that you can get include: 

  • FPS
  • Bitrate
  • Keyframe interval
  • Dropped frames
  • Video resolutions
  • Audio codec and frequency
  • Video resolution
  • Video Codec

Route checking to end platforms 

If one of your platforms identifies stream lagging, or users start to complain about lags and quality, then you need to look at the graph of the platform. As you check on the platform, ensure that the settings you have fit all the end platforms. If you have the wrong settings, they will lead to several issues. If your settings do not meet the requirements, there is no need of searching for a problem. 

Point to note: if an outgoing stream issue is identified, look at the requirements of a platform and check on the settings to see if they need to be adjusted. This is one of the most common issues that need to be resolved.