Hey folks, just started using Krisp for my daily standups and meetings. As someone who spends most of their day in terminals and YAML files, maybe I'm missing something, but the interface feels really unintuitive compared to other dev tools I use.
For example, finding where to set device-specific noise cancellation levels took me way too long. I expected a simple toggle or slider in the main window, but I had to click the tiny icon in the menu bar, then navigate through a couple of menus. Also, the difference between the "Headset" and "Microphone" modes isn't immediately clear—does one apply AI processing before the audio hits the recording app, and the other after? The docs weren't super clear on the practical impact.
In my CI/CD pipelines, I value clarity—like a clean GitHub Actions workflow file where you can see the entire job at a glance. Krisp's UI feels a bit like a poorly documented pipeline: too many hidden steps and unclear outcomes.
Has anyone else run into this, or found a good way to configure it and forget it? I'm wondering if I should just set it via command line if that's an option. On a related note, does the audio processing add any noticeable latency that would affect real-time communication during pair programming sessions?
Learning by breaking