- 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
- Navigate to HTTP Push
- 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)
- For this generic setup guide, keep the HTTP Streaming Providers dropdown selection on Generic HTTP
HTTP Push Settings configurations
Configure the HTTP Push settings according to your streaming needs (each setting explained below):
-
Retry on Error (Auto Restart and Recovery)
In Videon software version 10.4.0, a new feature has been added to HTTP Push outputs on all Videon devices. Users will now have the option to enable the automatic restart and recovery of the HTTP Push output similar to many other output protocols Videon devices support. By default, this feature is turned off. To enable the automatic restart and recovery of the HTTP Push output, follow these steps:
-
Access the Toggle
-
In the device’s local Web UI, navigate to Encoder Control. Click the HTTP Push output under Outputs section in the left-hand bar. There, you’ll find a toggle “Retry on Error” to enable this new auto-restart/recovery feature.
-
In the Cloud UI, you can go to the Devices section in the left-hand bar, then click “All Devices”. There, you can click on the device you want to make the changes on. Click “Configuration” then “Outputs”. Under the HTTP Push output you will find the toggle “Retry on Error”.
-
-
Enable Auto Restart/Recovery
-
Turn the toggle on to activate auto-restart and recovery for HTTP Push outputs. This will allow the device to attempt reconnecting automatically if the stream is interrupted, helping to reduce downtime.
-
Retry Logic and Exponential Backoff
-
With this feature, the system uses exponential backoff logic to control retry attempts, progressively increasing the wait time between each attempt. If the maximum number of retries (13 times) are reached without re-establishing the connection, the status will show "RETRYING_ENDED," indicating no further attempts will be made.
-
-
Impact on Live-to-VOD Workflows
-
A tooltip on the toggle provides details regarding potential impacts on Live-to-VOD workflows: each restart will overwrite existing manifests at the destination URL, which may disrupt playback on some players until they reload the new manifest.
-
-
-
-
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
-
-
Maximum = (# of segments)*(# of seconds)*(1000 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 -
DASH Time Service
In order to playback a DASH low latency stream, the DASH player needs to synchronize its clock with the encoder/packager. A DASH time service is an HTTP server that serves the current time, so that the player can use it to synchronize. The time service must be synchronized to the same NTP server that the encoder/packager is synchronized to. The time service is also required to serve the time in ISO/IEC 8601 format.
HTTP Push URL configurations
- Enter the HTTP Push URL and (optionally) Secondary HTTP Push URL as defined by your HTTP ingest provider
- Turn on HTTP Push with the ON/OFF switch and click Save to start streaming!
- 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:
- Chrome browser using the Native HTTP Playback extension: https://chrome.google.com/webstore/detail/native-mpeg-dash-%20-hls-pl/cjfbmleiaobegagekpmlhmaadepdeedn?hl=en
- Microsoft Edge browser
- Safari browser
- 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)
- 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:
To set up an origin server for HTTP Push Ingest, follow these instructions: