Troubleshooting

If you have an issue with NoiseTorch, you can either find logs written to standard out, or you can find a log file in /tmp/noisetorch.log

Please always attach this file when reporting a bug in NoiseTorch.

Here are a few issues users encountered and how to solve them:

Virtual Microphone is silent

The first thing you may want to check is that your Voice Activation Threshold isn't simply set to high. Drag the slider to zero, reload NoiseTorch and see if the issue persists.

If this does not solve your problem, you should take a look at your audio with pavucontrol a.k.a. "PulseAudio Volume Control", most users should have this installed by default, but you may have to install it separately.

Go to the "Input Devices" tab and speak into your microphone, and also observe the bars when talking.

Does the bar for your regular microphone move? If it does not, then it is likely an issue with your Microphone.
If the bar for your regular microphone moves, but your NoiseTorch Microphone doesn't, go to the Output Devices tab and again speak into your microphone. Do none of the volume bars on either "Null Output", or "LADSPA Plugin Noise Suppressor for Voice (Mono) on Null Output" move?

If they do move, please open an issue, if they don't try the following things:

• Make sure that you have not selected your NoiseTorch as your default microphone, e.g. via Gnome. The NoiseTorch Microphone needs to be set on individual applications and can currently not be set as the default device.

If it still doesn't work, there seems to be an issue that disproprtionally affects Manjaro Linux users, but you may still want to try it even if you don't use Manjaro.

Edit your ~/.pulse/daemon.conf configuration file, and append the folowing:

default-sample-rate = 44100

Now restart your pulseaudio by typing pulseaudio -k into a terminal. Try NoiseTorch again.