2025-04-11 (F) Weekly Summary

I started the looping code, but it was more complex than I realized, so I did not get more than variables and some rough code.
Looping code

I nearly gave up on the looping function. I tried to write a ton of code to tackle problems I did not even have. Once I gave up trying to simultaneously record five tracks with automatic chords and timestamps, I recorded and printed short sessions.
Recorded sequences

I got the loop playback partially working. The system will continue playing a sequence so long as I do not press more keys.
Playing a loop

I abbreviated the looping function to one track to avoid mudding up the process. The simplification made the difference, and I was noodling while the system replayed my loop. I needed more tweaks to implement chords and erase a lag before the first note, but I am happy with looping for the first shot.
Looping activity

I had a running list of TcMenu changes and tackled them all. I separated many options to make them more useful, like making an instrument changer for all fifteen melody channels and allowing each octave to act as another pitch and channel.
Over two-thousand code lines

Ray Jamison had a Kickstarter for his second issue of The Madcaps. The comic is a heist/caper fantasy story, and I enjoyed the first issue. Secret Level held a lot to enjoy and a lot to criticize.
Critical Affection: Secret Level
(1:30)

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
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11

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.

Comments