Subject: MAX Digest - 16 Apr 1998 to 17 Apr 1998
Date: Sat, 18 Apr 1998 00:01:21 -0400
From: Automatic digest processor 
Reply-To: MAX - interactive music/multimedia standard environments
     
To: Recipients of MAX digests 

There are 12 messages totalling 289 lines in this issue.

Topics of the day:

  1. jimmies.Max on the NeXT
  2. MSP buffer~ and capture~
  3. jimmies
  4. bpatcher works differently in 3.5.8? (2)
  5. Patcher printout (2)
  6. MSP Decision Objects (2)
  7. Label, okcancel, project, unlist for PPC (2)
  8. MSP, latency, and virtual memory

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

Date:    Thu, 16 Apr 1998 23:21:19 -0600
From:    =cw4t7abs 
Subject: jimmies.Max on the NeXT

>>Date:    Thu, 16 Apr 1998 00:19:20 +0200
>>From:    dudas 
>>Subject: Re: jimmies
>
>>The "Original Flavor Jimmies" are indeed available for MSP.
.....................
immediatelyu open up old
>>patches from Max on the NeXT and run them more or less as-is (90% of the
>>time).

open up old patches from max,
on the next, + run them mor etc

or

open up old patches from max on the next,
+ run them etc.

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

Date:    Fri, 17 Apr 1998 06:48:16 +0200
From:    dudas 
Subject: Re: MSP buffer~ and capture~

>>When you're doing analyzation of the signal which is 512 samples long it
>>can very confusing to turn that into milliseconds.
>
>Assuming sample rate of 44.1k
>
>(1000/44100) * 512 = 11.609958 ms

Don't forget the technical note in the MSP manual (sorry I don't have a
page number right now) that the 512-sample wavetable is actually 513
samples long, with the first sample duplicated at the end.

In come cases you might want to specify a 513th value if it is different
from the first sample value (when you are using the buffer~ for something
other than an oscillator wavetable - like a panning curve, for example).

Therefore: (1000/44100) * 513 = 11.632653 ms

Although I'm usually paranoid about these numbers and how they will be
interpreted in terms of samples, MSP seems to be very reliable about the ms
to sample conversion.

-R

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

Date:    Fri, 17 Apr 1998 07:19:56 +0200
From:    dudas 
Subject: Re: jimmies

>>The "Original Flavor Jimmies" are indeed available for MSP.
>>They are available through the Ircam Forum, and I believe they are a bonus
>>for those people who buy MSP from Ircam.
>
>
>!nformd dzat not yet ava!labl.

They have been available since April 1st - no joke!!

-R

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

Date:    Fri, 17 Apr 1998 09:48:06 -0500
From:    Steve Smith 
Subject: bpatcher works differently in 3.5.8?

It appears that the bpatcher works differently in Max 3.5.8 with regards
to items it covers.  Now any visible objects it covers are rendered
inoperable, whether they've been moved last before locking the patch or
not.

Is this perhaps true only on my Powerbook 1400cs running OS8?

Regards and remember -- When decanting wine, make sure that you tilt the
paper cup and pour slowly so as not to "bruise" the fruit of the vine.

S.Smith

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

Date:    Fri, 17 Apr 1998 12:26:52 -0400
From:    Stephen Kay 
Subject: bpatcher works differently in 3.5.8?

>It appears that the bpatcher works differently in Max 3.5.8 with regards=

>to items it covers.  Now any visible objects it covers are rendered
>inoperable, whether they've been moved last before locking the patch or
>not.

I don't know about this, but I will comment on one thing:  the old
trick of moving objects last which you want to be frontmost when
locking the patcher has not worked since 3.5.x.  David Z. changed
the way things work by introducing 3.5.x's Front/Back feature.

(I'm sure David will correct me if the following is wrong, but my
understanding is):
All of the objects in a patcher window are stored in memory as a
linked list (i.e. each object has a pointer to the next object =

in the patcher, with the last object pointing to nil).  In 3.0 and
earlier, the list was maintained in the order of how the objects
were moved; i.e. moving something moved it to the end of the list
(or the front?) Anyway, the end result was that you could control
layering of objects by the order in which you moved them before
saving the patcher.  The object you wanted furthest in the back
(bottom layer) would be the thing you moved last before lockinh
the patcher and saving.

In 3.5.x, the list is (apparently) maintained basically in the =

order that objects are created; however, the Front/Back commands
modify the list in some way to control the layering when the
patcher is created.

That is why, BTW, that carefully layered interfaces created in
3.0 do not necessarily have the same layering when being opened
in 3.5.x for the first time...

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
--------------------------------------------------------------------

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

Date:    Fri, 17 Apr 1998 07:13:50 -1000
From:    Matthias Hoffmann-Kuhnt 
Subject: Patcher printout

Dear Maxers,
I am trying to get a printout of a large and complex patch ( larger than
one page).
So what I was doing was to scroll through the different part and have a
little overlap to get the printout, but only the first page (upper left
corner) then is printed out. the rest comes out as a white page... any
suggestions???
also sometimes if I try to scroll to the other end and print that when I
say print the computer crashes!?! What do I do ? is that a memory problem
or what?
THX
Matthias

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

Date:    Fri, 17 Apr 1998 16:48:39 -0400
From:    Stephen Kay 
Subject: Patcher printout

>I am trying to get a printout of a large and complex patch =

>( larger than one page).

Max does not handle printing very well.  Many people do screen dumps,
then use SimpleText or Photoshop to print out a patch.

Another thing you can do, although I haven't tried this in awhile
but it used to work for me, is to position the patcher so that you are
at the upper left hand corner; then reduce the size (assuming you
are using a LaserWriter) to something like 60% or 80% in the Print
dialog (or Print Setup Dialog) before printing.

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

         feeling, and functioning patchers and applications.
                        Demos available at:
                    http://www.musikinetix.com
------------------------------------------------------------------

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

Date:    Fri, 17 Apr 1998 17:04:36 -0400
From:    Michael Sweet 
Subject: MSP Decision Objects

What other objects in MSP make decisions besides <~ and >~?

Here are some other suggestions for new objects.....It would be great to
someday also have the 'and' operator and the 'or' operator?  Also an 'if
then', 'maximum', and 'minimum' objects for MSP would be greatly
appreciated.

--Michael Sweet

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

Date:    Fri, 17 Apr 1998 15:31:48 -0700
From:    Kevin Walker 
Subject: Re: MSP Decision Objects

>What other objects in MSP make decisions besides <~ and >~?
>
>Here are some other suggestions for new objects.....It would be great to
>someday also have the 'and' operator and the 'or' operator?  Also an 'if
>then', 'maximum', and 'minimum' objects for MSP would be greatly
>appreciated.

Could you describe in more detail how you envision such objects working?
Would 'max' and 'min' be over an entire signal buffer?  Or would it take
two or more signals and compute once per sample?  Do 'and' and 'or' make
sense for floating point signals?

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

Date:    Fri, 17 Apr 1998 17:36:46 -0500
From:    Steve Smith 
Subject: Label, okcancel, project, unlist for PPC

Dear authors of Label, okcancel, project, & unlist;

Just a plea for the esteemed authors of these objects to update them to
PPC versions, if at all possible.  I'm sure this is a pain to go back to
do, so if it's not possible or convenient, c'est la vie!!

Have a good day and remember -- When  sending your wife down the road
with a gas can, it is impolite to ask her to bring back beer.

Steve Smith

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

Date:    Fri, 17 Apr 1998 19:16:38 -0400
From:    Stephen Kay 
Subject: Label, okcancel, project, unlist for PPC

>Dear authors of Label, okcancel, project, & unlist;

>Just a plea for the esteemed authors of these objects to update them to
>PPC versions, if at all possible. =

>Steve Smith



The MegaMAX collection contains "confirmBox", which does all
of what "okcancel" did, and far more - set up completely custom
modal dialog boxes (Macintosh, not fake max patcher windows)
with 1 to 4 buttons, set the text and button text, add icons, =

find which button the user clicked, etc. And it's FAT.

Since you already own it, Steve, why not check it out? ;-)

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

         feeling, and functioning patchers and applications.
                        Demos available at:
                    http://www.musikinetix.com
------------------------------------------------------------------

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

Date:    Fri, 17 Apr 1998 19:11:59 -0700
From:    Kevin Walker 
Subject: MSP, latency, and virtual memory

Perhaps most people already know this, but in case not...

After some recent system crashes (unrelated to Max), I noticed that the
latency in an MSP MIDI instrument I had been working on had become
unacceptably bad.  Previously, there was no perceptable delay between
pressing a key on my (MIDI) keyboard and the resulting sound.  Suddenly the
response time was lousy.  After a few minutes I figured out that restoring
my System file had turned virtual memory on.  (I usually keep it off.)
Turning VM off fixed the problem.

The moral: Turn VM off if you want MSP to be responsive to external events.

(I don't recall seeing this advice in any of the documentation, but maybe I
missed it.)

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

End of MAX Digest - 16 Apr 1998 to 17 Apr 1998
**********************************************