Subject: MAX Digest - 11 Apr 1998 to 12 Apr 1998
Date: Mon, 13 Apr 1998 00:00:24 -0400
From: Automatic digest processor 
Reply-To: MAX - interactive music/multimedia standard environments
     
To: Recipients of MAX digests 

There are 4 messages totalling 150 lines in this issue.

Topics of the day:

  1. T.C.Electronic M2000
  2. MaxPlay bug
  3. system upgrade question
  4. Not MaxPlay bug (Aliases)

----------------------------------------------------------------------

Date:    Sun, 12 Apr 1998 02:55:05 -0400
From:    Ben Thigpen <101762.3705@COMPUSERVE.COM>
Subject: T.C.Electronic M2000

Hi,

I've just started to work on a Max interface for the T.C.Electronic M2000=

effects processor.  I wonder if anyone on this list has any experience wi=
th
MIDI control of this machine.  =

Thanks in advance to anyone with advice, information, anecdotes, etc.

Ben Thigpen

------------------------------

Date:    Sun, 12 Apr 1998 09:42:05 +0100
From:    Timothy Edwards 
Subject: MaxPlay bug

Has anyone succeeded at getting MaxPlay to recognize the graphic command
"rect"?  Its failure to do so is keeping me from compiling some
graphics-oriented patches as stand-alone applications.  I've tried MaxPlay
3.5.8 and MaxPlayMSP 3.5.9.

Any suggestions?

Timothy Edwards
timothy@uic.edu

------------------------------

Date:    Sun, 12 Apr 1998 11:14:26 -0400
From:    David Crandall 
Subject: system upgrade question

I know this got hashed over last year mostly concerning v3.5.x, but my
question is: using Max 2.5.2 (yeah, yeah, dragging my heels) what are the
best precautions for protecting my installs if I upgrade to System 8?  Is
it worth the hassle or should I just go to System 7.6.1?  I've been
perfectly happy with System 7.5.3 on a PM 7600/132, but the Retro AS-1
software synth demo requires the upgrade.

Also if anybody has an inkling of how these issues would apply to Pro
Tools 4, which I also have, don't be shy.

thanks,

David Crandall

--------------
neo-spartan creed:
no pain
 no gain
  no fear
   no compassion
    no hope
     no brain

(ok, sue me, I've been reading goffman)
--------------
dcrand1@gl.umbc.edu

------------------------------

Date:    Sun, 12 Apr 1998 12:31:54 -0400
From:    Stephen Kay 
Subject: Not MaxPlay bug (Aliases)

>Has anyone succeeded at getting MaxPlay to recognize the graphic command=

>"rect"?  Its failure to do so is keeping me from compiling some

It's not a bug.  It has to do with objects that use aliases. Here
is a reprint of something I wrote to the list a while back:

----------- clip and save -------------------------------------

USING ALIASES IN MAX COLLECTIVES OR APPS.

When making a collective or application in MAX, some extra care
must be taken with objects that use "aliases", for example, the
"oval" object, which can also be named "rect".

When you create a collective, Max copies all the objects needed
into it's collective.  If you do not have the actual "original" =

named object in your patcher somewhere, it will not copy it =

into the collective; therefore, it will not find it when running =

the collective/app.

Also, when using an alias, Max must find the actual real object =

_first_ in it's collective (before the alias), or it will give =

you the error message "no such object".

Therefore, say you are using rect somewhere, but not oval.  In =

a patcher, this is acceptable; in an application or collective, =

it will not work.  How do you get around this?

By placing an instance of the oval object somewhere in your =

application, and making sure that when it is being loaded, Max =

will find it before it finds the rect object.  The way to do =

this is to make sure the oval object gets included into the =

collective as the _last_ object. (Max 3.0 apparently loads =

objects in the reverse order of how they are saved).  =

Therefore, before saving, select everything _except_ the oval =

object (easy way: do a command-A (All), then with the shift =

key down, de-select the oval).  Then move everything else =

1 pixel with the arrow keys.  Then save the collective.

(3.5 update)
I'm not sure this moving up/down one pixel works anymore, =

with the new back to front layering scheme of 3.5.  But I do =

believe if the last thing you put into your patcher before =

you make it a collective is the oval object, the results =

will be the same.

Stephen Kay
---------------------- The MegaMAX Collection ----------------------
 Over 30 Max objects for the creation of more professional looking, =

         feeling, and functioning patchers and applications.
                     http://www.musikinetix.com
                         sk@musikinetix.com
--------------------------------------------------------------------

------------------------------

End of MAX Digest - 11 Apr 1998 to 12 Apr 1998
**********************************************