Subject: MAX Digest - 6 Sep 1999 to 7 Sep 1999 (#1999-266)
Date: Wed, 8 Sep 1999 00:00:00 -0400
Automatic digest processor <LISTSERV@LISTS.MCGILL.CA>
Reply-To: MAX - Interactive Music/Multimedia Standard Environments <MAX@LISTS.MCGILL.CA>
To: Recipients of MAX digests <MAX@LISTS.MCGILL.CA>

There are 6 messages totalling 193 lines in this issue.

Topics of the day:

  1. newbie question; also: AW8/ASIO
  2. video out, startup sound
  3. startup sound
  4. hardware issues
  5. MSP/PowerBook/kaboom
  6. oms timeout problem w/MOTU Pocket Express midi interface


Date:Mon, 6 Sep 1999 19:25:46 -0700
From:M Stevens <m@SOLIPSIST.ORG>
Subject: Re: newbie question; also: AW8/ASIO

>I have created a patch which generates a pulse (300ms apart) using a
>metro and an oscillator. I notice that there is an unacceptable degree
>of latency - four or five 'notes' are perfectly spaced then there is a
>small delay, then the cyle repeats. Can anything be done about this, or
>does anyone know of the cause?

I recently started working w/ MAX/MSP and had what sounds like the same
problem. I fixed it by turning on overdrive ( options menu ), making all my
vector sizes as small as possible ( dsp status window ) and checking
"scheduler in audio interrupt" ( also in the dsp status window ). I assume
this must be a fairly common new-user issue.

On an unrelated note, my soundcard at present is an AudioWerk8. I'm trying
to access it using the MSP ASIO driver and am getting the folowing error
message at startup;
MSP ASIO Audiodriver: min buffer size (4096) too large
anybody know what's up w/ this?

+ M Stevens + +


Date:Tue, 7 Sep 1999 09:39:21 +0200
From:Jeffrey Burns <jeff@BERLIN.SNAFU.DE>
Subject: video out, startup sound

>I don't know if there is a video card I could buy that would
>give better results going out the video port, one of those
>ixMICRO or TARGA devices perhaps. I don't want to play games, I
>just want better video out the ports and I don't really know if
>these would help. Adding the 2 megs of video ram is also an
>option, but I don't see how that would improve the signal.

Tha MacPicasso graphic cards 540 and 850 have an optional video output
module that sends the content of the monotor out in video format.

Perhaps those who really want to kill the startup sound should install an
on/off switch to the Mac's internal loudspeaker ;-()

Jeff Burns


Date:Tue, 7 Sep 1999 10:19:46 +0200
From:Peter Castine <pcastine@PRZ.TU-BERLIN.DE>
Subject: Re: startup sound

On around 5=AD9=AD99 8:21, christophe charles said something like:

>well it didn't mute after a crash...
>btw does anybody knows who is the composer
>of the mac startup sound ?

Not sure about the current lot of Macs, but Marc Lentczner was part of
the engineering group who built the Mac II and he told me that he'd done
the resonant major triad on that machine.

But that was a long time ago...



Dr. Peter Castine| Benefit Concert for Disaster Relief in the
4-15 Music & Technology| wake of the Turkish Earthquake:
| St. George's Church (Preu=DFenallee 17-19)
| in Berlin on Friday, Sept. 10, 8:00 pm
| Artists from 5 continents performing music by
| W.F. Bach, Brouwer, Faur=E9, Gershwin, Schubert
| and Sibelius. Please come.


Date:Tue, 7 Sep 1999 11:19:32 EDT
From:Eric Lyon <Eric.Lyon@DARTMOUTH.EDU>
Subject: hardware issues


Has anyone had problems with losing control of the mouse and/or keyboard while
using MAX/MSP? I have a G3 400MHz and find this happens on a regular (but not
predictable) basis. Are there any strategies for avoiding or ameliorating this


Eric Lyon



Date:Tue, 7 Sep 1999 13:37:31 +0000
From:John Phillips <jpch@TERRAGIZMO.NET>
Subject: MSP/PowerBook/kaboom

Hi all-

I have tried everything I could think of to solve the following problem-
perhaps some has some advice. Bronze PB 333; OS8.6; latest Max/MSP. I have
built a panel of 8 modules, some using sfplay~,one with groove~, several
with buffers and play~. One very simple MIDI seq. running. I have used
pcontroland a coll to have several on at any one time. I am in that
frustrating period of seeing how long it's gonna run and strangely it's
about 130-150 minutes. The first two times it was -exactly- 132 minutes.
The sound kept going but not changing coll selections. Mouse froze, wouldn't
restart etc. Reset the "sleep" settings to "never" and it ran to 157
minutes then had a stack overflow. (Wonder what that means in MSP because
I'm pretty sure it isn't my 47 event MIDI seq.). I clicked my way out of
that one with Resume but nothing worked quite right with my coll. Just
recently it went to around 140 minutes and Error Type 2 occurred.

Should configuration setting be a 5ms?
My vectors are 256 each
I'm in overdrive without audio interrupt
The patch has 19 signals and 345 function calls
Approx. 60 megs of RAM free after loading
CPU is around 45-58% tops

Another odd thing about this patch: it saves as text a lot - I'm always
having to change it back to "normal."

Thanks for your time,

John Phillips / sound artist:


Date:Tue, 7 Sep 1999 15:57:58 -0400
From:"Daniel C. Heidebrecht" <dan@WDE.COM>
Subject: oms timeout problem w/MOTU Pocket Express midi interface


I'm having trouble sending midi clock information to a synthesizer
through a MOTU Pocket Express midi interface with Max 3.5.9-9 and OMS

I have no problem sending clock to a synth with my sequencer (Digital
Performer) - which is set up to use OMS with the latest version of

I have tested this with the help file for the timeout object and all of
the various formats the timeout object sends.

I saw a message in the archives about using the rt objects to send midi
clock messages (248,249 & 250, I think) - but I also need to send SMPTE
30 fps non-drop too.

Has anyone successfully used MOTU interfaces with the OMS timeout
object in Max?


Daniel C. Heidebrecht


End of MAX Digest - 6 Sep 1999 to 7 Sep 1999 (#1999-266)