Last time out, we created the LFOur, a generative patch composed of a quartet of synchronized LFOs whose output we can use to make noise. While it's interesting to watch how the different LFO configurations make combinatoric waveforms and it's restful and instructive to watch the sliders flick and rock, it would be nice to have something to connect it to. This tutorial includes some patches that will do just that.
I'm personally a lot more interested in the ability to synchronize processes in Max using time values that resemble musical note values to create control structures that can be easily time synced. This tutorial is about making one of those kinds of modules - a quartet of synchronized LFOs whose outputs I can sample individually for several kinds of data (triggers for waveform start, LFO outputs that I can sample at variably synchronized rates, and a nifty summed waveform I can use for more exotic kinds of control).
Some of us listen to many different types of music and are open to experimentation but, correct me if I'm wrong, sometimes the music that comes out of academic circles can be cold and dry. DR.OX is a welcome change. I had the pleasure of interviewing one half of DR.OX, Natasha Barrett, and I found her focused, enlightened and outspoken.
Brian Crabtree (who performs under the name tehn) and his partner Kelli Cain are collectively known as monome. They design what they call adaptable, minimalist interfaces. The musical instrument industry calls them alternate controllers. There are currently three models that interface with a computer. There is no hard-wired functionality; interaction between the keys and lights is determined by the application (such as Max/MSP) running on the computer. Basically the monome units can do whatever you program them to do and serve as alternate controllers for not just music but games, lights, video etc. Monome is fantastically successful. I found their story inspiring and exciting -- they represent a new breed of creative entrepreneurs who are environmentally and socially conscious.
Typically, when I talk to Jitter users about writing one's own shader programs for use with jit.gl.slab, I usually get glazed-over eyes and this sort of distant look of wonder. When I try to explain how easy it is, that look typically turns to one of annoyed disbelief. So, for a long time now I've been thinking about writing an article to de-mystify the process of writing your own GLSL shaders, and to help everyone avoid some common frustrations.
In this second installment of the ReWire Essentials series, we are going to look at hosting ReWire client applications. Clients route their information to the host (or mixer) application through the ReWire mechanism, and using Max/MSP as a host gives us options to have some fun with both the playback and output of the connected application.