4 ms·
(NoiseTorch maintainer here) This is a limitation that will likely be lifted with the pipewire version. Pipewire 0.3.25 released yesterday which added some of
by lawl 6y ago
(NoiseTorch maintainer here)
This is a limitation that will likely be lifted with the pipewire version. Pipewire 0.3.25 released yesterday which added some of the things we require, still some other things missing, but it seems like things are happening.
In the meantime it is possible to configure NoiseTorch as a systemd service[0], but it's not recommended because it constantly uses CPU even if no application is actually using the microphone. Afaik PipeWire uses a pull model where it pulls data when it needs it, so it shouldn't use CPU to denoise the microphone when it's not in use.
So it is currently possible to do that, but I'm deliberately not making it easy via the UI, because I don't want to deal with complaints about NoiseTorch killing people's laptop batteries or whatever.
[0]: https://github.com/lawl/NoiseTorch/wiki/Start-automatically-with-Systemd https://github.com/lawl/NoiseTorch/wiki/Start-automatically-...
- brnt 6y agoThanks for your reply! As I use NoiseTorch, it already knows the previous configuration, which is always what I want, so the only thing i need to do is press 'load'. I risk being terribly naive, but it seems like a flag (`noisetorch --autoload` or `--loadlastconfig`) could solve this as well. Then I could just run it that way on session start. Would that be possible?
- lawl 6y agoShould be possible. If someone wants to implement that, i suggest opening an issue with an implementation proposal and then send a PR.