Subject: MAX Digest - 2 Nov 1999 to 3 Nov 1999 (#1999-317)
Date: Thu, 4 Nov 1999 00:00:13 -0500
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 11 messages totalling 319 lines in this issue.

Topics of the day:

  1. MSP doesn't like my Audiomedia III (2)
  2. good news and bad news: Digigram VXpocket+ASIO2
  3. Digi 001
  4. Lpair Lproblem?
  5. jMax
  6. tcin object
  7. aesend/receive
  8. MSP and MOTU-2408, USB keyboard (2)
  9. That old rescopy() feeling


Date:Tue, 2 Nov 1999 21:25:51 -0800
From:David Zicarelli <zicarell@CYCLING74.COM>
Subject: Re: MSP doesn't like my Audiomedia III

MSP loves your audiomedia III. Please read on.

"please. Thank you very much." <Wiltz0023@AOL.COM> writes:

>I recently authorized MSP and it will not recognize my Audiomedia III card.
>When I startup MAX I receive an error message in the MAX window that says,
>Direct I/O Audiodriver: error-6011 acquiring device.

I think I finally figured out that this guy was trying to run
Protools (DAE) and MSP at the same time. Error -6011 means the
device has already been acquired. Direct I/O allows only
one client to access the hardware at once. They don't call it
Direct I/O for nothin'. They do have a new standard in development
called Direct Connect that, when I implement it in
MSP, will allow MSP to play into Protools, maybe even get
audio from Protools. Whoopee.

heiniger <W.Heiniger@UNIBAS.CH> writes:

>observed exactly same behaviour.
>Asked techsupport at Cycling : no answer so far ...
>bizarre ...

Uh, I answered within about an hour of getting this guy's
email. It bounced.

Bounced e-mail is a little like getting a busy signal when
calling someone back. You'll never remember to keep trying
and then people hate you.

David Z.


Date:Tue, 2 Nov 1999 21:32:02 -0800
From:David Zicarelli <zicarell@CYCLING74.COM>
Subject: Re: good news and bad news: Digigram VXpocket+ASIO2

Kasper T Toeplitz <kasper@CLUB-INTERNET.FR> writes:

>According to a recent mail from Digigram (asking about those very same
>issues) they tell me than "in theory" the latency is 75ms, but than Cubase
>(with ASIO driver) claims it to be 42ms
>Also they ship the card with both Sound Manager& ASIO drivers
(and have
>never tried with MSP, but "it should work" - so they say)

I don't know whose theory it is, but their buffer size is 2016
samples. Assuming no processing time (a bad assumption), we have
an absolute minimum I/O latency of (2016 * 2) / 44.1 = approx
91 ms.

>a question - I have seen all those ads for Cubase with ASIO II which claim
>you can have
0ms (!) latency time

This isn't latency for input-output or for doing something
spontaneous such as triggering a sound from MIDI or the
mouse/keyboard. It might be that they think MIDI and audio are
happening at the same time because ASIO II lets you know
about the latency of the card in relation to timecode or
some such thing. It has nothing to do with the way most people
would use MSP with an audio card.

David Z.


Date:Tue, 2 Nov 1999 21:36:12 -0800
From:David Zicarelli <zicarell@CYCLING74.COM>
Subject: Digi 001

According to my source at Digidesign, the Digi 001 will work
with MSP (and he's even "flame tested" it), but it has one of
those typical Digidesign issues that should be ever so familiar
to readers of this list.

Apparently the 001 has a MIDI interface in it, and they use the
same one-app-at-a-time driver to do the MIDI. So if OMS is using
the 001's MIDI driver, it thinks the device is busy when you
try to acquire it to do audio.

(I guess Protools has a secret way around this or something.)

Anyway, remove the MIDI driver from your OMS folder and you can
use the audio.

Tech support people the world over must love Digidesign.

David Z.


Date:Tue, 2 Nov 1999 23:27:40 -0700
From:Charles Lyons <charleslyons@EARTHLINK.NET>
Subject: Re: Lpair Lproblem?

Profuse if belated thanks to Peter Elsea for his amazingly fast response.
It really doesn't get any better than that - I'd only just started to think
of workarounds, and now I don't have to. Really made my day.

When's the next time someone here plays in Southern California? I missed
the last one for a chance to see Vonnegut.


Date:Wed, 3 Nov 1999 02:49:28 -0500

From:Louis Klepner <lou@EXPRESSIVEIMAGING.COM>
Subject: jMax

David Z.-

Can you comment at all on how IRCAM's jMax will relate to Max? Will
there be hope of porting patches created in Max to JMax for use on PC's? Any
information regarding the intergration of Max and JMax would be greatly
appreciated. Thanks.

-Louis Klepner


Date:Wed, 3 Nov 1999 13:31:15 +0100
From:Melvyn Poore <mpoore@BIGFOOT.DE>
Subject: tcin object

Hi folks,

Where can I get information on the tcin object. It has no help, does not
appear in the manual.



Melvyn Poore
Uferstrasse 166
D-53859 Niederkassel

Tel: +49-2208-911217
Fax: +49-2208-911218
see also:


Date:Wed, 3 Nov 1999 14:56:59 +0100
From:Manuel Poletti <Manuel.Poletti@IRCAM.FR>
Subject: Re: aesend/receive

Aesend/receive can be found there:



>Sorry if this has been discussed before:
>Is there a PPC version of aesend and aereceive and where?
>Jeff Burns

IRCAM Forum technical support
tel : (33) (0)1 44 78 16 05
email :


Date:Wed, 3 Nov 1999 10:40:09 -0800
From:Ian Knopke <iknopk@PO-BOX.MCGILL.CA>
Subject: MSP and MOTU-2408, USB keyboard

Does anyone have any experience with the new MOTU 2408 card and MAX/MSP? We have recently
acquired one of these things and have discovered some problems with certain kinds of
patches causing the computer to crash and/or lockup. The patches seem to work fine if the
MOTU sound driver is disabled and the basic Macintosh driver is restored. This is running
on a G3 with system 8.6. Without doing too much experimentation, this seems to involve at
least the FFT~ object, but might also be a combination of several objects. The 2408
configuration program that comes with the card is a little flaky to start with, menus seem
to disappear and or change, but I'm not sure that is the problem because I thought MSP used
it's own driver not provided by MOTU. Any workarounds / comments / suggestions?

On a separate note, there is also a report that the key object has difficulties on the same
machine. It seems that after receiving a single keystroke the machine seems to refuse to
accept any new input, making it impossible to even quit the program! Haven't seen this one
myself yet, just passing it along. Is this something to do with a USB keyboard or just
excessive solar flare activity?

Maybe our machine is having pre-Y2K jitters.

Ian Knopke


Date:Wed, 3 Nov 1999 11:23:54 -0800
From:Peter Elsea <elsea@CATS.UCSC.EDU>
Subject: Re: MSP doesn't like my Audiomedia III

I've had the same experience-
I updated MSP on a 9500 with AMIII (system 7.6) that has been running it
well for years (The same setup I used to beta test msp in fact). It ran for
a bit, then one afternoon would not. Naturally this was during class.

Eventually, to get it sorted out, I replaced the Direct I/O MSP Audiodriver
Jan 4 1999
with Direct I/O MSP Audiodriver Nov 26 1997.

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


Date:Wed, 3 Nov 1999 23:12:36 +0100
From:Timmy B <tim@TIMESUP.ORG>
Subject: That old rescopy() feeling

Hi Kids,

looking in the archive to find the source of my problem,
which for completeness is:

error: rescopy: failed to add CCOD -1, error -194

and other such niceties at boot time, I am told to empty
the trash. So I did and it didn't help. Any more clever ideas?
I have this happening on several (well, two) machines. The
only really different thing from a standard install is
the I-Cube objects....

Hope someone can help,


-------- ------------------------------------
\/Industriezeile 33 B
/\A-4020 Linz
-------- ------------------------------------
! Help B92 and the independent media in Yugoslavia:!


Date:Wed, 3 Nov 1999 17:11:19 -0500
From:Christopher Murtagh <chris@MUSIC.MCGILL.CA>
Subject: Re: MSP and MOTU-2408, USB keyboard

At 10:40 AM -0800 11/3/99, Ian Knopke wrote:
>Does anyone have any experience with the new MOTU 2408 card and
>MAX/MSP? We have recently
>acquired one of these things and have discovered some problems with
>certain kinds of
>patches causing the computer to crash and/or lockup. The patches
>seem to work fine if the
>MOTU sound driver is disabled and the basic Macintosh driver is restored.

I've been using MSP with a 2408 for some time and it has been
working really well (beige G3, OS8.6 and OS9). Haven't had many
problems with the configuration software either, perhaps your
connection to the breakout box via the 1394 (ie firewireish - MOTU
calls it'audiowire') cable is not very stable. Either that or
someone has installed some funky stuff on the machine that shouldn't
be there. I have seen cases where the connection wasn't very good and
heard rumours of MOTU sending out replacement cables.

Now if you want to talk about the problems with Digital Performer
2.61.... that's a long story.




End of MAX Digest - 2 Nov 1999 to 3 Nov 1999 (#1999-317)