Events and notifications help you manage the asynchronous aspects of the video application.
MediaPlayerStatus objects provide information about changes in player status. Notification objects provide information about warnings and errors. Errors that stop the playback of the video also cause a change in the status of the player. You implement event listeners to capture and respond to events (MediaPlayerEvent objects).
Your application can retrieve notification and status information. Using this information, you could also create a logging system for diagnostics and validation.
MediaPlayerNotification provides information that is related to the player’s status.
TVSDK provides a chronological list of
MediaPlayerNotification notifications, and each notification contains the following information:
A time stamp
Diagnostic metadata that consists of the following elements:
type: INFO, WARN, or ERROR.
code: A numerical representation of the notification.
name: A human-readable description of the notification, such as SEEK_ERROR
metadata: Key/value pairs that contain relevant information about the notification. For example, a key named
URL provides a value that is a URL related to the notification.
innerNotification: A reference to another
MediaPlayerNotification object that directly impacts this notification.
You can store this information locally for later analysis or send it to a remote server for logging and graphical representation.
You can listen for notifications.
The core of the Primetime Player notification system is the
Notification class, which represents a standalone notification.
To receive notifications, listen for notifications as follows:
TVSDK passes a
NotificationEvent object to the callback.
Notifications types are enumerated in the
You can use notifications to implement real-time logging in your video application.
The notification system allows you to gather logging and debugging information for diagnostics and validation without stressing the system.
The logging back end is not part of a production setup and is not expected to handle high-load traffic. If your implementation does not need to be absolutely complete, consider the efficiency of data transmission to avoid overloading your system.
Here is an example of how to retrieve notifications:
Create a timer-based execution thread for your video application that periodically queries the data gathered by the TVSDK notification system.
If the timer’s interval is too large, and the size of the event list is too small, the notification event list will overflow.
To avoid this overflow, do one of the following:
Serialize the latest notification event entries in JSON format and send the entries to a remote server for postprocessing.
The remote server can graphically display the provided data in real-time.
To detect the loss of notification events, look for gaps in the sequence of event index values.