Hacker News new | ask | show | jobs
by distantsounds 1986 days ago
I love these solutions but none are as easy as "install an app and click a button to turn on." RTX Voice has that locked down. I'd use RNNoise instead if there was a standalone app that just "worked" on my mic input. But here I have to jump through hoops for it to work.
1 comments
lawl 1986 days ago
Can you elaborate on what hoops exactly you have to jump through? (genuinely curious, i wrote noisetorch and always looking to improve it)
link
Dumbdo 1986 days ago
Not the OP, but I'd say noisetorch already works pretty good for that use case. Especially with the recent additions of pre-selecting the last device and stuff like that, I really appreciate those minor QOL improvements.

If I compare it to how RTX voice works, it's _slightly_ more complicated to setup (currently no distribution through standard package managers/simply downloading a file and clicking it to start everything) and it doesn't autostart like RTX voice does on windows startup. But jugding from your issues [0] I understand the decision and I'll set it up manually.

It might be an idea to allow for autostart for users who don't care about the CPU impact because their CPUs are big enough or whatever.

Nevertheless, your solution is actually very close to what OP is describing: "install an app and click a button to turn on". So thanks for maintaining, I use it daily!

[0] https://github.com/lawl/NoiseTorch/issues/6

link
design-material 1983 days ago
Compared to something like Krisp (since there's no RTXV on macOS) it was difficult because step one was to compile it.

Assuming the rest of the UX journey is similar (i.e. technically-oriented) compared to Krisp's menubar click-to-activate-mic UX it then becomes less approachable

On a tangent - nice work! That people are even comparing it to RTX Voice is impressive!

link