Millisecond Forums

Hi all,

It sounds like Inquisit maybe reacting to ambient noise from the microphone. To fix this, try setting the /voicekeythreshold on the <defaults> element. Increasingly higher threshold values configure the voice engine to react to increasingly louder sounds, ignoring sounds at volumes below threshold. 

Here's the documentation on /voicekeythreshold:
http://www.millisecond.com/support/docs/v4/html/language/attributes/voicekeythreshold.htm

Let me know if this helps.

-Sean

Hi,

Have you figured out a solution to this problem?  I am having a similar issue with the voicerecord attribute (i.e., super fast RTs that don't make sense).

Thanks

A quick add-on: my total trial time is 3000 ms (I omitted that part of the script), so it isn't a question of the trial ending immediately after the responsecue.

OK, so I upgraded to the latest version of Inquisit. Now, my responses are being recorded to the disk, which is great. However, I have a new problem. When I enable the inputdevice as "voicerecord", the to-be-responded-to stimulus is extinguished far too quickly from the display and reaction times are not collected (specifically, they are labeled something super-quick, like 4 or 5 ms). My script looks like this:

<trial verbgen>

/stimulustimes =
[0=fix; 1000=stimulus; 1150=responsecue;]

/responsetime = 1150

/inputdevice = voicerecord

</trial>

In the above case, I want subjects reponding to the "responsecue." However, as stated above, this cue disappears almost immediately and RTs are not recorded accurately. If I move "responsetime" to coincide with the stimulus presentation, the same thing happens to the stimulus (extinguished immediately, no RT recorded).

Any thoughts would be much appreciated.

I've had these problems with the August 20 build of 3.0.4.0. Voicerecord was working okay for me in 3.0.3.2 (minus the issues that led to the major revisions you mentioned). Anything more I can do to help tracking down the issue?

I just ran your script without any hangs or other problems. That means one of two things is causing this problem:

1) You're running an older version of Inquisit. (There was a fairly major update to voicerecord in 3.0.4.0 beta that was uploaded in August.)
2) The voicerecord feature is getting tripped up on certain machine configurations.

Number 1 should be easy enough to check. Make sure you have the latest release of 3.0.4.0. You can check this by selecting the About Inquisit command from the Help menu. You should see the following:

Version:        3.0.4.0
Build Date:   Aug 20, 2009
Build Time:  13:50:20

Let me know if this fixes the problem.

-Sean

Ok, thanks for the report. Sounds like we have a bug here. I'll investigate and report back as soon as possible.

-Sean

Just wanted to add that just yesterday I encountered the same problem as described by Jason. So there's definitely something wrong with 'voicerecord' as it stands. I hope this will be fixed soon.

~Dave

Thanks for the reply. Unfortunately, I get the same error when running the sample task - the program hangs when it encounters the portion of the script calling for voice record. In this case, when the first stimulus appeared on the screen ("red" in blue writing). I am unable to Ctrl-Q out of it, and must Ctrl-Alt-Delete and quit the program.

My microphone and speech recognition software are working correctly - verified using a different Inquisit  Stroop experiment I programmed using the voice recognition function.

Any other ideas? Again, thanks for your help.

Hi there,

Here are a few things to help troubleshoot:

1) First, make sure your microphone is connected and working properly. You can do this by selecting Tools->Speech Recognition->Microphone Wizard and running through the wizard.

2) Try running the Stroop Task sample that uses voice recording. You download the sample here: http://www.millisecond.com/download/samples/v3/Stroop/default.aspx

3) If the program still hangs, try pressing "Ctrl+Q" to stop it.

Let me know how these turn out.

-Sean