Articles in this section

Configuring EdgeCaster for HTTP Push streaming (HLS/DASH)

  • Updated
Follow
  1. Once your Videon hardware is fully set up and you are connected to the Videon Web UI, navigate to Encoder Control and make sure you have Input Settings properly configured correctly to be what video and audio you are using for input
  2. Navigate to HTTP Push
    mceclip0.png
  3. Select the Video Source and Audio Source you will use for this stream (as applicable, Audio/Video Source choice may vary based on the Videon product in use)
    mceclip1.png
  4. For this generic setup guide, keep the HTTP Streaming Providers dropdown selection on Generic HTTP
    mceclip2.png

HTTP Push Settings configurations

Configure the HTTP Push settings according to your streaming needs (each setting explained below):

  • Manifest Type

    This setting indicates whether you want to stream HLS, DASH, or Both. Streaming Both will not double bandwidth, but rather generate manifest files for both formats referencing the same video and audio data/files

  • Segment Window

    This indicates the number of video/audio segments to be included in the manifest, meaning it is the playback window for the live stream (# segments x seconds per segment). Videon allows setting up to 65535 segments in a manifest

  • Save Segment Window

    Off means the Videon device will send an HTTP DELETE request for all video and audio segments as well as manifest files when HTTP Push is turned off. On means that the manifest will be converted to a static manifest for what is effectively Video-On-Demand (VOD) playback

  • Media Type

    This setting indicates whether the stream uses fMP4 or TS media files for segments. Videon recommends fMP4 since it is the standard for CMAF, is required for DASH, and is also supported for HLS. Some HLS use cases may require TS, so it is supported as an option

  • Ultra Low Latency

    Off means that Chunked Transfer Encoding will not be used for sending media segments. On means Chunked Transfer Encoding will be used for sending media segments in chunks of the size defined by the Chunk Duration setting.

    Target Latency must be between 1 - Maximum milliseconds (calculate below)

    • Maximum = (# of segments)*(# of seconds)*(1000 ms)

      • e.g. if segment window is 10 segments of 2 seconds, the maximum target latency would be 20000 ms

  • DASH Presentation Delay (SPD)

    Off means SPD will not be defined in the DASH manifest. On means that SPD will be defined in the DASH manifest defined by the second(s) setting below it. This setting indicates a time at which multiple video players should synchronize their playback for a unified viewing experience
    mceclip3.png

HTTP Push URL configurations

  1. Enter the HTTP Push URL and (optionally) Secondary HTTP Push URL as defined by your HTTP ingest provider
    mceclip5.png
  2. Turn on HTTP Push with the ON/OFF switch and click Save to start streaming!
    mceclip7.png
  3. Generally, you can now view the stream at [HTTP Push URL]/master.m3u8 (HLS) or [HTTP Push URL]/manifest.mpd (DASH). Some CDN providers may provide a specific playback link.
    • Viewing the stream can be done by entering the URL into the URL bar of a browser that supports HTTP playback. Below is a list of suggestions:
      1. Chrome browser using the Native HTTP Playback extension: https://chrome.google.com/webstore/detail/native-mpeg-dash-%20-hls-pl/cjfbmleiaobegagekpmlhmaadepdeedn?hl=en
      2. Microsoft Edge browser
      3. Safari browser
      4. Chrome or Safari on a smartphone
    • Alternatively, the stream can be viewed with video players that support HTTP playback including, but not limited to:
      • NexPlayer
      • THEOPlayer
      • CastLabs
      • DASH.js (DASH only)

To set up an origin server for HTTP Push Ingest, follow these instructions:

Related articles