- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Feb 2018 03:15:06 +0000
- To: public-media-capture-logs@w3.org
I agree with @martinthomson down-scaling is critical. The use-case is obvious: 2880 x 1800 x 60 fps is too rich for most people's uplink. FWIW Firefox's (non-standard) screen-sharing has supported downscaling since inception ([Try it](https://jsfiddle.net/jib1/76szqnLy/)). However, cropping is not supported (instead all "settings dictionaries" have the same aspect). However, I find the implicit assumption that all track constraints defined anywhere should work everywhere else absurd. I think we owe implementers to list explicitly the constraints we expect to work on this source. I propose `width`, `height`, and `frameRate`. I consider `aspectRatio` and `resizeMode` useless (all settings dictionaries have the same aspect). But I'm open to including them (they'd have some informative value in `track.getSettings()` perhaps. I propose we don't crop. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/31#issuecomment-367200644 using your GitHub account
Received on Wednesday, 21 February 2018 03:15:53 UTC