3/23/97 12:00 AM
Subject: MAX Digest - 21 Mar 1997 to 22 Mar
1997To: Recipients of MAX digests 

There are 4 messages totalling 102 lines in this issue.

Topics of the day:

  1. MAX Digest - 19 Mar 1997 to 20 Mar 1997
  2. Setting the file format when using "saveto" message
  3. MAX
  4. font question


Date:    Sat, 22 Mar 1997 10:24:43 +0100
From:    Hans Tutschku 
Subject: Re: MAX Digest - 19 Mar 1997 to 20 Mar 1997

>I have problems when using the AiffPlay object, in layering sounds.  I'm
>attempting to use it to play up to 8 AIFF sounds simultaneously.  It does
>fine up to about 5, but then I get a "Buffer too small" error.  Have tried
>the buffer as big as 65535 bytes, to no avail.
>Stranger still is that when I close all files, then open one again, I still
>get a "buffer too small" error. It seems I need to be flushing the buffer
>or something like that.  Any suggestions?

Just give more memory to the MAX application.



Date:    Sat, 22 Mar 1997 09:58:29 -0500
From:    Bill Vorn 
Subject: Setting the file format when using "saveto" message

I'd like to know if there is a way to set a default file format when using
"chkmenu" and "saveto" messages.  When the dialog box appears, it is set
to Max Normal binary file format, but I'd like to have it set to Text file

The saveas_dialog routine allows to set the default file format but it
seems inaccessible when using "saveto" (Max takes care of opening the
dialog box).

The table and coll objects show the same kind of problem when saving using
"Save As" from the File menu.

I know it's not a very important problem because the object can save the
file in Text format anyway.  Just a matter of a "finishing touch".

Bill Vorn
Montreal (Quebec) Canada


Date:    Sat, 22 Mar 1997 12:25:46 -0500
From:    Alvaro Bertrand 
Subject: Re: MAX

Is there a "Max for dummies" type of book?



Date:    Sat, 22 Mar 1997 14:57:12 -0800
From:    David Zicarelli 
Subject: Re: font question

Paul Doornbusch  asks:

>Is there a way to go beyond the 36 point limit in the font
>menu for any display objects?

Yes. It's not pretty. You need to hack a Max patcher file as text.
Text objects are created by lines in the file like this:

#P comment 36 78 100 196617 comment;

The number 196617 is read as two 16-bit values. In hex it looks like

0003 0009

where "3" is the font number for Geneva and "9" is the font size.
If you change the second part to something bigger, you'll get a
bigger font size. The easiest way to do this is just to take the
value 196617 and add whatever you want to get a bigger size than
9. So for example, for a 72-point comment, you could add 63 to
get 196680. Save the file after making this change, and you'll
find that the rectangle in which the font is displayed is too narrow.
That's the third number after "comment"--make it larger and you'll
be happy. Or you can just resize the comment box once you read the
file in again.

This only works for comment, object box, and message box. Menus and
number boxes store font information differently. And number boxes
limit their font size to 36, to counteract a bug longtime users have
probably seen (it's been fixed for a while).

The menu object stores its font and size in the third number from the end of
a message line that creates a "user umenu"--and the font size is shifted
to the left by two bits in the lower 16-bit word of the value. You should
leave the two least significant bits as they are.

Naturally, this sort of hacking it not guaranteed to be free from
display glitches.

David Z.


End of MAX Digest - 21 Mar 1997 to 22 Mar 1997