Subject: MAX Digest - 9 Dec 1997 to 10 Dec 1997
Date: Thu, 11 Dec 1997 00:00:39 -0500
From: Automatic digest processor 
Reply-To: MAX - interactive music/multimedia standard environments
     
To: Recipients of MAX digests 

There are 5 messages totalling 190 lines in this issue.

Topics of the day:

  1. Lighting control / NSI info
  2. other mailing lists
  3. wrong apps, note filtering
  4. Looking for midi analyser
  5. Opps! More LoSchu!

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

Date:    Wed, 10 Dec 1997 08:03:20 -0500
From:    David Bianciardi 
Subject: Lighting control / NSI info

On Tuesday,  David Crandall wrote about: Re: Intelligent Light Control
>
>I'm interested in the light control patch.  Do you have any URLs for the
>light gear manufacturers?

I'm pretty sure this is the right info.  We've used NSI stuff on a few
installations and it's great.  Cheap, solidly built, etc.

As far as the IF 501's reliablility, we've had one doing MIDI to DMX in a
casino in Vegas for 2.5 years, without a hitch.

N S I
9126 SW Ridder Rd, Wilsonville, OR 97070-6766
503-682-1941

http://www.nsicorp.com/

have fun,

David Bianciardi              tech@idrc.com                gdb@interport.net
____________________________________________________________________________
        IDRC ||| 467 Greenwich St ||| NYC, NY 10013 ||| 800.767.8414

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

Date:    Wed, 10 Dec 1997 13:16:02 -0500
From:    jef chippewa 
Subject: other mailing lists

> Peter Nyboer wrote :
>
> >Does anyone subscribe to a list that does discuss
> >experimental/new/20th century music (any or all)?

here's another, though it isn't very (inter)active.

jef

__________

send the message:

'subscribe post-classical' or 'subscribe post-classical-digest'

to:

majordomo@cs.uwp.edu

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

Date:    Wed, 10 Dec 1997 11:46:40 -0800
From:    Peter Elsea 
Subject: wrong apps, note filtering

wrong apps
>I don't see exactly what it is you're fixing.  When 2 apps
>have the exact same creator ID (such as Max and LoShuMax, in the example)=
>,
>all you can do, by any type of voodoo or desktop rebuilding, is make one
>take precedence over the other.

 I'm sorry,  I thought it was clear from the context. That's exactly what I
meant to accomplish, give Max its precedence back. Since loShuMax owns no
documents, there's no harm.

Thanks for pointing out the preferencess box in resedit. I never read the
list without learning something. (Often things I thought I already knew.)

note filtering
(some basics here- old timers may wish to skip)
( I would normally send this type of answer directly to the original
inquiree, and have done, but since it was posted here, there seems to be
general interest.)

The difficulty here is that Max gives us MIDI note numbers, and we
musicians think in scale and octaves.

For the kind of processing desired, we need to break the notes into
numerical representation of scale degree (pitch class ) and octave. This is
done by dividing the MIDI note number by 12 to get the octave  and using %
12 to get the pitch class. When you do this, Do  maps  to 0, Re maps to 2
and so on to Si = 11. (Assuming C major. In other keys, subtract the pitch
class of the key from the MIDI note number before any processing and add it
back at the end).

Once you have pitch classes an easy way to remap is with funbuff. If you
feed it the message
0 0, 2 2, 4 4,  5 7, 7 7, 9 9, 11 12
You will get the mapping you want. (This will also map the chromatics to
the next lowest allowed note.)
you reconstruct the MIDI note by adding (12 * the octave you derived above).

(even more basic, all but beginners bail here)

The patcher included shows a fundamental misunderstanding of the nature of
notein and makenote. (Many of my students struggle with this for a while.)
notein gives you a note number and a velocity when a key is pressed, and a
note number and velocity of zero when the key is let up. So for each note,
notein responds twice.

Makenote generates this sequence when it receives a single value in the
left or a note number and velocity pair. When you attach notein directly to
makenote, you will usually get twice as many notes as you expect. (In the
patcher posted, the second is very short and may have a velocity of 0
anyway, but some synthesiszers will get confused.)

Stripnote is an important third member of this set- it passes note number
and velocity pairs only for the starts of notes, so if you are going to use
makenote (forcing your notes to be the same length, unless you go to a bit
more trouble) you should go through stripnote after notein.

If there is processing that will change note numbers, you have to be
careful what you  do or the note number for the offs might get away from
the note numbers for on, and you'll get hung notes. For the process
specified, it's ok to run the velocity from note in to note out, since the
processing on the note numbers is consistent and appropriate for offs as
well as ons.

Also, remember that with a keyboard synthesizer, you usually hear what you
play as well as what Max does to it, so turn local control off for this
problem.

I have some tutorials posted which address these and similar issues (in
word 5.1 format).
You can find them at ftp://arts.ucsc.edu/pub/ems/maxtutors/

Peter Elsea
Electronic Music Studios
University of California, Santa Cruz
http://arts.ucsc.edu/EMS/Music/index.html
 elsea@cats.ucsc.edu

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

Date:    Wed, 10 Dec 1997 22:39:29 +0000
From:    Philippe Lange 
Subject: Looking for midi analyser

Hello Opcodians.

I am using very old modified synth and try to understand the midi they
are sending. For instance, my old DX7 is continously speaking on my midi
channel 1. I see nothing of that in SVP or MAX.

In SVP I can not capture the REAL midi datas that are sended from my
synths to SVP, even in I disable all the filters.
I also tried with Max. It is the same.
Do you have any idea of a very simple soft which allows me to simply see
what is going out of a midi cable ?

Thank you for your help

Philippe

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

Date:    Wed, 10 Dec 1997 21:27:37 -0500
From:    muhenry 
Subject: Opps! More LoSchu!

Apologies to all who were inconvienced by my faux pas creator error in my
patch LoSchuMusic, and thanks to all who helped illuminate the problem.

My application patch did indeed re-name all the MAX file patches after
itself  on my hard drive- what I did was simply to encapsule the monster
in a Stuffit file and rebuild my desktop, a solution I suggested to Nicholas
J
Patterson (njp2@columbia edu), only his server kept returning my
e-mail as "unknown" (well, it happens sometime).

I originally posted LoSchuMusic to the info-mac archive ( along with
another patcher which has the same problem -FibonacciBlues) before I
noticed the problem. I didn't think anyone with the MAX program would
bother to download it!

Well, now I know! Again , my apologies. Incidently, the LoSchu is an
ancient Chinese mathematical "magic square" .

Otto
("Often wrong, but never in doubt!)

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

End of MAX Digest - 9 Dec 1997 to 10 Dec 1997
*********************************************