As pointed out, this seems to be missing a bunch of fields from the broader template..
On Thu, May 11, 2023 at 2:20 PM Yoav Weiss <[email protected]> wrote: > > > On Tue, May 2, 2023 at 4:29 PM 'Tony Herre' via blink-dev < > [email protected]> wrote: > >> Contact emails >> >> [email protected], [email protected] >> >> An explainer is missing, but you provided an inline one above, which is good enough from my perspective. A TAG review checkpoint is also missing. At the same time, we probably don't need to file for one here. > Spec >> https://w3c.github.io/webrtc-encoded-transform/#RTCEncodedVideoFrameMetadata >> particularly >> PR#173 <https://github.com/w3c/webrtc-encoded-transform/pull/173>. >> >> >> Summary >> >> Add a 'timestamp' field to RTCEncodedVideoFrameMetadata containing the >> presentation timestamp of the associated encoded video frame. >> >> Is this feature supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)? >> >> Yes >> >> Risks >> >> Interoperability and Compatibility >> >> Positive response from all members at W3C WebRTC WG April 2023 Interim, >> PR landed with no open issues. >> > While I agree that there seems to be general support on the PR, we typically require formal https://bit.ly/blink-signals > >> Ergonomics >> >> Added specifically to align with the timestamp field on the WebCodecs >> <https://www.w3.org/TR/webcodecs/#encodedvideochunk-interface> >> EncodedVideoChunk >> <https://www.w3.org/TR/webcodecs/#encodedvideochunk-interface>, and >> allow matching video frames with the timestamp in the WebCodecs >> VideoFrame <https://www.w3.org/TR/webcodecs/#videoframe-interface> >> object. >> >> Will also provide the same timestamp already exposed in >> requestVideoFrameCallback's 'mediaTime'. >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> >> ? >> >> Tested internally by RTCEncodedVideoFrame-capture-timestamp-id.html >> <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/fast/peerconnection/RTCEncodedVideoFrame-capture-timestamp-id.html>, >> upstreaming to WPT tracked in crbug.com/1441888. >> > It seems easier to land WPT directly with a ".tentative" suffix, and then rename them. > >> >> Entry on the feature dashboard >> >> None, small delta to launched API. >> > > I suspect this resulted in this intent not being captured in our tooling :/ > +Jason Robbins <[email protected]> - FYI > >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAArnMxH%2BNJKi80S4822wmjtQUqid8czA9AefCC_fm%3DHk3sTuiw%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAArnMxH%2BNJKi80S4822wmjtQUqid8czA9AefCC_fm%3DHk3sTuiw%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWoGftRYbOjZf%2B%2B1bXx8_bbbr%3DjNJG6xxy1y35z99DVPg%40mail.gmail.com.
