Hey guys,

here's our problem. We built an experiment where subjects are supposed to say several items in different emotions. For each 15 seconds they see the item and a countdown and for the whole 15s the voice is recorded with the "voicerecord"-function. The problem is: as soon as any sound is recorded with the microphone, the screen with item, countdown, etc. turns blank for the rest of the 15s. But the recording still works.

Do you know how to maintain the item-page+countdown while recording sound?

Here the page we want to last the 15s: https://www.dropbox.com/s/0mfixdya0lk141p/1.jpg

Heres the page which appears as soon as sound is recorded: https://www.dropbox.com/s/d2ypke6b8ysetvg/2.jpg

Thanks already now for your help!!

You'll have to look into specifying a different /responseinterrupt behavior. Details are available in the documentation topic for the respective attribute.

Thanks a lot for the quick help!! But only a part of our problem is solved... The video-countdown (reminder+micro) remains, but the textelements (calibration) still disappear. Here's what it looks like now (relevant parts):

<text calibration>
/ numitems = 15
/ items = calibration
/ select = sequence
/ fontstyle = ("Arial", 8%, true, false, false, false, 5, 0)
/ valign = center
/ halign = center
/ txcolor = (0, 0, 0)
/ txbgcolor = (230,230,230)
</text>

<trial calibration>
/ stimulusframes = [1=calibration, micro, reminder]
/ inputdevice = voicerecord
/ responseinterrupt = trial
/ trialduration = 15200
</trial>

<item calibration>
/1 = "           OTTO~r~rStimmlage: neutral"
/2 = "           OTTO~r~rStimmlage: hoch"
/3 = "           OTTO~r~rStimmlage: Noch höher"
/4 = "           OTTO~r~rStimmlage: tief"
/5 = "           OTTO~r~rStimmlage: Noch tiefer"
/6 = "           OTTO~r~rLautstärke: laut"
/7 = "           OTTO~r~rLautstärke: noch lauter"
/8 = "           OTTO~r~rLautstärke: leise"
/9 = "           OTTO~r~rLautstärke: noch leiser"
/10 = "           OTTO~r~rFreude"
/11 = "           OTTO~r~rTrauer"
/12 = "           OTTO~r~rÄrger"
/13 = "           OTTO~r~rÜberraschung"
/14 = "           OTTO~r~rAngst"
/15 = "           OTTO~r~rEkel"
</item>

screenshot: https://www.dropbox.com/s/aq7va43z4ji6e8y/3.jpg

You may have to set /erase=false for those elements. See the "How to Erase Stimuli" topic in the documentation for details on Inquisit's default erasing behavior and alternative approaches applicable to certain procedural requirements.

Thanks again, but I think I wasn't clear enough, sorry. The textelements are only supposed to remain on the page until the next page, because there, there is always a new textelement. With the /erase=false operation we've got the problem, that the textelements start to overlay on the second page. Any idea how to solve this?

Screenshot: https://www.dropbox.com/s/t9g3wl7ha1fpbes/4.jpg

You simply present a blank <shape> at the very beginning of every trial, which will overwrite any elements drawn to the screen by the previous trial. You can additionally specify the respective <text> element's /size and /txbgcolor attribute, to make sure that any previous instance is fully erased, i.e., the element takes up the same amount of screen estate regardless of the length / amount of text that it displays.

Yay, now it works perfectly!! Thanks for the great support!

Well, we thought everything works, but it seems like you should never celebrate before triple-checking...

Now everything
is displayed and the recording starts at the right time. But as soon as
any sound is exposed to the recording microphone, the record stops. (Before we changed anything the Item disappeared, but the recording kept up... wtf?!). But
for our task we'd need the whole 5 seconds recorded.

Sorry for annoying, but could you again help us?

<trial calibration>

/ stimulustimes = [1= blank; 2= calibration, trigger, countdown; 10000= micro, 5sec]

/ responsetime = 10000

/ inputdevice = voicerecord

/ showmousecursor = false

/ responseinterrupt = trial

/ trialduration = 15200

</trial>

Try adding another dummy stimulus to the /stimulustimes attribute at either 15000 or 15200 and setting /responseinterrupt to frames.