This feature in Platform allows you to send Live Streaming publications to social networks and platforms that accept RTMP publication, for example Faceboook, Youtube, among many others. This tool is only active in platform's Live video signals.
To use this function you must go to the Live menu, then select the desired Live and follow the steps below:
Click on the " +" button located on the upper right side of that section.
Two options will be displayed from which you must choose, according to what you need, Custom RTMP or Social Network.
With Custom RTMP you can publish to any platform that accepts this protocol, also configure these parameters manually from the social network interface (YouTube-Twitter-Facebook), otherwise if you use the Social Network option, the Facebook accounts linked in the Settings>Integrations module will automatically start publishing, without having to configure the publishing point.
RTMP configuration
To use this option by RTMP, we have to fill in the indicated fields:
Name: it assigns a name to identify the associated restreaming, it is not visible to the end user..
Publishing Point: in this section the rtmp publishing point of the external platform is assigned.
Stream ID: the stream ID assigned in the external platform
Quality to Restream: It will it allows you to select the quality according to the video bitrate configured in the signal (Live - Ecoding Profile). In case of selecting Choose for me, it will choose the 720 quality by default.
Once completed all these fields, you must click on Save to confirm the changes. In the platform section, the configured restreaming will be displayed with a gray box with an R and the assigned name.
Setup using Social Network
To use this option through Social Network, you must complete the fields listed below:
Name: assigns a name to identify the restreaming in platform.
Title: assigns a name that will appear associated to the content retransmission in the assigned facebook account.
Description: To add a description to the broadcast.
After completing the fields, select the facebook account you want to integrate with this restreaming.
Once these data have been completed, simply save the changes. In the platform section, the configured restreaming will be displayed with the RRSS logo and the assigned name.
Please keep in mind the following points:
The feature can have up to a maximum of 3 simultaneous live streaming retransmissions.
The RTMP broadcast will take up to 6 hours, with the highest quality available.
The YouTube and Twitter accounts assigned in integrations are not displayed in the Social Network configuration, because the RRSS does not have the automatic start option.
Once the retransmission has been assigned in any of the 2 ways, you only have to press the start button on the corresponding restreming.
Aspects to be considered for retransmission
1- Speed:
As a first step, before starting to publish a content, it is necessary to perform a speed test, especially the upload bitrate, since this is linked to the quality of the broadcast we must configure; it is recommended to perform this test on the page https://testmy.net/ is very fast and accurate when giving the results, and is hosted 100% in the USA, another page that can be used is https://www.speedtest.net/es The recommended bitrate should be at least 10 MB upload.
2- Social networks (resolution 720):
For a correct use of restreaming, you must consider the recommendations provided by each of the networks to reduce the number of alerts during transmission, below we will review each of them before knowing the recommended configuration for the encoders that send the signal to platform.
YouTube Recommendations
Frame rate: 30 fps
Bit rate: between 1500 and 4000 kbps
Keyframes: 2-4 seconds
Codec profile: H.264 Baseline Profile level 3.1
Audio codec: AAC-LC
Audio bit rate: 128 kbps
Audio sampling rate: 44,100 khz
Bit encoding rate: CBR
Facebook Recommendations
Frame rate: 30 fps
Bit rate: between 2000 and 4000 kbps
Keyframes: 2 seconds
Codec profile: H.264
Audio codec: AAC-LC
Audio bit rate: 96 to 128 kbps
Audio sampling rate: 48,000 khz
Bit encoding rate: CBR
Twitter Recommendations
Bit rate and video codec : 2500 kbps (recommended), 4000 kbps (max), H.264
Bit rate and audio codec : AAC-LC 128 kbps
Frame rate : 30 fps
Resolution : 1280 x 720
Keyframe interval : no more than 3 seconds.
Encoding Profile and encoder configuration for a correct restream using Platform
To properly integrate the emission to platform, the parameters we have configured in this must match exactly in the encoder, as any of the platforms mentioned, generates a series of alerts if they are not receiving the signal appropriately, also keep in mind the minimum configuration requested by other rtmp services available.
As a standard and for the best user experience, you should manage the broadcast in the encoder with the following parameters, these work perfectly for platform and for the 3 social networks:
- Maximum resolution: 1280x720 or 1920x1080 as required
- Frame rate: 30 fps
- Maximum bit rate: 2000 - 2500 kbps for 720p / 4000 for 1080p
- Minimum bit rate: 1000 - 1500 Kbps ( only if the RRSS buffer does not respond correctly, considering that it affects the original platform output)
- Key frames: every 2 seconds (recommended), maximum 4.
- Codec profile: H.264 Baseline Profile level 3.1
- Audio codec: AAC-LC- Audio bit rate: 128 kbps
- Audio sampling rate: 44.100 khz
- Bit encoding rate: CBR
At the end of a live restreaming broadcast, it is not necessary to delete the added links on the platform, but for every new retransmission it is advisable to check the publication parameters given by the networks again, as these could change without prior warning, causing an error when starting the retransmission from platform.
To avoid errors when finishing, it is better to stop the broadcast first in platform before stopping it in the social network, otherwise it will immediately generate an alert and the restream controls will be stuck.
Keep in mind that you can publish any content to the networks, if they detect a minimum copyright abuse, they alert and cut the broadcast in less than 5 minutes, and it is totally unrelated to Mediastream.
The person managing the RRSS rooms, is fully responsible for initiating and controlling the alerts on them, it should be noted at this point that any alert generated in the RRSS can be directly associated with internal issues of their servers; always be aware of the monitor and reception in platform.
If you have any related questions please do not hesitate to write us through the chat.
Atte. The Mediastream Team
