RTMP publishing and reception

Perfect Streamer works with RTMP and RTMPS as a client: it publishes an SPTS stream to an external ingest point (a video platform ingest or any RTMP receiver) and pulls a stream from an RTMP source on demand. Accepting incoming publications (push ingest, “the way video platforms do it”) is not supported — for such scenarios use a bridge through an external application (Other inputs and outputs). RTMP is available to SPTS streams only.

Publishing (output of type rtmp)

The output is added on the stream’s “Outputs” tab (the field names are those of the interface):

URL (rtmp(s)://…)

The address of the ingest point, including the stream key as issued by the receiving platform.

Bind interface

The local interface of the outgoing connection.

Client timeout

The connection timeout, 10 seconds by default.

Allow HEVC (Enhanced RTMP)

HEVC is published through the Enhanced RTMP extension (enabled by default; an additional setting). For receivers without Enhanced RTMP support, turn it off — only H.264 will then be published.

Verify TLS certificate

For RTMPS: verification of the server certificate (disabled by default; an additional setting).

The publishing format is a single program: one H.264 or HEVC video and no more than one AAC audio track. A multi-track source is narrowed down by PID filters at the stream input (MPEG-TS filtering); audio tracks in other formats are discarded. If the track layout is incompatible with RTMP, publishing does not take place — the reason is shown in the output statistics (Stream statistics).

Reception (input of type rtmp)

An input of type rtmp pulls a stream from an RTMP source by its URL: the node connects as a client, the received stream is remultiplexed into MPEG-TS and goes through the usual SPTS pipeline (Processing pipeline). The settings are the same: URL (rtmp(s)://…), Bind interface, Client timeout and Verify TLS certificate for RTMPS.