The following instructions provide guidance for implementation across all 2.x SDKs.
If you are implementing a 1.x version of the SDK, you can download the 1.x Developers Guides here: Download SDKs.
Quality of experience tracking includes quality of service (QoS) and error tracking, both are optional elements and are not required for core media tracking implementations. You can use the media player API to identify the variables related to QoS and error tracking.
qosObject
trackEvent(Media.Heartbeat.Event.BitrateChange, qosObject);
Call trackError("media error id");
Identify when the bitrate changes during media playback and create the MediaObject
instance using the QoS information.
QoSObject variables:
These variables are only required if you are planning to track QoS.
Variable | Description | Required |
---|---|---|
bitrate |
Current bitrate | Yes |
startupTime |
Startup time | Yes |
fps |
FPS value | Yes |
droppedFrames |
Number of dropped frames | Yes |
QoS object creation: createQoSObject
qosInfo = ADBMobile.media.createQoSObject(50000, 0, 24, 10);
When playback switches bitrates, call the BitrateChange
event in the Media Heartbeat instance: trackEvent
ADBMobile.media.trackEvent(ADBMobile.media.Event.BitrateChange);
Update the QoS object and call the bitrate change event on every bitrate change. This provides the most accurate QoS data.
Make sure that getQoSObject()
method returns the most updated QoS information.
When the media player encounters an error, and the error event is available to the player API, use trackError()
to capture the error information. (See Overview.)
Tracking media player errors will not stop the media tracking session. If the media player error prevents the playback from continuing, make sure that the media tracking session is closed by calling trackSessionEnd()
after calling trackError()
.