Subject: MAX Digest - 18 Jan 1999 to 19 Jan 1999 (#1999-19)
Date: Wed, 20 Jan 1999 00:00:00 -0500
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
     
To: Recipients of MAX digests 

There are 9 messages totalling 538 lines in this issue.

Topics of the day:

  1. MAX Consultants
  2. CD grabbers
  3. MIDI transmission problem
  4. compressor (2)
  5. Transpose, how to.....?
  6. VNS
  7. Bonk and fiddle here we go again....
  8. More Max

Email to MAX should now be sent to MAX@lists.mcgill.ca
LISTSERV commands should be sent to listserv@lists.mcgill.ca
Information is available on the WEB at http://www.mcgill.ca/cc/listserv

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

Date:    Tue, 19 Jan 1999 00:31:59 -0500
From:    Johnny DeKam 
Subject: MAX Consultants

David Z. Wrote:

> I regularly get requests from people looking for people to
> write Max patches for them, and it would be great if there
> would be a list of people who would be interested in doing
> this sort of work. Then I could point prospective clients
> to such a list, and feel like I was doing everyone a favor.
>
> I'm not sure how to proceed, but one idea might be that
> someone who was maintaining a Max-related web site might
> want to solicit e-mail from interested consultants, and
> then compile a nice list. Information in such a list might
> include relevant experience and some kind of statement of
> the sort of things the consultant likes to do.

The UnMAX web site would be an ideal venue for this sort
of thing... I volunteer to host and maintain the list of
MAX consultants.

I've set up a filter to route requests -
If you are interested in being available as a MAX consultant,
that is, available to write MAX patches for $$$ or pleasure,
send an email to the following address: consult@node.net
mailto:consult@node.net

Please include the following information:
Full name
email address
web site if applicable
interests and/or experience and/or area of expertise
(EG hardware interface, audio/MSP, composition, robotics,
performance, installation, sensors, instrument hacks etc. etc)
phone # (optional)
Brief bio and/or CV (also optional)

Any information you submit will be made public on UnMAX,
so keep that in mind.

If response is good, the next step might be a separate listserv
only for proposals/requests or work/job listings.

--- Johnny DeKam
http://node.net/MAX/  - Unauthorized MAX

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

Date:    Tue, 19 Jan 1999 01:44:50 -0600
From:    Darwin Grosse 
Subject: Re: CD grabbers

>>You might also want to look at Disc to Disk from Optical Media
International
>>JW.
>
>
>is there a version working with IDE drives?

OMI was apparently eaten by another company (maybe Microtest?), and was sent
to bed early.  I wouldn't expect to see anything from these guys for a long
time... sadly.  The last version I used was unwilling to work with IDE
drives...

[ddg]
Darwin Grosse

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

Date:    Tue, 19 Jan 1999 10:09:43 +0100
From:    Jens Jacobsen 
Subject: Re: MIDI transmission problem

Eirik Lie wrote:

> an OMS dialog box tells me:
> "There is a MIDI transmission problem on the Modem port. Either the
> interface is missing, or too much data is being sent.

Hi,
Have you tried to uncheck the box "Report serial overrun and framing
errors" in the OMS Setup: Preferences?

Best wishes

Jens Jacobsen

Danish Institute of Electroacoustic Music
http://www.diem.dk

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

Date:    Tue, 19 Jan 1999 13:12:12 +0000
From:    david stevens 
Subject: Re: compressor

i wrote:

>needing to control some fluctuating levels inside my patch, i made a simple
>compressor using metro/avg~ to read a table object, the numbers derived
from
>this being used to control a *~ object, through which the audio is passing.
The
>table provides the compression curve.

>the problem is that it's a bit clicky.(less so if i slow metro down, but
it's
>still there). does anyone have any suggestions for a clean compressor?

wolf replied

>a) lowpassfilter the "control"-signal (eg. at 10 Hz) and the clicks should
go...

don't you mean a highpass filter? presumably to remove low frequencies which
might cause the "compressor" to pump?  Assuming that this will work - how do
you
make a highpass filter in msp?
I wonder if this _is_ the problem tho'. It seems that it may be something to
do
with using *~ to control signal level - I've noticed that i get the same
kind of
clicks if i pull a fader controlling output volume down too quickly.

>b) use a envelopefollower (like a lowpassed square of the inputsignal)
passing
thru >a lookup rather than a table.

i can't figure this out from the manual. I'm not clear how lookup uses the
buffered curve to control overall signal level, and i have no idea how to
draw
the curve i require into a buffer! (I could see how to get a particular
curve,
like a sine wave, into a buffer - that's illustrated in the manual; but how
do
you do it for a curve that would be suitable for a compressor?)

has anyone made a simple compressor?

david

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

Date:    Tue, 19 Jan 1999 16:02:49 +0100
From:    Mats Claesson 
Subject: Transpose, how to.....?

--============_-1295364320==_ma============
Content-Type: text/plain; charset="us-ascii"

Hi
Is there a way to transpose an audio signal without changing its length in
Max/msp?
--============_-1295364320==_ma============
Content-Type: text/enriched; charset="us-ascii"

Hi

HelveticaIs there a way to transpose an
audio signal without changing its length in Max/msp?

--============_-1295364320==_ma============--

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

Date:    Tue, 19 Jan 1999 13:30:03 +0000
From:    MiS 
Subject: Re: VNS

>
>
> This sounds like the kind of thing the Very Nervous System is supposed to
> be good at, not just analyzing the raw [distance, position, etc] but
> analyzing it somewhat.  To find it do a web search on "David Rokeby."
>
> dc
>

http://www.interlog.com/~drokeby/

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

Date:    Tue, 19 Jan 1999 21:48:27 +0100
From:    Mats Claesson 
Subject: Bonk and fiddle here we go again....

--============_-1295343587==_ma============
Content-Type: text/plain; charset="us-ascii"

Hi.
Lets try this once more, doesn't seem like you Max guys like to answer
questions that much, so far I have had no luck. When I mail David Z
directly THEN I get an answer. But I mean Davids time is better spent
developing MAX then answering my stupid Q:s isn't it? :-)   Your time is
probably better spent doing something else to but then.....

Or maybe this Antisnorp thing has exhausted you all. Im the lucky one, I
don't understand a sh...of what his writing.....its all filtered out by
itself.

So please if you have any energi left  It would be great to have some
comments on bonk~ and fiddle~.

Bonk~
My experience with bonk has so far been that I cant get it to work
properly. Properly meens detecting transients in a very percussive
soundfile. My testfile is a cowbell playing a very simple line in not so
very fast tempo. I have tried loads of setting and it is newer better than
90-95% That means it ads a note or skip detection every 10-15 note or so.

Debounce stops bonk when value exedes 1?

bonk its somewhat random, it doesn't fail the same way  (that is
interesting by itself but not what i had expected). So what am i to
expect......anyone please....

Fiddle
Fiddle works much better. I think it works great but how to you do you mask
consonants,   (to name an example) noise sounds, so they doesn't  mess it
up. It would have been nice to have an "if frequency varies more than 500
cents in 0.x seconds then mute/drop/skip frequency output. Any
suggestions......
--============_-1295343587==_ma============
Content-Type: text/enriched; charset="us-ascii"

HelveticaHi.

Lets try this once more, doesn't seem like you Max guys like to answer
questions that much, so far I have had no luck. When I mail David Z
directly THEN I get an answer. But I mean Davids time is better spent
developing MAX then answering my stupid Q:s isn't it? :-)   Your time
is probably better spent doing something else to but then.....

Or maybe this Antisnorp thing has exhausted you all. Im the lucky one,
I don't understand a sh...of what his writing.....its all filtered out
by itself.

So please if you have any energi left  It would be great to have some
comments on bonk~ and fiddle~.

Bonk~

My experience with bonk has so far been that I cant get it to work
properly. Properly meens detecting transients in a very percussive
soundfile. My testfile is a cowbell playing a very simple line in not
so very fast tempo. I have tried loads of setting and it is newer
better than 90-95% That means it ads a note or skip detection every
10-15 note or so.

Debounce stops bonk when value exedes 1?

bonk its somewhat random, it doesn't fail the same way  (that is
interesting by itself but not what i had expected). So what am i to
expect......anyone please....

Fiddle

Fiddle works much better. I think it works great but how to you do you
mask consonants,   (to name an example) noise sounds, so they doesn't
mess it up. It would have been nice to have an "if frequency varies
more than 500 cents in 0.x seconds then mute/drop/skip frequency
output. Any suggestions......

--============_-1295343587==_ma============--

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

Date:    Tue, 19 Jan 1999 13:05:12 -0700
From:    Alex Stahl 
Subject: Re: compressor

>has anyone made a simple compressor?
>
>david

Here is an example similar to what you describe, but adding a line~ to
smooth the output of the table on its way to the *~.  The line is a sort of
lowpass filter on the control signal; it removes the stairsteps at metro
rate which were most likely the cause of your clicks.  Try hooking up a
scope~ to the control signal in your original patch and this one and see
the difference.

I hesitate to call it a compressor, since to an audio engineer that word
implies more attention to musical dynamics than I put into this quick
example.  But at least it doesn't click. And it can be fun to draw wild
curves in the table.

-Alex S.

max v2;
#N vpatcher 176 111 705 619;
#P user dial 214 72 40 40 1200 1 5 0;
#P user dial 298 73 40 40 100 1 0 0;
#P message 227 341 59 196617 interval \$1;
#P user number~ 175 376 225 391 9 3 3 2 0. 0. 0 0. 35 0.;
#P hidden message 298 1 23 196617 5.;
#P hidden message 214 4 20 196617 30;
#P hidden message 36 5 14 196617 0;
#P hidden newex 36 -26 45 196617 loadbang;
#P newex 345 120 40 196617 adc~;
#P flonum 298 121 35 9 0 100 3 3;
#P newex 175 239 39 196617 * 127.;
#P newex 175 290 38 196617 / 127.;
#P newex 375 398 27 196617 *~;
#P newex 345 398 27 196617 *~;
#P newex 36 159 27 196617 + 1;
#P user umenu 36 72 100 196645 1 64;
#X add unity_gain;
#X add soft_compressor;
#X add limiter;
#X add expander;
#X add gate;
#X add alloftheabove?;
#N vpreset 7;
#X append 1 1 17 265 175 table set 0 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 1 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 1 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 1 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 \;;
#X append 2 1 17 265 175 table set 0 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 2 1 127 127 127 127 127 127 126 126 126 125 125 125 125 124 124
123 123 122 121 121 121 120 119 118 117 116 116 115 115 114 114 113 113 112
112 111 111 110 109 109;
#X append 2 1 108 108 107 107 106 106 105 105 104 104 103 102 102 101 101
100 100 99 99 98 98 97 97 96 96 95 94 94 93 93 92 92 91 91 90 90 89 89 88
87;
#X append 2 1 87 86 86 85 85 84 84 83 83 82 82 81 81 80 \;;
#X append 3 1 17 265 175 table set 0 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 126 125 124 123 122
121 120 119 118 117 116;
#X append 3 1 115 114 112 111 110 109 108 107 106 105 104 103 102 101 100
99 98 97 96 95 94 93 92 91 90 89 88 87 85 84 83 82 81 80 79 78 77 76 75 74;
#X append 3 1 73 72 71 70 69 68 67 66 65 64 63 62 61 60 58 57 56 55 54 53
52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33;
#X append 3 1 31 30 29 28 27 26 25 24 23 22 21 20 19 0 \;;
#X append 4 1 17 265 175 table set 0 60 61 62 64 65 66 67 68 69 71 72 73 74
75 76 78 79 80 81 82 84 85 86 87 88 89 91 92 93 94 95 96 98 99;
#X append 4 1 100 101 102 103 105 106 107 108 109 111 112 113 114 115 116
118 119 120 121 122 123 125 126 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 4 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 4 1 127 127 127 127 127 127 127 127 127 127 127 127 127 68 \;;
#X append 5 1 17 265 175 table set 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127;
#X append 5 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 5 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127 127
127 127 127 127 127 127;
#X append 5 1 127 127 127 127 127 127 127 127 127 127 127 127 127 127 \;;
#X append 6 1 17 265 175 table set 0 0 0 0 0 30 60 90 120 121 122 124 125
127 127 126 126 126 126 125 125 125 124 124 124 124 123 123 123 122 122 122
122 121 121;
#X append 6 1 121 120 120 120 119 119 119 119 118 118 118 117 117 117 117
116 116 116 115 115 115 115 114 114 114 113 113 113 113 112 112 110 109 107
106 104 102 101 99 97;
#X append 6 1 96 94 93 91 89 88 86 84 83 81 80 78 76 75 73 72 70 68 67 65
63 62 60 59 57 55 54 52 50 49 47 46 44 42 41 39 38 36 34 33;
#X append 6 1 31 29 28 26 25 23 21 20 18 16 15 13 12 10 \;;
#X append 7 1 17 265 175 table set 0 0 0 0 8 14 30 41 52 62 77 83 88 97 116
118 124 126 127 127 127 127 123 122 120 2 0 0 0 0 0 2 5 7 10;
#X append 7 1 12 15 17 21 25 29 33 37 41 45 49 56 67 72 78 87 93 99 105 109
117 120 123 126 126 122 119 115 112 108 104 101 38 25 19 13 10 6 3 0;
#X append 7 1 0 0 0 0 0 0 0 0 3 6 9 13 16 19 22 25 28 32 35 38 41 45 49 53
58 63 70 77 87 100 112 127 127 27 31 36 42 49 55 62;
#X append 7 1 68 72 75 79 82 86 89 93 97 104 106 102 97 86 \;;
#P preset 36 191 47 27;
#N vtable 128 50 40 260 207 0 128;
#P newobj 175 265 30 196617 table;
#P newex 175 315 49 196617 pack 1. 1.;
#P newex 175 340 30 196617 line~;
#P newex 345 459 40 196617 dac~;
#P number 214 121 35 9 5 0 1 3;
#P newex 148 159 50 196617 metro 30;
#P toggle 148 72 15 0;
#P newex 175 215 30 196617 avg~;
#P newex 281 159 27 196617 *~;
#P comment 70 312 100 196617 use the metro rate as the line~ duration \,
and smooth the steps;
#P comment 35 38 100 196617 pick an example dynamics function;
#P comment 18 257 145 196617 this table describes output gain as a function
of average input level-- try examples;
#P comment 193 18 88 196617 crude response time control-- vaguely related
to "attack/release";
#P comment 24 413 315 196617 |__________in analog parlance this is the
"sidechain" __________|;
#P comment 290 31 111 196617 even cruder sensitivity control-- raise it to
lower "threshold";
#P comment 141 38 29 196617 make it go;
#P comment 409 167 100 196617 there are many improvements to make:
logarithmic gain control \, RMS level detection \, and independent attack
and release time constants \, to name an essential few.;
#P comment 225 139 31 196617 msec;
#P connect 10 0 24 0;
#P connect 9 0 10 0;
#P connect 11 0 12 0;
#P hidden connect 11 0 14 0;
#P connect 12 0 10 0;
#P connect 13 0 12 1;
#P connect 13 0 16 1;
#P connect 13 0 32 0;
#P connect 15 0 31 0;
#P fasten 15 0 21 1 180 369 367 369;
#P fasten 15 0 22 1 180 369 397 369;
#P connect 16 0 15 0;
#P connect 17 0 23 0;
#P hidden connect 30 0 33 0;
#P connect 32 0 31 0;
#P connect 20 0 18 0;
#P connect 21 0 14 0;
#P connect 23 0 16 0;
#P connect 22 0 14 1;
#P hidden connect 27 0 28 0;
#P hidden connect 27 0 29 0;
#P hidden connect 27 0 30 0;
#P connect 25 0 9 1;
#P connect 24 0 17 0;
#P connect 26 1 9 0;
#P connect 26 0 9 0;
#P connect 26 0 21 0;
#P connect 26 1 22 0;
#P hidden connect 29 0 34 0;
#P hidden connect 28 0 19 0;
#P connect 18 0 17 0;
#P connect 19 0 20 0;
#P connect 33 0 25 0;
#P connect 34 0 13 0;
#P pop;

>i wrote:
>
>>needing to control some fluctuating levels inside my patch, i made a
simple
>>compressor using metro/avg~ to read a table object, the numbers derived
from
>>this being used to control a *~ object, through which the audio is
>>passing. The
>>table provides the compression curve.
>
>>the problem is that it's a bit clicky.(less so if i slow metro down, but
it's
>>still there). does anyone have any suggestions for a clean compressor?
>
>wolf replied
>
>>a) lowpassfilter the "control"-signal (eg. at 10 Hz) and the clicks
>>should go...
>
>don't you mean a highpass filter? presumably to remove low frequencies
which
>might cause the "compressor" to pump?  Assuming that this will work - how
>do you
>make a highpass filter in msp?
>I wonder if this _is_ the problem tho'. It seems that it may be something
>to do
>with using *~ to control signal level - I've noticed that i get the same
>kind of
>clicks if i pull a fader controlling output volume down too quickly.
>
>
>>b) use a envelopefollower (like a lowpassed square of the inputsignal)
>>passing
>thru >a lookup rather than a table.
>
>i can't figure this out from the manual. I'm not clear how lookup uses the
>buffered curve to control overall signal level, and i have no idea how to
draw
>the curve i require into a buffer! (I could see how to get a particular
curve,
>like a sine wave, into a buffer - that's illustrated in the manual; but how
do
>you do it for a curve that would be suitable for a compressor?)
>

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

Date:    Tue, 19 Jan 1999 21:05:21 -0500
From:    Otto Henry 
Subject: More Max

?Thot I sent this to the list Monday but it never got there- sorry if this
is a repeat:

Hello again:

Some more of my max application-compositions have been placed on the
hyper-archive at
MIT. You can download them from the following script:

http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/art/aeaea-11.hqx

http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/art/crooked-sky11.hqx

http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/art/odyssey-14.hqx

(also some earier uploads are now available on the hyper-archive:)

http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/art/green-music-12.hqx

http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/art/parade.hqx

Don't mean to take up too much space here, but this is kind of my magnum
opus for the past 2
years. I have not been able to upload anything for some time due to some
difficulties with my
server and so they are coming out en masse. The programs are all
stand-alones with different
creator codes. Sorry they are so fat ( from 859k = parade to 1535 =
crooked-sky) but the QT
movies, MaxPlay bundle and snd samples take up a lot. They are perhaps too
large for the
ircam-max archive, but I wouldn't object to someone putting them there. Or I
could fix up
some copies without the MaxPlay app.bundle and invisible files if anyone is
interested.

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

End of MAX Digest - 18 Jan 1999 to 19 Jan 1999 (#1999-19)
*********************************************************