- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
Voice recognition is always crashing when I enable it in the same application already using hand gestures.
First, I configure the voice recognition: it recognizes my voice, it works fine. Then I call PXCMHandConfiguration.EnableAllGestures(); before starting my pipeline and voice recognition stops working.
Ex:
SpeechRecognition alert: ALERT_SPEECH_BEGIN
SpeechRecognition alert: ALERT_SPEECH_END
... call to EnableAllGestures, pipeline started
In a few seconds I get:
SpeechRecognition alert: ALERT_RECOGNITION_ABORTED
SpeechRecognition alert: ALERT_VOLUME_LOW
SpeechRecognition alert: ALERT_RECOGNITION_END
If I comment the line that enables the Gestures, everything works fine (but of course, I don't get gesture notifications anymore.
I tried creating one Session for each purpose but the problem happens as well.
Any thoughts?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Follow up:
If I start a new process from my app doing only speech recognition (while the main process is doing everything else: it works.
Also, if I dispose the PXCMSpeechSynthesis object, a next call to other module (hand or expressions, or whatever) throws an exception and the pipeline stops.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My guess is that different threads are accessing the same object. When you create a new process, you don't have to deal with thread sync, and that's why it works.
Make sure you have semaphores for mutual exclusion in critical parts of the code, or just use another process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Samontab, thanks for your comment.
That's the problem. Speech recognition deals with a complete different set of objects comparing to hand/face/eyes tracking. There's no concurrency problems there.
I tried to create another Session in a new thread and start from there without any luck.
I guess it's something to do with the sdk itself or even the hardware :(

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page