- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 15:21:31 +0000
- To: public-webrtc-logs@w3.org
Samples rather than frames were chosen for consistency with other metrics (we consistently use samples rather than frames when it comes to audio, e.g. [totalSamplesReceived](totalSamplesReceived)). This might not be ideal in hindsight, but it is addressed in the [Terminology section](https://w3c.github.io/webrtc-stats/#terminology): > An _**audio sample**_ refers to having a sample in any channel of an audio track - if multiple audio channels are used, metrics based on samples do not increment at a higher rate, simultaneously having samples in multiple channels counts as a single sample. > When does a capture device drop audio? If the browser has a polling based model it may not be able to keep up with all the samples in all circumstances, though I am not the audio expert here. I can try to figure out more information about this if you like -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/741#issuecomment-1458357533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 15:21:33 UTC