Bart Brouns

I've been wanting to update this issue for a while now, since clipster *has* turned slow for me, presumably because of my history size. Unfortunately my ssd died a few...

> I'd be interested to know at what history size the current code starts to be noticeably slower (to a human) - if that number is suitably small then I...

@sebastianst A workaround is to use clipster together with [rofi](https://davedavenport.github.io/rofi/), which has fuzzy matching: ``clipster -o -n 0 -0 | rofi -i -dmenu -sep '\x00' -eh 2 -p paste: |...

I later found out that the frequency is not constant, so you cannot notch it out.

No, I think it was 48k, but it might have been 44.1k. For sure nothing else.

I never thought CPU would matter, but here we are. I'm using a fairly recent Intel i5-10310U (8) @ 4.400GHz, if that helps.

To be clear, I agree with @gitterdude > I don't think it's audible under normal gain staging but it is there. So it's not high priority issue, imho. Just wanted...

I also think this is a very useful feature! Unfortunately, when I hit the reset button in GxTremolo.lv2, the plugin breaks: there is silence with maximum depth, and something that...

@06kellyjac Thanks! >I wouldn't mind being added as a maintainer once either of you adds to nixpkgs If you wan't I'll gladdly add you [here](https://github.com/NixOS/nixpkgs/pull/99898)!

I can answer the first question: https://github.com/rabite0/hunter/commit/67c973c0af1d35f0f832d4eb594c12868ef78008 https://github.com/thindil/hunter/commit/9768a07787d863614a10a3d38a63f5c85560dad0 So this one was a few months earlier.