Problems with Voice Recognition samples

[Robert_Oschler]

Whenever I run the voice recognition samples, C++ or C#, the status window says:

Start Recognition
Recognition Started
RECOGNITION_ABORTED
RECOGNITION_END

It doesn't work for me.  All the other samples do work (hand tracking, blob/contour viewer, hand tracking etc.  What can I try to do to fix this?  I have no other microphones or cameras attached to the system at all.  Just the RealSense camera.

Robert.

[samontab]

Try the demo with another camera. It only uses a regular microphone. Maybe the microphone drivers for the RealSense camera are not correctly installed.

[Robert_Oschler]

@samontab -

"Maybe the microphone drivers for the RealSense camera are not correctly installed."

I hope not.  That will kill my contest entry. 

[Robert_Oschler]

Bumping this.

Any response Colleen or David?

Robert

[Colleen_C_Intel]

We need you to check either In device Manager under Audio Inputs and Outputs for "Microphone Array (Creative VF0800)

or in Control Panel > Sound > Recording Tab and making sure the Creative Mic Array shows there. Assuming it shows either place, check the properties General Tab to make sure it shows device working properly.

You may need to load the audio drivers from Creative.

[Robert_Oschler]

Thanks Colleen.  If it does turn out to be audio drivers, can we rely on the contest judges to have the proper audio drivers for the RealSense camera?  Or is that something we need to figure out how to do with our installer?

Robert

[Colleen_C_Intel]

The audio drivers should be preloaded so not something you need to put in the installer. 

[Rupam_D_]

Hi Robert. User System.Threading.Thread.Sleep(5); in Voice recognition. Should fix the problem,.

I actually used semaphores. Either way, Voice continues gets the stream, eating up too much CPU in C#. You got to restrict the call so that other resources have sufficient CPU to work with.

[Robert_Oschler]

Hey Rupam!

I remember you from last year's contest.  Thanks for the tip.  I'll give it a try.

Robert.

[Robert_Oschler]

Hello Colleen,

"We need you to check either In device Manager under Audio Inputs and Outputs for "Microphone Array (Creative VF0800)

or in Control Panel > Sound > Recording Tab and making sure the Creative Mic Array shows there. Assuming it shows either place, check the properties General Tab to make sure it shows device working properly."

It looks like I have a real problem because the VF0800 shows up properly in both places.  However, it does not seem to be receiving audio input because on the Recording Tab of the Sound devices dialog, it does not respond to any sounds I make.  That is, the vertical "LED" meter next to it does not show any activity no matter how much noise I make.  Despite this the video works fine including the depth camera since I tested it with the User Segmentation sample.

Any suggestions?

Thanks,

Robert

[Colleen_C_Intel]

Did it show as working properly?  What version of the audio driver was loaded?

[Robert_Oschler]

Yes it said "This device is working properly".  I also had it check for a new driver (Update Driver) and it said I already had the latest.  Driver details:

Microphone Array (Creative 3D Gesture Camera VF0800)

Provider: Microsoft

Version: 6.3.9600.16384

Thanks,

Robert

[Colleen_C_Intel]

Do you have any other microphone you can try?  There's nothing special in the RealSense cam mic that you couldn't do with another mic. (for now)....Also did you try the driver set available at 
http://support.creative.com/downloads/download.aspx?nDownloadId=13324

[Robert_Oschler]

I found the problem Colleen.  After hours of chasing down drivers and upgrading everything in sight, only to find out it didn't help at all, I started tinkering.  There are two checkboxes on this dialog page and tab:

Control Panel -> Sound -> Manage Audio Input Devices -> Recording -> (select V0F000) -> Properties -> Advanced

The checkboxes are:

Allow applications to take exclusive control of this device
Enable audio enhancements

They are checked by default.  I unchecked both of them and the microphone came to life.  The only thing I can figure is that some other app or background process was grabbing exclusive control of the mic.

Thanks,
Robert