Migrating to Player V3
You can migrate from your legacy players to the Ooyala player.
Migrating from your legacy player to the current Ooyala Player V3 can be fairly
straightforward. This topic describes how to migrate your existing legacy player embed to the
Ooyala Player V3 embed and event model. The new Ooyala Player was designed to have minimal impact
on your existing set up. You can migrate your Flash player and custom modules in a fairly direct
manner.
Note:You can cut and paste your embed code from Backlot as you have done with prior players. If you use existing embed code callbacks and want to migrate to HTML5, you need to switch to using the message bus. Callbacks are not supported for the new embed style. They will continue to work for the Flash Player but not HTML5 Player.
- Comparing Embed Code Styles
Before migrating from prior player versions, it will help to understand the difference between the embed code models. - Migrating an Existing Embed Code
Migrating an existing embed code is straightforward in Player V3. - Destroying a Player
Under some conditions, you may want to destroy a player. - Migration FAQ
Frequently asked questions and answers about migrating to Player V3.
Parent topic: Player Developer Guide
Documentation
- Welcome
- Backlot Getting Started Guide
- Planning and Setup Guide
- Ooyala Ingestion Guide
- Player Developer Guide
- Core Platform Developer Guide
- Discovery Developer Guide
- Content Protection Developer Guide
- Backlot API Reference
- Player API Reference
- Rights Locker API Reference
- General Reference
- Glossary
- Archive
- Release Notes
