- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Jul 2019 17:33:17 +0000
- To: public-webrtc-logs@w3.org
There are several questions that we should ask ourselves: - Is it useful to easily query width, height and frameRate for a remote video track? - Is it useful to easily query width, height and frameRate for any video track? - Is it useful to downsample a remove video track? - Is it useful to upsample/forbid upsampling a remove video track? The current API is highly flexible and makes it hard to be fully interoperable across implementations. This is a bit concerning to me. At least for simple cases, I would hope we can get good consistency though. If a web application sets a width constraint of 640 for a remote track, I would hope all browsers to exhibit the same behaviour if the network decoded frames go from 1000 to 100 and then back to 1000 a minute after. If we forbid upsampling, I guess calling getCapabilities would for instance give the current allowed downsampling range which would go from [1, 1000] to [1, 100] and then back to [1, 1000]. The same principle would seem to apply for window screen share tracks. It seems that what we might want to enable here is to allow a web application to express something like 'provide me a video with width being at most XX'. If the call is successful, the web application should expect a consistent behaviour across browsers. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2188#issuecomment-515138749 using your GitHub account
Received on Thursday, 25 July 2019 17:33:18 UTC