- From: ivocreusen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Feb 2017 15:20:44 +0000
- To: public-webrtc-logs@w3.org
About the counter idea: it is typically the maximum echo likelihood in a time interval that's the most interesting to track, not the average (which is what you would get from the counter). This is why I implemented the max from the last 10 seconds, which is admittedly a compromise, but I couldn't think of a better way to do it. On Tue, Feb 14, 2017 at 4:15 PM, henbos <notifications@github.com> wrote: > I'm afraid the API is designed such that a caller should not need to know > about other getStats-callers. Any "since last call to getStats" logic means > invoking getStats affects all other callers. > > (Maybe residualEchoLikelihoodIntegral is a better name for > residualEchoLikelihoodCounter.) > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-stats/issues/153#issuecomment-279734896>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ARGCovOnRpRVd0Wu3EEfqWpg5GcMBA1vks5rccT2gaJpZM4Lz3cL> > . > -- GitHub Notification of comment by ivocreusen Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/153#issuecomment-279736594 using your GitHub account
Received on Tuesday, 14 February 2017 15:20:51 UTC