Intent to Ship: MediaStreamTrackProcessor frame counters

12 views
Skip to first unread message

Chromestatus

unread,
8:41 AM (2 hours ago) 8:41 AM
to blin...@chromium.org, agp...@google.com, gui...@google.com
Contact emails
agp...@google.com, gui...@google.com

Specification
https://www.w3.org/TR/mediacapture-transform/#track-processor-interface

Summary
Adds discardedFrames and totalFrames attributes to the MediaStreamTrackProcessor interface. These counters allow web developers to monitor the health of their media processing pipelines by tracking the number of frames received and dropped by the processor.

Blink component
Blink>MediaStream

Web Feature ID
insertable-streams

Motivation
No information provided

Initial public proposal
No information provided

TAG review
No information provided

TAG review status
Not applicable

Goals for experimentation
None

Risks


Interoperability and Compatibility
No information provided

Gecko: Positive (https://github.com/w3c/mediacapture-transform/pull/125) Spec PR was approved by Mozilla

WebKit: Positive (https://github.com/w3c/mediacapture-transform/pull/125) Spec PR was approved by WebKit

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No information provided


Debuggability
No information provided

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes

Is this feature fully tested by web-platform-tests?
Yes
third_party/blink/web_tests/wpt_internal/mediacapture-insertable-streams/MediaStreamTrackProcessor-stats.https.html, third_party/blink/web_tests/wpt_internal/mediacapture-insertable-streams/MediaStreamTrackProcessor-stats-transfer.https.html

Flag name on about://flags
No information provided

Finch feature name
MediaStreamTrackProcessorStats

Rollout plan
Will ship enabled for all users

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/513481577

Estimated milestones
Shipping on desktop150
Shipping on Android150
Shipping on WebView150


Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

No information provided

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6267249280286720?gate=4665260125585408

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages