Millisecond Forums » Millisecond Forums » Inquisit 3 » Voicerecord issue

RE: Voicerecord issue

seandr — Fri, 05 Apr 2013 10:37:46 GMT

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

RE: Voicerecord issue

pspowell — Thu, 04 Apr 2013 13:21:52 GMT

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

RE: Voicerecord issue

jkrompi — Wed, 28 Oct 2009 13:09:47 GMT

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.

RE: Voicerecord issue

jkrompi — Wed, 28 Oct 2009 13:08:53 GMT

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:

/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.

RE: Voicerecord issue

Dave — Wed, 09 Sep 2009 16:00:27 GMT

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?

RE: Voicerecord issue

seandr — Wed, 09 Sep 2009 15:51:43 GMT

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

RE: Voicerecord issue

seandr — Wed, 09 Sep 2009 09:49:47 GMT

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

-Sean

RE: Voicerecord issue

Dave — Fri, 04 Sep 2009 03:32:25 GMT

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

RE: Voicerecord issue

jkrompi — Mon, 31 Aug 2009 10:37:56 GMT

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.

RE: Voicerecord issue

seandr — Thu, 27 Aug 2009 09:25:48 GMT

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

RE: Voicerecord issue

jkrompi — Wed, 26 Aug 2009 19:48:40 GMT

Thanks for the quick reply. We do already have the speech recognition engine installed, so, unfortunately, that is not the solution. Any other help is much appreciated.

RE: Voicerecord issue

Dave — Wed, 26 Aug 2009 14:30:39 GMT

It's just a hunch, but I think the voicerecord feature needs the speech recognition engine installed -- even if voicerecord doesn't actually do any recognition. So, try and install the engine if you haven't already. It can be downloaded from here: http://www.millisecond.com/download/speech.aspx.

Hope this helps,

~Dave

Voicerecord issue

jkrompi — Wed, 26 Aug 2009 12:39:19 GMT

Hi there

I am running a simple verb generation task. I woudl like to use the "voicerecord" feature in Inquisit to record each verbal response to a simple list of serially-presented word stimuli. However, when attempt to set my input device as "voicerecord," my program will freeze as soon as it attempts to present a stimulus that requires a verbal response (I need to Ctrl-Alt-Del out of the program at this point). No .wav files are created. I have posted the script below (ignore the instructions, I am simply trying to get responses to three stimuli per block at this point). Any help would be much appreciated.

Jason

/font = ("Courier New", -43, 700, 0, 49)

/inputdevice=voicerecord

/screencolor=(0, 0, 0)

</defaults>

<data>

/ file="C:\Program Files\Millisecond Software\Inquisit 3\StroopS08\Individual\stroopsubXXXX.dat"

</data>

/ port = lpt1

/ subport = data

/ items = ("00000100")

</port>

/ port = lpt1

/ subport = data

/ items = ("00000000")

</port>

<expt>

/preinstructions = (demo)

/blocks = [1=practice; 2=practice2]

/postinstructions = (end)

</expt>

/preinstructions=(stroop)

/trials=[1=ready; 2-4=repeat]

/blockfeedback=(latency)

</block>

/preinstructions=(stroop)

/trials=[1=ready; 2-4=verbgen]

/blockfeedback=(latency)

</block>

/stimulustimes = [0=fix; 1000=repeatthis; 1150=fix;]

/trialduration = 3500

/responsetime = 500

</trial>

/stimulustimes = [0=fix; 1000=generatethis; 1150=fix;]

/trialduration = 3500

/responsetime = 500

</trial>

Specific characteristics for color naming trials, no "valid response" option here for some reason

/stimulustimes = [0=ready]

/correctresponse = (anyresponse)

/inputdevice = keyboard

</trial>

*******************

/items = repeat

/select=noreplace

/txcolor=(255,255,255)

/txbgcolor = (0,0,0)

</text>

/items = generate

/select=noreplace

/txcolor=(255,255,255 )

/txbgcolor = (0,0,0)

</text>

/1="apple"

/2="car"

/3="movie"

</item>

/1="apple"

/2="car"

/3="movie"

</item>

/items=("+")

/txcolor = (255,255,255)

/txbgcolor = (0,0,0)

</text>

/items=(" ")

/txcolor = (255,255,255)

/txbgcolor = (0,0,0)

</text>

/items=("Press the space bar when you are ready to start")

/color = (100,100,100)

/txbgcolor = (transparent)

/area = (400 200)

</text>

/items=(" ! ")

/color = (255,0,0)

</text>

/nextkey=(" ")

/nextlabel = "Space Bar"

/font = ("Arial", -23, 400, 0, 34)

</instruct>

^^^^^

Welcome to the Cognition and

Emotion Laboratory

</page>

^^^^

^^ On each of the following trials, the name of a color will be displayed.

^^ Your task is to say aloud the color in which the name is printed.

^^ Please do so as quickly and as accurately as you can.

^^ Press the Space Bar to begin the practice.

</page>

^^^^^^

The experiment is now concluded. Thanks for your participation!

</page>