Re:Re: MaxMSP looping -

[cpr@musetrap.com]

 I'm not a current Max user, but when I was working for Opcode I spent 
some time
exploring it, and even wandering thru the source code a bit.. :) in 
anycase,
it's a 'visual programming environment', and is capable of many things... 
what
it is used for is entirely up to the programmer, so one could assume that 
the
people who programmed the Max patches for the pieces you have heard did not
concern themselves with the rhythmic/time signature based issues...

 One of the things that is great about these type of environments is that 
it's
so easy to start experimenting... which, I believe, lends itself to more
'sound/data mangling', much like tweaking parameters on fx, than 'time
based/syncronized' work... as well, I believe time-based stuff can require 
more
of a 'programming' mindset, where fx based work is more about just plugging
objects together...

 It's been said here before, but writing time-critical software is not a 
simple
task... tools like Max make the easy parts far easier, but the hard parts 
are
still hard...

peace
-cpr

Quoting a k butler <akbutler@tiscali.co.uk>:

> 
> >
> >I think one possible answer to this cycle lies in the flexibility of
> Max/MSP.
> 
> hi Jeff
> a Max/MSP question
> 
> how good is it for rhythmically based music?
> 
> I've heard a number of max/MSP performances,  and have not yet heard 
> any rhythmic co-ordination
> going on, at least not in the time signature sense.
> Please don't take this as a criticism of the music, it isn't that at all,
> I'm interested in the capabilities of MAX
> 
> 
> andy butler
> 
> 




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.