Radiant Media Player

Working with Wowza


Radiant Media Player is an official Wowza Tech Alliance Player Partners.

Wowza Media Systems provides popular solutions to generate standard-compliant media streams that work well with Radiant Media Player.

In this article we will review how to use a Wowza-based streaming server (Wowza Streaming Engine) to display live, DVR or on-demand media content with Radiant Media Player. This article only outlines some of the possibilities of interaction between Radiant Media Player and Wowza.

Documentation sections:

If you want to use Wowza SecureToken version 2 with Radiant Media Player visit our blog post on the subject.

Required configuration

We support streaming from Wowza Streaming Engine version 4 and above. Previous versions of Wowza media software are untested and may or may not work depending on your project requirements.

Supported streaming protocols

Radiant Media Player supports the following streaming protocols from Wowza:

  • Apple HLS to HTML5 & Flash video
  • MPEG-DASH (H.264/AAC) to HTML5 video

Refer to our compatibility table for more compatibility related information.

Typically a Wowza-based streaming URL will look like (HLS in this case):


More precisely this URL consists of:


This is described further on Wowza support pages here.

Create a Wowza application

First you will need to create an application in your Wowza Streaming Engine Manager be it live or on-demand according to your needs. In this newly created application select the playback types: MPEG-DASH and HLS. Set up any additional configuration you might need and save your application.

CORS and cross-domain settings

  • For streaming with HLS or MPEG-DASH to HTML5 video, all HLS and MPEG-DASH resources must be delivered with CORS headers permitting GET requests. This also applies for Google Cast casting or cross-domain loading of external WebVTT files. Please refer to this Wowza documentation page to enable CORS on your streaming server.
  • For Wowza 4 but with version below 4.4 you can still enable CORS on your Wowza server as follows:
    • In your application go to the properties tab, under the custom section (at bottom) click "edit"
    • In the following screen click on "Add Custom Property" - in the pop-up window that just opened enter:
    • For path select: /Root/Application/HTTPStreamer
    • For name enter: httpUserHTTPHeaders
    • For type select: string
    • For value enter: Access-Control-Allow-Origin:*|Access-Control-Allow-Credentials:true|Access-Control-Expose-Headers:Date|Access-Control-Allow-Methods:HEAD, GET, POST|Access-Control-Allow-Headers:Overwrite, Destination, Content-Type, Depth, User-Agent, X-File-Size, X-Requested-With, If-Modified-Since, X-File-Name, Cache-Control, Range
    • Save your new custom property and restart your application. Your HLS and MPEG-DASH streams should now have proper CORS settings.
  • For streaming with HLS to Flash refer to this documentation section (HLS/HTTP streaming to Flash: cross-domain policy file).

Streaming requirements

Refer to our streaming documentation page to make sure you meet general requirements for streaming media content with HLS and MPEG-DASH. To better stream MPEG-DASH content from Wowza it is recommended to use a recent version of Wowza Streaming Engine (4.5+).

On-demand video streaming (smil-based)

You can either use a full HLS approach or an hybrid MPEG-DASH & HLS approach to stream on-demand video content.


Live video streaming (Stream Name Groups or smil-based)

As with on-demand video content you can either use a full HLS approach or an hybrid MPEG-DASH & HLS approach to stream live video content.

Please refer to the following Wowza documentation to properly generate Stream Name Groups streams from Wowza.


Wowza nDVR

Wowza nDVR allows to stream and record live DVR video content to Radiant Media Player. DVR streaming with Radiant Media Player is supported with HLS.

Please refer to the following Wowza documentation to properly generate nDVR streams from Wowza.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 3.0 License.