search

cta-standards / R4WG20-QoE-Metrics

Issue tracking repository for the R4-Wg20 QoE Initiative
9 stars 2 forks source link

Definition of "watched time" on page 18 is inaccurate #9

Closed tonihei closed 5 years ago

tonihei commented 5 years ago

There are two issues:

  1. The watched time should be defined in milliseconds as the other metrics. This would also remove the need to define decimal places.

  2. The definition says it's the sum of time between (a) playbackRequest and (b) playbackPause, playbackFinish, playbackFail. I'd argue (a) should be playbackRequest and playbackStart. Otherwise all "restart" scenarios are not really captures as if only expect one playbackRequest event.

gheikkila commented 5 years ago

The intention is to capture the time the user is watching, which should be between the (first) playbackRequest (i.e. usually when the user press "Play") and the next pause/finish/fail. If there are multiple playbackRequest events (without intervening pause/finish/fail, like if the user is seeking) these should probably not be used to mark the start of watched time.

The playbackStart event is not related to the user action, but only to when rendering of a content starts, so it's not related to when the user started to watch. Thus it should not be used in the calculation of watched time.

mlevine84 commented 5 years ago

For 1, WG will consider the request to use milliseconds and will be addressed with comment #22

For 2, WG agrees with Gunnar's response above to address the raised concern.