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

Allow incoming encoded frames to be forwarded to one or more senders on other PeerConnections #160

Open
alvestrand opened this issue Nov 27, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@alvestrand
Copy link
Contributor

This is in support of the use case outlined in w3c/webrtc-nv-use-cases#77

Experimentation has revealed two subissues here:

  • It must be possible to create multiple outgoing frames from a single incoming frame
  • It must be possible to adjust the metadata of the outgoing frame so that it corresponds to what is required for the outgoing PC

These will be filed as separate issues; this issue is filed to address other possible requirements.

@alvestrand
Copy link
Contributor Author

Added an explainer that covers both this feature and other usages of encoded media manipulations in #164

@aboba
Copy link
Contributor

aboba commented Dec 2, 2022

Related: #162, #168

@dontcallmedom-bot
Copy link

This issue was mentioned in WEBRTCWG-2023-09-12 (Page 48)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants