- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Oct 2020 12:48:23 +0000
- To: public-webrtc-logs@w3.org
> In a case of sync vs async w3c seems to prefer sync if at all feasible. I am not sure I see how deciding a default bitrate is an async getter attached to an OS resource. Are there hardware encoders one may not configure the bitrate of? The fact that RTCRtpSender.getCapabilities is providing a synchronous API is an identified issue, see https://github.com/w3c/webrtc-extensions/issues/49 If it is difficult to know which encoder (or which profiles) are supported, it is not easy to select a good default bit rate. Also, for video, the frame size might have a potential impact on a good default bit rate. In the case of passthrough codecs, it seems that we would like the bit rate to be set to 0 (?). Are we sure though that we can know synchronously that passthrough codecs will be supported for all remote tracks? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/205#issuecomment-712133003 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 October 2020 12:48:25 UTC