5/18/97 11:00 PM
Subject: MAX Digest - 17 May 1997 to 18 May
1997To: Recipients of MAX digests 

There are 4 messages totalling 91 lines in this issue.

Topics of the day:

  1. Max Digest archive
  2. MaxPlay / Native speak / ftp
  3. MAX written as C functions
  4. Is it possible to sell your standalone Max stuff?


Date:    Sun, 18 May 1997 09:57:12 +0200
From:    "David K. Mason" 
Subject: Max Digest archive

Is there an archive of the past year's issues of the Max Digest retrievable
on-line?  If so, what's its address?

Best regards, Dave Mason


Date:    Sun, 18 May 1997 10:25:31 +0100
From:    Nick Rothwell 
Subject: Re: MaxPlay / Native speak / ftp

>I thought the whole point of making MaxPlay in the first place was so it
>could be freely and legally distributed with peoples' patches, like the
>QuicktimeVR player or the OvalTune player of yore.

Nope: in "the first place" MAXplay was a commercial product, on sale here
in the UK for around $150.

         Nick Rothwell, CASSIEL        contemporary dance projects        music synthesis and control

             years, passing by, VCO, VCF, and again, and again


Date:    Sun, 18 May 1997 15:20:55 EDT
From:    Roland Hemming <100414.2220@COMPUSERVE.COM>
Subject: MAX written as C functions

>>I now write my MAX patchers as if they were C functions.
>could you provide an example of what you mean here?

What I mean is you have to write in this style from the ground up. I look at
everything I want to do in my program and break it down. I divide my program
into 2 parts: user interface and 'services'.

The user interface is obviously the windows the user works with, menus etc.
then write perhaps hundreds of 'services' - these are my functions. They are
written in a generic way so many parts of the program can use them.

For example I have a function that creates unique Ids for me. Any part of my
user interface might want a unique Id for something. So I send a list of
part of it is a return destination from the patcher that called for the

Some functions might be very small. What i find is that when I write a
is that I can divide that up into several smaller functions.

I'm sure we all do this a little but I have taken this to an extreme where
everything in this part program is a generic patcher. There are NO duplicate
similar patchers in my program. What I discovered after doing this is that
patcher size is considerably smaller.

The only other issue here is that your patchers no longer store any data
in data structures. What I mean by this is that you can't rely on pack or
objects to have the info you think they last had cos another function might
changed it. But anyone writing commercial apps will save every parameter in
data structure anyway.

Is this enough info?



Date:    Sun, 18 May 1997 15:12:38 -0700
From:    David Zicarelli 
Subject: Re: Is it possible to sell your standalone Max stuff?

I misspoke about MAXplay: you can give it away but you can't
re-sell it. You can re-sell an application you make with the
installer. The case I was thinking of is someone who makes a
collective and wants to distribute MAXplay with it, but they
want to sell the collective. What they would have to do is
sell the collective with a pointer to MAXplay. But again, this
is more in the domain of "should" then "note the gun pointed
at your dog."

David Z.


End of MAX Digest - 17 May 1997 to 18 May 1997