Skip to main content

Configuring IP Input Profiles

To receive video streams from third-party devices with a supported standard IP protocol, you need to configure IP input profiles that define transmission settings.

  1. In the INPUTS section's toolbar, click on
    .
  2. Click on
    to add an IP input profile.
  3. Select the IP protocol according to the type of streams to be received: RTSP, TS, HLS, RTMP, SRT or NDI.
    RTSP

    Real Time Streaming Protocol (RTSP) is a network protocol used to control and deliver audio and video between two endpoints. Video and audio streams are transmitted in RTP (UDP) between the two endpoints, usually using the public internet.

    1. Set a Name for the new profile. 
    2. Enter the Host name and Port provided by the RTSP server that sends the live stream to the StreamHub.
    3. Define a label that may complete the URL to obtain a unique RTSP stream. 
    4. If you need to secure this RTSP stream, enable the "Protect access with password" option. Then set a login and password
    5. Enter a De-jittering delay to help in case of jitter in received packets (minimum is 200ms and maximum is 5000ms).

      Note

      • In case of transmission over IP network, some jitter in packets' arrival may occur, and may lead to unexpected decoding issues. The de-jittering buffer temporarily stores arriving packets in order to mitigate delay variations.
      • The de-jittering delay needs to be set according to the network characteristics. It is a trade-off between resiliency and latency.
    6. Click the Save button.

    You can now assign this profile to an Input.

    Note

    You cannot edit or delete an IP input profile when it is selected for an input that is currently activated.

    You can click on

    to get more information about settings required. 

    TS

    MPEG-2 Transport Stream (TS) is a container format used for transmission of live video and audio data within a single multiplexed stream. Widely used in professional video contribution and distribution applications, it is usually delivered using managed IP networks. TS over IP Delivery is based on UDP or RTP protocol, using unicast for point-to-point distribution or multicast for point-to-multipoint distribution.

    1. Set a Name for the new profile. 
    2. Set the UDP Port used as it is set in the settings of the TS encoder that sends the live stream to the StreamHub.

      This port cannot be the same as the Base Port. 
      By default, output is sent in unicast.

      When enabling "multicast” 

      Enter both the multicast IP address and the port used by the TS encoder.
      Provided that your network can support IGMPv3, you can enable Source Filtering Multicast / Source Specific Multicast. You can then enter the IP address of the TS encoder sending multicast stream.

      When disabling "multicast” 

      Enter the port used by the encoder. Please note that you cannot use a port that is already used by the encoder. It cannot be the same as th Base port.

    3. Enter a De-jittering delay to help in case of jitter in received packets (minimum is 200ms and maximum is 5000ms).

      • In case of transmission over IP network, some jitter in packets' arrival may occur, and may lead to unexpected decoding issues. The de-jittering buffer temporarily stores arriving packets in order to mitigate delay variations.
      • The de-jittering delay needs to be set according to the network characteristics. It is a trade-off between resiliency and latency.
    4. Click the Save button.


    You can now assign this profile to an Input.

    Note

    You cannot edit or delete an IP input profile when it is selected for an input that is currently activated.

    You can click on

    to get more information about settings required. 

    HLS

    HTTP Live Streaming (HLS) is an HTTP-based streaming protocol. It is widely used for live video delivery to web browsers, media players, and mobile devices over public internet.

    1. Set a Name for the new profile. 
    2. Set the URI provided by the HLS server that sends the live stream to the StreamHub.
    3. Enter a De-jittering delay to help in case of jitter in received packets (minimum is 200ms and maximum is 5000ms).

      • In case of transmission over IP network, some jitter in packets' arrival may occur, and may lead to unexpected decoding issues. The de-jittering buffer temporarily stores arriving packets in order to mitigate delay variations.
      • The de-jittering delay needs to be set according to the network characteristics. It is a trade-off between resiliency and latency.
    4. Click the Save button.

      You can now assign this profile to an Input.

    You can click on

    to get more information about settings required. 

    SRT

    SRT is a video transport protocol based on UDP protocol. Designed for reliable live video delivery over the public internet, it supports error-correction mechanisms as well as stream encryption capabilities..

    You can click on

    to get more information about settings required. 

    1. Enter a Name to the input profile. 
    2. elect the Server mode to be applied:  CallerListener.

      Listener

      When in Listener mode, the StreamHub waits for a request to start an SRT streaming session. This session is initiated from the third party device / service.

      Caller
      When in Caller mode, the StreamHub is the initiator of an SRT streaming session.

      The Stream URL can be composed of the protocol, the destination host (its IP address or host name), the port, the application name, the instance name and the stream key.

      The pattern of an SRT URL can be as follows:

      [protocol]://[Host](:[port])/[applicationName](/[instanceName])/[streamKey

    RTMP

    RTMP is a TCP-based protocol for streaming video and audio over the Internet. It maintains persistent connections and allows low-latency communication.

    Typical port(s) used: TCP 1935

    According to the device or service from which the streams comes, you can configure the RTMP input in Push Mode or Pull Mode:

    1. Set a Name for the new profile. 
    2. Enable either PUSH or PULL mode.
       
      • PUSH mode

        When Push mode is enabled, the third party device / service operates as a client and pushes data toward StreamHub.  StreamHub operates as a server.

        Enter the Stream Key and if required, enable the RTMPS mode.

        Note

        The Stream Key cannot contain spaces or special characters, except hyphen and underscore characters.

        The pattern of an RTMP Stream Key is as follows:

        [protocol]://[Host](:[port])/[input)/[streamKey]

      • PULL mode

        When Pull mode is enabled, third party device / service operates as a server. StreamHub operates as a client and pulls data from third party device  / service. 
        The session is initiated by the third party device / service.

        Note

        URL is provided by the RTMP server. Typically, the URL of an RTMP stream is composed of the protocol, the destination host (its IP address or host name), the port, the application name, the instance name and the stream key. The pattern of an RTMP URL is as follows:

        [protocol]://[Host](:[port])/[applicationName](/[instanceName])/[streamKey]

        For instance, the URL of a Youtube live event could be: rtmp://a.rtmp.youtube.com/live2/channelname.zdxd-sgyj-4m7s-42sx.

    3. Enter a De-jittering delay to help in case of jitter in received packets (minimum is 200ms and maximum is 5000ms).

      Note

      • In case of transmission over IP network, some jitter in packets' arrival may occur, and may lead to unexpected decoding issues. The de-jittering buffer temporarily stores arriving packets in order to mitigate delay variations.
      • The de-jittering delay needs to be set according to the network characteristics. It is a trade-off between resiliency and latency.
    4. Click the Save button.

    You can now assign this profile to an Input.

    You can click on

    to get more information about settings required. 

    NDI

    Network Device Interface (NDI) is a standard used to receive, deliver, and control live video streams over an IP network, typically within a live production workflow. NDI uses a low latency and high quality compression codec, a typical HD stream (1080i) requiring about 100Mbps of data throughput.

    Important

    For NDI input, only full NDI is supported (not HX, not HX2). For these types of IP Protocols (except for NDI), only streams encoded by third-party devices with the following codecs and specifications are supported:

    • Audio
      • AAC-LC: CBR only
        • MPEG-1L2 (For TS over IP and HLS protocols only)
        • Opus (TS, HLS, SRT only): From 1 mono channel to 4 stereo or 8 mono channels
        • Max. sampling frequency: 48kHz
      • Video
        • H.264/AVC, up to High profile (4:2:2 10 bits)
        • H.265/HEVC, up to Main 8 and Main 10 profiles, 4:2:0, 4:2:2
    1. Enter a De-jittering delay to help in case of jitter in received packets (minimum is 200ms and maximum is 5000ms).

      Note

      • In case of transmission over IP network, some jitter in packets' arrival may occur, and may lead to unexpected decoding issues. The de-jittering buffer temporarily stores arriving packets in order to mitigate delay variations.
      • The de-jittering delay needs to be set according to the network characteristics. It is a trade-off between resiliency and latency.
    2. If required, enable the Low bandwidth decoding option.

      Note

      When enabling the Low bandwidth decoding, the StreamHub server will receive a downscaled version of the stream to reduce bandwidth.

    3. If required, select an Audio standard.

      Note

      You can use this setting to apply an adjustment on audio level according to a standardized reference:

      • none: no adjustment
      • EBU: apply EBU audio standard adjustment
      • SMPTE: apply SMPTE audio standard adjustment


      GROUPS
      To help you filtering NDI sources, you can create one or multiple group(s) to which you associate NDI inputs .

    1. Click Add Group button and enter a name for the group.
    2. Enter the extra IP address to detect  NDI sources. 


      You can now assign this profile to an Input.
      You can click on

      to get more information about settings required. 


JavaScript errors detected

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

If this problem persists, please contact our support.