I Figured It Out
I was able to figure out the problem, but it was pretty much an inversion of what the current Superlab help file suggests.
This is how I was able to set it up:
I wanted to have a Visual Event and a Sound Event to occur simultaneously. The context is that I want to have some events happen, and then a Visual and Sound event to which there can be participant response.
My Sound Event should last 250ms, and the Visual Event should last 5000ms.
The help file is very clear about the order in which they must be presented;
“The order is important: the sound event must come first.”
In other words, in my trial I need this:
[x] Sound Event
[x] Visual Event
And then I need the “end immediately after the event is presented” checkbox on, and the “wait for sound to finish playing” checkbox off.
But that didn’t work.
What did work was this:
[x] Visual Event(0ms)
[x] Sound Event(250ms)
[x] Visual Event(copy)(4750ms)
It is important to have the Sound Event come second. Here’s why:
For whatever reason, the Sound Event refused to allow the Visual Event to be presented concurrently; it either would wait for the Audio File to finish playing first, or the Audio File would play at strange times and skip, or other things.
Essentially, you have to maintain the same properties that the Help File describes, except switch the order of the events.
The Visual Event should “end immediately after the event is presented.” Then the Sound Event (which needs to be an Audio File type, by the way), will begin at the same time as the Visual Event–and since it isn’t a visual type of Event, it won’t clear the screen and the Visual Event will remain displayed until the Trial is over, or some other visual-type Event supplants it.
Anyway, the settings on the Sound Event should be:
[x]Stop audio: when the event ends
Input: End This Event and Move to the Next One:
[x]After any response from the participant
[x]…or a time limit.
But I’m not done. I want the Visual Event to continue past the Sound Event, but if the Sound Event doesn’t end at the same time that the Audio File does, it will extend the Audio File’s duration by looping it in a record-skipping kind of way. And I don’t want that.
So to have the Visual Event continue past the Sound Event, I just copy the Visual Event and put it after the Sound Event, which becomes the Visual Event(copy).
If I want the total of the Visuals to be 5000ms, then there’s the 250ms of the Sound Event (which preserves the Visual Event onscreen), followed by a Visual Event(copy) which lasts 4750ms, which is a total of 5000ms of the same image presented onscreen.
What if I want participant response at any stage during the Visual Event? Well, that ties into this other thread that Hong helped me so much with. I use a Feedback setting to end the event as soon as any participant response occurs, and hey, presto, I’m done.
So: essentially, the properties of the Sound Event and the Visual Event are reversed. Participant response will be coded to the Sound Event, the end of which will signal the end of the Visual Event.
Thanks for all of the help I’ve received!