Subject: MAX Digest - 16 Jan 1998 to 17 Jan 1998
Date: Sun, 18 Jan 1998 00:02:00 -0500
From: Automatic digest processor 
Reply-To: MAX - interactive music/multimedia standard environments
     
To: Recipients of MAX digests 

There are 6 messages totalling 234 lines in this issue.

Topics of the day:

  1. Sensors and such
  2. Concert announcement/annonce de concert
  3. msp||ichi.objektz
  4. screen questions
  5. problems with 'key' (2)

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

Date:    Sat, 17 Jan 1998 03:19:51 EST
From:    MediaMat 
Subject: Sensors and such

In a message dated 1/16/98 4:43:28 PM, you wrote:

<>

Check out our new and updated web page at www.mediamat.com

All kinds of fun Midi to the rest of the world stuff.  We'll also be at NAMM
with a NEW product!

Dan Jamele

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

Date:    Sat, 17 Jan 1998 09:55:35 +0100
From:    Le Quan Ninh 
Subject: Concert announcement/annonce de concert

Hello,
My piece - Oscille - for 4 Lightnings II and computer will be premiered the
23rd of January '98 by the Quatuor Helios in Champigny (France) within the
Festival Sons d'Hiver. Oscille is an extented version (2 new movements) of
Initiale(s) (http://www.mygale.org/10/ninh/initiales_eng.html) which had
been premiered in May '97 at the Center of Research in Computing and the
Arts at UCSD.
The piece involves 4 Buchla's Lightnings II, 4 processed stones and a Max
program.

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

Bonjour,
Ma piece - Oscille - pour 4 Lightnings II et ordinateur sera creee le 23
janvier 1998 par le Quatuor Helios a Champigny dans le cadre du Festival
Sons d'Hiver. Oscille est une version augmentee (2 autres mouvements) de
Initiale(s) (http://www.mygale.org/10/ninh/initiales.html) qui a ete creee
au Center of Research in Computing and the Arts de l'Universite de
Californie, San Diego.
La piece utilise 4 Lightnings II de Don Buchla, 4 pierres traitees et un
program Max.

Ninh

__________________________________________
              Le Quan Ninh
            ninh@musique.net
      http://www.musique.net/ninh/
__________________________________________

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

Date:    Sat, 17 Jan 1998 16:13:35 +0100
From:    Tom Mays 
Subject: Re: msp||ichi.objektz

=cw4t7abs responded:

>>ae ie ie se
>>de ae _- ||

Nobody would dare to correct your Antiorpese, but if you're going
to write in Ge, please use correct grammar and syntax.

The ye,

    Ze
    Xe

"Academic wankers for better spelling."

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

Date:    Sat, 17 Jan 1998 19:12:10 +0100
From:    Peter Castine 
Subject: Re: screen questions

Ed Hartley asks:
>    I've read that one can force the mouse pointer to jump to a new
location
>on the screen by sending the message "pupdate X,Y" to the Max application
>itself. Is this true?

Moving the mouse behind the user's back is an abominable, beastly,
contemtible, detestable, evil, flagitious, ghastly, heinous, iniquitous,
jack-ass, knout-worthy, lousy, malevolent, nasty, odious, peccant,
quaggy, repugnant, sinful & scurvy, terrible, ugly, vicious & vile,
wicked, X[-Windows]-like sort of thing to do. Oh, I forgot yucky and
zymotic (in its original sense).

But you want to do it anyway. No, I don't know if it's true (offhand),
but I'm prepared to believe it. So...

>    How does one send a meesage to Max? Can you use the
>"send" object?

Use a semicolon in a message box (see the documentation of the message
box)

As in:

  ; max pupdate 32767 32767

>    Also, is it possible to eliminate both the current pacther's title bar
>and the menus at the top of the screen?

The only suggestion I can make is to position the window so that the
title bar is off-screen. You can initialize graphic windows with
appropriate coordinates to do this. You might be able to edit window
coordinates in a patcher saved as text (but I've never tried this).

[
A close reading of Mac Human Interface Guidelines would indicate that a
Mac app ought to re-position a window if the saved coordinates would
position the title off-screen, but Max might turn a blind eye to this.
]

I'm pretty sure Max understands showmenubar and hidemenubar messages.

Tangentially...
>    I seemed to have been disconected from the Max Listserve for a few days
>(maybe it had to do with the weather they've had in Montreal recently)

We're having one of the warmest winters ever (35 C warmer than last
year!) over here. What's with those Canadians? They always gotta be cold
in the winter.-)

Cheers,

Peter

---------------- http://www.prz.tu-berlin.de/~pcastine/ ----------------
Dr. Peter Castine           | I believe that the use of noise to make
pcastine@prz.tu-berlin.de   | music will continue and increase until we
                            | reach a music produced through the aid of
                            | electrical instuments.  -- John Cage, 1937

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

Date:    Sat, 17 Jan 1998 19:12:16 +0100
From:    Peter Castine 
Subject: Re: problems with 'key'

Stephen Kay  writes:

>I wanted to use the keyboard of the computer to play some notes
>and trigger some effects - but the response of the key object
>seems very erratic, especially when pressing more than one at =
>
>a time.  For example, simply hookup a key to a print, and press
>the first 4 number keys (1, 2, 3, 4) at the same time.  As
>expected, you get (49, 50, 51, 52).  However, now press number
>keys (2, 3, 4, 5) at the same time. At least on my computer, you
>do not get all 4 values - sometimes you get 2, sometimes you
>get none(!), sometimes you get a few when you _release_ the keys.

The short answer: a typewriter is not a piano keyboard.

The boring details:

The things (typewriter/computer keyboard) are really designed for you to
type one key at a time, with maybe a modifier or two.

The MacOS guarantees (more or less) that you can press up to *two*
[normal] keys plus any combination of the five modifier keys (Shift, Caps
Lock, Cmd, Opt, Ctrl) and that the keydown/keyup state will be correctly
reported by _GetKeys (cf. documentation for this trap in _Inside Mac_).

Some keyboards give you a little better than this (Apple's ADB extended
keyboard will handle maybe 4-5 keydowns plus the mod keys). I once had a
report of a 3rd party keyboard that would happily track the state of all
100-some-odd keys. Sorry, don't remember the manufacturer.

One easy way to check how many simultaneous keydowns your keyboard will
handle is to open up Key Caps (a DA that should be used a lot more often
by a lot more people, IMHO), and experiment. If you notice anomalies
similar to those reported above, well, then you can't exactly blame Max
for not being able to do better, now can you?

Cheers,

Peter

---------------- http://www.prz.tu-berlin.de/~pcastine/ ----------------
Dr. Peter Castine           | I believe that the use of noise to make
pcastine@prz.tu-berlin.de   | music will continue and increase until we
                            | reach a music produced through the aid of
                            | electrical instuments.  -- John Cage, 1937

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

Date:    Sat, 17 Jan 1998 15:12:51 -0500
From:    Stephen Kay 
Subject: Re: problems with 'key'

Peter Castine:
>The MacOS guarantees (more or less) that you can press up to *two* =

>[normal] keys plus any combination of the five modifier keys (Shift, Cap=
s =

>Lock, Cmd, Opt, Ctrl) and that the keydown/keyup state will be correctly=
 =

>reported by _GetKeys (cf. documentation for this trap in _Inside Mac_). =

OK, I looked at GetKeys(), but this is something you use when you want
to read the keyboard directly.  I'm assuming that keyboard events are
passed to MAX in an Event Loop, so it seems possible that individual
key downs could be reported with more accuracy.  Isn't an event generated=

for each key down?

David, how is "key" doing its reporting?  Would it be possible to write
an object with greater accuracy?  If so, I'll try it, but I'd like your
opinion before diving in.  Can I write an object which intercepts events
before they get to max, or look at them somehow, with greater accuracy
then "key"?

Thanks,
Stephen Kay

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

End of MAX Digest - 16 Jan 1998 to 17 Jan 1998
**********************************************