- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Oct 2020 19:43:32 +0000
- To: public-webrtc-logs@w3.org
I am not sure adding another constraint is the best approach, constraints are difficult to use when they are not fully orthogonal one with each other. Let's say we do not care about device selection and we already have a video capture track. UAs could expose the native presets of the track camera. Developers could then ask for a particular preset. Pixel/frame rate downsampling adaptation could still be a thing through regular width/height/frameRate constraints on top of preset selection. In that case, the native capture format information would naturally be exposed within presets so that web developers can decide which preset to use. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/739#issuecomment-713831929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 October 2020 19:43:33 UTC