Conversation
github-actions
bot
added
Content:WebAPI
|
Preview URLs External URLs (3)URL:
(comment last updated: 2025-08-27 12:12:48) |
chrisdavidmills
changed the title
chrisdavidmills
changed the title
| An object with the following properties: | ||
|
|
||
| - `audioLevel` | ||
| - : A number representing the audio level of this frame. The value is between 0 and 1 inclusive (linear), where 1 represents 0 dBov, 0 represents silence, and 0.5 represents approximately 6 dBSPL change in the sound pressure level from 0 dBov. The value is converted from the -127 to 0 range specified in [RFC6464](https://www.rfc-editor.org/rfc/rfc6464) via the equation `10^(-rfc_level/20)`. If the RFC6464 header extension is not present in the received packets of the frame, `audioLevel` will be `undefined`. |
There was a problem hiding this comment.
I had this comment on the stats PR that exposes audioLevel: #40495 (comment) and think it applies here too.
Is this the same thing as that one? They have slightly different information associated, should it be the same? Should we find a single place to document this, rather than repeating it?
There was a problem hiding this comment.
It is essentially the same piece of information, except that in this case, it is extracted from the metadata about an individual frame, rather than from statistics related to a stream.
I'd certainly be happy to make the language more consistent with what Hamish wrote; I'm not sure if there is a sensible common place we could document this and link to from both.
Would you rather I linked to Hamish's definition?
There was a problem hiding this comment.
I think:
- ideally, the WebRTC docs might have a single guide page that precisely defines concepts like audio level, that reference pages like this and @hamishwillee 's could link to. This page doesn't exist AFAIK and it's surely out of scope to ask you to add it in this PR.
- minimally I think we should consider if we want to explain what things like dBov and dBSPL are, which was my original comment on Hamish's PR.
- optionally we should make this language more consistent with the language in the other page.
I don't think linking from one reference page to another on an ad hoc basis is particularly useful. Linking to a single canonical definition ought to be part of a systematic organization of this documentation, which gets us into (1) territory.
There was a problem hiding this comment.
That sounds reasonable. I've updated the description to improve consistency and add the same explanatory links as Hamish added. I've kept the extra bit of text I included.
chrisdavidmills
deleted the
RTCEncodedAudioFrame-getMetadata-audioLevel-return-property
branch
4 participants
Description
Chrome 139 updates the
RTCEncodedAudioFrame.getMetadata()method so that theaudioLevelproperty is available in its return object. See https://chromestatus.com/feature/5206106602995712.This PR adds content for this new return property.
Motivation
Additional details
Related issues and pull requests