Subject: MAX Digest - 5 Jul 1999 to 6 Jul 1999 (#1999-202)
Date: Wed, 7 Jul 1999 00:00:09 -0400
Automatic digest processor <LISTSERV@LISTS.MCGILL.CA>
To: Recipients of MAX digests <MAX@LISTS.MCGILL.CA>

There are 4 messages totalling 116 lines in this issue.

Topics of the day:

  1. msg from
  2. data transference
  3. grouped audio faders
  4. Formula used by curve~


Date:Tue, 6 Jul 1999 02:22:19 -0400
From:Stephen Kay <sk@COMPUSERVE.COM>
Subject: msg from

>(hope I am not breaking any rules here but it seems interesting for lots=
>of people on the list I think, anybody doing similar things? gz)

Actually, you *are* breaking rules. Duh. But you knew that.


Date:Tue, 6 Jul 1999 13:13:21 +0000
From:andy g <adg@PODCENTRE.DEMON.CO.UK>
Subject: data transference

firstly thanks to jeremy for his tips so far. i'd now like to throw this
question at the wider circle of list members.....

i'm starting a few projects that use a sensor laden 'probe' device to
monitor its environment, send the data into max via an i-cube and then have
the host computer transmit the data to a 'target' machine anywhere else on
the planet.
so far it looks that the data will be midi files and the patch will be
based around i-cube and seq objects.

i've had a couple of useful views on midiTjet from jeremy and i'd
appreciate any other views on this software, other max objects, in fact
anything related. i get the impression that a lot of tcp/ip objects are 68k this true?

please spell out complicated issues in easy english!!




Date:Tue, 6 Jul 1999 15:56:45 +0100
From:Benjamin Thigpen <Benjamin.Thigpen@IRCAM.FR>
Subject: grouped audio faders

Neal Farwell wrote:

>a "set" message to a volume fader does change the display without changing
>the audio - you need a subsequent "bang" for that; it's just like a "set"
>message to another message box - what's displayed changes, but no output

>til you bang or click the box.

This is true. However, according ot the MSP manuel:

"Set in left inlet:Sets the value of the slider, ramps the output signal
to the level corresponding to the new value over the specified ramptime,
but does not output the slider's value out the right outlet."

This, which it does not in fact do, would be much more useful than what it
actually does. It would allow you, for instance, to link a pair of stereo
faders together with 2 "set $1" messages - like this:

max v2;
#N vpatcher 50 40 205 293;
#P message 72 125 35 196617 set \$1;
#P message 73 105 35 196617 set \$1;
#P user gain~ 31 57 24 100 158 0 1.071519 7.94321 10.;
#P user gain~ 8 57 24 100 158 0 1.071519 7.94321 10.;
#P newex 8 26 35 196617 noise~;
#P user ezdac~ 8 189 52 222 129;
#P connect 1 0 2 0;
#P connect 1 0 3 0;
#P connect 4 0 3 0;
#P connect 5 0 2 0;
#P connect 2 0 0 0;
#P connect 2 1 4 0;
#P connect 3 0 0 1;
#P connect 3 1 5 0;
#P pop;



Date:Tue, 6 Jul 1999 22:45:25 +0000
From:Trond Lossius <lossius@IAFRICA.COM.NA>
Subject: Formula used by curve~

Could someone please help me shed some light on which formula is used
for curve~? As far as I can see from tests carried out, curve~ seems to
be run by a formula looking something like:

c1 + c2 * exp( c3*t + c4 )

with c1, c2, c3 and c4 being constants depending on start value, end
value, time and curve parameter. Is this the right formula, and if yes:
What is the relationship between theese parameters and the constants
c1-4? I find it hard to use curve~ for e.g. exponential decays as long
as I'm not able to relate time and curve parameter to e.g. the half life
time of the exponential part of the formula.


Trond L.


End of MAX Digest - 5 Jul 1999 to 6 Jul 1999 (#1999-202)