First long phrase missed – Politepix /forums/topic/first-long-phrase-missed/feed/ Tue, 23 Apr 2024 15:00:15 +0000 https://bbpress.org/?v=2.6.9 en-US /forums/topic/first-long-phrase-missed/#post-1022245 <![CDATA[First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022245 Fri, 15 Aug 2014 14:03:03 +0000 giebler The first long phrase I say is interrupted in the middle of the phrase.

I was running 1.65 and Rejecto 1.65, but even after updating to 1.71 (is there a new Rejecto?) I have the same problem.

I have a phrase with 15 words and it only gets about half of that. 1.71 captures more of the phrase but still misses the last half.

Once it misses one long phrase, it works fine with the same phrase after that.

Even if you say short phrases first (which it works fine with), it will still miss the first long one. After that, it works fine with long phrases.

Have you seen this before? Do I need to preallocate something or increase something so that it catches the first one? I’m at a loss trying to find a work around for this.

Thanks for your help.

]]> /forums/topic/first-long-phrase-missed/#post-1022246 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022246 Fri, 15 Aug 2014 14:12:07 +0000 Halle Winkler Greetings,

No, I haven’t seen it before, but I would generally advise against taking a phrase that long in a single recognition round since it creates so many opportunities for wrong recognition due to an intermittent noise or hesitation from the user that affects a syllable in the middle. There is no technical reason that the first long phrase wouldn’t have a sense of the silence/speech threshold unless there is something else in the app affecting audio, or the calibration isn’t long enough.

]]> /forums/topic/first-long-phrase-missed/#post-1022247 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022247 Fri, 15 Aug 2014 14:20:55 +0000 giebler It works great after the first try, and there is no pause or hesitation and no intermittent noise during the first try. I’m working in a relatively quiet environment. How would I do a longer calibration and how would that help?

I don’t have any choice with the length of the phrase – we’re asking questions and as I said, it works fine AFTER the first attempt.

Here’s a sample question:

Which doctors have the highest net switching for my product over the last thirteen weeks?

First try after starting the app always fails while I’m still speaking, and after that it works fine.

In 1.65 it would give the following message:

2014-08-14 17:07:45.144 coach[23556:a107] There is reason to suspect the VAD of being out of sync with the current background noise levels in the environment so we will recalibrate.

In 1.71 it no longer gives that message and as I said, it gets more words in 1.71 but still misses the last half.

]]> /forums/topic/first-long-phrase-missed/#post-1022248 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022248 Fri, 15 Aug 2014 14:57:54 +0000 Halle Winkler

It works great after the first try, and there is no pause or hesitation and no intermittent noise during the first try

Under real-world conditions it’s likely to create interaction stress for your users since they will hesitate and experience intermittent noise, among other challenges such as mic distance, accent, etc. Avoiding long queries via voice recognition is a suggestion I make when I give talks on the subject of speech UI, since it reduces user interaction stress.

You can check out the calibration options in PocketsphinxController’s docs and I’d also recommend setting a longer secondsOfSilence pause time along with the longer calibration.

It sounds like maybe there is something about the app setup that is leading to a poor calibration (maybe another audio object interrupting it or something weird when the listening loop starts), so that is an area you could troubleshoot to detect why the calibration results aren’t ideal.

]]> /forums/topic/first-long-phrase-missed/#post-1022252 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022252 Fri, 15 Aug 2014 18:46:06 +0000 giebler I tried all three calibration times and I even set the timeout to 1.6 seconds. Here’s the results:

2014-08-15 14:38:01.855 coach[24101:6923] Calibration has completed
2014-08-15 14:38:01.857 coach[24101:6923] Listening.
2014-08-15 14:38:11.276 coach[24101:6923] Speech detected…
INFO: file_omitted(0): Resized backpointer table to 10000 entries
INFO: file_omitted(0): Resized score stack to 200000 entries
2014-08-15 14:38:14.734 coach[24101:6923] Stopping audio unit.
2014-08-15 14:38:14.865 coach[24101:6923] Audio Output Unit stopped, cleaning up variable states.
2014-08-15 14:38:14.866 coach[24101:6923] Processing speech, please wait…
INFO: file_omitted(0): cmn_prior_update: from < 47.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 >
INFO: file_omitted(0): cmn_prior_update: to < 58.97 -2.76 -0.05 -2.55 -2.07 -2.80 -0.86 0.27 -0.82 -0.19 -0.09 0.13 -0.02 >
INFO: file_omitted(0): 8462 words recognized (24/fr)
INFO: file_omitted(0): 477916 senones evaluated (1350/fr)
INFO: file_omitted(0): 305552 channels searched (863/fr), 41300 1st, 165791 last
INFO: file_omitted(0): 23343 words for which last channels evaluated (65/fr)
INFO: file_omitted(0): 14266 candidate words for entering last phone (40/fr)
INFO: file_omitted(0): fwdtree 1.95 CPU 0.551 xRT
INFO: file_omitted(0): fwdtree 3.60 wall 1.016 xRT
INFO: file_omitted(0): Utterance vocabulary contains 145 words
INFO: file_omitted(0): 4616 words recognized (13/fr)
INFO: file_omitted(0): 337969 senones evaluated (955/fr)
INFO: file_omitted(0): 342829 channels searched (968/fr)
INFO: file_omitted(0): 22321 words searched (63/fr)
INFO: file_omitted(0): 18710 word transitions (52/fr)
INFO: file_omitted(0): fwdflat 1.27 CPU 0.358 xRT
INFO: file_omitted(0): fwdflat 1.27 wall 0.358 xRT
2014-08-15 14:38:16.145 coach[24101:6923] Pocketsphinx heard “WHICH DOCTORS HAVE A HIGHEST NET SWITCHING FOR MY PRODUCT OVER ALL” with a score of (0) and an utterance ID of 000000000.
2014-08-15 14:38:16.147 coach[24101:6923] Checking and resetting all audio session settings.
2014-08-15 14:38:16.148 coach[24101:907] _isSpeaking: 0
2014-08-15 14:38:16.149 coach[24101:6923] audioCategory is correct, we will leave it as it is.

Here’s the second try in the same debug session:

2014-08-15 14:38:16.270 coach[24101:6923] Listening.
2014-08-15 14:38:39.491 coach[24101:6923] Speech detected…
2014-08-15 14:38:45.964 coach[24101:6923] Stopping audio unit.
2014-08-15 14:38:46.094 coach[24101:6923] Audio Output Unit stopped, cleaning up variable states.
2014-08-15 14:38:46.096 coach[24101:6923] Processing speech, please wait…
INFO: file_omitted(0): cmn_prior_update: from < 59.07 -2.73 -0.26 -2.34 -2.00 -2.78 -0.94 0.16 -0.72 -0.18 0.02 0.04 -0.03 >
INFO: file_omitted(0): cmn_prior_update: to < 57.70 -2.95 -0.09 -2.21 -1.92 -2.72 -0.87 0.11 -0.72 -0.14 0.03 0.01 -0.05 >
INFO: file_omitted(0): 8648 words recognized (18/fr)
INFO: file_omitted(0): 557984 senones evaluated (1136/fr)
INFO: file_omitted(0): 315338 channels searched (642/fr), 57386 1st, 147718 last
INFO: file_omitted(0): 28447 words for which last channels evaluated (57/fr)
INFO: file_omitted(0): 14112 candidate words for entering last phone (28/fr)
INFO: file_omitted(0): fwdtree 2.27 CPU 0.463 xRT
INFO: file_omitted(0): fwdtree 6.62 wall 1.348 xRT
INFO: file_omitted(0): Utterance vocabulary contains 127 words
INFO: file_omitted(0): 3739 words recognized (8/fr)
INFO: file_omitted(0): 328839 senones evaluated (670/fr)
INFO: file_omitted(0): 276068 channels searched (562/fr)
INFO: file_omitted(0): 21483 words searched (43/fr)
INFO: file_omitted(0): 18104 word transitions (36/fr)
INFO: file_omitted(0): fwdflat 1.17 CPU 0.238 xRT
INFO: file_omitted(0): fwdflat 1.17 wall 0.238 xRT
2014-08-15 14:38:47.281 coach[24101:6923] Pocketsphinx heard “WHICH DOCTORS HAVE THE HIGHEST NET SWITCHING FOR MY PRODUCT OVER THE LAST THIRTEEN WEEKS” with a score of (0) and an utterance ID of 000000001.
2014-08-15 14:38:47.282 coach[24101:6923] Checking and resetting all audio session settings.
2014-08-15 14:38:47.284 coach[24101:6923] audioCategory is correct, we will leave it as it is.

Let me know if you see anything in this listing. As you can see, it can and does recognize the entire sentence perfectly after the first attempt.

]]> /forums/topic/first-long-phrase-missed/#post-1022253 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022253 Fri, 15 Aug 2014 18:54:52 +0000 Halle Winkler It looks like there is something else going on in the app preventing the initial calibration from working correctly, such as another audio object or something obstructing the calibration in the PocketsphinxController setup. I would focus troubleshooting on other app code.

]]> /forums/topic/first-long-phrase-missed/#post-1022254 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022254 Fri, 15 Aug 2014 18:59:13 +0000 giebler Here’s what I think is happening:

When it receives a long phrase, the average gain (AGC) is adjusting so that it starts to detect silence during the phrase. When I set the timeout to 3.6 seconds, it gives the app enough time to finish the phrase before it times out.

From the debug log, I see that AGC is set to none with a threshold of 2.

I’m using an iPad (2nd Gen) with its internal mic.

Is there a way to change the averaging detection for silence so that it doesn’t change its value over 5 seconds of speech? (Hopefully I’m saying this correctly). Just in case, let me try another way. The level it uses to determine silence is appearing to change over a few seconds of speech so that eventually the speech looks like silence. I need a slower response so that speech still looks like speech after 5 seconds.

Does that make any sense?

]]> /forums/topic/first-long-phrase-missed/#post-1022255 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022255 Fri, 15 Aug 2014 19:07:38 +0000 Halle Winkler Sorry, that isn’t the issue here; there is no AGC with the audio session on the device or used in the voice audio detection. This isn’t a normal result, so I would investigate other aspects of the app, specifically other audio objects and any timing issues with other operations at the time that calibration should be executing.

]]> /forums/topic/first-long-phrase-missed/#post-1022257 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022257 Fri, 15 Aug 2014 21:34:31 +0000 giebler Well, I disabled everything except OpenEars and it still is happening. I’m going to try it in another app to see if I can determine what is happening. I’ll let you know what I find.

]]> /forums/topic/first-long-phrase-missed/#post-1022266 <![CDATA[Reply To: First long phrase missed]]> /forums/topic/first-long-phrase-missed/#post-1022266 Sat, 16 Aug 2014 18:01:25 +0000 Halle Winkler OK, the best way to troubleshoot this kind of issue is to take either the tutorial example or the sample app, and without changing anything else about it, just add your language model generation code and test against a recording of your phrase using pathToTestFile.

That way, you will either get a better result, which suggests that it is something going on with the app (and then you can start adding in your related app features until you learn what causes the issue), or you will get the same result, which suggests that it is an edge case of some kind with the language model, and then you will have a test case replicating the issue that is simple enough to send me (something that only diverges from the sample app or tutorial example by a few lines of code) and I can take a look at it.

If you end up with such a simple example which demonstrates that it is an edge case issue with the language model, go ahead and send the example to the email address your framework license was sent from, along with the audio file for testing and the device you’re testing on and its iOS version, and I’ll check it out.

]]>