- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Mar 2021 20:14:22 +0000
- To: public-webrtc-logs@w3.org
> Web Audio says the following: If contextOptions.sampleRate is specified, set the sampleRate of this AudioContext to this value. Otherwise, use the sample rate of the **_default output device_**. @youennf Exactly, and what singular testable value is that? I see no definition of _"default output device"_, so this is presumably defined by the user agent and its interpretation of the platform, not the spec. This seems to support the model @bradisbell wants. >The mediacapture does not say anything while exposing a similar API as Web Audio (optional sampleRate value). It too says defaults are up to the user agent: *"The User Agent MAY choose new settings for the constrainable properties of the object at any time. When it does so it MUST attempt to satisfy all current Constraints. ... the UA can use any information available to it. ... the energy usage of the camera varies ..., or whether ... will cause the device driver to apply resampling."* The spec even mentions "[platform defaults](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-constrainablepattern-getsettings)" as being useful (and preferable?) results, but shies away from mandating them. Part of the reason for that is that unlike output, there's no singular camera or microphone greater than another always. Another reason ironically is our desire to be conservative and biased toward RTCPeerConnection (I also wonder, would https://github.com/w3c/mediacapture-output/issues/87 influence it?) -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/775#issuecomment-789183582 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 March 2021 20:14:23 UTC