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

Support unified-plan #54

Closed
notedit opened this issue Jul 30, 2018 · 5 comments
Closed

Support unified-plan #54

notedit opened this issue Jul 30, 2018 · 5 comments

Comments

@notedit
Copy link
Contributor

notedit commented Jul 30, 2018

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

@backkem
Copy link
Member

backkem commented Jul 30, 2018

Thanks @notedit . Let us know if you have any specific needs for this feature. That allow us to determine the correct priority.

@notedit
Copy link
Contributor Author

notedit commented Jul 30, 2018

If we have want to support multi MediaStreams or build a SFU, we need this feature.

@notedit
Copy link
Contributor Author

notedit commented Dec 24, 2018

unified plan is default in chrome m72 now.

@trivigy
Copy link
Member

trivigy commented Feb 11, 2019

@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.

@notedit
Copy link
Contributor Author

notedit commented Feb 12, 2019

@trivigy here is the specific https://tools.ietf.org/html/draft-roach-mmusic-unified-plan-00
What i want is that multi streams use one ice transport, it is common in the sfu server, one peer receive multi remote streams through one peerconnection.

@Sean-Der Sean-Der added this to the 2.0.0 (Spear of Destiny) milestone Feb 12, 2019
Sean-Der added a commit that referenced this issue Mar 12, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Mar 13, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 1, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 3, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 3, 2019
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
Sean-Der added a commit that referenced this issue Apr 3, 2019
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
Sean-Der added a commit that referenced this issue Apr 3, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 3, 2019
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
Sean-Der added a commit that referenced this issue Apr 3, 2019
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
Sean-Der added a commit that referenced this issue Apr 3, 2019
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
Sean-Der added a commit that referenced this issue Apr 3, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 3, 2019
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
Sean-Der added a commit that referenced this issue Apr 4, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 4, 2019
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
Sean-Der added a commit that referenced this issue Apr 4, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
Sean-Der added a commit that referenced this issue Apr 4, 2019
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
Sean-Der added a commit that referenced this issue Apr 4, 2019
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
Sean-Der added a commit that referenced this issue Apr 4, 2019
This allows us to demonstrate multi-track easier, without having to
worry about encoding multiple times

Relates to #54
@Sean-Der Sean-Der removed the backlog label Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants