- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Sep 2022 12:39:31 +0000
- To: public-webrtc@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-stats: == powerEfficientEncoder/powerEfficientDecoder == getStats() does not explicitly contain a boolean for whether or not the current encoder/decoder is hardware accelerated. The question of HW vs SW has raised some concerns in the past, but in many other specs we've usually gone the "isPowerEfficient" path instead, e.g. [powerEfficient](https://www.w3.org/TR/media-capabilities/#dom-mediacapabilitiesinfo-powerefficient) or [powerEfficientPixelFormat](https://w3c.github.io/mediacapture-extensions/#def-constraint-powerEfficientPixelFormat). This frames the question about efficiency instead of hardware, which is the thing you really want to know (but in most cases HW = efficient, SW = inefficient). Can we add this to RTCInboundRtpStreamStats and RTCOutboundRtpStreamStats? The lack of this metric has lead some implementations (Chromium) to heuristically include this information in the [encoderImplementation](https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-encoderimplementation), so this is to some extent exposed already. @eshrubs Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/666 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 September 2022 12:39:32 UTC