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(you're here) || eight || nine || ten

|| journal seven || 31. III. 03 || expansion.

well it took me over two hours of troubleshooting, but i expanded my physical interface to include three on/off switches. in intend to use data coming from these switches in Max to change which patch i am executing. kind of like switching between different movements of a sonata. my current BX-24 code is here: MIDIMax.txt.

you may be wondering, why did it take her so long to add simple on/off functionality? well, instead of simply checking to see if the three circuits were closed using the method getPin(x), i was asking the program to send me the electrical resistance of the circuit, using getADC(x) - that's "get analog to digital conversion". whoops.

so, what's next? i finally get to do more work in Max. now that i can switch between at least three different patches, i need to finalize what my three main algorithms will be. i am really thinking of this as switching between different "movements" of my piece. so far i have some interesting FFT going on, processing and granularizing the hell out of a sample... but it's only one "movement". i also need to switch from using sfplay~ to using buffer~ and groove~ . i had some trouble earlier trying to use multiple sfplay~ objects, whereas i am certain that it is possible to use multiple buffer~ objects.

a view of the circuitry in its current state. i should label this, no? looks like kind of a mess. learn more about the BX-24 microcontroller and its design here. you can also download a larger image.

another view of the circuitry. download a larger image.