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

There are 5 messages totalling 189 lines in this issue.

Topics of the day:

  1. Patcher printout
  2. jimmies
  3. unlist
  4. hard disk recording in msp
  5. MSP Decision Objects


Date:    Sat, 18 Apr 1998 08:45:20 +0200
From:    Jeffrey Burns 
Subject: Patcher printout

>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

I once had the same problem. Just take one or more screenshots of the
printout areas and print them in Simple Text or Photoshop.

Jeff Burns


Date:    Sat, 18 Apr 1998 08:52:01 +0200
From:    "Dr. Karlheinz Essl" 
Subject: Re: jimmies

The "jimmies" are available on the new CD-ROM of the IRCAM Forum User
Group. However, this is only available for members of that group. I am
wondering if user who did not buy MSP from IRCAM would also have access to
the "jimmies"... I'd appreciate if they could be downloaded from the IRCAM
ftp server.

Here is the list of the available "jimmies" which I extracted from the
manual, sorted by types:


decibel conversion              db1
frequency to radians            hz->radians
radians to frequency            radians->hz
range scaling                   scale


chorusing                       stchorus1~
delay line                      delay2~
flanger                         flange1~
frequency shifter               complex-mod~, fshift1~, hilbert~
hamonizers                      harmv2~, stharms1~
phase shiftor                   phaseshift1~
reverberation                   rev1~, rev4~
ring modulator                  rmod1~
sampling module                 sampv1~


all-pass filters                apass1~, apass2~, apass3~
band-pass filter                bpass1~
comb filters                    comb1~, comb2~
high-pass filters               hpass1~, hpass2~
low-pass filters                lpass1~, lpass2~
notch filter                    bstop1~
parametric EQ                   peq1~, peq2~, peqbank1~
shelving filters                coef_bpass3~, coef _hishelf2~
tone control                    tone1~


mono signal muting              mute1~
mono volume control             gain1~, gain2~
quadraphonic volume control     qgain1~
quadraphonic panning            qpan1~
stereo volume control           stgain1~
stereo panning                  stpan1~


peak meter                      peak~
signal probe for debugging      probe1~
signal capture for debugging    bag~
vu meter                        vu1~

Signal Utilities

ADC with DC filter              adc1~
enveloppe follower              envfol1~
noise detection                 zerocross~
signal energy measure           rms1~


   Dr. Karlheinz Essl - Composer
   Vienna / Austria
   Studio for Advanced Music & Media Technology


Date:    Sat, 18 Apr 1998 10:58:24 +0100
From:    peter elsea 
Subject: unlist

unlist is indeed PPC ready, and has been since the release of 3.5. It is
part of the Lobjects (OK it doesn't start with L) and can be found on the
3.5 CD. Some of the others on the CD are out of date- you can find new
versions at
and some new items, like a sensible counter.

Peter Elsea
Director of Electronic Music Studios
University of California, Santa Cruz


Date:    Sat, 18 Apr 1998 22:08:52 +0100
From:    Jem Finer 
Subject: hard disk recording in msp

Is there a way, a la Super Collider, to record the output of an MSP patch
straight to hard disk or is it  a case of using record~ and a very large
buffer ?


Jem Finer

Kentish Town
London NW5


Date:    Sat, 18 Apr 1998 18:03:57 -0400
From:    Michael Sweet 
Subject: Re: MSP Decision Objects

Kevin Walker wrote:

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

Good questions.

I'm trying to build a phonetic recognition patch without having to write my
own object (cause I'm a really bad C programmer).  If I do an fft on a wave
which works in real time I need fast objects to analyze the wave and tell
me where the forments are (the 3 or 4 loudest frequencies in the signal).
Max and min could work over a specified period of time on a buffer~ to tell
me at what frequency the maximum signal is.  Its more complicated than that
but thats the general idea.

'&&~' and '||~' objects would allow me to make multiple comparisons on
different parts of the wave. For instance I would like to compare the
current signal with another signal (easy enough with the >~ object), then I
need to find out whether that signal is also greater than my stored highest
position; if it is store it, if not throw it away.  Then  when I get
through analyzing all 512 samples I can have my own maximum~ object.

My biggest problem with this is I don't know how to store just one value in
a buffer and then use it in real time dsp.  I've tried to do all this using
the sah~ as well as delta~ and I haven't got it working quite yet.  In fact
this easy object sounds so complicated to do using just the >~ and <~ that
I've pulled out my C books.

I've only been using MSP for a month now, and as when I first learned Max,
I keep asking stupid questions.  Half of my problems I figure out before I
get a response from the list.

Thanks Richard Dudas for your comments about about the pages I missed in
the MSP manual about 512 vs. 513 sample lengths and buffers.

Any other comments would be greatly appreciated.

--Michael Sweet


End of MAX Digest - 17 Apr 1998 to 18 Apr 1998