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

Unable to receive more than 300 kbps in licode base_example #1434

Closed
vpoddubchak opened this issue Jul 19, 2019 · 3 comments · Fixed by #1440

Comments

@vpoddubchak
Copy link

commented Jul 19, 2019

Description
Can't get receive bandwidth more that 300 kbps in licode's example.

Steps to reproduce the issue:

  1. Run docker licode:staging
  2. Change values in licode/scripts/licode_default.js: defaultVideoBW = 800; maxVideoBW = 800;
  3. Commit and restart container
  4. Open page http://localhost:3001/ to start publishing
  5. Open chrome://webrtc-internals to check publishing bitrate: it is 800kbps
  6. Open another page: http://localhost:3001/?onlySubscribe=true and press Start to subscribe to the stream
  7. check webrtc-internals - publishing BW drop to 300kbps:
    webrtc-internals-800to300
  8. check http://localhost:3001/quality_layers.html to see limit in 300kbps on subscriber side:
    quality_layers_300_limit

Describe the results you expected:
I expect to see 800 kbps stream on receiver side because there:
https://github.com/lynckia/licode/blob/master/scripts/licode_default.js#L54
Default and max video bandwidth parameters to be used by clients for both published and subscribed streams

But looks like it is hard-coded somewhere.

@ashar02

This comment has been minimized.

Copy link

commented Jul 19, 2019

I am also facing same!!

@jcague

This comment has been minimized.

Copy link
Contributor

commented Jul 23, 2019

I found the issue, as @vpoddubchak suggests there is a default max video bw hardcoded to 300 in various places of our codebase, we should remove that limit or put a much higher one.

@jcague

This comment has been minimized.

Copy link
Contributor

commented Jul 23, 2019

This is a quick fix #1440

@jcague jcague closed this in #1440 Jul 24, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.