Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Constructors for RTC encoded frames with custom metadata #942

Open
1 task done
guidou opened this issue Apr 3, 2024 · 1 comment
Open
1 task done

Constructors for RTC encoded frames with custom metadata #942

guidou opened this issue Apr 3, 2024 · 1 comment
Assignees
Labels
Mode: async Work to be done asynchronously Progress: pending external feedback The TAG is waiting on response to comments/questions asked by the TAG during the review Review type: small delta Topic: media Venue: WebRTC WebRTC and media capture

Comments

@guidou
Copy link

guidou commented Apr 3, 2024

こんにちは TAG-さん!

I'm requesting a TAG review of [feature name].

[One paragraph summary of idea, ideally copy-pasted from Explainer introduction]

In some use cases, a Web application would like to have control over the metadata attached to RTC encoded frames. One example would be adjusting timestamps to introduce a delay in playout. Another one would be relaying incoming encoded data from one or more input peer connections to one or more output PeerConnections use case 3.2.2, which requires encoded frame metadata to conform with the requirements of its destination. The proposed solution consists of a constructor for encoded frames that takes data from an existing frame + customized metadata.

Note: Fully supporting use case 3.2.2 also requires an additional API for inserting encoded frames into an RTCPeerConnection, for which a separate TAG review will be requested.

Further details:

  • I have reviewed the TAG's Web Platform Design Principles
  • The group where the incubation/design work on this is being done (or is intended to be done in the future): W3C WebRTC Working Group
  • The group where standardization of this work is intended to be done ("unknown" if not known): W3C WebRTC Working Group
  • Existing major pieces of multi-stakeholder review or discussion of this design: Constructor frame w3c/webrtc-encoded-transform#223 (review of PR adding the constructors)
  • Major unresolved issues with or opposition to this design: No major issues. Some details about the API surface and precise wording of the spec are under discussion at Constructor frame w3c/webrtc-encoded-transform#223
  • This work is being funded by: Google

Please provide feedback here (not on w3c/webrtc-encoded-transform#223).

@martinthomson
Copy link
Contributor

Hi @guidou,

I've looked at this explainer several times and now the pull request. I have to confess that I still do not understand what it is that you are trying to achieve.

Our explainer explainer suggests that you outline use cases for the proposal, starting with end user objectives. I don't see that here, just "we would like to attach metadata to encoded frames".

I see that the WebKit issue was closed as "invalid". Should we be doing the same?

@martinthomson martinthomson added Topic: media Review type: small delta Venue: WebRTC WebRTC and media capture Mode: async Work to be done asynchronously Progress: pending external feedback The TAG is waiting on response to comments/questions asked by the TAG during the review and removed Progress: untriaged labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mode: async Work to be done asynchronously Progress: pending external feedback The TAG is waiting on response to comments/questions asked by the TAG during the review Review type: small delta Topic: media Venue: WebRTC WebRTC and media capture
Projects
None yet
Development

No branches or pull requests

4 participants