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 for multiple simulcast configurations for published streams in one connection #1720

Conversation

lodoyun
Copy link
Contributor

@lodoyun lodoyun commented Jun 3, 2021

Description

This PR moves simulcast configuration from the Stacks to Streams. That allows for publishing multiple simulcast streams with different configurations in the same connection.

[] It needs and includes Unit Tests

Changes in Client or Server public APIs

[] It includes documentation for these changes in /doc.

}
stream.setSpatialLayersConfigs(spatialLayerConfigs);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this line should be out of the loop

log.debug(`message: Maybe set simulcast Layers config, simulcast: ${JSON.stringify(that.simulcast)}`);
if (streamInput.hasSimulcast() && streamInput.getSimulcastConfig().spatialLayerConfigs) {
streamInput.stream.transceivers.forEach((transceiver) => {
if (transceiver.sender.track.kind === 'video') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is not from this PR, but I've seen issues with Unified Plan because transceiver.sender can be null sometimes, can you add a check here to avoid issues?

@lodoyun
Copy link
Contributor Author

lodoyun commented Jul 8, 2021

Better version of this in #1726

@lodoyun lodoyun closed this Jul 8, 2021
@lodoyun lodoyun deleted the add/improveSimulcastConfigurationInClient branch July 8, 2021 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants