Configurable automatic gain control

[ara4n]

We seem to be using WebRTC's defaults for AGC - we should probably either force it on via audioConstraints (https://developer.mozilla.org/en-US/docs/Web/API/MediaTrackConstraints/autoGainControl) and/or make it configurable.

[foxlet]

A checkbox to disable AGC would be particularly beneficial for podcast or production use, where mic gain is already carefully controlled and fluctuations would be detrimental.

[bblacher]

Also, the checkbox within Element Desktop that should disable AGC doesn't do anything when using Element Call in Element Desktop.
element-hq/element-web#24355

[natanox]

For anyone who also can't use the call feature due to this unsolved issue (or with participants who regularly complain about their ears falling off), this is the workaround we're currently using:

Find out the correct number for your source with wpctl status. Then, when connecting to a call, execute while sleep 0.01; do wpctl set-volume 54 .25; done in a terminal (replace 54 with your source and .25 with the target volume, on a scale from 0.01 to 1.00). This will set the correct volume every 10 milliseconds.

[perru]

For anyone who also can't use the call feature due to this unsolved issue (or with participants who regularly complain about their ears falling off), this is the workaround we're currently using:

Find out the correct number for your source with wpctl status. Then, when connecting to a call, execute while sleep 0.01; do wpctl set-volume 54 .25; done in a terminal (replace 54 with your source and .25 with the target volume, on a scale from 0.01 to 1.00). This will set the correct volume every 10 milliseconds.

Well, it works but what an ugly workaround...

Me and all my contacts have this bug and nobody wanna use Element cause of it. Same on Linux and Windows.

[Ceiridge]

For anyone who also can't use the call feature due to this unsolved issue (or with participants who regularly complain about their ears falling off), this is the workaround we're currently using:

Find out the correct number for your source with wpctl status. Then, when connecting to a call, execute while sleep 0.01; do wpctl set-volume 54 .25; done in a terminal (replace 54 with your source and .25 with the target volume, on a scale from 0.01 to 1.00). This will set the correct volume every 10 milliseconds.

This probably also causes it to change all the time, meaning for some milliseconds, you are quieter/louder than you should be, which will sound very unprofessional

[bblacher]

This is just fixing an issue that shouldn't be there in the first place with a very sloppy workaround. I can't imagine that telling livekit not to do agc would be that hard.

[ParzivalWolfram]

Any fix yet? This causes a friend of mine to be unable to play any other audio without muting his microphone entirely, or it immediately adjusts his gain to ridiculous levels to pick up the audio (and blows everyone else's ears out if he speaks after that.)

[Ceiridge]

@ParzivalWolfram

Any fix yet? This causes a friend of mine to be unable to play any other audio without muting his microphone entirely, or it immediately adjusts his gain to ridiculous levels to pick up the audio (and blows everyone else's ears out if he speaks after that.)

You can open the devtools in Element (Ctrl+Shift+I), use the element selector (Ctrl+Shift+C) to select an element inside the call iframe (important!!!) so that the javascript scope is inside the iframe, then run the Anti AGC JavaScript linked below and finally mute, unmute and temporarily select another microphone, then go back to the microphone you want to use. AGC is now disabled for this call.

Anti AGC: https://github.com/joeywatts/disable-autogain-control-extension/blob/master/disableAutogain.js

[ParzivalWolfram]

That is far too much to explain to affected users, who will not not know what JavaScript is, or that Electron apps run in a browser. It was already a huge pain in the ass to get my group's affected user onto anything other than Discord at all.

…

On January 10, 2025 7:51:27 AM CST, Philipp Paul G ***@***.***> wrote: @ParzivalWolfram > Any fix yet? This causes a friend of mine to be unable to play any other audio without muting his microphone entirely, or it immediately adjusts his gain to ridiculous levels to pick up the audio (and blows everyone else's ears out if he speaks after that.) You can open the devtools in Element (Ctrl+Shift+I), use the element selector to select an element inside the call iframe (important!!!) so that the javascript scope is inside the iframe, then run the Anti AGC JavaScript linked below and finally mute, unmute and temporarily select another microphone, then go back to the microphone you want to use. AGC is now disabled for this call. Anti AGC: https://github.com/joeywatts/disable-autogain-control-extension/blob/master/disableAutogain.js -- Reply to this email directly or view it on GitHub: #248 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[Destinyg133]

This is just fixing an issue that shouldn't be there in the first place with a very sloppy workaround. I can't imagine that telling livekit not to do agc would be that hard.

Agree, this should be more in focus to fix AGC and to make it configurable