nime: new interfaces for musical expression
a course at my master's program, itp. visit the course website.

aya karpinska
e-mail: ank212 at nyu dot edu

other journals: one || two || three|| four || five || six || seven || eight || nine(you're here) || ten

|| journal nine || 18. IV. 03 || significant improvement of program flow.

okay, this is it. after a three-minute conversation with one more knowledgeable than i, i know why my MIDI data is coming out of te BX-24 incorrectly. ha! i got it! and here is my final code: MIDIMaxFinal.txt ... basically, i hdidn't realize that i can send from 1 to 127 different controllers on channel 1 (status message 176). no need to increment the status message for my five controllers, i just send the data like this:
1) identify the byte being sent as MIDI status message "176", that is, controller channel 1
2) send the number of the controller (for me, 1 through 5)
3) send the variable that holds the value of the controller (resistance for flex sensors; on/off for switches)

i swiped some thin wooden coffee stirrers form Starbucks, and i am going to use them as miniature shims to stabilize my interface elements in their respective holes (remember the square peg/round hole issue?). i can also use the sticks to surround the perimeter of each interface element and hide those jagged holes. i'm still using paper sleeves and tape to hold my flex sensors in place - i know it's silly, but it works well! paper is just the right flexibility for those sensors. and i upgraded - instead of shreds of masking tape i'm using bright red duct tape. on to max programming...

** UPDATE ** silly me, thinking that the code i had here was the final version... he he he... check out journal ten for details...