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

Issues with audio input "Roboting" on Ubuntu 21.10 #78

Open
Binzy-Boi opened this issue Jan 4, 2022 · 3 comments
Open

Issues with audio input "Roboting" on Ubuntu 21.10 #78

Binzy-Boi opened this issue Jan 4, 2022 · 3 comments

Comments

@Binzy-Boi
Copy link

I've been using Cadmus on Discord for a while now. While it works great overall, every now and again my friends in calls will tell me that my voice is "Roboting".

While I don't know what initially causes it, I've determined the issue lies within cadmus. I've unplugged and re-plugged my mic, left and rejoined the call, restarted Discord and checked my internet connection, but the issue only stops when I disable my noise suppression.

I am on Kubuntu 21.10, and my microphone is a Blue Snowball if that at all helps.

@Sirenwa
Copy link

Sirenwa commented Apr 20, 2022

I've been having these problems to. Whilst teaching sometimes students will inform me that my voice has gone robot. Turning cadmus on and off doesn't fix it generally, but restarting the computer and then opening Cadmus fixes it always.

@Foxite
Copy link

Foxite commented May 19, 2022

I was having this exact problem with Noisetorch while using PulseAudio, but it has not happened since I switched to PipeWire. This leads me to believe this is definitely caused by a bug in PulseAudio. Although I don't feel confident that I can file a meaningful bug report to PA, and the author of NoiseTorch was likewise out of his depth there.

@Sirenwa @Binzy-Boi are you using Arch Linux? It may also be a problem with the distro packages of PA.

Here's the issue on the NoiseTorch repository, it may be useful in pinpointing where exactly this problem comes from: https://github.com/lawl/NoiseTorch/issues/182

@Foxite
Copy link

Foxite commented May 19, 2022

Alternative theory: this is a bug in Discord's interaction with PulseAudio, good luck convincing Discord to fix that though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants