Google Cast™ is a protocol allowing media data to be sent from an emitting (or casting) device to a receiving device (example a TV). This is generally referred to as "second screen experience" in the industry. The emitting/casting device can be a notebook or an Android tablet for example. One can then watch video content on a TV while still being able to control the content through the casting device. .
Radiant Media Player support in-player casting from Google Chrome to Google Cast enabled devices (like Chromecast or Android TV) for a top-notch second-screen video experience. Our implementation is based on Google Cast SDK v3. Information on Google Cast SDK can be found here.
When a Google Cast enabled receiving device is detected the player will automatically display a casting icon (as part of a player module). A dedicated user interface has been designed within Radiant Media Player to support Google Cast. Radiant Media Player Google Cast implementation consists of a sender application and a receiver application (custom receiver). We have published our receiver application with Google for you to use out of the box. You can also build your own receiver application and publish your own Google Cast application with Google.
Assistance for setting up a Chromecast device can be found here.
Version 3 of Google Cast SDK does not currently support casting from Chrome on iOS. This will be enabled in a future Google Cast SDK release.
Radiant Media Player will automatically detect an in-range Google Cast enabled device and will provide in-player casting options when needed.
The following player settings are available:
Enables or not Google Cast detection and layout. Default: true. This setting is not supported and automatically set to false for: 360 video, related/playlist layout, DVR streaming, audio-only, outstream ads and when our customer ad scheduler is used.
In order for casting to work a valid player
poster must be present as the receiver application will use the player
poster attribute as artwork.
Google Cast receiver app id. Since Radiant Media Player 4.0.6 we use the default receiver application from Google. You can develop your own and publish it with Google if needed. Default: ''.
The content title to be displayed in the receiver app. Default: ''.
Additionally casted WebVTT captions can be customised. See our closed captions documentation for more information.
If you want to customize the receiver application you must publish your own application with Google. A reference receiver application is provided by Google here.
It is to be noted that neither the Cast SDK v3 nor the IMA SDK v3 from Google officially support video ads casting from Google Chrome. As such Radiant Media Player will not render video ads on the receiving device. Radiant Media Player will display video ads on the sender device, while not in casting mode. When casting is engaged video ads will be discarded on the sender device and will not render.
Refer to this section of Google Cast SDK documentation for proper CORS set up.
Radiant Media Player scope of support does not cover troubleshooting set up of Google Cast enabled devices or assistance for building a custom receiver application.
AirPlay is managed in iOS Control Center. Through the AirPlay option in Control Center you can push any video content being played through Radiant Media Player on iOS to a receiving AirPlay device. Note that only the raw video stream (live or on-demand) is pushed with AirPlay.
Apple AirPlay for videos works for the following emitting devices:
And the following receiving device:
Use this link to enable Apple AirPlay on your device.