NoiseTorch unconfigured?

[Doug140]

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?

[AXDOOMER]

It's an issue since 102d6fd and/or f2d726a.

Even though you may be using your device (in Discord or elsewhere), if it's not selected in Pulse Audio, it shows unconfigured.

[TheDukeofErl]

Interesting. I don't have this issue with pipewire and don't have any systems running pulseaudio so I'm not surprised I missed it during testing. I'd best that it's this if specifically: https://github.com/noisetorch/NoiseTorch/blob/master/ui.go#L85.

Pulseaudio must be handling things differently under the hood compares to pipewire and a different method of detecting if the state is unconfigured may be necessary on both. I suppose that's not super surprising but it is a bit disappointing in this case.

I'll have to spin up a VM or something to take a look. Hopefully Ubuntu 22.04 (or something else that doesn't require much configuration on my end) still uses pulseaudio out of the box.

[AXDOOMER]

I run Ubuntu 22.04 LTS

[RiemaruKarurosu]

In case this help, replicated issue, it seems it's only with pulseaudio

m

[TheDukeofErl]

Thanks for confirming. Hopefully I'll have some time on my end to spin up a VM to work out a solution soon.

[Doug140]

It shows unconfigured even when I have the NoiseTorch mic. selected in PulesAudio.

[Doug140]

In case it helps, here's my system information. Feren OS is based on Ubuntu.

[TheDukeofErl]

Created #340 to track this issue. Going to go ahead and lock this, if anyone would like to add anything else feel free to do so over there!