Subject: MAX Digest - 7 Jan 1998 to 8 Jan 1998
Date: Fri, 9 Jan 1998 00:01:21 -0500
From: Automatic digest processor 
Reply-To: MAX - interactive music/multimedia standard environments
     
To: Recipients of MAX digests 

There are 4 messages totalling 134 lines in this issue.

Topics of the day:

  1. Max 3.5.9
  2. Now utilities
  3. To NULL or not to 0L (WAS: unknown message argument type)
  4. maybe my PB190 cannot have the QTAM-editor work?

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

Date:    Thu, 8 Jan 1998 01:26:15 -0800
From:    David Zicarelli 
Subject: Max 3.5.9

You can now download the Max 3.5.9 update from version 3.5.8.
This update will primarily be of interest to people using MSP or
the timeline object. It provides optional scheduling in the audio
interrupt when running with MSP and fixes several timeline bugs.
In addition, there are changes to the msd object and miscellaneous
other bug fixes.

Currently, the only site with the update is
www.cycling74.com/support, but Opcode should have it up on their
site in the next day or so. Once Opcode has it up, I may remove
it from Cycling '74 for a while just to allow more bandwidth to
people trying to download MSP.

Note that you have a choice of two files to download, depending on
whether you are using the new (3.5.8) master disk compatible with
OS 8, or the old (3.5 or 3.5.1) master disk.

If you're updating from a version earlier than 3.5.8, download
the 3.5.8 update first from the Opcode web site (www.opcode.com/dl)
then download 3.5.9.

If you have problems downloading or installing the files, let
me know by e-mail as soon as possible so I can make any necessary
corrections.

David Z.

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

Date:    Thu, 8 Jan 1998 02:45:47 -0800
From:    David Zicarelli 
Subject: Now utilities

Now software was purchased by Qualcomm. They've announced a
future OS 8 compatible update available in March. Not much
more info than that available at http://www.eudora.com/nowutilities/

David Z.

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

Date:    Thu, 8 Jan 1998 17:47:32 +0100
From:    Peter Castine 
Subject: Re: To NULL or not to 0L (WAS: unknown message argument type)

First off, apologies for my idiosyncratically formatted/encoded previous
message. 8-bit ASCII and source code don't mix very well on a mail list
digest...

Anyway, David pointed me in the direction of a solution to my problem
with...

>    * check failed: unknown message argument type

[The asterisk is really a bullet in the Max window]

...and I post the solution (for my case) here in case anyone else comes
across it.

Essentially, the message comes at instantiation time when Max decides

> your object's instance method
> arg list is bogus

How can that happen, you ask?

Well, if you do something like this:

>    setup(&gQKSendClass,               // Pointer to our Class Definition
>          NewQKSend,                   // Instance Creation Function
>          NULL,                        // No Instance Destruction Function
>          (short) sizeof(QKSend),      // Class Object Size
>          NULL,                        // No Menu Function
>          A_SYM, 0);                   // Type list for Arguments

Note that I use NULL whereas the sample code uses 0L. I am used to NULL
being #defined as ((void*) 0), which is close enough to a long zero as to
make no difference for the stack. But  compiles conditionally on
a couple of things, and when using the Metrowerks C compiler NULL
resolves to 0 *with no size qualifier*! So, of course, if you compile
with two-byte ints (as I usually do), the above call to setup() has a
seriously munged stack.

I think I was pretty lucky that Max didn't croak when I call setup();
think about what the menu function parameter looks like.

Anyway, I think this is a bug in Types.h, and will say as much as soon as
I can get a hold of Apple's Bug Reporter Stack. I can't think of any
reason for NULL to be #defined to 0 (as opposed to ((void *) 0) or 0L).
In the mean time: make sure you know what NULL means when you use it.

Cheers,

Peter -- hoping y'all found this more amusing than I did

---------------- http://www.prz.tu-berlin.de/~pcastine/ ----------------
Dr. Peter Castine           | I believe that the use of noise to make
pcastine@prz.tu-berlin.de   | music will continue and increase until we
                            | reach a music produced through the aid of
                            | electrical instuments.  -- John Cage, 1937

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

Date:    Fri, 9 Jan 1998 07:18:17 +0000
From:    BUYO-BUYO-IGOR 
Subject: maybe my PB190 cannot have the QTAM-editor work?

Hi, Peter!
BUYO-BUYO-IGOR thank you for teaching me the way to call the new QT
intruments from MAX.
But now, unfortunately the system-extention that I gave birth with the
editor seem to be not working..
Actually when I try to save the instrument the application freeze...but
the extention appears when I force the program to stop....I tried in a
lot of ways..my powerbook is 190 and have only 16MB of RAM....but now I
gave 16 more MB of virtual RAM to the machine...and am now giving 20 MB
to QTAM-editor..but the result is always the same...
Is this something that is already reported?
Since I'm not rich enough to buy a new synth for my planned microtuing
oriented music...I really want this application to work...mmmm...I want
the sound itself to be microtuned.
Can somebody let me try the right extention created?

Thanx.

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

End of MAX Digest - 7 Jan 1998 to 8 Jan 1998
********************************************