Re: [webrtc-stats] RTCMediaStreamTrackStats.audioLevel clarification

We have totalAudioEnergy defined now, which is computable. Is it possible to define audioLevel in terms of a computation over totalAudioEnergy?

I worry about audioLevel since it's inherently a "windowing" operator - instantaneous audioLevel doesn't make much sense at all. We could leave it implementation-defined, but that will give implementation variance. gives a JS implementation that shows two versions of exponential-decay calculation.

"Linear" kind of makes sense if you think that each halving of audio level should represent another 6 dBSPL change (0.25 = -12dB compared to 0 dBov). There are many other curves that could go through the other two defined points (0 dBov and -6 dBov) if the word "linear" is dropped. Suggestions for clearer description?

GitHub Notification of comment by alvestrand
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 25 October 2017 12:15:15 UTC