Sadly the CPU load and maintaining the setup with ever changing OSes has been too much. Though I do still maintain easier keyboard shortcuts almost religiously. AutoHotKey and Karabinder FTW.
Perhaps dedicated voice hardware can help.
What sort of CPU load are you seeing? I'm able to dictate on battery, peaks averaging ~20% cpu. (Dragon is a different beast, peaking to >80% anytime it's over the noise threshold, so you need a really good mic to get good battery life).
Script here: https://github.com/talonvoice/examples/blob/master/vlc.py
Alternate minimal script:
from talon.voice import Context, Key
ctx = Context('vlc', bundle='org.videolan.vlc')
ctx.keymap({'video (pause | play)': Key('space')})But I wonder if we'd be better off enabling voice input sooner, before we're in serious trouble, and using it sporadically. Mixing voice and keyboard input at need looks like a way to substantially reduce typing while still using a keyboard whenever voice work is too inconvenient.
On the other hand, it's really not much slower with the state of the art, especially when you mix in stuff like eye tracking at a really core level (we're playing stuff like autocompleting based on a symbol you just looked at!). I'm not far enough along with Talon to be pushing the benchmarking side of things heavily yet, but one early test was about 2/3 the code input performance of a 90wpm typist on the same code, with a lot of obvious places to improve. I think good application of continuous recognition, resumable grammars, and really context-specific helper code can push specific workloads way past what a keyboard/mouse can do (which calls back to the goal of impressing people who aren't injured yet).
Then there's the professional app space - e.g. Photoshop, CADD, and video/audio production tools could really benefit from voice workflows (imagine using a pen tablet augmented with voice + eye tracking instead of complex UI).
For more detail, I was sleeping in two wrist braces every night and doing stretches and strength exercises for an hour or more a day before the diet changes. Now I don't need any exercises or braces.
When I regress for a day or two it comes back, but not as bad.
Why did you omit wheat? Was it in direct response to RSI?
There is also this: https://news.ycombinator.com/item?id=17109010
I'd probably start by asking for audio samples of you saying a couple of sentences and commands in english
Then I'd try them locally against a couple of speech recognition engines
Then talk about potential issues and ways to influence recognition accuracy
Then I can help you try out Talon for both dictation and command input
As an anecdote, I've heard from some of my non-english-native users that they need to avoid certain word sounds in commands (by changing the command trigger words) because their accent doesn't emphasize them enough for good accuracy.
Anyway, on Github I’ve collected several dozen articles and created a table of things people have tried.
https://github.com/melling/ErgonomicNotes
My personal feeling is that if programmers embraced voice input, simply not having to type when issues arise would help. Of course, most programmers will rant about how keyboards are so much more efficient, which they might be until you can’t use one.
Here’s the current state of voice programming:
https://github.com/melling/ErgonomicNotes/blob/master/progra...