Andross

Ok...I guess you could say I diddn't really plan this post but while programming in Max I consistently come across a problem of my logic getting stuck so that I can't figure out how to do the next step of my program. I remember reading that it is best to have some sort of a 'plan' written out before you start programming so I tried starting out just by writing down thoughts of what I wanted to do (starting with the ideals) and then trying to work out

1) What things I want this prog to do and how I plan to do them.

2) What information you'll need to give the user and how I plan to display it, and

3) What information I need to get from the user and how the user can best provide it.

...The problem is that often my planning is very abstract (such as I might want this subpatch to control the rhythm of this piece of hardware while another subpatch does something else etc.) and I was wondering if anybody had any advice on how to write out 'classes' and those sorts of things before hand just to make the actual programming a little smoother.

methods-of-planning-a-patch

http://faculty.roosevelt.edu/malone/downloads.htm

it takes all of us
LoneMonad
http://faculty.roosevelt.edu/malone/downloads.htm


ok....looked at the patch....don't get it.

Coffee, aderol, Beethoven's 9th... that should get you started...

> 1) What things I want this prog to do and how I plan to do them.

> 2) What information you'll need to give the user and how I plan to display it, and

> 3) What information I need to get from the user and how the user can best provide it.

you should not start with the GUI, though this is what most

people do and it can work for a fun project.

what could be done before making a software is creating

a socalled "machine model", some kind of graphical layout 

which shows off the most basic logical connections between 

parts of the DSP or message system. - so that you do not 

i must say i dont feel it is neccessary in an object 

orientated enviroment like maxmsp .. or visual basic.

having one in mind can help you of course to find out

at which points to make abstractions and subpatches.

where are the modules and where are the interfaces 

between them can be an important question in a music 

you should not start with the GUI, though this is what most
people do and it can work for a fun project.
what could be done before making a software is creating
a socalled "machine model", some kind of graphical layout 
which shows off the most basic logical connections between 
parts of the DSP or message system. - so that you do not 
forget one part later on.

i must say i dont feel it is neccessary in an object 
orientated enviroment like maxmsp .. or visual basic.

having one in mind can help you of course to find out
at which points to make abstractions and subpatches.
where are the modules and where are the interfaces 
between them can be an important question in a music 
app development process.


Methods of Planning a Patch