Recognition lag – Politepix /forums/topic/problems-with-version-2-0/feed/ Tue, 23 Apr 2024 15:00:57 +0000 https://bbpress.org/?v=2.6.9 en-US /forums/topic/problems-with-version-2-0/#post-1023425 <![CDATA[Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023425 Thu, 11 Dec 2014 18:21:56 +0000 nrbrook I’ve upgraded to 2.0 in a new branch so I can easily switch between versions. I haven’t changed any implementation details other than those required to support the API changes. I’m having a number of problems which could all be related, they are hard to pin down. Here’s one problem I keep getting:

An utterance appears to be stuck in listening mode. Exiting stuck utterance.

Before this is logged speech recognition hangs for quite a few seconds.

]]> /forums/topic/problems-with-version-2-0/#post-1023428 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023428 Thu, 11 Dec 2014 18:36:48 +0000 Halle Winkler Slow recognitions have been reported a couple of times and both times it was due to not all the steps in the upgrade guide having been completed.

]]> /forums/topic/problems-with-version-2-0/#post-1023429 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023429 Thu, 11 Dec 2014 18:39:18 +0000 nrbrook Which steps? I have followed all the steps and apart from step 1, step 2 and step 5 the project would not compile if I had not made the changes successfully

]]> /forums/topic/problems-with-version-2-0/#post-1023430 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023430 Thu, 11 Dec 2014 18:44:57 +0000 Halle Winkler For this issue, my best guess would be that your app is still linking to the old acoustic models. As you mentioned, there are a lot of steps that won’t lead to compilation errors if you skip them, so it has to be done pretty carefully.

]]> /forums/topic/problems-with-version-2-0/#post-1023431 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023431 Thu, 11 Dec 2014 18:50:56 +0000 nrbrook I replaced them again with the versions from the archive, I’m still getting the message 25 seconds after I start listening, every time.

Step 1 and 2 are replacing the bundles and frameworks. I’ve definitely done this.

Step 5 is architectural changes. The pocketsphinx usage I have changed, I’m not generating a language model. I am using OEEventsObserver correctly.

Thanks

]]> /forums/topic/problems-with-version-2-0/#post-1023432 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023432 Thu, 11 Dec 2014 19:05:55 +0000 Halle Winkler If you can replicate it with isolated changes to the sample app I can take a look at it. There’s no known bug which does this, so without any logging info or device/version info or code to run I don’t have a way of helping out.

As I mentioned in the other thread, Rejecto is not designed to create language models for import without Rejecto running in the app, so that should be fixed in order to remove it as a potential issue, and I would be concerned about the switching branches back and forth thing since 2.0 isn’t just an API change but also changes in assets. That ought to work fine in theory, but it sounds like a source of debugging complexity right now.

I think that if I was seeing weird behavior like this, my steps would be as follows:

1. Use Rejecto as designed or use an OELanguageModelGenerator to create your LM if you aren’t using Rejecto,
2. Attempt to replicate in the sample app using the smallest-possible changes, and
3. If it doesn’t replicate, compare the two apps to see what’s different, and if it replicates, share the minimal code alterations and device and iOS version that causes it to replicate with the sample app with me.

]]> /forums/topic/problems-with-version-2-0/#post-1023444 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023444 Thu, 11 Dec 2014 19:55:02 +0000 nrbrook I have a sample App which exhibits the problem, where should I send it?

]]> /forums/topic/problems-with-version-2-0/#post-1023445 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023445 Thu, 11 Dec 2014 19:56:31 +0000 Halle Winkler Great. I only want the changed lines, not the entire app, but you can send them to the email address that you received your framework license email from.

]]> /forums/topic/problems-with-version-2-0/#post-1023446 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023446 Thu, 11 Dec 2014 19:59:45 +0000 Halle Winkler Remember to also send me your device and iOS version where this replicates, thanks!

]]> /forums/topic/problems-with-version-2-0/#post-1023485 <![CDATA[Reply To: Recognition lag]]> /forums/topic/problems-with-version-2-0/#post-1023485 Thu, 11 Dec 2014 22:38:02 +0000 Halle Winkler OK, the issues I see in your sample app version is that the vadThreshold is too low to operate (I would leave it on the current default of 2.0), which is going to create oversensitivity in combination with your lowered secondsOfSilenceToDetect, and it is using Rejecto in an unsupported way (see above, and our previous discussion). If fixing those issues doesn’t improve the slow search, it’s fine to send me a sample app version which uses Rejecto to dynamically generate your LM to demonstrate the issue.

]]>