- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Aug 2022 19:40:38 +0000
- To: public-webrtc@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-stats: == remove outbound-rtp totalEncodedBytesTarget == https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-totalencodedbytestarget is implemented by libwebrtc but returns 0. So far nobody has complained (but me but I complain about *everything*) This doesn't offer much value over comparing targetBitrate to 8*bytesSent/second The difference is RTP packetization overhead which is a few bytes per RTP packet (or frame) which is depending on the codec and not modifiable in any way. Additionally it poses some extra problems for encoded-transform. Since that operates on frames, adding encryption bytes to it should be accounted for in the totalEncodedBytesTarget. Which is a major headache given how this is currently implemented in libwebrtc at least. Please vote with 👎 to remove or 👍 to keep Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/653 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 August 2022 19:40:40 UTC