Requirements for Chromecast Integration
The latest version of the Ooyala mobile SDK for Android and/or the Ooyala mobile SDK for iOS from Ooyala Downloads.
|Enablement||To enable streaming protocols for processing profiles, please contact Ooyala Tech Support.|
Note: Please note that these hosting prerequisites do not apply if you are using Ooyala's sample applications, as they are hosted by Ooyala and are CORS enabled.
|Registration||Register with Google as a developer to get a receiver application ID (this shows the sender application which receiver to send to). The Cast developer license can be found at https://cast.google.com/publish/#/overview. This will register the URL of the receiver app webpage.|
CORS and Chromecast
All resources not hosted by Ooyala (video, audio, images, closed captions, css, js, etc.) that are used with your Chromecast or HTML5-based playback must have the appropriate CORS headers configured. If your resources do not follow the CORS standard, your player will not function correctly and may break when trying to access files across domains.
You must set up CORS enablement on the CDN that you use for content serving. For information on how to enable CORS, see http://enable-cors.org/ or talk to your hosting provider or vendor.
Chromecast Device Registration and Concurrent Stream LimitThe sender application and receiver application are different devices. If you play content on both the sender and receiver devices, the mobile device and Chromecast will both be registered as devices. This typically happens on a play and cast scenario (see Introduction to Chromecast Integration). If the user does a cast and play, which means playback only happens on the Chromecast receiver, then only Chromecast gets registered as a device.
However, for concurrent stream limits, play from a sender and a receiver application is counted as a single concurrent stream. An example of this is if the user does the 'play and cast' scenario from their mobile device, where they play the content on their mobile device, use their mobile device to cast the content to a receiver application, and then continue to watch the content on the receiver. This is counted as one concurrent stream. The same count happens on a 'play and cast' scenario (one concurrent stream counted for play from a sender and a receiver).