Hi Fons,
Thanks for the info regarding Ardour. Although I’m not an application developer
(nor aspire to be), I have used Python. Not too long back, I purchased some
sensors from Phidget to make a response box. I also built a few gadgets based
on the Arduino microcontroller, and Python code simplified a few of the
interfacing tasks.
I’m a proponent of ergonomic response boxes and generally design and build my
own response boxes in lieu of off-the-shelf interface devices. If the control
layout (generally push-button switches) isn’t intuitive to the user, then I
would question whether response time could be valid, at least not without a lot
of user training. (Measuring response time can be useful in many experiments).
All switches/keys should be equally accessible, and there shouldn’t be any
ambiguity as to what each switch represents. Using a standard keyboard is
generally a compromise.
Sometimes making an interface device ‘talk’ isn’t the only issue. For example,
it’s difficult to route wires through a sound test booth if it isn’t
pre-equipped with a patch bay/panel. One of my response boxes sends its signal
along a single-conductor shielded cable (terminated with a BNC connector for
ease of use). This response box used a pre-programmed microchip from a Velleman
electronics kit: The design allowed me to send 15 discrete ON/OFF channels
along the single-conductor cable which, in turn, was considerably easier to
route than a multi-pin connector or multi-conductor cable would have allowed.
Adding a patch panel or multi-conductor connector to the heavy steel walls of
an audiometric test booth isn’t easy: I’ve had to do this (for others) in the
past.
In other instances, a subject’s safety has to be insured in order to obtain IRB
approval for a study. Fiber optic communication comes in handy when grounding
or electrical isolation is a concern. The downside of fiber optics is that a
battery-operated response box (or preamplifier when electrodes are used) is
needed, but this is just a minor inconvenience. But with the aforementioned
single-conductor setup, DC power (along with the multiplexed signal) is sent
along the wire, and one need not worry about battery life.
Regardless of user-interface / hardware, talking with the computer is the next
step. Having open source software (and Arduino hardware) has certainly made
life easier for the experimenter. Once I get my Linux rig together, I’ll look
into the possibilities offered. I make no claims as to being software or
computer savvy, but I generally find a creative solution (or an adept person)
to get things rolling. I’ll let you know how things progress with my Ambisonic
setup as well as future hearing experiment(s).
Kind regards,
Eric C.
PS—Maybe I should have titled this AAAA (Adriaensen, Ardour, Arduino,
Ambisonics)?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://mail.music.vt.edu/mailman/private/sursound/attachments/20120113/6fb17e16/attachment.html>
_______________________________________________
Sursound mailing list
Sursound@music.vt.edu
https://mail.music.vt.edu/mailman/listinfo/sursound
