Radiant Media Player relies on the device it runs on to provide HEVC decoding support in order to render HEVC encoded content with HTML5 video. This is true for native HTML5 video rendering (e.g. progressive download) or through media source extensions (HLS, DASH). Currently the following environments are supported:
For HEVC support in MS Edge for Windows 10 a compatible graphic card with HEVC decoding support is also required.
We recommend using HLS-fmp4 for better HEVC support. Because HEVC is still not widely available we need to use a combination of HEVC & AVC encoded content to reach a large range of devices. We have 2 options:
Option 1: HLS/DASH manifest holding both HEVC & AVC variants. When both HEVC & AVC variants are available in a HLS/DASH manifest the player will automatically pick the appropriate format based on device capabilities. However this option may not always be available among streaming service providers and may restrict support for older devices that do not support HLS-fmp4.
Option 2: use a combination of hls & hlsHevc (or mp4 & mp4Hevc) properties of the bitrates object. For newer devices that support HLS-fmp4 with HEVC the
bitrates.hlsHevc URL will be used and for devices that do not support HLS-fmp4 with HEVC but do support classic HLS-ts with AVC the
bitrates.hls URL will be used. The player will automatically pick the appropriate format based on device capabilities.
Example of bitrates object for HLS with option 2:
var bitrates = {
hlsHevc: 'https://www.rmp-streaming.com/media/hls/fmp4/hevc/playlist.m3u8',
hls: 'https://www.rmp-streaming.com/media/hls/test-vectors/bbb-abr/playlist.m3u8'
};
Example of bitrates object for MP4 progressive download with option 2:
var bitrates = {
mp4Hevc: [
'https://www.rmp-streaming.com/media/ed-hevc-360p-2m.mp4'
],
mp4: [
'https://www.rmp-streaming.com/media/ed-360p.mp4'
]
};
In the above examples content is different to clearly identify which is HEVC-encoded and which is not.