Radiant Media Player has always been an HTML5-first web media player. When we started development of Radiant Media Player in late 2014 it made sense to add an advanced Flash fallback providing a unified API between HTML5 & Flash. As Flash becomes widely deprecated in the industry we will progressively phase out Flash of our player. This is a good thing - do not be afraid.
On an advertisement point of view on January 4, 2017 Google announced the end of Flash support in the IMA SDK by June 1, 2017. They leave this note:
Over the past few months we have seen a significant drop in Flash usage by Radiant Media Player customers. In Q4 2016 Flash only represented 10% of the traffic we saw through our player - we expect this to rapidly fall under 5% within the first six months of 2017. Flash-based ads are generating less and less revenue as modern browsers actively block Flash and opting out of them seems to now be the right choice.
Following Google leads Radiant Media Player 4 will gradually stop supporting Flash with the below schedule:
With the release of Radiant Media Player 4 we have compiled a lightweight and robust Flash fallback to best fit Flash end-of-life cycle. This is mainly provided to support HLS streaming with legacy Desktop browsers like Internet Explorer 11 on Windows 7 and versions of Firefox before 42 (those browsers do not support Media Source Extensions or native HLS streaming).
The bottom line is that we consider it is acceptable and reasonable to provide a lesser user experience, while still being able to access the media content, to those legacy browsers following the graceful degradation doctrine. For HLS on-demand video streaming we recommend to provide a MP4 progressive download fallback to the player so as to completely avoid the use of Flash.
All other player methods and events are not available with Radiant Media Player 4 Flash fallback. Refer to our player API documentation for details about the above API methods/events.
Only one skin is provided for Radiant Media Player 4 Flash fallback. It cannot be customised.
Refer to our main documentation for details about the above settings.
The following settings only apply to Radiant Media Player 4 Flash fallback:
flashFallBack: Boolean - enable or disable flash fallback - default: true
flashWMode: String - set Flash Window Mode, possible values are 'window', 'direct', 'opaque', 'transparent', 'gpu' - default: 'direct'
flashHlsMinbufferlength: Number - minimum buffer length in seconds that needs to be reached before playback can start (after seeking) or restart (in case of empty buffer). If set to -1 some heuristics based on past metrics are used to define an accurate value that should prevent buffer to stall - default: -1
flashHlsLowbufferlength: Number - low buffer threshold in seconds. When crossing down this threshold, HLS will switch to buffering state, usually the player will report this buffering state through a buffering statement. Playback may still continue - default: 3
flashHlsMaxbufferlength: Number - maximum buffer length in seconds. The player will try to never exceed this value for its buffer - default: 60
flashHlsCapLevelToStage: Boolean - this setting limits bitrates usable in auto-quality by the stage dimensions (width and height) - default: false
flashHlsCaplevelonfpsdrop: Boolean - this setting causes an automatic level switch down when frame rate loss is considered too high by player - default: true
flashHlsStartFromLevel: Number - from 0 to 1, indicates the preferred initial bitrate - default: -1
flashHlsAutoStartMaxDuration: Number - max fragment loading duration (bandwidth test + fragment loading) in automatic start level selection mode (in milliseconds) - default: -1
If you have a business requirement to support one of this feature in Flash you can still use Radiant Media Player 3 - however we do not recommend it.