-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Doesn't work when selecting "use echo cancellation“ on Windows 10 #3923
Comments
Audio card and microphone? |
Integrated audiocard on Intel Z370 in Alienware R8,the microphone is the one on AW988 |
I see they can be connected through USB. Is it just for power or audio as well? Did you try both wireless and wired mode? |
@davidebeatrici |
You're using WASAPI, right? It could be related to #1731. |
@davidebeatrici yes it looks like that,the input and output have different names,if i want to use different input output,i have to uncheck echo checkbox and select signal to noise ratio,or it won't work |
The fact that you have to select "signal to noise ratio" is a different issue though. What happens when you select "Amplitude"? You don't see any input? |
@davidebeatrici okay..yeah,no input |
Is the sound clean when using "signal to noise ratio"? |
@davidebeatrici not at all,no matter how to config,the signal is really easy to get pass the gate,generates a lot of squeal |
We recently received a patch for the echo canceller. It turned out that our implementation was buggy (see #4167 for details). Thus it might very well be that the issues you have encountered are due to that. Please let us know if the problem persists with Mumble 1.4.0 or newer (not released yet though - but you can get it if you compile the current master branch) |
Doesn't work when selecting "use echo cancellation“ on Windows 10 1803,have to uncheck the option going through audio wizard.if i check the checkbox,my voice is not going through,also 90% of the time i can only use signal to ratio,raw amplitude from input is not working also,anyone have a fix? this happens on both 1.2 and 1.3
The text was updated successfully, but these errors were encountered: