Introduction
Real-time messaging Protocol, or RTMP, is a live streaming protocol that provides high-performance transmission of video, audio, and data between an encoder and a server across the Internet. RTMP is an essential part of live streaming and is supported by most streaming providers, encoders, and platforms.
RTMP Syntax
Videolinq accepts RTMP streams originating from hardware or software encoders. When creating a channel and selecting RTMP as a video source, we present you with the RTMP path that uses by default TCP port 1935 in a path, followed by a stream key. Here is an example of a generic RTMP path and stream key. These values can be copied and used by most streaming encoders:
rtmp://go-xx.videolinq.net:1935/ingest?user=tgwpFv9sOp@pKmKNTwe:dyBNIlZa4N
cC9jY42w@pKmKNTwe
Some encoders do not support the insertion of a separated RTMP path and stream key. Simply add the stream key at the end of the RTMP path like this:
rtmp://go-xx.videolinq.net:1935/ingest?user=tgwpFv9sOp@pKmKNTwe:dyBNIlZa4N/cC9jY42w@pKmKNTwe
Some encoders or platforms will require a username and password:
RTMP: rtmp://go-xx.videolinq.net:1935/ingest/
Stream key: cC9jY42w@pKmKNTwe
Username: tgwpFv9sOp
Password: dyBNIlZa4N
Customers who want to secure the stream sent to Videolinq can use the RTMP path and stream key provided and change RTMP to RTMPS. Read below.
Using RTMPS
RTMPS (RTMP over SSL) provides a secure and reliable way to stream live video, protecting data during transmission by encrypting the connection between the broadcaster and the streaming server. This ensures that sensitive information, such as stream keys and authentication credentials, cannot be intercepted or tampered with by malicious actors. With growing concerns over privacy and compliance with data protection regulations, RTMPS is increasingly essential for users who need secure streaming solutions for business-critical events, live broadcasts, or monetized content. By using RTMPS, users can build trust with their audience and meet industry standards for secure live streaming.
How to Use RTMPS with Videolinq?
Configure an RTMP video source and copy the RTMP path and stream key.
Change the values to convert the RTMP path to an RTMPS path. Use the RTMPS path in your media encoder. Here are the changes you will need to make:
Sample RTMP path
rtmp://go.videolinq.net:1935/ingest?user=AHGTs5K214@pKmjHTw5:GHsNAdAYg7
Sample RTMPS path (add the letter "s" and change the port number)
rtmps://go.videolinq.net:443/ingest?user=AHGTs5K214@pKmjHTw5:GHsNAdAYg7
There is no change to the stream key or the rest of the Videolinq workflow.
Bitrate and Resolution
RTMP can be generated by software encoders, hardware encoders, or 3rd party streaming service providers and media platforms. Regardless of what your RTMP source is, for proper capture and signal re-distribution, the RTMP stream must meet the following requirements:
Resolution between 720p to 1080p.
Video bitrate between 2 to 8 MBps (8 MBps maximum).
Audio bitrate between 60 to 128 KBps.
Video encoded with H.264 Baseline, Main, or High profile.
Video frame rate up to 60 frames per second.
Insert a keyframe (GOP) every 1 or 2 seconds.
Use Constant Bitrate (CBR) and not Variable Bitrate (VBR).
Adaptive Bitrate (ABR) is not supported.
To satisfy output to most social media platforms, we recommend the following configuration: CBR Video of 1920x1080 resolution at 6 MBps using the H.264 Main profile, 25-30 frames per second with a keyframe every 2 seconds, and audio at 128 Kbps Stereo using the AAC codec.
Videolinq will reject RTMP streams that lose packets on the way after a few minutes of transmission.
Signal Monitoring
The channel preview player provides a good indication of the incoming RTMP/RTMPS stream. The stream you see in the preview player was received by Videolinq and distributed to the Videolinq content delivery network (CDN). The stream is then pulled back into the preview player, providing a simulation of the quality you can expect to see when you point to the stream with a player or distribute the feed to social media or third-party platforms. Remember to insert one keyframe every two seconds to start playback faster.
If you have questions about this article contact technical support.