09.23.17 | Week 4. Blog Debrief
Leading up to the presentation, I'm already going to have my assets / main infographics established in that week's blog debrief, so for this post I was going to go over some of the more high-concept stuff I had in mind.
Long story short, the Arduino project is going to have a bank comprised of multiple bite-sized compositions that transition into one another in sort of a jazz fusion / liquid DnB style to help keep the pieces modular without making the switches sound too jarring. Things like specific composition to play and instrumentation vary based on a limited number of inputs.
I wasn't planning on using a ton of inputs to work the whole thing, instead relying on a smaller amount but using some programmatic smoke and mirrors to extrapolate certain factors: for example, a relatively consistent way to detect if the Arduino is being held by a human (as opposed to resting on a flat surface) is having a vertical velocity, detected via accelerometer. It's highly unlikely someone would be able to hold it perfectly still for an extended period of time, so that's a cheaper solution compared to something like an ultrasound sensor.
Here's a very basic rundown of what I was roughly envisioning:
- Tempo is controlled by a heartbeat sensor. If no heartbeat, it uses lateral velocity.
- In its startup state, the Arduino makes ambient whistling noises or synthesized "cries" to try and draw people in. It has to be "armed" in order to enter its dedicated improvisational mode.
- Smaller factors such as light intensity and color can be used to grade the overall theme of the piece - use of sharper and more dense-sounding waveforms in harsh colors compared to smoother sines and extended attack periods in cold light, etc.
Long story short, the Arduino project is going to have a bank comprised of multiple bite-sized compositions that transition into one another in sort of a jazz fusion / liquid DnB style to help keep the pieces modular without making the switches sound too jarring. Things like specific composition to play and instrumentation vary based on a limited number of inputs.
I wasn't planning on using a ton of inputs to work the whole thing, instead relying on a smaller amount but using some programmatic smoke and mirrors to extrapolate certain factors: for example, a relatively consistent way to detect if the Arduino is being held by a human (as opposed to resting on a flat surface) is having a vertical velocity, detected via accelerometer. It's highly unlikely someone would be able to hold it perfectly still for an extended period of time, so that's a cheaper solution compared to something like an ultrasound sensor.
Here's a very basic rundown of what I was roughly envisioning:
- Tempo is controlled by a heartbeat sensor. If no heartbeat, it uses lateral velocity.
- In its startup state, the Arduino makes ambient whistling noises or synthesized "cries" to try and draw people in. It has to be "armed" in order to enter its dedicated improvisational mode.
- Smaller factors such as light intensity and color can be used to grade the overall theme of the piece - use of sharper and more dense-sounding waveforms in harsh colors compared to smoother sines and extended attack periods in cold light, etc.
Comments
Post a Comment