Player V3 Run-time States (Deprecated)
This topic introduces Player V3 run-time states. It applies to Ooyala's web-based players (HTML5 / 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 StatesA running player undergoes various states during its lifecycle. The following table introduces the most common player run-time states. There are also other states that apply only to specific platforms.
State changes are triggered by events (see Player V3 Run-time Events (Deprecated)), which occur either through user interaction (for example, the user clicks the play button) or programmatically via API calls. The current player state determines which functionality is available in the current context. For example, the play operation is available when the player is in the ready state, and the pause operation is available when it is in the playing state.
|loading||The embed code has been set. The video and its metadata are currently being loaded into the player.|
|ready||Playback of the video is ready to begin (including replay).|
|playing||The player is currently playing video content.|
|paused||The player is currently paused (after playback had begun).|
|buffering||Playback is currently stopped because it does not have enough video data to continue and is downloading more.|
|error||The player has encountered an error that prevents playback of the video. The error could be due to many reasons, such as video format, syndication rules, or the asset being disabled.|
Developer Resources for Player V3 Run-time StatesDue to different technical requirements across platforms, the list of player run-time states can vary by platform. Some states are universal (such as loading and ready), while others (such as init) apply only to certain platforms. In addition, the names of the player states differ across platforms to be consistent with platform SDK conventions. Refer to the following resources to learn how to access player state information programmatically.
|Development Platform||For more information|
|Android||Documentation for com.ooyala.android.OoyalaPlayer.State: https://apidocs.ooyala.com/android_mobilesdk/enumcom_1_1ooyala_1_1android_1_1_ooyala_player_1_1_state.html|
|iOS||See OOPlayerProtocol.h in the Ooyala SDK for iOS.|