slatepipe

i am new to this program and i have been introduced to it via the sonic art degree that i am currently studying at college. i am working my way through the tutorials and am getting my head around the basics and am slowly making progress.

we have to complete an assignment using max msp in a couple of months and need to make a patch and a soundpiece that was made using this patch.

i have an idea to make a patch that makes a generative music piece starting from a sample that i load into it that is continually effected in a variety of ways and recorded by max msp as a wav file

i have been loading a sample using replace and buffer, then i have tried to separate out different numbers from it using an external i found called fiddle. i have also experimented with the drunk object too, but not with much success so far

i think that i would like to do something like : use fiddle to generate different numbers based on the type of sample fed into it, then feed these numbers into other objects like drunk (are there others like drunk? i am slowly learning) and then feed the results back to the start of the chain to be effected again, hopefully forming a continually changing generative music piece.

sorry about the long (first) post but can anyone offer me any helpful advice to help mew complete this task? any examples of similar ideas? what problems am i likely to encounter? what objects would you use to achieve something like this?

many thanks in advance, i cant wait to get my head around this program properly

i have an idea to make a patch that makes a generative music piece starting from a sample that i load into it that is continually effected in a variety of ways and recorded by max msp as a wav file 

many thanks in advance, i cant wait to get my head around this program properly


new-to-max-msp-generative-music-advice

On Feb 27, 2008, at 4:26 PM, Chris Muir wrote:

> Though Max/MSP doesn't encourage it much: First Design, Then Code. 

> It's much easier to implement something, if you've really thought 

> about what it needs to do, and have a design in mind.

This is so important. AFTER I have conceived of an idea and narrowed 

its scope sufficiently, I usually spend at least a week, and sometimes 

two, with it on the backburner. Meaning, I don't really even 

consciously devote cycles to it, I just work on whatever else I have 

going on but keep thinking about the problem in the back of my head in 

Usually when I finally sit down to start coding, this initial waiting 

period its more than made up for in robust and clean implementation.

A lot of planning goes on in your head when you aren't thinking about 

> Though Max/MSP doesn't encourage it much: First Design, Then Code.  
> It's much easier to implement something, if you've really thought  
> about what it needs to do, and have a design in mind.

This is so important. AFTER I have conceived of an idea and narrowed  
its scope sufficiently, I usually spend at least a week, and sometimes  
two, with it on the backburner.  Meaning, I don't really even  
consciously devote cycles to it, I just work on whatever else I have  
going on but keep thinking about the problem in the back of my head in  
the shower, driving, etc.

Usually when I finally sit down to start coding, this initial waiting  
period its more than made up for in robust and clean implementation.

A lot of planning goes on in your head when you aren't thinking about  
it.

San Francisco, CA
Work: 857-544-3967
Email: bthrew (at) gmail (dot) com
Web: www.barrythrew.com


many thanks for this advice everybody. it seems some flowcharts are the way to go for the moment. i am looking forward to the time when it all starts to slot into place

"A lot of planning goes on in your head when you aren't thinking about

Is this also why you feel creative when you come back to music after being away for a while?

"A lot of planning goes on in your head when you aren't thinking about
it."

new to max msp, generative music advice