Streaming is not proceeding due to insufficient network bandwidth for live streaming or incorrect RTMP address.
We inform you about situations where streaming does not proceed due to insufficient network bandwidth for live streaming or incorrect RTMP address.
The current error occurs when the connection between the PRISM app’s RTMP streaming engine and the live platform’s RTMP receiving server is lost for more than 10 minutes.
And this situation can be divided into two cases as follows.
- A case where the connection was disconnected during live streaming and could not be reconnected for more than 10 minutes.
- A case where the connection could not be made for more than 10 minutes from the start of the live streaming. (The situation was not connected even for a moment)
I will walk you through the details.
1. A case where the connection was disconnected during live streaming and could not be reconnected for more than 10 minutes.
This case is due to a problem with the network status.
The live streaming process has the heavy task of transmitting large amounts of video data over the network in real time. That is why it is of utmost importance to have a stable and sufficient bandwidth network.
Even when using a network with sufficient bandwidth, the bandwidth may be temporarily reduced due to external circumstances. For example, when someone else is sending or receiving large amounts of data on that network.
Therefore, it is essential to check the status of the current network in advance before live streaming.
However, if you are unable to adjust your network environment right away, you may want to consider adjusting your live streaming settings as a workaround.
This streaming will require more network bandwidth because higher resolutions are made with a larger amount of data. Therefore, if your network is not enough, it is advantageous to select a lower resolution to make stable streaming.
It may also be helpful to set the ‘Video Quality’ option to ‘Adaptive’ among the streaming options provided by the PRISM app. This is a function that adjusts the amount of video data in real time according to the current network conditions.
This option is set to ‘Adaptive’ by default when installing the PRISM app. However, if you ever change this option, we recommend that you set the option to ‘Adaptive’.
2. A case where the connection could not be made for more than 10 minutes from the start of the live streaming. (The situation was not connected even for a moment)
This situation may also be caused by a problem in the network, please refer to the information above for network problems.
And it can also be caused by various situations such as the list below.
(1) When the RTMP address format is invalid
(2) When the RTMP address form is valid but there is no such address in reality
(3) The problem between the streaming engine of the PRISM app and the live platform
(4) The problem with the streaming rights of the streamer on the live platform.
I will explain each item in more detail.
(1) When the RTMP address format is invalid
RTMP address consists of RTMP Stream Url and RTMP Stream Key.
If the RTMP Stream URL is ‘rtmps://prismlive.com/rtmp/’ and the RTMP Stream Key is ‘2twt-wwvu-gxqa-e97d’, the RTMP address is combined with the following form.
‘rtmps://prismlive.com/rtmp/2twt-wwvu-gxqa-e97d’
In general, RTMP addresses cannot have spaces, nor do they contain strings that refer to web protocols such as ‘https://'.
If the current error repeats, please check if the RTMP address you are using is in the correct format.
(2) When the RTMP address form is valid but there is no such address in reality
In some cases, even though the RTMP address is valid, it may not be able to connect to the RTMP server of the live platform. This is the case when the entered address is an RTMP address that does not actually exist.
The following YouTube RTMP address is an example.
‘rtmp://a.rtmp.youtube.com/live2/prismlivestudio’
There is no problem with that form. However, the actual YouTube RTMP Stream Key consists of a list of characters that do not have any meaning as follows.
‘rtmp://a.rtmp.youtube.com/live2/2twt-wwvu-gxqa-e97d’
If the current error repeats, please check if the RTMP address you are using is the correct address.
(3) The problem between the streaming engine of the PRISM app and the live platform
In some cases, an actual RTMP address is used, but the RTMP streaming engine of the PRISM app cannot connect to the RTMP data receiving server of the live platform.
The RTMP streaming engine of the PRISM app has been successfully connected to the RTMP servers of popular live platforms such as Facebook, YouTube and Twitch. However, anyone can build their own RTMP data receiving server, and as a result, there are platforms that do not comply with the RTMP standard.
In this situation, the issue may need to be fixed in the live platform and not in the PRISM app so that the error can be addressed. Therefore, it becomes difficult to solve the problem, and it takes a lot of time even when the process of solving the problem begins.
(4) The problem with the streaming rights of the streamer on the live platform.
Most live platforms manage the live streaming rights of streamers. And depending on its own operating policy, there are situations in which the streaming rights of streamers are restricted when necessary.
In this situation, even if you try to stream with your own RTMP address, the live broadcast may not be exposed on the service page of the live platform.
And since this is a situation according to the processing inside the live platform, you should try to solve the problem through the customer center of the live platform.
- Android error code : 5007
- iOS error code : -1001 / -1
