Player V3 Run-time Events (Deprecated)

This topic introduces Player V3 run-time events. It applies to Ooyala's web-based players (HTML5 and Flash) and mobile native app players (iOS and Android).

Important: Ooyala Player V3 is deprecated and is scheduled to be disabled on 2018-01-31. After that date, Player V3 will no longer play your video or audio content. Customers still using Player V3 need to migrate to Player V4 (see Migrating from Player V3 and Player Migration FAQ).

About Player V3 Run-time Events

Player run-time events can be triggered in either of the following ways:
  • manually by end user actions (for example, clicking the play or pause button)
  • programmatically via an API call
Here are some examples of common playback events:
  • play has started
  • play has completed
  • an ad has started playing
  • one or more ads have completed playing
  • an error has occurred
Events can trigger changes in the player state. For example, a user clicking the play button fires the "play has started" event and changes the player state to "playing". For more information, see Player V3 Run-time States (Deprecated).

Developer Resources for Player V3 Run-time Events

Ooyala's developer resources provide event listeners, event notifications, and callback functions that fire when certain run-time events occur. Due to different technical requirements across platforms, the list of player events varies by platform. Some states are common across platforms (such as play starting or stopping), while many others are platform-specific. In addition, the names of the player events differ across platforms to be consistent with platform SDK conventions. Refer to the following resources to learn more about player run-time events.
Development Platform For more information

Was this article helpful?