Should we stop the watch timer when user pauses the video? about clappr-stats HOT 5 CLOSED

We basically have these main timers:

• session time (this should be the time measured from the intent to play to leave the page or video end)
• watch time (this should be the time that user was really watching something)
• pause time (this should be the time the player was paused)
• buffer time (this should be the time of buffering)
• startup time (this should be the time from intent to play to playing)

Does it make sense?

from clappr-stats.

Makes sense to me

On 22 Sep 2016, at 19:32, Leandro Moreira [email protected] wrote:

We basically have three main timers:

session time (this should be the time measured from the intent to play to leave the page or video end)
watch time (this should be the time that user was really watching something)
pause time (this should be the time the player was paused)
buffer time (this should be the time of buffering)
startup time (this should be the time from intent to play to playing)
Does it make sense?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

from clappr-stats.

What do you @towerz @flavioribeiro @tjenkinson @bernardocamilo @fcapinho @rafaelzacarias think should we consider the paused time as part of watch time?

from clappr-stats.

I'd say yes if it's meant to be a measure of how long it's been playing. Maybe a report of the furthest point in the video the user has seeked to would be useful too to see how far users have watched into, or an array of time ranges that have been played if playbacks can provide this?

On 22 Sep 2016, at 14:58, Leandro Moreira [email protected] wrote:

What do you @towerz @flavioribeiro @tjenkinson @bernardocamilo @fcapinho @rafaelzacarias think should we consider the paused time as part of watch time?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

from clappr-stats.

IMHO, I don't think so IF we want both the real_watch_time and the entire_watch_time.

Considering that entire_watch_time means "how long it's been playing" and real_watch_time means (entire_watch_time minus paused_time)

At the server side, its easy to calculate the entire watch time
(1)entire_watch_time = last_ping_timestamp - first_ping_timetimestamp

But to calculate the real watch time is a little tricky:
(2)real_watch_time = last_ping_timestamp - first_ping_timestamp - (paused time)

I think that would be easier to receive the real watch time (discarding the paused time) at the server side, to avoid to do this math(2) on the server: if a user has a lot of pause and plays during a video watch, we should retrieve messages for every pause/play events to reach the value of real_watch_time.

Or... send both the watch_time and the pause_time :)

from clappr-stats.