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

[webrtc-pc] Add RTCRtpSender.getSynchronizationSources() to expose audioLevel (#2103)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 14 Feb 2019 13:35:04 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-410302431-1550151303-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Add RTCRtpSender.getSynchronizationSources() to expose audioLevel ==
A lot of people poll getStats() frequently to obtain audio levels, which is supposedly inefficient to the point that it can make your laptop sound like a helicopter. We already have RTCRtpReceiver.getSynchronizationSources()[i].audioLevel, should we add getSynchronizationSources() to RTCRtpSender as well? It would represent the RTP packets sent instead of the ones received, so you can read the local audio levels without setting up a loopback connection.

Related question:
- Is this audioLevel "good enough" to replace getStats()'s audio level? This is an instantaneous value, and while it can be polled frequently without any significant overhead, it may be based on something other than what people are used to.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2103 using your GitHub account
Received on Thursday, 14 February 2019 13:35:06 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC