Welcome Guest, you are in: <root>Elements • Login

Page History: Auditory Stimuli

Compare Page Revisions

10 9 8 7 6 5 4 3 2 1 0 Current 10 9 8 7 6 5 4 3 2 1 0

« Older Revision - Back to Page History - Newer Revision »

Page Revision: 2012/05/22 09:44

EventIDE provide multiple approaches for presenting auditory stimuli depending on used audio format and required timing accuracy.

Table of Contents [Hide/Show] Selecting element for delivering auditory stimuli    Wave Player Element

Selecting element for delivering auditory stimuli ¶

There are four elements in EventIDE that can deliver audio in experiments.

Wave Player Element¶

• Wave Player is a default element for delivering audio stimuli stored in the raw Wave format. The element is simple to use and it can used to make a stimulus set. The element is recommended as a standard choice because it provide the best time accuracy and fidelity of audio playback. The element supports a choice of multiple sound cards allows to select the sound playback API among four different sound playback APIs available in Windows system.
  

• Wave Player is similar to Wave Player element but it design to work only with Direct Sound API. In exchange, the element allows more advanced control of settings of the sound hardware. The element can be recommended in Windows XP systems with old-fashion sound cards.
  

but allows more advanced control. a default element for delivering audio stimuli stored in the raw Wave format. The element is simple to use and it can used to make a stimulus set. The element is recommended as a standard choice because it provide the best time accuracy and fidelity of audio playback.

All audio elements in EventIDE can be used in parallel, including multiple instances of the same type.

can be adopted to , can

You can use this element to deliver rich auditory stimuli in experimental scenarios where accurate timing is important and a playback process need to be controlled. For simplest sound tones you can get even better good temporal precision if you use the Beeper element. Alternatively, in scenarios where temporal precision is not necessary, for example: for a post-stimulus voice feedback, you can use the Audio Player element that supports the widest range of sound formats.

You can use this element to deliver rich auditory stimuli in experimental scenarios where very accurate timing is important. For the comparable temporal accuracy but better control on a playback process, use DirectSound element. For simplest sound tones you can get even better temporal precision if you use the Beeper element. Alternatively, in scenarios where temporal precision is not necessary, for example for a post-stimulus voice feedback, you can use the Audio Player element that supports the widest range of sound formats.

The ASIO element has few properties for tuning of the sound hardware (other settings are typically available via ASIO driver software). By element, the clip mixing can be switched on and off, and, with monitoring turn on, a basic playback statistics can be measured, like a real startup latency and actual playback duration at runtime. These settings affect the playback performance and, it's always a good idea to test the real playback empirically, with the current hardware, drivers and audio clips.

The element can be used even with sound hardware that does not support ASIO protocol directly. For this purpose you can download and install one of the WDM to ASIO drivers, available for Windows (e.g. ASIO4ALL driver). However, in this case, the temporal accuracy of playback is normally quite poor.