Prerequisites for Using Player V4

Prior to using Player V4, you must have the following resources.

Account Manager/Technical Support Resources

Please be sure to contact your account manager or technical support before you begin your migration.

If you currently have premium content that needs to be protected with DRM, we do not recommend that you migrate at this time. Please stay tuned for additional updates.

Technical Expertise

If you are customizing the look and feel of the player, you simply need to be able to modify a JSON file. If you are developing with the Player V4, you need experience with JavaScript development. With the new player architecture, you need to load modules, such as the skin module, Discovery module, and ad module.

Developer Resources

You can clone, host, fork, and modify forked versions of the html5-skin and skin-config repositories.
Warning: Ooyala will support any pre-defined and valid modifications to the skin.json file. If you fork the skin-config repository and make non-valid modifications, or if you fork the html5-skin repository and make changes, we will not offer technical support for these changes.

Hosting Resources

Ooyala hosts default Player V4 resources. If you want to make customizations to the default player, Ooyala recommends that you host your Player V4 resources, including your HTML skin configuration file, images, and other resources. Advantages to hosting the plugins and files yourself include:
  • You can optimize fast downloads for your personal routes.
  • You can optimize even more by downloading these files and then concatenating all of your plugins and core into a single file which allows everything to download at once. This is faster and more reliable.
  • If you are making any player look and feel customizations you will need to host skin configuration files anyway, so it will not be much more effort to host more files at the same endpoint.

All resources (video, audio, images, cc, css, js...) that are part of Player V4, or can be used by Player V4, must be CORS enabled if the files are hosted on more than one domain. Set up Cross-Origin Resource Sharing (CORS) enablement on the CDN you use for content serving. See Cross-Origin Resource Sharing (CORS) and Hosting Player V4 Resources for details.

Note: These CORS prerequisites do not apply if you are using Ooyala-hosted content, as CORS is enabled for all Ooyala-hosted domains. These requirements apply to remote assets, etc.

Was this article helpful?