Subject: MAX Digest - 16 Oct 1998 to 17 Oct 1998 (#1998-39)
Date: Sun, 18 Oct 1998 00:00:00 -0400
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
To: Recipients of MAX digests 

There are 10 messages totalling 502 lines in this issue.

Topics of the day:

  1. glassbeadz=w!nner=kreate mozt elaborate tr!k
  2. filename object
  3. check failed zgetfn
  4. Joysticks for Max/Mac? (2)
  5. BeOS and custom movie
  6. Unsig~?
  7. BeOS (long post)
  8. vst and adc~?
  9. Wuttdu Ph|_|KK

Email to MAX should now be sent to
LISTSERV commands should be sent to
Information is available on the WEB at


Date:    Sat, 17 Oct 1998 00:14:17 -0400
From:    =cw4t7abs 
Subject: glassbeadz=w!nner=kreate mozt elaborate tr!k

re: david stevens' querr! on ga!n kontrol.
ma! w!sh 2 !mplement 1 agc such az dzose oftn
!mplementd !n hear!ng a!dz.


- a. amer!kka...d.fekatd upon ent!re veLt
w!th free !dealz. kap!tal!zm + loose women...
komp!l!ng > | < a trap spy at A000
s!mulacrum . d-konztrukt!on = ovrkompensat!on
kort!k-L rEsponsEz.


Date:    Sat, 17 Oct 1998 13:57:46 +0200
From:    Peter Swinnen 
Subject: Re: filename object

dominic robson  wrote

> Is there an object that will allow me using the standard Mac read file
> dialog to load and be able to access just the filename chosen

My external "filename" does exactly that. I also wrote an external
"pathname" which, in conjunction with David Z's "odoc", allows users to
load a data file into your patcher by double-clicking from the Finder.
Great for stand-alones with unique crator-types!

Check them out at my web site on

Happy Maxing,
Peter Swinnen


Date:    Sat, 17 Oct 1998 15:22:59 +0200
From:    Oeyvind Brandtsegg 
Subject: Re: check failed zgetfn

Thanks a lot for the info.
Now I've gotten rid of the error message,
I haven't tested it thoroughly to see if the error is *really* gone,
but it seems nice and smooth now.
Guess I just got paid for keeping most of the subpatcher stuff in separate
files :-)

btw. the error patch was used as a bpatcher, if that could be of any use
for others to know... (?).

One more related question.
I noticed that when this error message appear in the max window while
opening a patch,
if I then close the patch, and then re-open it, max will freeze/crash my
This also happens with other patchers sometimes, without no error message

Is it possible that this kind of error might appear "silently", e.g.
without printing an error in the max window ?

Oeyvind Brandtsegg

Stephen Kay wrote:

> >Oeyvind Brandtsegg:
> >Does anyone know what the max window error message:
> >check failed zgetfn (loadbang): corrupt object
> >actually means, and what I could possibly do to get rid of it.
> It means that something has gotten corrupted in your patch.
> It's a horrible, difficult to locate problem that has happened
> to me several times.  What I have done in all cases was start
> deleting sections of the patcher, and resaving it with a different
> name.  Then close/open it again.  Repeat until it goes away and
> you have possibly located the offending section.  I say "possibly"
> because in some cases, I never really located it, but just
> the activity of moving things around and resaving causes the
> data to get saved again correctly, and the problem goes away.
> If you do locate the offending section, you can recreate it, or
> move things around, etc.
> Note: sometimes the "repeat until it goes away" section above
> requires that you quit and restart Max every time you test the
> patch with a section removed.
> Stephen Kay
> ---------------------- The MegaMAX Collection ----------------------
>  Over 30 Max objects for the creation of more professional looking,
>          feeling, and functioning patchers and applications.
> --------------------------------------------------------------------
> Email to MAX should now be sent to
> LISTSERV commands should be sent to
> Information is available on the WEB at


Date:    Fri, 16 Oct 1998 09:29:38 -0500
From:    Bob Falesch 
Subject: Re: Joysticks for Max/Mac?

On Tuesday, 28 Jul 1998  Stephen Kay wrote:

> Thanks to all who replied concerning joysticks.
> I have a SideWinder arriving today...


Have you had a chance to work with the SideWinder and MAX?   Any


Date:    Sat, 17 Oct 1998 11:50:52 -0400
From:    Stephen Kay 
Subject: Re: Joysticks for Max/Mac?

>On Tuesday, 28 Jul 1998  Stephen Kay wrote:

>> Thanks to all who replied concerning joysticks.
>> I have a SideWinder arriving today...

>Have you had a chance to work with the SideWinder and MAX?  =

>Any observations...?

Actually, I bought it and worked with it only briefly before
getting SideTracked (haha) but it seemed to work very well,
and was easy to interface to Max.  I hope to get back to =

what I originally intended to do with it soon!

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

         feeling, and functioning patchers and applications.
------------------------ Free Max objects! -------------------------


Date:    Sat, 17 Oct 1998 22:10:40 -0000
From:    Peter Castine 
Subject: Re: BeOS and custom movie

On around Fri, 16 Oct 1998 03:17:03 -0400 =cw4t7abs 

>zuper koll!der = altzo be!ng portd 2 beos

With both SuperCollider and Max available on BeOS, the question I want to
no the answer to is:

     What's the status of BeOS on G3s?

I haven't been following this for a while, but last time I looked G3s
weren't yet supported. Anyone have some good news?

On Thu, 16 Apr 1998 14:46:01 +0200 subcontrol@MUU.AUTONO.NET asked,
quoting someone else:
>>>Jeff Burns just showed me a revised movie object by Peter Castine that
>>>positions itself off to the side without the title bar to use with a
>where is this object available  ?

It's not really "available" anywhere. This is the deal: David Z. sent me
the source code to his movie/imovie object (they are both in one .c file
and are only distinguished by some conditional compilation). I tweaked
the source code so Jeff would have a version that positioned itself more
neatly for his needs. This was ages ago, and I forget the details. Either
it was so the object would remember where you positioned its window, or
(more likely) I just hard-coded the top-left corner so that the window
frame would surround Jeff's second monitor.

Since this was no more than a one-off special-purpose hack/patch that was
made to handle one person's very specific needs (particular monitor
sizes, particular monitor alignment, particular movie X/Y dimensions), I
had no intention of distributing the thing. It's not "original work"
(well, if "Lord of the Dance" counts as original work, than maybe this
does, too). Whatever: the thing was not intended for world-wide
distribution. If people are interested in seeing a more flexibly
positionable movie object, they should promise David that they'll buy
extra copies of MSP when the enhanced object becomes available (that
ought to provide the correct motivation). Donate them to charities. Or
donate an MSP license to me; that's the sort of motivation I would need
to spend the time needed to do the job right.

This is the second time I've had to write about the patched movie object
in a week. Maybe there is a need after all?



Dr. Peter Castine          | I am very pleased to announce that the
4-15 Music & Technology    | 26th International Computer Music Conference
                           | will take place in Berlin in the year 2000.
                           | We look forward to seeing you here!


Date:    Sat, 17 Oct 1998 14:45:21 -0700
From:    Patrice Coulombe 
Subject: Unsig~?


How can I convert a signal value to a max ordinary message? (A kind of

It could be useful for manipulating the output of a line~ (for exemple).


Get your free address at


Date:    Sat, 17 Oct 1998 15:15:43 -0700
From:    Richard Zvonar 
Subject: Re: BeOS (long post)

At 3:10 PM -0700 10/17/98, Peter Castine wrote:

>     What's the status of BeOS on G3s?

Here is the straight dope, direct from Be, Inc.:

Q:  Does the BeOS run on Apple's new "G3" Power Macs, which use the PowerPC
750 (or "G3") processor?

A:  No, the BeOS is not compatible with Apple's "G3" systems. We have
requested from Apple the detailed technical specifications we would need to
provide support for these systems, and Apple has declined our requests.

This information, concerning the design of the logic board (including
information about address spaces, etc.), is available only from Apple, and
they do not make this information public to anyone (anymore; they used to
give it to Mac clone makers). Without this technical information, it is
impossible for us to support the new hardware.

Q:  Can't you reverse engineer the information you need to run on Apple's
"G3" machines, maybe from LinuxPPC, which runs on such systems?

A:  No. Partly it's because we're nervous about porting to a platform who's
owner doesn't want to share technical information. Sure, we could figure it
out, with help from Linux source, but that's a tricky way to build a
commercial, stable platform, and we'd always be at the mercy of
undocumented, unnanounced changes to the hardware.

Even if we did want to take this approach, this would take a lot  of
resources, and we're stretched to the max as it is.

There's also two legal issues, one, would Apple let us do this (who cares
if legally it's OK, they have a lot more lawyers than we do), and two,
could we use the Linux sources and still keep the BeOS proprietary (which
we intend to do, see the FAQ on that).

Q:  Does this mean that Be is abandoning the PowerPC/Power Mac platform?

A:  Not at all! Be fully intends to continue supporting existing BeOS Ready
Systems for as long as possible, and we will add support for new systems
where that is technically and economically feasible.

Q:  So how long will Be support the PowerPC/Power Mac platform? What does
"technically and economically feasible" really mean?

A:  We plan the BeOS two releases out, and that plan shows us shipping
PowerPC (Mac and BeBox) support for (at least) the next two releases. After
that, it depends on customer demand.

That's not just weasel words. By late next year, it's unclear how many
people will actually be using their 2-3 year old Macs running the BeOS. If
Apple has not changed their minds about assisting us in our efforts to add
value to their  hardware, it seems unlikely that many people will want to
run the BeOS on obsolete systems.

Q:  Will the BeOS run on systems with PowerPC 750 ("G3") upgrade cards? How
about upgrading my 6100/7100/8100 with one of Newer's upgrade cards?

A:  The BeOS Preview Release (1 or 2) is not compatible with any system
using a PowerPC 750 processor, whether built-in or added as an upgrade.

The BeOS Release 3 for PowerPC generally works with otherwise BeOS Ready
Systems which have been upgraded with a PowerPC 750 processor card, but
that is not an officially supported configuration.

 As for NuBus-based systems upgraded with PowerPC 750 cards from Newer, or
any other card vendor, the systems remain NuBus-based, and will not be
supported, regardless of the processor inside. The BeOS does not support
NuBus-based systems, period.

Q:  Apple just released a bunch of new CPU models, and yet you haven't
updated your BeOS Ready  Systems page to mention them. Are you compatible
with those systems?

A:  We update the BeOS Ready Systems page on our web site as  soon as we
have verified compatibility with the BeOS, one way or another. Really, we
are maintaining this page!

When new machines come out, from any manufacturer, we  have to obtain and
test them for compatibility, and evaluate how supporting that model will
impact our engineering efforts.

We're a very small company (fewer than 30 engineers!), and so even testing
and evaluation can take some time. Please be patient, we really do put this
information up on the Web as quickly as we can!

Q:  How about PowerBooks or other Mac laptops?

A:  We'd like to support PowerBooks, but the challenges of the very custom
hardware inherent in laptop designs makes this  much more difficult than
supporting the fairly standardized designs for desktop Macintoshes and
Macintosh clones.

We do understand that many PowerBook owners would like the BeOS to run on
their systems, but the engineering challenges are formidable, and at this
time we do not have the technical information necessary to even begin work,
nor does Apple seem inclined to give it to us.

At this time the BeOS is not compatible with any PowerBook system. Maybe in
a future release. Thanks for understanding this issue.

Richard Zvonar, PhD                    
(818) 788-2202 voice                   
(818) 788-2203 fax                     



Date:    Sat, 17 Oct 1998 17:54:33 -0700
From:    Patrice Coulombe 
Subject: vst and adc~?

Is there a reason why vst~ doesn't work with adc~.
Should it be?
Am I doing something wrong?
Thank you for a response.

(to try my TestVST patch, just click on "plug" and choose a VSTplugin)

max v2;
#N vpatcher 9 51 1029 561;
#P message 145 131 34 196617 mix 0;
#P message 146 95 34 196617 mix 1;
#P user meter~ 150 240 230 253 100;
#P user meter~ 340 232 420 245 100;
#P user meter~ 479 134 559 147 100;
#P newex 428 97 29 196617 adc~;
#P user ezdac~ 254 341 298 374 -164954634;
#P user number~ 369 258 408 273 9 3 3 1 0. 0. 0 0.43 250 0.;
#P newex 287 304 27 196617 *~;
#P newex 254 304 27 196617 *~;
#P message 225 116 26 196617 plug;
#P newex 254 195 110 196617 vst~ none;
#P connect 11 0 0 0;
#P connect 10 0 0 0;
#P connect 6 0 0 0;
#P connect 6 1 0 1;
#P connect 6 1 7 0;
#P connect 6 0 7 0;
#P connect 4 0 2 1;
#P connect 4 0 3 1;
#P connect 3 0 5 1;
#P connect 2 0 5 0;
#P connect 1 0 0 0;
#P connect 0 0 9 0;
#P connect 0 0 2 0;
#P connect 0 1 3 0;
#P connect 0 1 8 0;
#P pop;

Patrice Coulombe
Montreal, Quebec, Canada

Get your free address at


Date:    Sat, 17 Oct 1998 21:45:49 -0400
From:    Nicholas Longo <71477.2332@COMPUSERVE.COM>
Subject: Wuttdu Ph|_|KK

Wow Those iMacs sure are selling great aren't they?  You can get em
for only $1299.00 from Mac Zone!  Hurray for Apple!

"From the ethereally translucent cover art to the equally delicate and
beautiful sounds realized inside, this recording [Actuality] will make you
re-think your biases about purely electronic music.  Longo's lengthy
academic and experiential quests into the realms of music perception and
biological cybernetics has led him to create technology [developed in MAX,
patent allowed] which allows his battery of synthesizers to sing, cry, and
sigh the way a violin or guitar can and use them as expressively as any
acoustic instrument.  The result is a lushly arranged ten song set which
melds galactic textures with uncoventionally pretty melodies;  you may not
be able to identify the tones, but their warmth and pleasantness are as
easy to enjoy as a deep, soothing massage.  Wonderful!"

        (       )    (   )
      /                      \
    /                          \
             *)        (*  )   |
   |              O             |
   |                           /
    \         \_______/       /
     \           |_|         /
      \                     /
         \                /
           \  ________  /
               \ | /
                / \               Hey look at me!  I'm a Code Boy!



End of MAX Digest - 16 Oct 1998 to 17 Oct 1998 (#1998-39)