- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Feb 2020 09:34:21 +0000
- To: public-webrtc-logs@w3.org
This is not just debugging information. WebRTC requires the application to negotiate which codecs to use. The more encoder/decoder capability information available to the application, the smarter it can be at making decisions. It would not _necessarily_ have to know about HW/SW - what the application _really_ wants to know is which encoder is performant. "hardwareAccelerated" would be the low-hanging fruit used as a heuritstic for "isPerformant". A more sophisticated API might express these things in terms of expected performance metrics in various setups. But implementing the sophisticated version of the API would be impossible without running various performance benchmarks prior to invoking the API. In some cases, HW accelerated vs SW only could be the difference between an HD experience and a VGA experience. Today the application is left to aimlessly guess unless it remembers its own "benchmarking" from previous application experiences, but trial-and-error would likely be worse than trying out the HW accelerated option in most cases. This is a lot more complicated than that, but the point is, this is useful information to the application - it's not debugging only. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/21#issuecomment-590234655 using your GitHub account
Received on Monday, 24 February 2020 09:34:23 UTC