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

NoiseTorch using Pulseaudio shows unconfigured if input device is not selected #340

Open
TheDukeofErl opened this issue Jun 19, 2022 Discussed in #326 · 1 comment
Open

Comments

@TheDukeofErl
Copy link
Collaborator

Discussed in #326

Originally posted by Doug140 June 7, 2022
I have a message at the top of the NoiseTorch window that says "NoiseTorch unconfigured." Everything seems to be working normally. Is there something I still need to configure, or is this a bug?

Screenshot_20220607_061425

@melo0187
Copy link

melo0187 commented Jul 8, 2022

Experiencing the same issue, but adding an observation. Once you select the noisetorch device in an application (tested with gather.town) and actually use the device there, NoiseTorche's UI refreshes and shows the "NoiseTorch active" label.
When tabbing away from gather.town, device returns to unused and NoiseTorche's UI changes the label back to "NoiseTorch unconfigured".

Imho this is a degradation in UX.

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

2 participants