-
Notifications
You must be signed in to change notification settings - Fork 186
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
[BUG] Bandwidth goes up slowly on every new sesssion #182
Comments
hey @karasusan - let us know if there is any way you need helpt testing |
To fix this issue, I erased the operation of using customized SDP. |
hey @karasusan , thank you! Unfortunatly we cant verify it gettign better. Let us know if we can help testing. |
This issue is caused by the customized SDP. |
Hey yes please ignore my previous post. I just checked it and it works! The bandwidth rises quickly. |
@WaltzBinaire I expect the input system is the cause of it, but there is no proof of that yet. |
Hey @karasusan - yes i think we should reopen the issue. The challenge here is that multiple issues seem to be connected to the same procedure - and that makes it important to tackle the moment they start to appear. From our side:
I believe all those issues spin around the lines that control sdp - and i think this is the most important issue of the repo - since control and quality determine the overall quality. However im als not able to tackle the issue - really sorry! |
@karasusan Are you able to recreate the input lack? #164 |
@WaltzBinaire |
Describe the bug
When starting the demo you will see the image quality ramping up slowly everytime you create a new connection.
It seems almost animated as if a control value was not initialized and interpolates up over time.
To Reproduce
Only on 2.1.0
Start demo - local or on server.
Bad quality on startup slowly progressing to full quality over 15-30 seconds
Expected behavior
A quick recovery of the image quality matching the actual bandwidth
Screenshots
Environment (please complete the following information):
Additional context
Bug was introduced in 2.1.0 - we couldnt find this particular behavior before.
The text was updated successfully, but these errors were encountered: