Quortex supports RTMP and RTMPS as input protocols. Although it offers less flexibility and resiliency than SRT, RTMP is still widely available and can be used for ingesting your stream. You can check this article if you want to learn more about SRT and RTMP protocols.

Selecting RTMP

When using RTMP, the endpoint will be automatically created by the platform. Hence, you don't have any parameter to enter.

Push your RTMP stream to the platform

Once your input is created, the platform will generate two RTMP endpoints:
One with RTMP, without stream encryption (rtmp://{endpoint})
One with RTMPS, with additional stream encryption (rtmps://{endpoint})
Both versions can be used without any further configuration, but both can't be used at the same time.

The RTMP endpoints are shown when clicking on the input details.

Example using ffmpeg

For this example, we will use ffmpeg to ingest streams in the platform. The following command line will stream a sample colorbar with a timecode to the Quortex platform:

ffmpeg -re -f lavfi -i testsrc=duration=3600:size=640x360:rate=25 -c:v libx264 -b:v 100000 -pix_fmt yuv420p -an -f flv rtmp://{endpoint}

Once the RTMP handshake is made, the platform will switch from "Listening" to "Connected" and "Receiving" state


This is it!

Get stream status

RTMP offers limited information on the stream status. Still, you can monitor your RTMP streams by going to the "status" tab and selecting "RTMP" streams. The input bitrate will then be shown.



You may want to use SRT to get detailed information about the link bandwidth, the amount of dropped packets and the link QoS.

Updated on: 01/03/2024