7/20/97 11:00 PM
Subject: MAX Digest - 19 Jul 1997 to 20 Jul
1997To: Recipients of MAX digests 

There are 7 messages totalling 264 lines in this issue.

Topics of the day:

  1. large font question clarification...
  2. MAX Digest - 18 Jul 1997 to 19 Jul 1997
  3. large numbers
  4. Large Number boxes/fonts
  5. large font help - thanks!
  6. how do I... ?
  7. codeWarrior


Date:    Sat, 19 Jul 1997 23:09:36 -0700
From:    David Zicarelli 
Subject: Re: large font question clarification...

The famous Jeremy Roberts  writes:

>I'm trying to make a number box visible and legible at 10-15 feet. I'm
>looking to make a minimum of 72 pt. type... if not larger.

Here's how to do it:

Open your Max patcher as text. Find the object whose text you
want to be big. If it's a message box or comment, it will be in a
line like this:

#P comment 61 55 100 196617 this is the text;

The number "196617" encodes both the font and size. The size is
the lowest 16 bits. In practice, just add the difference between the
font size you have and the one you want. For example, 196617 encodes
Geneva 9, so if you want Geneva 72, just add 63 and replace it with
196680. After doing this, save the patch and re-open (not as text).

Now your text will be huge but you'll need to resize the box to deal
with the new font size. Save again after doing this. As long as
you never delete this object its font size should remain the same.

David Z.


Date:    Sun, 20 Jul 1997 00:46:42 -0700
From:    "Scott R. Looney" 
Subject: Re: MAX Digest - 18 Jul 1997 to 19 Jul 1997

I'm a newcomer to this group, though I've used MAX for about three years or
so.  Recently, I'v e been interested in doing live DSP processing using MAX
objects.  I have downloaded Ichi's usnd object and that does some
interesting things, but i'd like real-time filtering or pitch oriented
effects.  I've gone to the IRCAM site, where I heard that they have their
own version of MAX to be used in conjunction with FTS, but I have no clue
as to how much it costs.  I also would like to know if there might be any
possibility to run ISPW type stuff on a DEC Alpha machine with a 26114
processor.  I've read about FTS being written in portable ANSI C, but how
hard would it be to port something like that to a DEC Alpha machine?  These
machines offer a lot of processing speed at a fairly reasonable price these
days.  Or is it just better to take the plunge and get an SGI O2 Machine
with Audio package?  Any places to go for more info on this stuff?  I get
the feeling like the information I've looked at is fairly old.  Any and all
assistance regarding any live DSP objects or environments for MAX would be
greatly appreciated.

thanks in advance,

Scott R. Looney


Date:    Sun, 20 Jul 1997 12:57:26 +0200
From:    Paul Steenhuisen 
Subject: large numbers

leave your number box at a small size,  connect it to
a message box with set $1 to send the number.
save it and open as text.

in the line that says
#P message (x) (y) (z) (value) (#);

change the last three numbers of (value) to 714 (or something like
re-open the patch, adjust the size of the comment window and there you

paul steenhuisen


Date:    Sun, 20 Jul 1997 19:26:35 +0200
From:    Joerg Spix 
Subject: Large Number boxes/fonts

Hi folks,

I think there were some questions some weeks (?) ago about getting larger
number boxes, message boxes etc. than 36 points.

I tried some things out by modifying the text representation of a patcher
and came to the following conclusions. I only checked out int and float
number boxes, message boxes, comments and menus. All checked with Max 3.0
(borrowed, not mine, but I think most of you are not interested if I check
this with 2.5.2).

1) number boxes (int and float)

The maximum size for number boxes is 36 points. It seems, that there is a
restriction inside of MAX, because if I put in a 37, there is a line in the
Max window telling "(bullet)check failed:number box font size 37". Font
size 35 is OK (I didn't check if it was really one point smaller...).

Typical line for a int number box in text representation:

#P number 322 53 106 36 0 127 0 3;

#P     means "for last defined patcher" (guess!)
number means "create a number box"
322    means "322 pixels from the left of the patcher window"
53     means "53 pixels from the top of the patcher window"
106    means "width of the number box is 106 pixels"
36     means "font size is 36"
0      means "minimum is 0"
127    means "maximum is 127"
0      means "combination of switches in get info dialog"
3      means nothing to me, it is always there...

The line for the float number boxes is the same except that "number" is
replaced by "flonum".

2) comments & message boxes

Comments and message boxes are similar to the number boxes, but there is a
offset in the parameter which controls the font size. I'm not sure wheather
this offset may change depending on any settings for the object or if it is
a constant. Anyway here are my results:


#P comment 106 22 173 196680 aaa;

#P     means "for last defined patcher" (guess!)
number means "create a number box"
106    means "106 pixels from the left of the patcher window"
22     means "22 pixels from the top of the patcher window"
173    means "width of the number box is 173 pixels"
196680 means "font size is 196680 - 196608 = 72"
aaa    means "text being displayed is aaa"

The same applies to message boxes except that "comment" will be replaced by

3) menu

menu objects are still a bit more complicated, because there is a scaling
factor after subtracting the offset. Here is the example:

#P user umenu 112 40 212 196897 1 64;

In this example the number 196900 calculates as follows:
72 * 4 + 196609 = 196897
font_size * 4 + offset = parameter

The first three numbers have the same meanng as before, the last two are
dependent on the parameters which can be set by the get info dialog (64 =
max. number of menu items).

Well, that's it. You can experiment yourself to find out more.
Don't forget, that you need more room for large items, so better make your
objects wide enough before you make them bigger. Specially the menu object
needs enough room to pop up with several (3?) items.




Date:    Sun, 20 Jul 1997 18:08:42 -0400
From:    Jeremy Roberts 
Subject: large font help - thanks!

Thanks to everyone who sent me the answer to my "large font" question...
It works like a charm.

I am LOVING this app!!!!!!!

You guys are awesome.

I compiled my first stand alone patch last night and I'm blown away. Now,
time to make it look good.

All the best,


p.s. I know I'm only scratching the surface here, but the fact that MAX
can basically do anything is mind blowing.


Date:    Sun, 20 Jul 1997 18:08:44 -0400
From:    Jeremy Roberts 
Subject: how do I... ?

OK, for my 2nd patch, I want to enhance the patch chain operation of the
Studio 5.... Once I've made my patch chain, I will make a list of the
patch numbers. MAX will display the current patch number (very easy,
simple pgmin) but I want to also have a message box display the "next"
patch in the chain (also easy).

Now, the chain is fixed... this is for a long-running Broadway musical...
it will NEVER change. HOWEVER, if the musician overshoots the patch,
using a "next" or "previous" pedal, they need the ability to jump to a
particular sub-section start and find the correct place in the chain. ALL
the time, I want MAX to tell them where they are, and what's next.

I would still use the S5 so that the processing and routing happens in

Here is what I think I want to do:

Event numbers in the chain and pgm #'s in S5 will be independent of each
other. The patch chain can have hundreds of events, but the S5 limits me
to 127 patches. Not a problem.

Make a list of the event #'s with corresponding patch #'s. This is the
patch chain list.

An incoming controller will bang the next event#, sending the pgm # to
the S5.

I have to make it so the musician can skip to a specific event #, but
understanding the limit of midi pgm #'s, we can limit it to a little more
than 100 unique event numbers for jump-to's.

So here's my problem...

I have successfully made my patch with pgmin, a menu list showing current
and next and a pgmout, to the studio 5.

***I can not figure out the best way do the "next" bang event.***

I keep getting into loop situations. I need advise.

Is it appropriate/good nettiquite to post a script to the list? It's not
all that long...

Has anyone done anything like this? Anyone who can shed some light on
this to a MAX beginner is much appreciated.

Thanks in advance for any tips.



Date:    Sun, 20 Jul 1997 18:33:24 -0400
From:    Tom Igoe 
Subject: codeWarrior

Sorry for the repeat, but I had a disk crash and lost all my mail archives
from this list (among other things).  Someone mentioned here a while back
(I think it was here) about a really really cheap price on Code Warrior.
Anyone got the details?

Tom Igoe
Digital Whatsis


End of MAX Digest - 19 Jul 1997 to 20 Jul 1997