Recalling Body Hacking Con was fun with Tim. He was excited by the people I met and the things I experienced. My newest implant also made him a bit envious since I got a VivoKey Spark first. The live episode went relatively long for us.
Here is our unedited video recording (55:45) and here is the show page for the edited podcast with episode 059.
The project got off to a strong start. Generating pseudo-random, prandom, notes on a pentatonic scale worked. A six-second clip was recorded to demonstrate the sound of these prandom notes. Thankfully, none of them seem to land poorly, but they were not musical.
Earlier, this project write-up mentioned that it uses the pentatonic scale, but it would be more accurate to say that it uses one of the pentatonic scales, but there are five different pentatonic scales. A button was programmed to cycle through them.
The very first program played notes that went from the lower limit of human perception to the upper limit. My hearing at the upper limit is limited compared to most people my age, so a couple of listeners have said that it is unnecessarily ear-piercing. Reigning those limits in seemed like a good idea to me too since the notes could bounce from low sounds up to high sounds alarmingly fast. Two potentiometers were programmed to deal with this. One determined the lowest note possible while the second determined how many notes above it that could be played.
In the programming sense, chords and scales were similar. In this program anyhow since they both used named arrays with a series of numbers corresponding to the root notes. Sadly, chords played like this sounded like every single one was stumbling over the previous.
Learning about a new field, like music, is difficult even when things go well. It would be like taking a foreign language class which you have never spoken and a few sessions in, the teacher is replaced with someone who doesn't understand the curriculum. That is what happened with this. Hardware failures became overwhelming. The biggest problem was reading the potentiometers. Changing one would significantly mess up the readings on other channels. No amount of filtering could correct it. Without significant investigation, it seemed the problem was with the cheap hardware, and it would be better to move on to bigger and better equipment. An expansion was already on the menu, and things would be moving to modular system. The final verdict was to use an Arduino Mega instead of a Micro Pro and a handful of Arduino Pro Minis.
Here is our unedited video recording (55:45) and here is the show page for the edited podcast with episode 059.
Brian - Left _____ Tim - Right
The project got off to a strong start. Generating pseudo-random, prandom, notes on a pentatonic scale worked. A six-second clip was recorded to demonstrate the sound of these prandom notes. Thankfully, none of them seem to land poorly, but they were not musical.
(0:06) Demonstration of some prandom notes
Earlier, this project write-up mentioned that it uses the pentatonic scale, but it would be more accurate to say that it uses one of the pentatonic scales, but there are five different pentatonic scales. A button was programmed to cycle through them.
(0:41) Scale selection
The very first program played notes that went from the lower limit of human perception to the upper limit. My hearing at the upper limit is limited compared to most people my age, so a couple of listeners have said that it is unnecessarily ear-piercing. Reigning those limits in seemed like a good idea to me too since the notes could bounce from low sounds up to high sounds alarmingly fast. Two potentiometers were programmed to deal with this. One determined the lowest note possible while the second determined how many notes above it that could be played.
(0:41) Demonstration of LOWER LIMIT and RANGE
In the programming sense, chords and scales were similar. In this program anyhow since they both used named arrays with a series of numbers corresponding to the root notes. Sadly, chords played like this sounded like every single one was stumbling over the previous.
(0:52) Demonstration of chords
Learning about a new field, like music, is difficult even when things go well. It would be like taking a foreign language class which you have never spoken and a few sessions in, the teacher is replaced with someone who doesn't understand the curriculum. That is what happened with this. Hardware failures became overwhelming. The biggest problem was reading the potentiometers. Changing one would significantly mess up the readings on other channels. No amount of filtering could correct it. Without significant investigation, it seemed the problem was with the cheap hardware, and it would be better to move on to bigger and better equipment. An expansion was already on the menu, and things would be moving to modular system. The final verdict was to use an Arduino Mega instead of a Micro Pro and a handful of Arduino Pro Minis.
Next hardware choices
The rest of the weekly summaries have been arranged by date.
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Disclaimer for http://24hourengineer.blogspot.com/
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
Comments
Post a Comment