Code nuiance.

My code was buggy, laggy, and messy. I was able to reduce lag by passing in only necessary info. Additinally, I had to modify the code and re-assess the data read by the sensorts to figure out how to make the sounds it produces a bit more consistent and precises. This boiled down to finding the bugs or errors on my part. (A lot of time was taken only to realize that I was missing an absolute value function – and other such details).

I will clean my code further as I move forward. I am tempted to test out how much more I can change about the sound if I have time, but higher up on the proiority list of my to-do’s for this week is to place the buttons that will allow the user to switch between modes (different notes being played).

Power

For power, I was able to find resources online stating that the nano can be powered via a 9v battery. Since it has a nice small footprint, I believe it will be my best bet. I will be soldering this by Monday/Tuesday.

Visual

I also coded Visuals to go along with the sound so the interface isn’t too boring to look at.

Product/Presentation

To present the product, I am thinling of putting it inside a ball shaped object so that people can move it around. There are many ways to experiment with sound and movement once I get it to be a bit more wireless. The ball shaped object is for the purpose of ease of use, as well as the potential for the device to aide in physical therapy.

To-Do

Because I love and need lists.

• !!Solder Power Supply

• !Create modes to change up notes played (experiment with this if time permits)

• Create Static website x Presentation

• Letter to Next Cohort

• Course eval