Re: question for max/msp gurus ? [software loopers redux]

[Alex Stahl <alex@pixar.com>]

You might get more responses on the max list, but:

Perhaps the simplest way to get started is to use tapin~ and tapout~ instead of buffer~. If you want to use buffer~, it's possible to set up counters and peek~ objects to do it. Note that in order to feed a tapout~ object's signal back into a tapin~, you need to add a send~ and receive~ in the feedback loop or it won't run, due to some mysteries of the DSP graph.

Anyway, once you've done this you can vary the tapout~'s position at will during performance.  

Bridging Max and SC via OSC doesn't make sense on one computer, because of the overhead of running two DSP schedulers on one machine, and who knows what other competition for CPU the two apps would suffer. Some people do mix and match them on networks, although I don't myself see why.

-Alex S.


At 7:04 PM -0500 2/24/03, Clark, Darcy wrote:
> I know there are a few Max/MSP users on this list, hopefully some have attained "guru" status :) To gurus and non-gurus alike I would ask - have you solved the problem of making a buffer~ whose length is determined by the first "tap" - i.e. I'd like the buffer~ to work in the classic looping sense, not just be a sampling looper of predefined length. All the looping apps I have seen so far in Max/MSP (jhno's looper being the primary example) have pre-defined loop lengths. My dream, and I'm sure that Max/MSP must be capable of this, is to reproduce something like the Repeater in Max/MSP.
>
> Another idea that occurs to me as I type this is to use some of the "bridging" externals between Max and Supercollider or C-Sound - maybe these languages are more suited to looper creation and the looping module could be run inside of Max (Max taking care of the UI, midi control etc...).
>
> Finally has anyone tried this app out ?
> <http://www.dexterssandbox.com/sooperlooper/>http://www.dexterssandbox.com/sooperlooper/
> (if only this were available for Max/MSP!)
>
> Darcy