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

Return max spatial layer from selectors. #1743

Merged
merged 3 commits into from
May 26, 2023
Merged

Return max spatial layer from selectors. #1743

merged 3 commits into from
May 26, 2023

Conversation

boks1971
Copy link
Contributor

With differing requirements of SVC and allowing overshoot in Simulcast, selectors are best placed to indicate what is the max spatial layer when they indicate a switch to max spatial layer.

With differing requirements of SVC and allowing overshoot in Simulcast,
selectors are best placed to indicate what is the max spatial layer when
they indicate a switch to max spatial layer.
@boks1971
Copy link
Contributor Author

@cnderrauber Can you try this with SVC also please?

@boks1971
Copy link
Contributor Author

Thought about replacing IsSwitching... with just layer values, but have to initialise in every selector with-1 as default value of 0 is a valid layer. So, left the IsSwitching... booleans in there.

@cnderrauber
Copy link
Contributor

@cnderrauber Can you try this with SVC also please?

The branch works well for me

@boks1971 boks1971 merged commit 1c92081 into master May 26, 2023
@boks1971 boks1971 deleted the raja_max_spatial branch May 26, 2023 07:19
hautvfami pushed a commit to Stark-Industries-Ltd/livekit that referenced this pull request Jul 21, 2023
* Return max spatial layer from selectors.

With differing requirements of SVC and allowing overshoot in Simulcast,
selectors are best placed to indicate what is the max spatial layer when
they indicate a switch to max spatial layer.

* fix test

* prevent race
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