I’ve been giving some thought on what to call the types of vocalizations we care about, and I figured we might as well get specific about this. I’ve settled on calling these “ideophones” in general. I’ve outlined my thought process below, and tried to write this in a way that’s accessible–though let me know if anything is unclear! At first I was toying with calling these vocalizations…

We’re implementing a UI for the Voodle! The parameters we want to manipulate are: gain smoothing device settings: pin # reverse direction (related/optional): FlexiBit-mode, RibBit mode mapping The last point is a huge issue, and Paul suggested using a MaxMSP style interface to control how certain inputs map to different parameters. For example, a user may (arbitrarily) connect nodes from input…

I see the Voodle as a vocal interface that embodies your speech. This could mean two  things: its physical behaviours translate your speech, or, its behaviours react to your speech. In the translation scenario, we can expect a meaningful mapping between speech and robot movement. For example sounds that require the tongue to be more constricted or pointy (like /k/, or /i/) could map to behaviours…

Test post please ignore

Thank-you for ignoring this post.

A music video I did for the (amazingly talented)