Setup of MPEG-DASH output from UDP multicast input.


The following procedure describes configuration of MPEG-DASH output from UPD multicast input. Steps needed for creation of input Channnels and output Templates. So, if input channel and video template are already configured, you may proceed to the actual output setup.

1. Setup an output stream.

Click on the “Output streams” tab and then “Add output”.  Enter a description (optionally). Then fill the fields as follows:
Start mode – auto
Channel – select input channel from the drop down list
Template – choose a template you have created earlier 
Audio template – select an audio template
Format  - DASH
Encryption key provider (optionally) – in this example we use WidevineCENC as Cloud DRM provider
Key providerURL (optionally) – use Widevine test URL for key requests https://license.uat.widevine.com/cenc/getcontentkey
Key request interval in minutes (optionally) – for dynamic key rotation leave default 10, if you do not need key rotation, put 0
DRM content ID (optionally) – can be any integer, put 1234567 for testing perposes
Segment length – 4 (seconds, recommended value for mpeg-dash live output, allows faster startup).
Output URL – put the folder name, where manifest file and video files will be stored. If publishing to Web-DAV or SMB file share is globally configured, the final URL will look like Error! Hyperlink reference not valid.output.mpd

 

2. Starting the channel output

On the “Channels” page click the start icon. After a few seconds if all settings are correct the state of channel should be “transcoding”

If at least one output (for instance, HLS) for the selected channel was already configured and started, you need to open Output Streams page and click Start icon to initiate generation of manifest and subsequent mp4 video segments.

3. Checking playback of mpeg-dash live stream

You may use http://www.dash-player.com/demo/drm-and-protection to playback your *.mpd stream (including encrypted by Widevine CENC).

IMPORTANT!
Please make sure that the Web-server to which you publish streams has CORS (Cross Origin Resource Sharing) enabled. Otherwise there will be an error in debug console of Chrome browser like “No 'Access-Control-Allow-Origin' header is present on the requested resource” which indicated blocked cross-domain requests (when player and manifest file are hosted on different domains).