W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2020

[webrtc-stats] framesEncoded exists only for video? (#573)

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Mon, 18 May 2020 16:08:45 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-620332876-1589818124-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-stats:

== framesEncoded exists only for video? ==
https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-framesencoded says
> Only exists for video

However, https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-totalencodetime does not have that restriction (even though it is missing in Chrome for audio) and we typically say that you can calculate the average by dividing the encodetime by the number of frames. Note that for most audio codecs the number of frames per packet is 1 (speex being one of the few exceptions iirc)

So how does one calculate the average time spent on encoding/decoding for audio?

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/573 using your GitHub account
Received on Monday, 18 May 2020 16:08:47 UTC

This archive was generated by hypermail 2.4.0 : Monday, 18 May 2020 16:08:48 UTC