Reply To: Potential Bug? RapidEars setRapidEarsReturnNBest

Home Forums OpenEars plugins Potential Bug? RapidEars setRapidEarsReturnNBest Reply To: Potential Bug? RapidEars setRapidEarsReturnNBest

#1027875
Halle Winkler
Politepix

I investigated this for the upcoming update and I noticed the reason for it, although it would need a large refactor plus an API alteration to change, and as you mentioned, RapidEars nbest is experimental and consequently it isn’t a focus for this update. What I have done is expanded the documentation for this update to mention that nbest first should be set to FALSE (and something else weird that I discovered thanks to your report, which is that generally OEPocketsphinxController nbest should also be turned off at the same time as turning off RapidEars nbest, sheesh) and further setters such as segments should be turned on only afterwards. I appreciate the report and I’ll give some long-term consideration to how to improve this without causing too much API shifting.