Skip to main content

Streaming to YouTube

Purpose

StreamHub can be configured to output stream using RTMP or RTMPS Protocol for streaming to social media such as YouTube.

Prerequisites

  • StreamHub license
  • IP Output license (AW-OR-OIP)
  • Firewall and network configured to allow RTMP or RTMPS output
  • YouTube account

Note

A StreamHub Live Encoding license (AW-OR-ENC) may be required depending on the characteristics of the input stream from the transmitter/encoder.

Procedure

  1. To begin, you must obtain a Link and Stream Key from YouTube. Log in to YouTube and click on your profile picture to access the YouTube Studio. Click on the Go Live icon as shown in the screenshot below.



  2. Under Stream Settings you will see the Stream URL and Stream Key (protected).



  3. In a separate browser tab, access your StreamHub server.
  4. To create a new RTMP IP Output in StreamHub, click on the (+) icon in the IP Output section and click the next (+) button under IP Output Profiles.



  5. Click on the RTMP protocol button to create an RTMP output profile. 



  6. Configure the RTMP Profile, using the Stream URL, Stream Key, and RTMP Push Mode from YouTube (refer to step 3 above).


    Tip

    If RTMPS is desired, click on the padlock icon next to the YouTube Stream URL to change the URL from RTMP to RTMPS. StreamHub can support both RTMP and RTMPS.

  7. Save the RTMP IP output profile.
  8. Select the RTMP IP Output profile by clicking on the associated radio button. An IP Output with the selected RTMP profile is enabled.





  9. Configure the StreamHub Encoder.

    Important

    As per YouTube specification on the following page:
    https://support.google.com/youtube/answer/2853702?hl=en
    There are certain requirements on the video / audio codec as well as resolution and frame rate which can be managed by YouTube. If the source transmitter is sending non-supported configuration such as HEVC video codec then an error will appear in the StreamHub RTMP output about “Codec not supported”.
    In this case, it is necessary to transcode the stream first using the StreamHub encoder function to make it compatible with YouTube.

    Tip

    Transcoding in StreamHub requires an encoder license and adequate resources for live encoding in a supported format.

    Note

    If the transmitter is already sending in a supported video/audio format, codec, resolution, and frame rate, this step can be skipped.

    1. Click on the (+) Icon in the StreamHub Encoder section and create a new Encoder Profile by pressing the  (+) button in the Encoder Profiles selection. 
    2. Provide a name and select the Web Streaming encoder preset. The example at left shows the recommended YouTube streaming parameters for 720p30:
       
      1. Video: H.264, bitrate range 1,500 Kbps ~ 4,000 Kbps 
      2. Audio: AAC LC, bitrate = 128 Kbps 

    3. Click on Save once satisfied with the settings.

    Note

    Please consult the YouTube support page for other recommended resolutions and bitrates.

  10. Select the saved Encoder Profile by clicking the associated radio button. An Encoder with the selected Encoder profile is enabled.





  11. Link the workflow from Input > Encoder > Output. This allows the input stream to be transcoded first to a YouTube compatible format before outputting the stream to YouTube. There are two methods:

    Method A: Drag and drop the desired input icon onto the Encoder, and then drag and drop the Encoder onto the Output icon.



    Method B: From the Encoder drop down, select the input desired to be transcoded, and then select the Encoder in the output drop down to output to YouTube.

     


    The input is now assigned to the Encoder for transcoding into a YouTube compatible format, and then the transcoded stream is set to output to YouTube as configured under RTMP IP Output.

  12. If the stream is not already live, click the Live button on the input (or from the transmitter unit) to start live streaming. 



  13. The live stream should appear in the YouTube Studio view: 



JavaScript errors detected

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

If this problem persists, please contact our support.