Re: [mediacapture-main] Mark resizeMode, sampleRate, sampleSize, latency as features at risk (#958)

- `sampleRate` _can_ make some sense if you want to filter out low-quality devices (e.g. bluetooth handsfree), or understand some things about the local devices (e.g. if you have very high sample-rate), but it's pretty niche. It can be used for fingerprinting.
- `sampleSize` _can_ be useful if you want to know very advanced properties of the device, but generally it's not particularly useful. It can also be used for fingerprinting. It's useless without knowing how the bits are stored: it's possible to have a 32-bits DAC, but what's important to know is if those samples are float32 (because the OS is exposing f32 audio samples) or int32 (because you have a _real_ 32-bits dac and this is getting through somehow to script -- only webcodecs supports dealing with s32 audio samples afaik), and this is not possible. I'd say it's not very useful in the current state of the web platform. Similarly, this can be used for fingerprinting.
- `latency` can typically and generally only be trusted after measuring it while the device is being used. We're adding good APIs to get this number. Again, this can be used for fingerprinting.

-- 
GitHub Notification of comment by padenot
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/958#issuecomment-1725917655 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 19 September 2023 15:42:31 UTC