2021-02-05 (F) Weekly Summary

I started the week by unearthing a problematic statement in some filler code. I was supposed to write a line that would turn on a note and not much else. The problem was that I used 128 for the velocity (volume) but the function would reject anything over 127.
(0:10) Notes at 127 velocity, full volume

Next, I expanded the temporary code to factor in different instruments, the likelihood of playing, and I thought it calculated the tempo based on the sliders.
Code updates and notes

I was wrong about the tempo control, and I don't know what is happening there. I discovered that my spreadsheet had 128 for a lot of the instrument velocities, so I corrected that error and confirmed that my other changes worked properly.
Screenshot of new code

Changing tempos gave me trouble, and I found that I was not updating at the correct times, so I changed that. Another issue was that my screen updated multiple moods when I changed the first three. I tracked this down to a bit that didn't reset in time.
I found the issue

I tried shifting octaves before, but my code wanted to make all notes close to zero. To track down the issue, I made a few new moods that each tried something different, and I decided I didn't want to shift entire octaves at a time, but if I work in multiples of twelve, I still have the ability.
Octave shifting the easy way

I started the write the code that would fade an instrument in or out based on the spreadsheet. As each mood comes into focus, notes may become louder, more frequent, or both, depending on the parameters. Controlling these factors using only integer math is probably more trouble than it is worth.
Experimental moods

The rest of the summary posts 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

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.