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

Cannot disable Echo Cancellation through Audio Wizard unless explicitly ticked and unticked #6544

Open
StrangePeanut opened this issue Aug 27, 2024 · 1 comment · May be fixed by #6611
Open
Labels
bug A bug (error) in the software client good first issue Good for first-time contributors ui

Comments

@StrangePeanut
Copy link

Description

Discovered a bug whilst helping my mate set up Mumble last night.

The Echo Cancellation option in the Audio Wizard does not take effect when left unticked with the intention to disable the feature. To disable Echo Cancellation through the Audio Wizard, one needs to explicitly tick and untick the option. Enabling Echo Cancellation does work as intended.

Steps to reproduce

Reproducible on fresh and existing installs.

Scenario 1 (fresh install)

  1. Complete Audio Wizard leaving Echo Cancellation unticked
  2. Echo Cancellation is enabled

Scenario 2

  1. Complete Audio Wizard ticking and unticking Echo Cancellation
  2. Echo Cancellation is disabled

Mumble version

1.5.634

Mumble component

Client

OS

Windows

Reproducible?

Yes

Additional information

No response

Relevant log output

No response

Screenshots

No response

@StrangePeanut StrangePeanut added bug A bug (error) in the software triage This issue is waiting to be triaged by one of the project members labels Aug 27, 2024
@Hartmnt
Copy link
Member

Hartmnt commented Sep 13, 2024

Can confirm. Reproducible when having an established client configuration with echo cancellation enabled. The audio wizard will not take the active echo cancellation setting into account and show an unchecked checkbox.

Offending code is probably in here:

if (AudioInputRegistrar::qmNew) {
foreach (AudioInputRegistrar *air, *AudioInputRegistrar::qmNew) {
qcbInput->addItem(air->name);
if (air->name == AudioInputRegistrar::current) {
qcbInput->setCurrentIndex(qcbInput->count() - 1);
EchoCancelOptionID echoCancelOptionId = firstUsableEchoCancellation(air, qcbOutput->currentText());
if (echoCancelOptionId != EchoCancelOptionID::DISABLED) {
qcbEcho->setEnabled(true);
qcbEcho->setChecked(Global::get().s.echoOption != EchoCancelOptionID::DISABLED);
}
}
QList< audioDevice > ql = air->getDeviceChoices();
}
}

@Hartmnt Hartmnt added client ui good first issue Good for first-time contributors and removed triage This issue is waiting to be triaged by one of the project members labels Sep 13, 2024
Hartmnt added a commit to Hartmnt/mumble that referenced this issue Oct 15, 2024
The echo cancellation checkbox had two separate, but similar
problems:

1) It would never load in a checked state when you open up the
AudioWizard

2) It would also never load the correct checked state representing
the user settings when switching AudioInput or AudioOutput systems.

The first problem can be traced back to commit 0104375
where the state of qcbEcho depends on the selected element of the AudioOutput
dropdown menu, before it has been filled.

The second problem probably goes back to 2991d20 where the
enabled state of the qcbEcho checkbox was changed on changing audio systems, but
the checked state was not reloaded.

This commit refactors the code (swaps initializing input and output)
and adds a shared method to update the qcbEcho checkbox appropriately.

Fixes mumble-voip#6544
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug (error) in the software client good first issue Good for first-time contributors ui
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants