Xiaobian explains in detail how to build a live video system

In today's Internet society, if you want to have your own video live broadcast platform and a stable live broadcast system, you must first find a reliable CDN, and then find a reliable professional technology development cloud company. Especially after the mobile phone live broadcast became popular last year, this threshold suddenly became higher. Because the content generator becomes the mobile terminal. Let’s analyze why from a few points:

1. First of all, the producer of live video content is the streaming end. Now the mainstream IOS, Android, and IOS are relatively simple, just those few models, basically everyone adapts well. However, the fragmentation of Android is very serious, and a lot of energy needs to be adapted to Android, and the power consumption of software is generally very high. The mobile phone will get hot after using it for a while, and I am worried about whether it will explode. The user experience is that under different network conditions, the uploaded video may be stuck, may be incoherent, and various errors will be reported. This is impossible for him as a developer to adapt. To put it bluntly, the demand from the user is that the streaming end should not be stuck, the picture quality should be better, and it should not be too hot. This is the real question raised by the customers we have contacted. We extracted it from a somewhat technical perspective. What things correspond to.

2, and then the distribution network. The distribution network is actually hidden in a very back place, and users are actually invisible. Users can’t put forward the real demand for the distribution network, so basically this part of the demand will be put forward to the playback side, and the demand should not be stuck, and the screen should not be blurred. Make it too big. In fact, many of these are related to the distribution network of the source station, but users who do not see this requirement on the live video end will be connected to the following players.

For example, the first screen time is only viewed by users when they click on it. In the past, those open source architectures were rtmp servers, which could not be viewed by a single click. Now some open source domestic resources are written relatively well and can be seen. (yunbao) We developed it by ourselves, so it took some work to save the information of the previous keyframes, and users can see it with one click. This is a very detailed thing. If this is not done well, the screen will be black, green, or unable to see the image for a long time.

3. On the player's side, when we are receiving business, we encounter the most complaints from users, because all the problems are reflected when watching, and all the thunder must be carried by the players of the player. This requirement also cannot be stuck, and the delay cannot be too high. If the delay is too high, it needs to be chased back. The sound cannot be changed when chasing. It is best to control the chase strategy by yourself. This is the real demand of users.

To meet these needs, we need to do a good job of multi-resolution adaptation, to ensure good fluency, and to ensure that our catching up strategy will not cause any abnormalities. Therefore, many of these three terminals are coupled with each other, such as streaming and distribution, to ensure the smoothness and image quality of users, and to ensure low latency and smooth playback together with the player. One thing in common with all of these needs is not to freeze.

 

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325619519&siteId=291194637