suspend listen at first start – Politepix /forums/topic/suspend-listen-at-first-start/feed/ Tue, 23 Apr 2024 15:08:16 +0000 https://bbpress.org/?v=2.6.9 en-US /forums/topic/suspend-listen-at-first-start/#post-1024030 <![CDATA[suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024030 Wed, 31 Dec 2014 08:08:22 +0000 sckramer Hello,

Where is the best place to suspend listening at first start? I’ve tried various places but it’s ignored the first time (right after startListeningWithLanguageModelAtPath–) and suspending/resuming works fine after that…

Thanks!

]]> /forums/topic/suspend-listen-at-first-start/#post-1024033 <![CDATA[Reply To: suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024033 Wed, 31 Dec 2014 11:37:59 +0000 Halle Winkler Welcome,

It isn’t a good design for various reasons to suspend immediately after starting. What is the design consideration that is leading to that requirement?

]]> /forums/topic/suspend-listen-at-first-start/#post-1024035 <![CDATA[Reply To: suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024035 Wed, 31 Dec 2014 18:08:22 +0000 sckramer Ok, just checking if it’s an easy option, but agreed and I’ll rethink my design. I built it into it’s own NSObject (gui-less, using NSnotifications to talk to the current viewcontroller) so I can activate it anywhere, and in my case when I first launch the app I load it in viewDidload (with a background queue because there is a 5-7 second delay when you do the “startListening”) but then I need it suspended until the right time in my app.

So thinking about it more, I’ll load it on the first time it’s needed…

]]> /forums/topic/suspend-listen-at-first-start/#post-1024037 <![CDATA[Reply To: suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024037 Wed, 31 Dec 2014 18:19:57 +0000 Halle Winkler OK, the new 2.0 design is that OEPocketsphinxController is a singleton, so the design feature of being able to control it from anywhere is now built-in and since there is no more calibration it starts very quickly, so I’d just upgrade to 2.0 and see if the updated design solves some of these problems for you out of the box without needing to start and then suspend.

]]> /forums/topic/suspend-listen-at-first-start/#post-1024038 <![CDATA[Reply To: suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024038 Wed, 31 Dec 2014 19:15:46 +0000 sckramer Cool, did the update to 2.0–

starts in 2.8 seconds on an iPod touch, 1.5s on iPhone 5, 0.85s on iPad air2

So I’ll lazy-instantiate it on the first request for speech recognition & call it a day, thanks!

]]> /forums/topic/suspend-listen-at-first-start/#post-1024039 <![CDATA[Reply To: suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024039 Wed, 31 Dec 2014 19:18:39 +0000 Halle Winkler OK, I’m actually just seeing a .5 second startup on my test devices, so there might even be something delaying that for you which could be reduced with some troubleshooting.

]]> /forums/topic/suspend-listen-at-first-start/#post-1024042 <![CDATA[Reply To: suspend listen at first start]]> /forums/topic/suspend-listen-at-first-start/#post-1024042 Wed, 31 Dec 2014 21:48:37 +0000 sckramer I’ll check it out, Thanks!

]]>