#Sound makers page media
1 messages · Page 1 of 1 (latest)
Only things I would change are the brightness of the background just to not blind people and make a clear distinction for the values for the treble and bass clefs, as someone seeing it at a first glance might assume bc of the ± sign, that a +7 or -7 would equal to a G (obviously starts to fall apart if you compare both clefs and see they are different notes but still that first glance is important and would be easier for people that don't know much of music. Other than that I have this thing I did a while back, I'll prettyfy it and include it as well just to have options in case someone doesn't know how to read sheet music and the like
I was probably going to remove the background also i fixed a couple inaccuracies in the sound generating block descriptions
here is the image with no background, that is clearer to read and has separate numbers for the bass and treble clef
hmm a ToneMaker..hmmm
I could possibly make a React app for transcribing music hooks into TM notes..hmmmmm
Is there a spreadsheet on this somewhere?
In what way? Closest thing I can think of is the pic I sent earlier in this thread
A tonemaker app sounds like pain to make -from someone who also attempted this once 
I was looking into https://tonejs.github.io/
Just a datasheet of your pic information .. 🤪
Okiday, I can put it into a spreadsheet for you
That would be awesome... to have the data broken down in the simplest form
If you ever want to punish yourself you are welcome to help with the TrailFlow project
So far I a found a way, a demo, to convert any midi file into JSON data of the Note Key/Timing/Vel/Note Duration...etc
Have a look:
https://tonejs.github.io/Midi/
I've attached some test midi files
Now once we get that datasheet of the TM sound scale data - I can write a parser/convert to convert the JSON output into TM notes with added options , of course.
https://docs.google.com/spreadsheets/d/1xYmmAzSrIqOxOhFDTP35HKnbEjNtlzHlEpEBmYcjUsY/edit?usp=sharing Hope that's what you are looking for
@scarlet delta that's awesome!
I found a general midi note sheet.. Does this correspond to the TM logic in any way?
yeah, it's just shifted. See the first cell at C,-2? if that 0 was instead at C,0. then it should be the same. And also that it only goes to 24 and -24
ah
SO TM only goes from: -24 to 24 in total notes?
SO that would mean that only these are usable:
So, Middle C (TM note = 0) becomes MIDI number 24?
Does that sound accurate?
If so, I will update a new column ("midi number") to the spreadsheet
@scarlet delta thanks for that spreadsheet!!
yep
wait, hold on. I saw somewhere that middle C is 60 in Midi, so the 0 should be there
oh. OK let me update the screenshot
yeah, 60 in standard Midi, but still just a matter of shifting the values
Ye that looks to be right
OK so I will have to log these numbers and convert any midi number (from a midi file) that fall outside of the logged numbers, to the closest octave. This will give it a TM sound value.
Aye
Please note that the tone generators are the only blocks that actual have a full four octave range. Unless they fixed it everything else has only two octaves and tunes in quarter steps instead of half steps
Is it even possible to edit the delay and duration and tone value of a block through the modding api
No, at most you can get instructions to manually type the values in
I've added additional mapped columns and data to this spreadsheet
The interesting thing is how a 61-key organ keys (1-49) matches TM Tone structure keys perfectly, minus the last 12 keys!
Methodology and Process for Achieving a SoundMaker App:
-
The user creates or downloads an instrumental MIDI file.
-
The file is uploaded into a parser that extracts key details such as MIDI Key Notes, Note Start Times, Note Timing/Duration, Total Duration, Common Time, BPM (Beats Per Minute), etc., from the MIDI file.
-
The system then uses these values to determine:
A. The number of tone blocks required for beats per Common Time, per Total Duration.
B. The number of tone blocks needed per note. For notes that form harmonies or chords (based on their start times), the output would be blocks separated into tracks (or lanes). -
The system matches each note's MIDI Key to its corresponding TM Tone Value.
-
It then generates a list of block settings, including tone values, timing, and duration, for each block and track.
Caveats:
- The system should include a Total Duration Limit and possibly a total block limit.
As I am thinking of the total process, I am sure it could be optimized if Logic Blocks are included..
as the music guy I can confirm that logic blocks allow you to loop the song with much more complexity and efficiency but it would be hard to implement in code.
@upbeat bridge hmmm.
So I just thought about it. There is no need to export harmony tone notes as this could be made manually. Just the melody (lead/hook/chorus), percussion(beat), bass (foundation)
Question for anyone. Trying to figure out how I will code the output, so im gonna need some TM building expertise. I've read somewhere that using ANDGates as the seconds (metronome) and to activate sound (notes) in tracks, maybe a good solution?
What do you say?
Imagine 4/4 with 8 bars of melody, and 8 bars of Chorus for a total of 16, which the beat could be the full 16 and on a different track. What method/arrangement of blocks would you use in its simplest form?
I just use individual note blocks with their own timings then or gates controlling loops, volume, ect. Here are a couple of my music boxes if you want to go through them.
the pink tan and grey ones are probably the best to look at since they are my most recent ones are are perfect loops