Player Migration FAQ

For general information, see:

Q: How do I migrate from Player V3 to Player V4?

A: To load existing video assets with Player V4, simply create a new Player V4 and associate the Asset ID of the existing video with the new player. You may also need to update your ad configuration parameters. With the Ad Manager Framework, configuration parameters and some page level settings are different from Player V3. If you don't have any page level overrides to Backlot settings, your ads will have full backwards compatibility. See Migrating from Player V3 for full migration steps and details.

Q: How long do I have to migrate from Player V3 to Player V4?

A: We do not have a specific end of life date for Player V3 at this time. We will continue our Player V3 maintenance mode for existing customers, but will no longer make enhancements and improvements to that player. We will fix Player V3 bugs based on impact to service and monetization capabilities to make sure that you can seamlessly continue your operation.

Q: How do I enable Flash-free playback for Player V4?

A: By default, the Ooyala player uses the Flash plugin to playback HLS across all browsers. The bit_wrapper plugin for DASH and HLS (bit_wrapper.min.js) plays HLS using the HTML5 standard (and Media Source Extensions), enabling HLS on web browsers without the use of Flash. HTML5 MSE also supports playback of MPEG-DASH (clear and DRM-protected content). To enable Flash-free playback using the Ooyala player, see Using Flash-free Playback with Player V4.

Q: What happens if I have a custom Ooyala Player Framework (OPF) Flash module for Player V3?

A: OPF modules in Player V3 were developed to allow you to integrate with third-party analytics providers and make UI/UX customizations (swf files, etc.). The Analytics Framework allows you to integrate third-party analytics with the player. You can use the Analytics Framework to re-create your integrations with third-party analytics providers.

Q: Will custom skins created for Player V3 work with Player V4?

A: Player V4 CSS customizations are made by modifying html5-skin.min.css. If you have built your own CSS for Player V3, you will need to re-create these skin customizations with html5-skin.min.css for Player V4. For details, see Customizing the Player V4 Appearance Using CSS.

Q: Do I need to reprocess my clear assets to move from Player V3 to Player V4?

A: No, not usually. Re-processing is required only if:
  • You want to add DASH encoding to your processing profile.
  • You want to add HLS to your processing profile and you have MP4 or HDS ONLY encodings.

Q: Do I need to reprocess my DRM-protected assets to move from Player V3 to Player V4?

A: Yes. Reprocessing is required in order to support Apple Fairplay HLS (Apple requires Apple-issued certificates), and Widevine Modular and Playready DASH.

Q: Are there any changes to the Player APIs and message bus?

A: Yes, certain query string parameters, embedded parameters, and player events used with Player V3 are no longer supported. There are also many new parameters and events introduced with Player V4. A complete list of changes is captured in Differences Between Player Versions.

Q: How do I embed the player in 3rd party websites - is it the same as Player V3? Where’s the hosted iframe.html?

A: The player can be loaded in any 3rd party, 4th party site. The iFrame can actually be found in the player 'embed' tab. See Embedding Player V4 in an HTML iframe for details.

Q: I see Player V3 and Player V4 embeds in the Backlot UI. What is the difference between them?

A: The Player V3 embeds will load Player V3. The Player V4 HTML5 embed will load Player V4. Player V3 embeds will continue to coexist with the Player V4 HTML5 embed. You can use the Player V4 embed if you'd like to try and test out the new Ooyala Player. The Player V4 embed allows you to simply copy and paste the page script into an HTML page.

Was this article helpful?