WebRtc: Implement RTCRtpEncodingParameters.resolutionScaleDownBy
Reported by
rajsripe...@gmail.com,
Jul 1 2016
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: At present there is no way for the app written on top of WebRtc to change the resolution of the send stream after it was created. This ability is important to adjust to the peer's requirements dynamically. The only way to achieve this right now is to tear down the current stream and create a new one with different constraints. This is expensive. We need support for RTCRtpEncodingParameters.resolutionScaleDownBy to achieve this. eg: var params = sender.getParameters(); // ... decrease sending resolution by 50 percent params.encodings[0].resolutionScaleDownBy = 2; sender.setParameters(params) What is the expected behavior? What went wrong? It is not easy for WebRtc peer to request a different video resolution after the stream was started. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: canary OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Jul 5 2016
Marking the above issue as Untriage as this is a feature request. Dev team will take a call on the above issue. Thank you!
,
Jul 5 2016
,
Oct 26 2016
,
Nov 10 2016
,
Nov 13 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 15 2017
,
Jan 18 2018
Ping for triaging.
,
Jan 18 2018
Related issue: https://bugs.chromium.org/p/chromium/issues/detail?id=803494
,
Jan 21
(2 days ago)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by b...@chromium.org
, Jul 1 2016