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

AGC makes microphone volume too loud during conference calls #4634

Closed
foxlet opened this issue Jul 19, 2017 · 4 comments
Closed

AGC makes microphone volume too loud during conference calls #4634

foxlet opened this issue Jul 19, 2017 · 4 comments
Labels
A-VoIP P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround

Comments

@foxlet
Copy link

foxlet commented Jul 19, 2017

Description

When running a conference call in a Matrix channel using the Riot desktop app, some type of AGC keeps adjusting the system's microphone level allowing the sound to clip.

Steps to reproduce

  • Start conference call
  • Talk for a while
  • Volume increases automatically.

Ideally the volume shouldn't change, or be allowed to clip. The Windows Sound panel shows the volume increasing, and bringing it back down only works for a moment. Possibly adding an option to disable automatic gain control could help.

Log: not sent

Version information

  • Platform: Desktop

For the desktop app:

  • OS: Windows 7
  • Version: 0.11.4
@lampholder lampholder added S-Major Severely degrades major functionality or product features, with no satisfactory workaround P1 A-VoIP labels Jul 19, 2017
@foxlet
Copy link
Author

foxlet commented Jul 19, 2017

Possible some hints as to what is managing AGC (as part of Google Chrome's WebRTC)?

https://stackoverflow.com/questions/37326846/disabling-auto-gain-conctrol-with-webrtc-app

@uhoreg
Copy link
Member

uhoreg commented Jul 20, 2017

@ahsanshaokat please don't pollute issues with unrelated questions.

Regarding the actual issue reported here, part of the blame could be the conferencing server, which is due to be replaced in the next couple of weeks, and hopefully will fix many issues including this. One way to check would be to see if you have the same issue with 1:1 calls, since 1:1 calls don't use the conferencing server.

@tleydxdy
Copy link

is this still relevant?

@SimonBrandner
Copy link
Contributor

No, it doesn't seem to be - we use Jitsi now and #6278 seems to cover the problem for 1:1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP P1 S-Major Severely degrades major functionality or product features, with no satisfactory workaround
Projects
None yet
Development

No branches or pull requests

5 participants