Subject: MAX Digest - 27 Jul 1998 to 28 Jul 1998
Date: Wed, 29 Jul 1998 00:00:00 -0400
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
     
To: Recipients of MAX digests 

There are 12 messages totalling 422 lines in this issue.

Topics of the day:

  1. Joysticks for Max/Mac? (2)
  2. MAX Digest - 26 Jul 1998 to 27 Jul 1998 (2)
  3. max a la francaise
  4. A Joystick Alternative
  5. joystick...
  6. MSP in the year 2040
  7. dynamic allocation
  8. max question
  9. Of execution and order
 10. Joysticks for Max/Mac and other related analog to midi interfaces

McGill is running a new version of LISTSERV (1.8c on Windows NT).
Information is available on the WEB at http://www.mcgill.ca/cc/listserv

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

Date:    Tue, 28 Jul 1998 00:44:24 -0400
From:    Gordon Adams 
Subject: Joysticks for Max/Mac?

Just got the digest -- it seems that there is some confusion over the
current state of the art of joysticks for Macs.  There is no convolution
required to connect a SideWinder to a Mac -- Microsoft already makes an
ADB-compatible version (with software, to boot!).  There are also other
models, about which I know less (Gravis [www.gravis.com] has a very
well-respected line of Mac-compatible joysticks), but the SideWinder is
most definitely Mac (and MAX) friendly, and, at US$70 - $80, a
significantly more cost-effective joystick than I-Cube.

Following is the text of email I sent privately to Steven Kay (slightly
edited):

I highly recommend the SideWinder Pro as a joystick input device (in spite
of the usual misgivings about Microsoft).  It plugs into the ADB port, and
joystick functions can be mapped to keystrokes.  It does this by means of
an editor application (there is an extension, but I believe that the
application needs to be running in the background).

Some of its greatest assets:
-- any button or action can be assigned multiple keystrokes;
-- the x and y axes have seven positions in either direction, each of which
can be assigned its own keystroke;
-- a "pitch & yaw" function (rotation of the joystick on its axis) is
similarly sensitive and assignable, as is a 14-position slider on the side;
-- the software is application-aware;
a physical switch on the joystick switches between mouse functioning and
joystick functioning
-- and, the so-called "hat switch" (on top of the joystick) is pretty
useful -- each of 8 directions can be individually assigned a keystroke,
and the switch springs back to the center position.  I figure that, if one
wanted to configure the joystick for their word processing program, one
could type up to 24 characters, without getting into the levels of
sensitivity.

>
>In fact, you can download the latest version of the software:
>http://support.microsoft.com/download/support/mslfiles/MACSW3D.BIN
>The download includes an online user's manual.
[note: the software will not run without the joystick, but the user's
manual is available for your perusal.]

Gordon Adams.

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

Date:    Tue, 28 Jul 1998 08:48:47 +0000
From:    "john.magarshack" 
Subject: Re: MAX Digest - 26 Jul 1998 to 27 Jul 1998

PLEASE-PLEASE! TAKE ME OFF THIS LIST!!!!

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

Date:    Tue, 28 Jul 1998 02:51:04 -0400
From:    Les Stuck 
Subject: max a la francaise

>Que l'on cesse d'etre puriste au detriment de la comprehension.
Todor Todoroff 

je suis tout a fait d'accord, mais il faut pas oublier:
quand on voudrait garer la bagnole, en francais on cherche
un "parking", et en anlgais on cherche un "garage".

ca pete le concept completement!

les

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

Date:    Tue, 28 Jul 1998 00:49:24 -0700
From:    Peter Nyboer 
Subject: Re: MAX Digest - 26 Jul 1998 to 27 Jul 1998

>I have several Korg keyboards (surprise, to those who know my past).  The=
>y
>all come outfitted with joysticks.  The difference between these as
>implemented on a keyboard and as implemented for a game controller is
>that the keyboard units "snap back" to a center position when released.

This may be merely an annoying aside or perhaps useful info, but, the TG33
does not snap back to center when used, it merely stays where you left it.

P.

Peter Nyboer
pnyboer@loop.com

http://www.loop.com/~pnyboer/
--home of Slambassador multimedia gallery--

http://www.loop.com/~pnyboer/product
--product prototype! new material!--

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

Date:    Tue, 28 Jul 1998 05:20:33 -0500
From:    Bill Felton 
Subject: A Joystick Alternative

Another approach to getting a joystick to work with
Max might be the Peavey PC-1600.  It has 2 analog
inputs which do cv to midi conversion (continuous
controller only, mind you), which would allow each
axis of an analog joystick to plug in to an analog
in, with the CC of your choice being output.

Bill F.

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

Date:    Tue, 28 Jul 1998 13:14:59 +0200
From:    Robert Henke 
Subject: joystick...

Another joystick to MIDI solution :

Every axis of a normal joystick is connected to a potentiometer.
The easiest way to acces that potentiometer is with a midifader box:  cut
the connections to two of the faders and connect the potentiometer of the
joysticks instead.
A good faderbox for all these jobs is the "Cooper Fader Master" which
provides 8 Faders. The value of the external potentiometers are quite
uncritical ( R >1k , maybee up to 100k ) so it should work with allmost
every joystick.

rob.

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

Date:    Tue, 28 Jul 1998 09:37:20 -0400
From:    Stephen Kay 
Subject: Joysticks for Max/Mac?

Thanks to all who replied concerning joysticks.

I have a SideWinder arriving today; I'll let the list know
what I think of it in a few days.

Stephen Kay

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

Date:    Tue, 28 Jul 1998 09:55:56 -0700
From:    David Zicarelli 
Subject: Re: MSP in the year 2040

Georg Hajdu  writes:

>I copied my MAX/MSP files to my new G3 Powerbook and everything worked fine
>(I should say, great!!) for a few days until for some reasons the 'dates
>created' (and modified) had been set to 2040 for most of my files.
>Running MAX/MSP prompted my to enter a new authorization code, and entering
>the current one led to the following message:

>Error while verifying your authorization. The serial  number you specified
>has already expired. You need a new serial number in order to use this
>software. Result code: 32.

>Of course, I thought, I just need to reinstall my system and maybe this
>problem will go away. I also tried to run MAX from an external hard disk.
>But, unfortunately, the problem persisted.

>Interestingly, reinstalling MSP gave me the same results (The installer
>somehow accesses a file or resource with my name and address and maybe a
>wrong date; does this need to be erased?). So I wonder what's going on.

After consulting with Georg and our friends at PACE, we determined
that Georg had unwittingly run his copy of Max/MSP with the date
set into the next millenium. This caused his authorization code
(or what the error dialog box calls a serial number) to expire
permanently. This is, when an attempt to authorize MSP occurs
in which the clock's date is past the expiration of the authorization
code, you will never be able to use that authorization code on
that computer again. Harsh.

If this happens to you, contact Cycling '74 and a new authorization
code can be sent to you that expires one day later than the
expiration date on your current code.

David Z.

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

Date:    Tue, 28 Jul 1998 21:45:23 +0200
From:    subcontrol@MUU.AUTONO.NET
Subject: Re: dynamic allocation

>You can also connect those objects by sending message like folowing to
>thispatcher.
>
>    connect 0 0 2 1

just finished reading this months max lists
and i found something great!
this dynamic maxing gives me tri
how about deleting objects, patch cords dynamically? possible?
i want to program max with some other interface than mouse and keyboard:
sensor system that creates control data in max to further program max
but it seems to be tricky figure out how is the a particular objects number
changing as new objects are introduced

jukka ylitalo / ifxs

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

Date:    Tue, 28 Jul 1998 13:24:23 -0700
From:    Christopher Dobrian 
Subject: Re: max question

Britt.H.Myers@DARTMOUTH.EDU wrote: "I don't want one of the controllers to
be stored in the '-' object while the other one triggers the calculation.  I
want the movement of either controller to trigger a calculation."

You may find the following subpatch, called "both", useful for what you are
trying to do. When a number is received in *either* inlet, it sends out
*both* the numbers it has received in its two inlets.

In your case, send the values from one controller into one inlet of "both",
and the values from the other controller into the other inlet of "both".
Send the output of "both" into the two inlets of a "-" object.

Save the following text as a file called "both", then put that file in any
folder in Max's search path and you can use it as a "both" object in your
own patches.

max v2;
#N vpatcher 40 55 185 251;
#P newex 11 110 32 1441802 i $1;
#N comlet (int) most recent left input;
#P outlet 11 132 15 0;
#N comlet (int) send out both numbers;
#P inlet 11 59 15 0;
#P newex 11 78 38 1441802 t i b;
#N comlet (int) send out both numbers;
#P inlet 57 59 15 0;
#P newex 57 78 38 1441802 t b i;
#P newex 85 111 32 1441802 i $2;
#N comlet (int) most recent right input;
#P outlet 85 133 15 0;
#P comment 8 32 111 1310730 Input in either inlet causes output of both
numbers;
#P connect 8 0 7 0;
#P connect 6 0 5 0;
#P connect 5 0 8 0;
#P connect 5 1 2 0;
#P connect 4 0 3 0;
#P connect 3 0 8 0;
#P connect 3 1 2 0;
#P connect 2 0 1 0;
#P pop;

--Chris

                              ----------------
             Christopher Dobrian / School of the Arts - Music
             University of California / Irvine, CA 92697-2775
                Phone: (949) 824-7288 / Fax: (949) 824-4914
                      http://www.arts.uci.edu/dobrian/

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

Date:    Tue, 28 Jul 1998 13:24:28 -0700
From:    Christopher Dobrian 
Subject: Re: Of execution and order

alex@PIXAR.COM wrote: "[In my patch] the index~ is supposed to happen first
[before poke~, driven by the same count~ object, writes to the same
location in the buffer]. An existing signal is read from the buffer~,
scaled, combined with new signals, and written back to the same location."

Got it. I figgered it must be something like that. OK, so I'm imagining
you're doing something like this (plus other operations accessing the same
buffer~):

max v2;
#N vpatcher 50 40 255 242;
#P newex 27 144 140 1441802 buffer~ thebuffer 1000;
#P toggle 6 98 15 0;
#P newex 25 123 43 1441802 dac~ 1;
#P newex 25 97 44 1441802 *~ 0.5;
#P newex 131 51 44 1441802 adc~ 1;
#P newex 25 74 116 1441802 +~;
#P newex 71 123 98 1441802 poke~ thebuffer;
#P newex 25 51 103 1441802 index~ thebuffer;
#P newex 54 25 92 1441802 count~ 0 44099;
#P comment 78 92 83 1310730 ...or any other kind of processing here;
#P fasten 1 0 2 0 59 46 30 46;
#P fasten 1 0 3 1 59 46 178 46 178 118 120 118;
#P connect 2 0 4 0;
#P connect 4 0 6 0;
#P connect 5 0 4 1;
#P fasten 8 0 7 0 11 118 30 118;
#P connect 6 0 7 0;
#P fasten 6 0 3 0 30 118 76 118;
#P pop;

Since you've been working on it with David Z., you already have the most
expert advice you could get. But here's just an additional two cents (which
is about what it's worth): Intuitively, it seems to me that MSP would
decide to do the the peek (by index~) before poking the new value, because
it "needs" the value from index~ in order to know what to poke~. The index~
object (on the contrary) doesn't care what's in the buffer~ when it gets
the sample. So, if I were MSP (glad I'm not) constructing this instrument
internally, I'd execute the index~ before the poke~. Of course, I have no
idea if that's correct or not, so if you want to be sure, you're probably
best off (as I believe David suggested) delaying the signals going into
poke~ by using a couple of "delay 1" objects. [Coming in the next version
of MSP.]

--Chris

                              ----------------
             Christopher Dobrian / School of the Arts - Music
             University of California / Irvine, CA 92697-2775
                Phone: (949) 824-7288 / Fax: (949) 824-4914
                      http://www.arts.uci.edu/dobrian/

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

Date:    Tue, 28 Jul 1998 23:15:30 +0200
From:    marc ravelomanantsoa 
Subject: Re: Joysticks for Max/Mac and other related analog to midi
interfaces

--------------212F90D70B24F278348072E9
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854";
x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit

> Date:    Mon, 27 Jul 1998 09:05:10 -0400
> From:    Chris Murtagh Hrdc-drhc 
> Subject: Re: Joysticks for Max/Mac?
>
>
>  If this is a lasting and good $$ gig, and you like to fidget with
> electronic gear, I would strongly suggest getting an iCube. ......

get a look at this URL , iCube is one among other solutions to interface the
real world

http://www.ircam.fr/equipes/analyse-synthese/wanderle/Gestes/Externe/comparison.html

I did'nt try yet any of those solution.
The question is always the same : which one to choose ?
The answer always begin with : " it depends on the purpose ..."

Another way to look into :  I know that IRCAM is under development for a
midi to
interface device.
Can we have few words on the  progress report please  (V. Puig, ...)
thanks,

ciao

--------------212F90D70B24F278348072E9
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit



Date:    Mon, 27 Jul 1998 09:05:10 -0400 From:    Chris Murtagh Hrdc-drhc <chris.murtagh@HRDC-DRHC.GC.CA> Subject: Re: Joysticks for Max/Mac?    If this is a lasting and good $$ gig, and you like to fidget with electronic gear, I would strongly suggest getting an iCube. ......
get a look at this URL , iCube is one among other solutions to interface the real world http://www.ircam.fr/equipes/analyse-synthese/wanderle/Gestes/Externe/comparison.html I did'nt try yet any of those solution. The question is always the same : which one to choose ? The answer always begin with : " it depends on the purpose ..." Another way to look into :  I know that IRCAM is under development for a midi to interface device. Can we have few words on the  progress report please  (V. Puig, ...) thanks, ciao  

--------------212F90D70B24F278348072E9-- ------------------------------ End of MAX Digest - 27 Jul 1998 to 28 Jul 1998 **********************************************