The name of the sequence or track (ie, text). This event is primarily used to add 'comments' to a MIDI file which a program would be expected to ignore when loading that file. The two data bytes ss ss, are that number which corresponds to the MIDI Cue message.Īny amount of text (amount of bytes = len) for any purpose.

Note that Meta messages are not for realtime use but for use in MIDI files.

However it is recommended to insert most of the messages in the beginning of the stream/file. They can appear in the MIDI data stream at any time (except for Time Signature and End of Track). I didn’t get any further to figure out how you would use graph nodes to generate what is probably a log calculation, but the bottom line seems to be the node is expecting a frequency not a MIDI note number.Meta messages are not associated with any one MIDI channel. To use a trigger counter to generate octaves, the step count would have to multiply the current value by 2 each repeat and could then produce octaves (e.g., if you want to produce A octaves A4=440, A5=440x2, A6=(440x2)x2 etc). It appears the node expects a frequency and its function is to quantize that to the nearest note in a tempered scale (possibly provided through the array pin?). If you were to somehow increment by 523 (resulting in 1046) on the C5 value (the third time through), you’ll get roughly a C6. If you change the trigger counter start value to 261.63 (middle C) and step increment to 261, the first two notes will be (roughly) C4 and C5. The problem is it is expecting a frequency. Hopefully someone else will weigh in who is good with Log functions, but I can shed a little light on what the trigger counter is producing versus what the Midi Quantization is expecting.

Midi to note numbers chart