From Where I Left Off.
My previous senior project proposals had their complications due to lack of skill or to range of scope. This caused me to be a question my idea of creating a web based project since I don’t think I have adequate skill in the frontend web-dev to be able to create something good in the amount of time left (I know some front-end but I am not good at debugging it). Additionally, I was having trouble figuring out how to properly scope the project (since 17 SDGs is a lot).
This entire situation, thinking about senior project, graduating, and a relevant career, had me spiralling down; leading me to turn to books and movement for isnpiration and hope. It is in times like this that I forget to prioritize my owwn well-being.
Upon remembering to do so, I made a firm decision that it would be best to pursue something more me. Somethign good for my wwell-being. Something that felt like play. And so, I ended up back to where I began: Creating a physical-computing based project.
Changes
With this relatively new topic, I had to brainstorm once more. (The book Big Magic served as a good input for me in this phase; in terms of accepting failed ideas in pursuit of a better one.)
Ultimately, I ended up going with an idea that came to me during a mindless walk through the subway station steps. It is an inspired by one of my mom’s favorite movie scenes from the film “Big.”
The idea was to reverse the roles of music and movement in dance; where the movement creates the music in a manner that is consistent. This then allows the user to create music and potentially change the way they move in order to do so.
Catching up / Progress So Far
With this new idea, I knew I had a lot fo catching up to do. I began by coding the low-fidelity prototypes as proof of concept.
I initially considered force and distance as my primary factors, centering around the cocnept of footwork. Fo rthis I utilized an FSR and a ping sensor along with arduino and p5, communicating via serial port. As I was planning this out, I decided to test with 3-4 sounds and test the distance and force factors.
After meeting with professor explaining my idea and showing my new low-res prototype; I was told I oculd consider other factors like acceleration and utilizng capacitive touch. This led me to broaden my ideas for inputs like stretch sensors, mechanical switches, etc. Another suggestion was to utilize optics; which I will keep in mind, despite being hesitant about since I lack the skill and sicne it is typically heavier on software.
I did attempt to utilize the accelerometer from a Circuit Playground alongside Tone.js (which I had to re-learn a little bit because it has been a year since I last used it). Thankfully I found experimental code I had from a year ago that helped ease me into learning it again.
For this portotype, instead of force as an input, I just used the left arrow on my computer (to minimize hardware issues due to prototyped circuits – simplify for testing purposes). The idea was to change notes depending on the tild of the device. This worked really well. The code has it so that after 16 notes, it would loop. Which is an idea I could consider implementing nin my project where the user can create the music initially and the dance to it once it loops.
The next thing I did was update my timeline. I am currently in the process of updating my initial project plan; which I am realizing has a lot of similarities to my current project.
Surprises
It was a surprise to me when I read over my initial project plan again since a lot of what wwas written on there still ended up holding true; even inputs and inspirations. Its as if I had wanted to something then but didn’t know wwhat it was; and now, after some heavy iterating and jumping around, I finally do.
I wrote:
- “This project is for those looking to take a break and engage in a form of play.”
- “I want my users to experience the joy and satisfaction from hearing movement turn into sound.”
Reading these truly came as a surprise. It also helps me realize that I am on the right track. Often, consistency reveals to me what it is I want to achieve and the principles in my initial plan and current plan intersect heavily and show a good amount of consistency.
Challenges
With all code, I encountered bugs and had to troubleshoot. Some key points included:
- serial port communication (reding the values and converting as opposed to using ascii)
- delay value (how long is long enough; how to make sound stop and go)
- material (socks are not the best material for ping sensor to detect)
- 3v vs 5v devices
- Hardware issues (alligator clips touching – which I tried to insulate with tape, general wiring issues – wrong pin)