3 ms·
Attempted to train it by typing for ~2 minutes. Basically typed everything on the GitHub page and tried getting predictions. Results were disappointing. I didn
by scarlac 8y ago
Attempted to train it by typing for ~2 minutes. Basically typed everything on the GitHub page and tried getting predictions.
Results were disappointing. I didn't see any accurate predictions. Even with the default p/q program I see mostly random results.
I tested on a 15" Macbook Pro 2018 (latest version of keyboard that is softer to type of / less noisy)
- justAnotherNET 8y agowell if anyone has the resources to train NN's for evrry keyboard out there... it's government.
- deleted 8y ago[deleted]
- ggerganov 8y agoThe p/q test fails on my Macbook Pro 2013 as well. Plugging an external mechanical keyboard makes it work, so it's definitely due to the soft type of keyboard and not the mic.
- carbocation 8y agoSounds like the author has the same experience: if the keyboard is not mechanical, then this library doesn’t work: https://github.com/ggerganov/kbd-audio/issues/3 https://github.com/ggerganov/kbd-audio/issues/3
- ggerganov 8y agoCorrect. I just made a short video to demonstrate what a working setup looks/sounds like: https://www.youtube.com/watch?v=2OjzI9m7W10 https://www.youtube.com/watch?v=2OjzI9m7W10
- kalmi10 8y agoMacbooks usually have multiple mics for noise filtering. That could also be an issue.
- amelius 8y agoStill, I suspect that certain words, when quickly typed, have specific sounds.
- cbg0 8y agoI've tested this on my Filco Majestouch 2 with MX Browns but it barely managed to detect anything, and even then it didn't do very well. I think this is also highly dependent on the microphone used (I used the one in my Logitech webcam).