Events - Storm Library

Player events are related to player behaviors (not the video/stream itself).

Event nameAdditional dataDescriptionCan be fired more than once?
playerReadynoThis event fires when the player is ready to receive API calls. No method should be called upon the player before this event is registeredno
interactionRequirednoSome browsers and devices do not allow for a player (media) to start on its own and require direct user interaction (like a mouse click). This event indicates that such “push” is neededno
playerStartnoThis event is called whenever the player is preparing to start a videoyes
playerStopnoThis event is called whenever the player stops playing video and awaits in an IDLE stateyes
playerDisconnectednoEvents fires when the player is disconnected from a storm server (it might be because of viewer connection or other network issues)no
playerConnectionFailednoThis event fires when the player could not connect to a storm server (server is not running, some network issues). If there are more servers on the config list, the player will try to connect to a different server insteadyes
onAllServersFailednoThis event is related to "playerConnectionFailed". If the player fails to connect to all provided servers on a config list, this event means that it cannot do anything moreno
compatibilityErrornoIf a browser or device does not support provided sources, this event will be fired. Please keep in mind that the player will do whatever it can (switch between multiple modes) to provide the best compatibility with a given device. Still, at some point, it might simply be impossible to start a videono
noSLLErrornoIf SSL layer is required for given sources and the browser does not provide it – this error will be firedno
Table 1. Player events table
On this page

Player events