Re: [mediacapture-main] what is the default channelCount (#775)

> > Why do users have to be able to override defaults? (I mean, other than "which device")
> 
> > @henbos There's another contradiction: defaults may be device dependent, like channelCount in Firefox.
>
> Not a contradiction. You can ... have a default that is device-dependent like defaulting to the maximum ... capability 

Sure, that works up to 2 if we pick channelCount 2, but not 1. But what's your goal? E.g. why restrict user overrides if we're allowing channelCount to change through device switching anyway? Where's the invariant?

> If an app developer writes code and tries it out with a couple of devices on a couple of browsers and consistently get the same result they might think that the behavior is well-defined and have no idea that some user in the wild is able to change this in OS settings.

...or they may not have tested enough devices or not devices sold next week. It's the same problem (if you default to 2).

But I'd rather hear about the user in the wild: were they able to configure their microphone in a way that is unique enough to break this app? Did their customization have absolutely no impact on any site they visited? Or did it work on the ones that mattered (e.g. audio sites) and had no change on others (web conference ones)? I think that's the use case.

> Chrome shipped its stereo=1 hack and so by the sound of it has probably been upsampling to stereo when talking to Firefox. Not what was wanted, but slipped through the cracks. This illustrates that everything is not sufficiently tested.

@henbos Wrong spec. My understanding of the Chrome bug is it affected all audio input sources to RTCPeerConnection, not just stereo microphones, hence clearly a bug, and not related to defaults. Tests can use constraints and don't depend on defaults AFAIK.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/775#issuecomment-788569242 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 04:21:40 UTC