W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > April 2020

[webrtc-stats] targetBitrate should be defined as current encoder target settings (#560)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Tue, 21 Apr 2020 08:28:50 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-603809975-1587457728-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-stats:

== targetBitrate should be defined as current encoder target settings ==
In #423 I proposed marking this metric obsolete in favor of [totalEncodedBytesTarget](https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-totalencodedbytestarget) but there may be [issues with totalEncodedBytesTarget](https://bugs.chromium.org/p/webrtc/issues/detail?id=11443). For the time being, let's keep targetBitrate.

Its definition doesn't make sense. Especially "It is measured in bits per second and the bitrate is calculated over a 1 second window."
- It's an instantaneous target reflecting the encoder setting, not something you measure over a period of time.
- I'm not sure what the TIAS reference is accomplishing? Looks like a bandwidth modifier in SDP?

I propose just saying this is the current encoder target settings, which is a target for the payload bytes excluding retransmissions.

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/560 using your GitHub account
Received on Tuesday, 21 April 2020 08:28:56 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:50 UTC