![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
YEEEeeeeEEEEEEEEEEEEEEEEEEEES!*
Jan. 3rd, 2009 02:01 amI'M READY TO GO ON STAGE!!!*
( Read more... )
( Read more... )
I've Cracked the Code!
Jan. 2nd, 2009 03:32 amAfter nearly a month of intermittently looking at the problem, I finally have come to the conclusion that MIDIStroke doesn't differentiate between the three different types of MIDI signals at *all*. The idea that it did was what sent me off on this wild goose chase to begin with, since it would be kind of stupid if a program treated playing note #5 the same as changing to instrument #5 or the pedal passing point 5 our of 128, but, evidently, MIDIStroke is stupid.
( Read more... )
( Read more... )
Go to the Source
Dec. 3rd, 2008 03:13 amOr, if you don't have the source, go to the assembler. :)
I made a bit more progress in using the GNU Debugger to run around inside MIDIStroke, and also made some progress in disassembling the entire program using otool. It does look like it might be possible to actually figure out the encoding scheme for program changes and control changes using this method, thought it won't be easy. For those generally unfamiliar with this sort of thing, what I'm doing is taking a complete program and looking at it's guts to try to figure out something about how it works. When you create a program, you have something called "source code", which is a sort-of englishy-language description of how you want the program to run. The computer can't read this, though, so it has to be translated into machine language, which is called assembler. Generally, when you're using an existing program you didn't write, you only get the assembler to look at, which is very much akin to trying to figure out how a car works without having the design diagrams or any manuals.
( Read more... )
I made a bit more progress in using the GNU Debugger to run around inside MIDIStroke, and also made some progress in disassembling the entire program using otool. It does look like it might be possible to actually figure out the encoding scheme for program changes and control changes using this method, thought it won't be easy. For those generally unfamiliar with this sort of thing, what I'm doing is taking a complete program and looking at it's guts to try to figure out something about how it works. When you create a program, you have something called "source code", which is a sort-of englishy-language description of how you want the program to run. The computer can't read this, though, so it has to be translated into machine language, which is called assembler. Generally, when you're using an existing program you didn't write, you only get the assembler to look at, which is very much akin to trying to figure out how a car works without having the design diagrams or any manuals.
( Read more... )
The Pedal for the Metal
Dec. 2nd, 2008 12:38 amMy Rocktron MIDI MATE arrived while I was gone at the Freaktactular. I've confirmed that it can do what I want it to do, insofar as being able to give me single-button access to at least 10 midi signals, with a lot more a few presses away. However, my frustration at figuring out how to get MIDIStroke to recognize Program Change and Control Change information has now reached the "it's time to disassemble the program" levels. I sent the author a very complimentary e-mail, even offering money, asking how it's done, but so far I haven't gotten any replies, and can't find the info on the Interweb anywhere. I need MIDIStroke to transform the incoming Program Change message into keystrokes for use with Ableton. Other than ControlAid, another program by the same author, I'm not aware of any other program for MacOS that will do this, so I'm a bit stuck at the moment music-wise.
