- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jun 2019 14:32:59 +0000
- To: public-webrtc-logs@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-stats: == Audio samples and channels == totalAudioEnergy is based on totalSamplesSent or totalSamplesReceived, as is totalSamplesDurations. These are all based on number of samples. The spec never mentions audio channels though. The current implementation in Chrome calculates all of these things without taking the number of channels in to account. For example, assuming no packet loss, the totalSamplesDuration increase by 1 second per second. If we took in to account the fact that the audio has 2 channels, we would expect the true samples count to be twice as high, and as a consequence that the totalSamplesDurations increased by 2 seconds per second. Is Chrome doing the right thing or the wrong thing? Should we update the spec to say "samples per channel" everywhere it currently says "samples"? Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/448 using your GitHub account
Received on Tuesday, 25 June 2019 14:33:01 UTC