Agreed, 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 some

Agreed, 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.