46 ms·
Looks excellent and keen to delve into the code a bit. One quick question since you'll clearly know the codebase - do you think this could easily be adapted to
by g_p 6y ago
Looks excellent and keen to delve into the code a bit.
One quick question since you'll clearly know the codebase - do you think this could easily be adapted to create a "playback-side" noise filter?
Use-case rationale here is noisy and poor quality podcasts or "other people's" audio - it would be awesome to be able to configure your tool as the output for Chrome or Firefox or whatever program I'm listening to, then route the cleaned audio from your tool to the physical audio port.
Is that something which would be feasible to do here?
- lawl 6y ago> do you think this could easily be adapted to create a "playback-side" noise filter? Yes, the hardest part about this is making the UI not confusing when you now have two separate instances loaded in PulseAudio.
- g_p 6y agoAgreed, but now this has piqued my interest in a good way. Having two instances loaded might be a bit confusing as you say - I imagine it would need to be something like "NoiseTorch for Recording" and NoiseTorch for Playback. I'd need to go and play around with Pulse but I guess it would be possible to present 2 interfaces into Pulse with different names, then hope users can see the distinction when selecting a microphone versus the output device.