With the new v0.2 I noticed a regression in the filtering of keyboard strokes from mechanical keyboards. rnnoise now fails to filter agressive, loud typing noises. I've since downgraded to 1cbdbcf1, which fixes the issue.
Any idea what could cause this?
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
It could be about the training data, which was recently changed to exclude all non-free data. Could you give some other versions a try, e.g.
e10a669e8e5d480659178707
and see if they work better? In all cases, make sure you re-run autogen.sh to ensure the corresponding model gets downloaded.
Couldn't test them live - I'm using rnnoise with easyeffects, and it fails with undefined reference to 'rnnoise_model_free'.
Instead, I recorded a sample file (https://fb.hash.works/zYRJrEMk/) and tested it with rnnoise_demo. Besides speech, it contains two tests on a mechanical keyboard (MX Brown keys):
Test 1: Normal typing
Test 2: Aggressively hitting a single key
I converted the files to and from PCM using ffmpeg:
As you can see some commits you mentioned are a bit better than v0.2. In test 1, 59178707 even wins over the old 1cbdbcf1. But in test 2 the old version still excels.
Just pushed some augmentation improvements as well as new models. That seems to fix the test clip you have and improve things overall. Let me know how things go. If you have any other useful test clips, I'm also interested.
I've tested the exp_fgnoise2 branch for a week now, it seems to fix the problems I had. Thanks! Feel free to close the issue once you merge and draft a new release.