Skip to main content

RTMP Route Examples

The following walk-throughs step you through the process of creating various routes:

Creating a Route Using RTMP Input Example

RTMP is a TCP-based protocol that allows for low-latency communication while maintaining persistent connections between the player and the server – making it ideal for LIVE broadcasting/streaming (e.g., with the popular GoPro devices). Our RTMP Input Hublet has two modes: Consumer and Publisher. The Publisher mode will provide you with an ingest URL once the route is started. The same URL will be used every time the route is started.

To create a route using the RTMP Input Hublet:

  1. Create a route and add an RTMP Input Hublet
  2. Change the Mode to Publisher

    Route Builder Screen, labeled, with a Hublet panel open. The cursor is hovering over the Publisher option in the Mode dropdown menu.

  3. You can use the random Stream Key
    , or specify one manually by unchecking the Generate a Stream Key checkbox 
    and entering your key directly in the Stream Key field

    Route Builder Screen, labeled, with a Hublet edit panel open.

  4. Click the Start Route button.
  5. Once the route is running,

     copy the URL field
    and supply it to your streaming device's RTMP configuration (e.g., GoPro device).


    If you specified a stream key, you will need to 

    copy and paste this separately 

    Route Builder Screen, labeled, with a Hublet panel open.

Sending RTMP to Microsoft Stream Example

You can send RTMP directly to MS Stream from Haivision Hub using an RTMP Output Hublet paired with a Makito X or Makito X4. To do this, you will need to configure some additional parameters to provide Azure Media Services (AMS) the stream bitrates of each media type. The preferred way is to set the Makito X encoding parameters to meet the MS Stream Requirements and then append the audio and video data rates to the RTMP Output Hublet Server Ingest URL. 

To configure an RTMP stream from HUB to MS Stream: 

  1. In Microsoft Stream, click the Create menu and select the Live Event option.

    Microsoft Stream screen with Create menu open.

  2. When prompted, enter the details for your event and click Save

    Microsoft Stream Live Event detail entry screen.
    Under Encoder Setup, a pair of ingest URLs appears. 

  3. Click the Server Ingest URL Copy button. These settings are used to configure the Hublet (see Step 7).

    Microsoft Stream Encoder Setup tab.

  4. On the Makito X encoder, configure the output RMTP streams, and make note of the video and audio bitrate to be used when configuring the RTMP Output Hublet on Haivision Hub (see Step 9). NOTE: These values must match the streaming arguments being sent to the Microsoft Stream RMTP server.

    Haivision Makito X Video Encoders screen.

    Haivision Makito X Audio Encoders stream.

  5. In Haivision Hub, create a new route.
  6. Create an Input Hublet (an SRT Input Hublet is shown in this example).

    Input Hublet edit panel.

  7. Add an RTMP Output Hublet.

    Output Hublet type selector.

  8. In the Server Ingest URL field for the RTMP Output Hublet, paste the Server Ingest URL  you copied from Microsoft Stream.
  9. Next, at the end of the pasted Server Ingest URL, replace the following {bolded text}  with the values you made note of on the Makito using the following syntax:

rtmp:// {hostname} :1935/live/ {guid} / {streamname} ?videodatarate= {value} &audiodatarate= {value}

    • The orange text is the Server Ingest URL copied from MS Stream and pasted.
    • The blue text is appended with the Makito values inserted.
    • {streamname } replace with either srt or hub.
    • {value replace with the Kbps values from your Makito that you made note of in Step 4.
      • Make sure to use the Makito Video Encoder Bitrate for the videodatarate= {value} and the Audio Encoder Bitrate for the audiodatarate= {value} .

For example:

rtmp:// srt?videodatarate=4000&audiodatarate=128 

Output Hublet edit panel.


  • While the Microsoft specification calls for “strict CBR encoding”, Makito X VBR is known to work (with or without traffic shaping), as does the Makito X4 CVBR setting.  
  • While the Microsoft documentation on encoder settings recommends an upper limit of 720p30, Microsoft Stream has been confirmed to work with resolutions up to 1080p30 from a Makito X encoder. The important consideration is that the data rate values declared in the RTMP URL match the target data rates of the stream. 

  1. Finish configuring and then start your route.
    Route Builder screen, labeled.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.