I did it!

[errantember]

I *finally* found the location of the *actual* MIDI message inside MIDIStroke! It's at 0xF007FD6E! Of course! I was already pretty excited when I discovered the part of it moved into r2 looked like the preamble for a note-on, but after changing the MIDI transmission channel and hitting the key with different levels of force, which changes the velocity number at the end of the note, I'm 100% sure I've got it!

The path from this info to finding out what needs to be in the box to make my pedalboard work should be *short*. I'm *very* pleased with myself!

Go me!

Eventually I will post a link to a little presentation that explains all of this in more laymen understandable terms, at which point it won't be *nearly* as rad.

Comments

[bouncyone.livejournal.com]

hahahahaha!

take that evil software! look who just pwned your bits!

[dancingb4diana.livejournal.com]

ah yes, midistroke and controlaid were critical apps when i was doing all the ableton work. i haven't used them in a long time since i've just been doing studio stuff but will likely work on some live thing again early next year. i'm really surprised ableton STILL hasn't baked those two apps directly into Live yet. Live just isn't complete without a way to create batches of midi instructions like that.

[errantember.livejournal.com]

Ableton *does* support a lot of this stuff natively in 7.x, but I'm still working with an old copy of 5.x, which doesn't.

I've looked at ControlAid, but haven't actually found a specific use for it, yet.

I don't suppose you ever figured out how to enter a Program Change or Control Change into MidiStroke? Or did you use ControlAid to transform them into NoteOn/Off messages first to avoid having to know that?

geekery

[hobgadling.livejournal.com]

dude, I'm totally getting geekwood from your recent posts. Keep it up!

Re: geekery

[errantember.livejournal.com]

Excellent. I'll be doing more tonight...