You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an analyst I want to be able to know how much time a user really spent playing some content. Current metrics are affected by speed and represent the duration played (in the reference frame of the content), not the actual time required by a user to play it (if playing at high / low speeds).
This nice-to-have has been discussed during one of our API sync meetings.
Hints
Our player could provide a standard metric for the playback duration in wall-clock time, i.e. not affected by speed settings. This could be useful.
Note that the playback duration (probably affected by speed, but to be checked) in AVMetrics is called playbackDuration. It is called watchDuration in AVAccessLog but the new terminology is likely more generic. If we provide a new value we should probably pick a close name but with clear meaning.
Acceptance criteria
A (wall-clock based) playback duration metric is available.
Tasks
Add new metric (only measure time when rate != 0 and player not buffering, most likely).
The text was updated successfully, but these errors were encountered:
As an analyst I want to be able to know how much time a user really spent playing some content. Current metrics are affected by speed and represent the duration played (in the reference frame of the content), not the actual time required by a user to play it (if playing at high / low speeds).
This nice-to-have has been discussed during one of our API sync meetings.
Hints
Our player could provide a standard metric for the playback duration in wall-clock time, i.e. not affected by speed settings. This could be useful.
Note that the playback duration (probably affected by speed, but to be checked) in
AVMetrics
is calledplaybackDuration
. It is calledwatchDuration
inAVAccessLog
but the new terminology is likely more generic. If we provide a new value we should probably pick a close name but with clear meaning.Acceptance criteria
Tasks
The text was updated successfully, but these errors were encountered: