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.
Developer ResourcesYou can clone, host, fork, and modify forked versions of the html5-skin and skin-config repositories.
- 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.