- From: amn via GitHub <sysbot+gh@w3.org>
- Date: Sun, 18 Oct 2020 13:09:59 +0000
- To: public-webrtc-logs@w3.org
I agree with the above statement -- it also seems to me that there is a slightly different behaviour with regard to obtaining "actual" bitrate values as used by an active recorder, as opposed to obtaining the media type -- which, in my understanding, may change from what was passed to the constructor to whatever actual value the recorder decides to use upon starting recording. In other words, the specification is either deliberately or accidentally vague on this matter, while I think it could benefit from standardizing it -- there should be no harm in being able to obtain actual bitrate values? For the record (not that I claim either works according to the spec here), I see that Chrome reports zero for all bitrate values for an active recorder when no bitrates were explicitly specified to the recorder constructor. Firefox, in contrast, reports non-zero values I assume to be actual [constant] bitrates, even when no values were specified for the constructor. -- GitHub Notification of comment by amn Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/205#issuecomment-711165809 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 18 October 2020 13:10:01 UTC