- From: Justin Uberti <juberti@google.com>
- Date: Fri, 28 Mar 2014 09:19:53 -0700
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
Received on Friday, 28 March 2014 16:20:41 UTC
So far I have been asked about these real-world use cases on discuss-webrtc: - Choose between 720p and sub-HD (typically 480p or 360p) resolution (maxHeight, maxWidth). - Choose frame rate, especially for screen capture (maxFrameRate) - Control DSP settings (echoCancellation et al.) - Choose camera (sourceId). I am not aware of any scenarios that require complicated fallback semantics. On Thu, Mar 27, 2014 at 3:47 PM, Martin Thomson <martin.thomson@gmail.com>wrote: > Earlier today, I enjoyed Cullen's use of the slippery slope fallacy in > response to the request that a use case be produced to support the > current constraints expressiveness. > > Can anyone produce one? We're not going to build a castle on this > foundation, but it might be interesting to know just how high we need > to pile our stones. One probably isn't enough, but I can't recall > anything. > > A mailing list URL would suffice. > >
Received on Friday, 28 March 2014 16:20:41 UTC