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

Make connection quality level depend on strategy #1767

Conversation

jcague
Copy link
Contributor

@jcague jcague commented Nov 15, 2021

Description

Make Connection Quality Levels depend on the BW distributor strategy.

[] It needs and includes Unit Tests

Changes in Client or Server public APIs

Possible quality levels are now: 'good', 'low' and 'very-low'.

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

Copy link
Contributor

@lodoyun lodoyun left a comment

Choose a reason for hiding this comment

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

👍 I like this simple idea to get that signal from the distributor but I have two comments:

  1. Variable names suggestion in comments.
  2. Consider adding to the unit tests to cover this. I think we already have cases that cover both options and it would be easy to just check the output of the tooLowBandwidhEstimation call.

@@ -32,6 +32,10 @@ void StreamPriorityBWDistributor::distribute(uint32_t remb, uint32_t ssrc,
}
ELOG_DEBUG("Starting distribution with bitrate %lu for strategy %s", remaining_bitrate, getStrategyId().c_str());
strategy_.reset();

bool has_no_default_levels = false;
Copy link
Contributor

@lodoyun lodoyun Nov 16, 2021

Choose a reason for hiding this comment

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

These variable names are really confusing to me. I think it's because I think of fallback and slideshow as "default levels". An alternative would be has_no_spatial_levels and distribute_bitrate_to_spatial_levels since we always expect temporal layers there anyway.
Other options are probably fine as long as we avoid default as it's not clear what default is in the context.

@jcague jcague merged commit 58722d1 into lynckia:master Nov 22, 2021
@jcague jcague deleted the update/base_connection_quality_levels_on_stream_priorities branch November 22, 2021 12:37
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