-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Support unified-plan #54
Comments
Thanks @notedit . Let us know if you have any specific needs for this feature. That allow us to determine the correct priority. |
If we have want to support multi MediaStreams or build a SFU, we need this feature. |
unified plan is default in chrome m72 now. |
@notedit Any specific parts regarding the unified-plan that you need? Personally I only need the BUNDLE protocol to work according to the unified-plan, and only related to data channels. What about you? I am going to end up fixing whatever is wrong but only related to data channels. If I know what you need, I might try looking into it along the way. Or at the very least it will be documented here for future work. |
@trivigy here is the specific https://tools.ietf.org/html/draft-roach-mmusic-unified-plan-00 |
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This commit has breaking changes. This API change means we can no longer support an arbitrary number of receivers. For every track you want to receive you MUST call PeerConnection.AddTransceiver We do now support sending an multiple audio/video feeds. You can see this behavior via gstreamer-receive and gstreamer-send currently. Resolves #54
This allows us to demonstrate multi-track easier, without having to worry about encoding multiple times Relates to #54
firefox supports unified-plan, latest chrome supports unified-plan too.
https://tools.ietf.org/html/draft-roach-mmusic-unified-plan-00
https://bugs.chromium.org/p/chromium/issues/detail?id=799030
The text was updated successfully, but these errors were encountered: