OvenMediaEngine uses HLS and MPEG-DASH to support streaming even on older browsers that do not support WebRTC. Also, if you use OvenPlayer, it detects the browser status and performance, and automatically falls back using HLS or MPEG-DASH during streaming. HLS and MPEG-DASH are not Ultra-Low Latency protocols, so you can decide whether or not to use them.
OvenMediaEngine provides the following features:
If you want to use MPEG-DASH and HLS, you need to add the
<HLS> element to the
<Publishers> in the
Server.xml configuration file as shown in the following example.
Sets the HTTP port to provide MPEG-DASH and HLS. Also, MPEG-DASH and HLS can use the same port.
Sets the length of the segment in seconds. The shorter the
Sets the number of segments to be exposed to
Controls the domain in which the player works through
Most browsers and players prohibit accessing other domain resources in the currently running domain. You can control this situation through Cross-Origin Resource Sharing (CORS) or Cross-Domain (CrossDomain). Moreover, OvenMediaEngine can set CORS and Cross-Domain as
You can set it using the
<Url> element as shown above, and you can use the following values:
Allows requests from all Domains
Allows both HTTP and HTTPS requests from the specified Domain
Allows HTTP requests from the specified Domain
Allows HTTPS requests from the specified Domain
MPEG-DASH and HLS Streaming are ready when a live source is inputted and a stream is created. Viewers can stream using OvenPlayer or other players.
Also, you need to set H.264 and AAC in the Transcoding profile because MPEG-DASH and HLS use these codecs.
When you create a stream as shown above, you can play MPEG-DASH and HLS through OvenPlayer with the following URL:
If you use the default configuration, you can start streaming with the following URL:
We have prepared a test player that you can quickly see if OvenMediaEngine is working. Please refer to the Test Player for more information.