When I added labels, I put them on in the order that made sense, and when I checked with my weeks-old code, they aligned. I made a function to act on the nine operation buttons, like changing instruments, tracks, and melody. I reversed the buttons that increase or decrease the selection because their numbering starts at the top with zero, and increasing the variable moves down, typically declination.
I created an array to store each track's instrument value, but I decided it was better to add that to the end of the velocities array and keep everything together. Increasing and decreasing the melody was trickier since I had been toggling lights when I pressed a button, so I wrote a function that looked at every variable in a melody and changed lights accordingly. Since this is processor-heavy, I will still use the old method.
I almost stopped before tackling the button to assign pseudo-random notes to an entire melody, but I pushed it. Instead of coding an arbitrary likelihood that a note will play, I used the slider position to increase or decrease the number of prandom instances. In the animation below, you can see the slider moving up in each frame and the value on the screen changing.
Prandomized tracks
The rest of the posts for this project have been arranged by date.
First time here?
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 6
Completed projects from year 7
Completed projects from year 8
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.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.
2021-12-15
I created an array to store each track's instrument value, but I decided it was better to add that to the end of the velocities array and keep everything together. Increasing and decreasing the melody was trickier since I had been toggling lights when I pressed a button, so I wrote a function that looked at every variable in a melody and changed lights accordingly. Since this is processor-heavy, I will still use the old method.
I almost stopped before tackling the button to assign pseudo-random notes to an entire melody, but I pushed it. Instead of coding an arbitrary likelihood that a note will play, I used the slider position to increase or decrease the number of prandom instances. In the animation below, you can see the slider moving up in each frame and the value on the screen changing.
The rest of the posts for this project have been arranged by date.
First time here?
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 6
Completed projects from year 7
Completed projects from year 8
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.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.
2021-12-15
Comments
Post a Comment