errantember (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
errantember) wrote2008-12-27 01:51 am
errantember) wrote2008-12-27 01:51 am
Entry tags:
The MIDI Quest Continues!
When we last left Our Hero, he was here. I had finished tracing out the functionality of the first MIDI subroutine in MIDIStroke, only to find that all it did was convert incoming MIDI signals into a list of pre-defined numbers, presumably for use Elsewhere in the Program.
After a successful Christmas and first-turkey roasting (thanks to the New Best Recipe, which I should be a salesman for, and my Mom, who'd I'd rather not sell) it's time to find out, exactly, where Elsewhere in the Program is, and precisely what it is they *do* there.
After a busy few hours of tracing through the midiConvert subroutine, I've *definitely* discovered the place where it checks through your list of signals to discover whether or not to output a keystroke from a given MIDI input. I've also differentiated between the portion that gets run for every incoming MIDI signal, and the part that gets run for a signal that creates output. I've only done this *definitively* for the capture and uncaptured Note ON messages, because those are the only ones I know how to enter into The Box.
You remember The Box, right? The entire point of this effort, at least initially, is to figure out what goes into The Box to translate incoming Program Change and Control Change messages into keystrokes. Why? Because I need it to perform my musical act on stage with my version of Ableton Live. The food pedal I'll be using to control the show won't send Note ON messages, which is the only kind the MIDIStroke documentation tells you how to enter into The Box. To figure out how to do it for PCs and CCs, I'm reverse engineering the program.
To be honest, I'd rather RTFM. But since TFM doesn't exist, what can you do?
The Next Step will be to start looking at the actual code in the subroutine I've just mapped, and figure out exactly where the part is that does the comparison to the contents of The Box. At that point, I should be able to figure out what I have to *put* there to get MIDIStroke, and thereby Ableton, to work with my MIDIMate pedal board.
After a successful Christmas and first-turkey roasting (thanks to the New Best Recipe, which I should be a salesman for, and my Mom, who'd I'd rather not sell) it's time to find out, exactly, where Elsewhere in the Program is, and precisely what it is they *do* there.
After a busy few hours of tracing through the midiConvert subroutine, I've *definitely* discovered the place where it checks through your list of signals to discover whether or not to output a keystroke from a given MIDI input. I've also differentiated between the portion that gets run for every incoming MIDI signal, and the part that gets run for a signal that creates output. I've only done this *definitively* for the capture and uncaptured Note ON messages, because those are the only ones I know how to enter into The Box.
You remember The Box, right? The entire point of this effort, at least initially, is to figure out what goes into The Box to translate incoming Program Change and Control Change messages into keystrokes. Why? Because I need it to perform my musical act on stage with my version of Ableton Live. The food pedal I'll be using to control the show won't send Note ON messages, which is the only kind the MIDIStroke documentation tells you how to enter into The Box. To figure out how to do it for PCs and CCs, I'm reverse engineering the program.
To be honest, I'd rather RTFM. But since TFM doesn't exist, what can you do?
The Next Step will be to start looking at the actual code in the subroutine I've just mapped, and figure out exactly where the part is that does the comparison to the contents of The Box. At that point, I should be able to figure out what I have to *put* there to get MIDIStroke, and thereby Ableton, to work with my MIDIMate pedal board.