henbos

”Feature at risk” is another name for it if you want to avoid the term ”obsolete”

Implementation step 1: Implement "sender" and "receiver" in order to expose trackIdentifier for inbound-rtp. Implementation step 2: Deprecate "track" stats in implementations. Spec step 1: Move unimplemented metrics into a...

Aaaand we have a plan: #621 / #622 Let's close this issue in favor of that one and iterate?

I think the spec is in a pretty good state now, though we should sanity check by going over them again. Also I filed #660 as a follow-up since some...

Question/discussion for @vr000m @alvestrand

👍

Ping. Is this something we want to fix? :) What does other browsers do? @jan-ivar @youennf

Filed two sub-issues, one here on mediacapture-main to tweak/clarify the existing setting (https://github.com/w3c/mediacapture-main/issues/906) and one on mediacapture-extension to propose two new attributes (https://github.com/w3c/mediacapture-extensions/issues/76).

I don't think applying a transformation should be required to obtain a frame rate. Besides, I want both the FPS achieved and the FPS of dropped frames and for that...

What I propose are total counters, let the app worry about averaging.