Cloud Player & Self-hosting

Cloud-hosted player

All Radiant Media Player required files are available through our global CDN (content delivery network) partner CloudFlare for delivery to a global audience. See the list of production builds here.

Self-hosted player

In this case scenario you are hosting the player files on your servers. Self-hosting is only available for paid Radiant Media Player customers.

First, download the self-hosted player files package in our back-end (click the "Downloads" tab and select the player version you want to download). Unzip the files. You should have the following structure:

• dash/
• dist/
• examples/
• hls/
• rmp-vast/
• src/
• three/
• vtt/
• LICENSE

Only static files are present within those folders. Folders must not be renamed. If you do not host the player files at the root of your site you must tell the player where to find the required files with the pathToRmpFiles player setting. Example:

<script src="radiantmediaplayer/dist/rmp.min.js"></script>
<div id="rmp"></div>
<script>
  const src = {
    hls: 'https://your-hls-url.m3u8'
  };
  const settings = {
    licenseKey: 'your-license-key',
    src,
    width: 640,
    height: 360,
    contentMetadata: {
      poster: [
        'https://your-poster-url.jpg'
      ]
    },
    speed: true,
    // Here we tell the player to look for the required dependencies in radiantmediaplayer/
    pathToRmpFiles: 'radiantmediaplayer/'
  };
  const rmp = new RadiantMP('rmp');

  // Player initialisation
  async function initRmpPlayer() {
    try {
      await rmp.init(settings);
    } catch (error) {
      console.error('Radiant Media Player failed to initialize', error);
    }
  }
  initRmpPlayer();

</script>

The pathToRmpFiles setting can either be a relative or absolute path or a URL.

In self-hosted mode the player will still attempt to contact our logging and licensing servers periodically (same as in cloud-hosted mode). We do not record any personal data about your audience on our servers. We however need those technical data to insure proper billing (for PLATFORM Edition) and to keep our service healthy.

Some Google-related player features require loading player dependencies from Google servers. Those files are thus not provided with our self-hosted package. Here is the list:

Google HTML5 IMA SDK

https://imasdk.googleapis.com/js/sdkloader/ima3.js

https://imasdk.googleapis.com/js/sdkloader/ima3_dai.js

Google Analytics

https://www.google-analytics.com/analytics.js

Google Cast

https://www.gstatic.com/cv/js/sender/v1/cast_sender.js?loadCastFramework=1

Those files are automatically loaded by the player from Google servers over HTTPS when needed. Referencing these files from Google's servers ensures that you get access to new features and product updates as they become available. You may opt out of the related player features to avoid loading those files from Google servers but the player will then not be able to use the disabled features.

HTTPS support

Loading the player over HTTPS is always recommended. Cloud-hosted files for Radiant Media Player are thus HTTPS compatible. If you self-host the player files you must host them on a domain/server with a valid HTTPS certificate to be HTTPS compatible.

If you use HTTPS all the images, closed captions, logo and streaming URLs called by the player must be HTTPS compatible. Failure to do so can result in unwanted warning/behaviour for your viewers.