Forum Replies Created
July 14, 2016 at 3:14 pm in reply to: note: Module debugging should be disabled when shipping static libraries. #1030686
indeed, downloading and reimporting the latest Openears fixed the warnings.
Huh, I always figured the ‘static’ in static library means those things can’t be changed. TIL.July 10, 2016 at 10:51 pm in reply to: note: Module debugging should be disabled when shipping static libraries. #1030669
“using a beta Xcode” – definite no, I have it installed but in order to provision for external beta-testers I need to use the non-beta one.
” some point recompiled the framework” Not that I am aware of. I did open the project that OpenEars is in in Xcode-Beta, but I didn’t see any changes checked in git.May 10, 2016 at 10:50 pm in reply to: Error when using AcousticModelGerman #1030303
Thanks for those tips.
I noticed that ‘Bottom’ is much better recognized then ‘Top’ in english, makes sense if one-syllible words are hard.
Otherwise the cardinal directions would really suffice, both in german and english. “top”/”left”/”bottom”/”right” are easy to explain, maybe I can try something like ‘above’.
Will try that later this week and let you know what happens :)May 10, 2016 at 10:41 pm in reply to: Error when using AcousticModelGerman #1030300
Without rejecto the german works ok too for vadThreshold = 1.8, as long as one keeps absolutely quiet otherwise.May 10, 2016 at 10:37 pm in reply to: Error when using AcousticModelGerman #1030299
Oh yeah, turning off rejecto did the trick, now with english and vadThreshold = 2.5 it works pretty well.May 10, 2016 at 10:35 pm in reply to: Error when using AcousticModelGerman #1030298
I tried getting english first, so I first played around with the english vadThreshold value.
Either it picks up on any noise like mouseclick or my breathing (under vadT <2.5) or when I am above 2.5 it starts to miss the majority of the ‘left’ commands.May 10, 2016 at 10:30 pm in reply to: Error when using AcousticModelGerman #1030296
PS: I am also using the rejecto demo already.May 10, 2016 at 10:29 pm in reply to: Error when using AcousticModelGerman #1030295
So, I did find the vadThreshold now, setting it like:
[[OEPocketsphinxController sharedInstance] setVadThreshold:2.9];
I guess ‘read the documentation’ would have helped ;)
This does fix the clicking/breathing problem, but now ‘LEFT’ isn’t often recognized anymore, ‘top’/’bottom’/’right’ still seem ok.May 10, 2016 at 10:07 pm in reply to: Error when using AcousticModelGerman #1030292
Thank you for your help :)
I did indeed miss that the model, when it’s used again lower in the file.
Maybe you could set it as a variable in the example code, so it’s clearer we use it multiple times?
Now that german&english recognition is working, it kind of recognizes sound all the time, even very low volume sounds like breathing or a car driving by moves it into recognition mode.
I assume my use-case will be rather quiet places with users speaking in normal voice, is there some way I can increase the volume threshhold that starts the recognition?
Even with Rejecto (which I’d be happy to buy) it often doesn’t detect when I say something, since it’s still in the middle of recognizing the ‘mouse-click’ that happened 0.5s before.
In the languages section you also mention a ‘vadThreshold’ value, but when I search for this in the project nothing comes up.
Thank you for providing such interesting software, when in absolutely quiet space (me sitting still & not breathing loudly) the english recognition already works 9/10 times.
Using ‘german’ and only the words ‘open’/’unten’/’links’/’rechts’ It fails to detect 50% of the ‘links’ and often confuses ‘oben’ and ‘unten’. Maybe the language model is not as good?