Subject: MAX Digest - 1 Apr 1999 to 2 Apr 1999 (#1999-103)
Date: Sat, 3 Apr 1999 00:00:01 -0500
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
     
To: Recipients of MAX digests 

There are 10 messages totalling 328 lines in this issue.

Topics of the day:

  1. q's: bit decimation etc
  2. ignore/respond to click (2)
  3. Bomb and MSP
  4. new objects on Ircam's ftp
  5. Max-and blue-G3
  6. fsplit
  7. MAX Digest - 31 Mar 1999 to 1 Apr 1999 (#1999-102)
  8. Matrixes
  9. protools i/o >> msp

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

Date:    Fri, 2 Apr 1999 09:56:58 -0800
From:    Kim Cascone 
Subject: q's: bit decimation etc

anyone know of a way to reduce the bit depth of an .aif file/adc in MSP?
also does anyone know offhand where a list of the messages to MSP (for
example: ";dsp status") would live in the manual?
thanks in advance,
KIM

__________________________
sound.designer...composer

kim@anechoicmedia.com
http://www.anechoicmedia.com

Out Now:
                blueCube( ) (Rastermusic)
                nb2e_Vortex.aiff (Mille Plateaux)
                vortexShedding (Caipirinha Music)

"the medium is no longer the message, the tool has become the message"

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

Date:    Thu, 1 Apr 1999 23:56:00 -0800
From:    David Zicarelli 
Subject: Re: ignore/respond to click

>Max' user interface object seem to react to a message beginning with
>"click" in order to make them ignore/respond to mouse clicks.
>I tried several second arguments to "click" (on/off, 1/0,...) but did
>not find...
>Does anyone know this second argument?

Even if you could get the "point" structure correctly
formatted in Max, which you can't, click messages to
objects are messages that cannot be sent to an object
via its inlets. In the parlance of Writing External Objects
for Max, they have "A_CANT type specifiers."

Or, if you like Moliere, because it has a dormitive principle.

David Z.

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

Date:    Thu, 1 Apr 1999 23:58:56 -0800
From:    David Zicarelli 
Subject: Re: Bomb and MSP

Scott Draves  writes:

>>  When Bomb is the front window, all the control mechanisms no longer
>> work in the MAX patch.
>
>i guess this is because bomb takes the keystrokes for its own use.
>i'll look into a way to disable this.

The frontmost window in Max gets keyboard events. If the
window chooses not to process them, they should be available
to the "key" object. I will work with Scott to provide a
way to disable the keyboard input to bomb.

David Z.

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

Date:    Fri, 2 Apr 1999 10:48:54 +0000
From:    Trond Lossius 
Subject: Re: new objects on Ircam's ftp

Roby Steinmetzer wrote:

> There is a name conflict here.
> "matrix" already exists by Panaiotis.
>
> Is there somewhere on the net a more or less official database of existing
> max externals?
> Thus the authors could consult it before breeding new externals ;-)
>
> Perhaps one could also put online a database like the Max Object Thesaurus
> at the end of the Max Reference book or the MSP Object Thesaurus.
> I often find this very useful, if only it could be updated with all those
> 3rd party objects.

Here is another name conflict: Peter Swinnen and McCartney both has objects
named
"listiter".

I've been thinking of putting together an extended thesaurus at the un-max
site,
but there are copyright issues involved if such a thesaurus is to include
the text
of the thesauruses from the Max and MSP manuals. Also it would be time
consuming. A
database of existing max externals should be considerable quicker to put
together.

I've also been collecting patches submitted to the max-l for half a year or
so. If
I'm posting these at un-max, would I have to ask each of the authors for
permission
to include their patches? After all the patches are available already at the
Max-l
archive.

So far I've got patches by: Stephen Kay, Michal Seta, Robert Henke, Michael
Sweet,
Christian Dobrian, Alex Stahl, John Brit, Ken Gregory, Georg Hajdu, Peter
Elsea,
David Zicarelli, Tom Mays and Richard Dudas. There is a few more patches
that I
still have to credit. If anyone of you has opinions on posting of the
example
patches, please respond to me privately (lossius@iafrica.com.na).

Generally I've tried to leave the patches the way they were submitted, but
have
included a few comments (credits and occasionally quotes from the thread
they were
a part of).

Cheers.

Trond L.

un-max:

http://node.net/MAX/

max-l archive:

http://www2.cybernex.net/~jonwitte/max/welcome.html

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

Date:    Fri, 2 Apr 1999 10:58:32 +0200
From:    Brigitte Marbehant Jardin 
Subject: Max-and blue-G3

Bonjour!

Is anyone already working with new Blue G3, audiomedia III, MAX-MSP?
Thank you very much for your answer.
Brigitte Marbehant Jardin

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

Date:    Fri, 2 Apr 1999 11:48:55 +0000
From:    Trond Lossius 
Subject: fsplit

In the MSP example folder there is an abstraction named fsplit, working
as a split object for floats. Does this object belong to any particular
library of 3rd part externals? The reason why I'm asking is that I have
a suggestion for an improved algorithm, but don't know who to suggest it
to.

Thanks

Trond L.

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

Date:    Fri, 2 Apr 1999 19:03:16 +0200
From:    Peter Castine 
Subject: Re: ignore/respond to click

On around 2-4-99 9:56, David Zicarelli said something like:

>Even if you could get the "point" structure correctly
>formatted in Max, which you can't,

Maybe I'm misunderstanding something basic, but this remark I was a
little surprised by. The Point typedef (or Record) was specifically
designed for storage in a 32-bit word (for typecasting to long/Long
Integer). The standard C syntax is a little ugly and I've probably
misplaced a parenthesis, but code snippets like the following:

     Point     p;

     p.v = 100; p.h = 200;

     ...

     long l = *((long *)(&p));

     ...

     short x = (l & 0xffff0000) >> 16;
     short y = (l & 0x0000ffff);

     ....

ought to feed v/h coordinates into a long int (for passing to a callback
expecting A_LONG) and extract them back into two short ints.

>         click messages to
>objects are messages that cannot be sent to an object
>via its inlets. In the parlance of Writing External Objects
>for Max, they have "A_CANT type specifiers."

This point is pretty compelling (and makes the previous issue moot). I
suppose one could write one's own objects to respond to a "klik" message
(expecting a long or three as parameters: the first for the point
coordinates, the second for the state of the modifier keys, and another
long for "when"). But if David sez standard Max objects aren't prepared
for that, well, a man who knows his Moliere can't be wrong!-)

Cheers,

Peter

----------------- http://www.prz.tu-berlin.de/~pcastine/ -----------------
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:    Fri, 2 Apr 1999 09:25:47 -0800
From:    Charles Baker 
Subject: Re: MAX Digest - 31 Mar 1999 to 1 Apr 1999 (#1999-102)

> ------------------------------
>
> Date:    Thu, 1 Apr 1999 21:10:09 +0200
> From:    Roby Steinmetzer 
> Subject: Re: new objects on Ircam's ftp
>
> >The Iso and Matrix object have been recompiled 'fat' by their author -
> >Charlie Baker - and put on Ircam
> >ftp: >.
> >sea.bin>
> >
> >The package is much composition oriented and includes the C source code.
> >
> >Thanks, Charlie, for making the archive growing !
> >
> >
> >_Manuel
>
> There is a name conflict here.
> "matrix" already exists by Panaiotis.
>
> Is there somewhere on the net a more or less official database of existing
> max externals?
> Thus the authors could consult it before breeding new externals ;-)
>
> Perhaps one could also put online a database like the Max Object Thesaurus
> at the end of the Max Reference book or the MSP Object Thesaurus.
> I often find this very useful, if only it could be updated with all those
> 3rd party objects.
>
> peace,
>
> Roby Steinmetzer
> Luxembourg, Europe
>

Please examine dates of these objects (mine has date reported in Max window
on
installation.)
My matrix object pre-dates Panaiotis'. By several years... it was 'lost'
when I
lost my
academic position, and had to work for a living (after dominating 35 years
of my
life, as student, composer and professional performer, music has *sigh*
become a
beloved hobby). I waited to buy a PPC machine until MSP woke me up. .. now
(after
purchasing (own $ ) the MetroWerks compiler, I found time to port my object,
originally written in 1993.

So...yes, Panaiotis should of had a master list of object names to look
into. Oh! I
just noticed!
There is one on IRCAM ftp! I guess we need to just use the resourses
available, eh?

CharlieB

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

Date:    Fri, 2 Apr 1999 18:58:23 +0800
From:    sven 
Subject: Matrixes

Thank you for the response on the matrix inquiry. At present it seems
that LCS and Richmond makes the most controllable matrixes with
implemented cuelist/MIDI-facilities. There are, however, people
working on other solutions that can do impressive spatialisation on up
to 32 channels or more, but none of these have stock models yet.
Thanx noch einmal!

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

Date:    Fri, 2 Apr 1999 16:28:45 PST
From:    v a u g h n 
Subject: protools i/o >> msp

i have an old protools system (16 voice) hanging around that is running
version 2.2. (expansion chasis + 5 quad audio interfaces)      i was
wondering if anyone could help me utilize this for use with msp as a
multiple channel i/o.  the hardware was designed for use with nubus, so
would there be a way to use it with a blue G3?  and what drivers would
be needed, etc... i'm sure this has been covered before, but i am
clueless in this regard, so any info would be appreciated.

thank you,
vaughn~
Get Your Private, Free Email at http://www.hotmail.com

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

End of MAX Digest - 1 Apr 1999 to 2 Apr 1999 (#1999-103)
********************************************************