- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Wed, 18 May 2011 16:19:26 +1000
On Fri, May 6, 2011 at 3:04 AM, Steve Lacey <sjl at chromium.org> wrote: > > > On Thu, May 5, 2011 at 2:54 AM, Jeroen Wijering <jeroen at longtailvideo.com> > wrote: >> >> Hey Steve, >> >> This looks great; would be a really useful set of data for video players / >> publishers. Since none of the metrics have a time component, developers can >> sample the data over the window / at the frequency they prefer. >> >> Would jitter be calculated over decodedFrames or >> decodedFrames+droppedFrames? In the first case, jitter is a more granular >> metric for measuring exact presentation performance. In the latter case, >> jitter can serve as a single metric for tracking processing power (simple!). >> In either case, it's fairly straightforward to calculate towards the other >> metric. > > Actually, I would expect presentedFrames + droppedFrames would be used. This > implies all decoded frames that were supposed to be presented. Do we also expose to the JS developer how many frames we actually requested, so we can calculate rates? Silvia.
Received on Tuesday, 17 May 2011 23:19:26 UTC