LGTM2
On 2/27/25 11:51 AM, Chris Harrelson wrote:
Thanks!
LGTM1
On Thu, Feb 27, 2025 at 8:36 AM Guido Urdaneta <gui...@chromium.org>
wrote:
The capture timestamp is now merged in the spec.
https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedvideoframemetadata-capturetime
https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedaudioframemetadata-capturetime
On Wed, Feb 26, 2025 at 7:23 PM Guido Urdaneta
<gui...@chromium.org> wrote:
The capture timestamp is in an "Editors can integrate" PR
<https://github.com/w3c/webrtc-encoded-transform/pull/240>,
and is expected to be merged into the spec tomorrow.
On Wed, Feb 26, 2025 at 5:28 PM Chris Harrelson
<chris...@chromium.org> wrote:
On Tue, Feb 25, 2025 at 5:28 AM Chromestatus
<ad...@cr-status.appspotmail.com> wrote:
Contact emails
gui...@chromium.org
Explainer
https://github.com/guidou/webrtc-encoded-transform/blob/master/timestamps.md
Specification
https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedaudioframemetadata-receivetime
Summary
This feature consists in exposing to the Web some
timestamps that are present in WebRTC encoded frames
transmitted via RTCPeerConnection. The timestamps in
question are: -Capture timestamp: the timestamp when a
frame was originally captured -Receive timestamp: the
timestamp when a frame was received
I see receive timestamp in the spec, but not capture
timestamp?
Blink component
Blink>WebRTC
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebRTC%22>
TAG review
https://github.com/w3ctag/design-reviews/issues/1049
TAG review status
Pending
Risks
Interoperability and Compatibility
Interoperability risk: The main risk is that other
browser do not implement this change. However, this
change has the support of other major browsers and it
is small enough that it should not be difficult to
support. Compatibility risk: No compatibility risk as
the change is strictly additive.
/Gecko/: Positive
(https://github.com/w3c/webrtc-encoded-transform/pull/240)
No position requested at
https://github.com/mozilla/standards-positions since
this is a minor addition to an existing spec. Linked
to PRs instead (merged into spec or "editors can
integrate").
/WebKit/: Positive
(https://github.com/w3c/webrtc-encoded-transform/pull/237)
No position requested at
https://github.com/WebKit/standards-positions/ since
this is a minor addition to an existing spec. Linked
to PRs instead (merged into spec or "editors can
integrate").
/Web developers/: Positive
(https://github.com/w3c/webrtc-encoded-transform/issues/225)
/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?
N/A
Debuggability
None
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
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCEncodedFrame-timestamps.html?label=experimental&label=master&aligned
<https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCEncodedFrame-timestamps.html?label=experimental&label=master&aligned>
Flag name on about://flags
None
Finch feature name
None
Non-finch justification
None
Requires code in //chrome?
False
Tracking bug
https://crbug.com/391114797
Availability expectation
Feature is available in Chromium in the short term,
and eventually available in other browsers.
Adoption expectation
Feature is used by multiple partners to provide
functionality within 12 months of launch in Chrome.
Non-OSS dependencies
Does the feature depend on any code or APIs outside
the Chromium open source repository and its
open-source dependencies to function?
N/A
Estimated milestones
Shipping on desktop 135
Shipping on Android 135
Shipping on WebView 135
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).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6294486420029440?gate=5205778715377664
This intent message was generated by Chrome Platform
Status <https://chromestatus.com>.
--
You received this message because you are subscribed
to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving
emails from it, send an email to
blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67bdc57a.2b0a0220.2aae14.02b8.GAE%40google.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67bdc57a.2b0a0220.2aae14.02b8.GAE%40google.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BBuZxYeHYT7dbXzxWARu9ZGMfwhBxUc74BMDM2JSm6r%2BeLBaw%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BBuZxYeHYT7dbXzxWARu9ZGMfwhBxUc74BMDM2JSm6r%2BeLBaw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_A7-gi7_V8ZtEQr%2Bj-zuRjpgSsXDejnmMZzEP6MCW0OQ%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_A7-gi7_V8ZtEQr%2Bj-zuRjpgSsXDejnmMZzEP6MCW0OQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f75661d0-e71d-4b16-b7d3-1031d2f0767b%40chromium.org.
