- From: amn via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Oct 2020 13:17:25 +0000
- To: public-webrtc-logs@w3.org
> If by "actual" you mean what the recorder happens to be **producing** at any given time, then that is out of scope for these attributes. They denote the bitrates the encoders were **configured** with. > The start() method is pretty clear on these attributes in the spec. To get actual bitrate values one could approximate this by looking at the size of the produced blobs. Or if done when the encoding is complete, it would be exact. Ultimately I have to concede. What actual bitrates apply can be inferred from the size and rate of the blobs that the recorder generates. > The spec was updated. Chrome was not (yet). See [wpt.fyi](https://wpt.fyi/results/mediacapture-record/MediaRecorder-bitrate.https.html?label=experimental&label=master&aligned) for more details. Well, if we go by the spec as you explained it to me, then zero *should* be reported for bitrate when no bitrate was passed to constructor? -- GitHub Notification of comment by amn Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/205#issuecomment-713563272 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 October 2020 13:17:27 UTC