W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2018

Re: [webrtc-pc] RTCRtpSynchronizationSource.audioLevel algorithmic equality

From: Cullen Jennings via GitHub <sysbot+gh@w3.org>
Date: Tue, 27 Feb 2018 17:07:41 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-368951887-1519751260-sysbot+gh@w3.org>
Yes, I think we need to report what is present in the header if the headers is there - I would be fine if there was a separate API that always reported a computed value. The problem is, that the MCU might report the level in the original audio but being doing noise suppression that would make the computed value no match. We would also have the problem that we would have to agree on an algorithm to compute the level so that different browsers did not compute different levels. It's not easy to agree on an algorithm because things like how long a time period the level is averaged over. 

GitHub Notification of comment by fluffy
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1760#issuecomment-368951887 using your GitHub account
Received on Tuesday, 27 February 2018 17:07:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:01 UTC