Articles in this section

See more

HTTP Push - Recommended settings

  • Updated
Follow

HTTP Push is an output type that supports HLS and DASH workflows streaming to an origin server, from which content is then usually distributed via a CDN.

Common origin servers and/or CDNs that Videon products are used with include AWS, Akamai, and Fastly, though any server accepting standard HTTP PUTs of files should work with Node/EdgeCaster's HTTP Push.

Always first check with the recommended settings provided by your media service (origin/CDN) provider. Settings provided here are generic, not specific to any particular origin/CDN.

Default settings

Videon's default settings for HTTP Push are shown in the following screenshots:

mceclip0.png

ULL Streaming

ULL streaming means that Ultra Low Latency is enabled on Node/EdgeCaster in the HTTP Push settings. ULL is only supported for DASH manifest output, and not HLS manifest output. This sends files by chunk (defined by Chunk Duration), rather than by whole segments. This allows the stream to be played back with a minimal buffer, which results in stable glass-to-glass latency of under 3 seconds.

Video Profile

When performing HTTP Streaming, Videon recommends the below Video Profile settings for a single 1080p60 stream. Depending on the resolution used, the bitrate should increase/decrease respectively to keep equivalent quality. If these settings work well, you can try increasing the Video Bitrate to improve video quality. Make sure to not exceed 50-75% of your network's upload bandwidth (you can check upload speed at speedtest.net):

mceclip3.png

MBR Group

If using MBR, make sure that MBR Group Member is enabled on all Video Profiles to include in the stream, keeping the total resolution less than or equal to 4Kp30. Videon recommends the following MBR Group settings for ULL workflows:

mceclip4.png

Audio Profiles

For a ULL workflow, Videon recommends an audio bitrate of 128kbps or higher.

HTTP Push Output

Videon recommends the below settings for HTTP Push ULL output:

 

Non-ULL Streaming

Non-ULL streaming is mainly only used in the case that the origin server or, more often, player does not support chunk-based playback. Using a non-ULL player in a ULL workflow will likely result in unstable playback.

The recommendations are all the same other than HTTP Push.

HTTP Push Output

Videon recommends all the same settings for Non-ULL other than Ultra Low Latency being disabled:

 

For more information on HTTP streaming, see the following guides:

Setting up an MBR stream using HTTP Push

Configuring Node/EdgeCaster for HTTP Push streaming (HLS/DASH)

Related articles