7/2/97 11:00 PM
Subject: MAX Digest - 1 Jul 1997 to 2 Jul
1997To: Recipients of MAX digests 

There are 5 messages totalling 123 lines in this issue.

Topics of the day:

  1. Yamaha SYSEX messages (TX81Z)
  2. Tempo stability problems with detonate
  3. reverse to MouseState
  4. was re: thanks stephen - is table tricks
  5. Max Resource Guide


Date:    Wed, 2 Jul 1997 12:11:31 +0200
From:    Joerg Spix 
Subject: Re: Yamaha SYSEX messages (TX81Z)

Hi TX81Z-fans,

I don't have my manual here, but at least in the german part of the manual
(and as I remember also in the english part) there are many misprints in
the sysex description. I think the english part was better but had still
some bugs in it. The best thing you can do is to check the descriptions in
the other languages and look out for changes in the numbers. As I can
remember the bugs were inside the header of the sysex, for example I never
got into one of the sysex groups.
If you found out the problem, try things out if you are not sure which is
the correct value (there are only a few possibilities).

Hope this helps a bit,




Date:    Wed, 2 Jul 1997 13:47:40 -0400
From:    Antonio Monasterio 
Subject: Tempo stability problems with detonate

Dear max users:

        I have been following this list for quite some time and find it very
interesting and of an excelent level. congratulations

        I have been working in a system for live performance of music in
I use the detonate object together with some "analog style" sequencers
made in max with external harware control which has been custom made for
ths purpose. to beguin I import a midi file from a sequencer where I
also have a sync track (24 ppqn) . The main problem I have is that
detonate seems to drift out of time causing long samples and vocals
recorded in Hard disk (ususally 8 bars long ) to drift.
I have tried to adjust the tempo and it seems to work for a while but
always ends up drifting. Also, depending on how much information is in
the midi file the sequence plays at a diferent tempo!

Has anyone experienced this problem. Is this normal to happen?

Thank you

Antonio Monasterio


Date:    Wed, 2 Jul 1997 19:40:51 +0200
From:    Jean Paul Laurent 
Subject: Re: reverse to MouseState

>>Try the following patch:
>>max v2;
>>#N vpatcher 46 56 446 356;
>>#P message 29 36 105 196617 \; max pupdate 100 200;
>>#P message 28 135 113 196617 \; max pupdate 100 100;
>>#P pop;

>Great! thanks!...

Indeed it's great! Where is this "message to max" (; max pupdate)
Are there other undocumented features of "; max" messages?

Jean Paul Laurent


Date:    Wed, 2 Jul 1997 21:18:27 +0200
From:    Tom Mays 
Subject: was re: thanks stephen - is table tricks

>>If you really want to use tables as global arrays with numbered arguments=
perhaps you could also store the output of the each table (a list) inside=
"v" object in your main patcher, so the data could be saved with the main=

patcher, and then dump it into the various tables when initially opening
the patcher, thus restoring your tables.

OR, save the table with the main patcher and then recover its contents
wherever and whenever you want with

expr tablename[$i1]

the table name being made variable with

expr $s2[$i1]

and inputing 'symbol tablename' into the second inlet



Date:    Wed, 2 Jul 1997 20:50:15 -0400
From:    Tommy DOG 
Subject: Max Resource Guide

First and foremost; I want to thank everyone for all the nice E that I
received throughout the day.
Second I want to assure the people who sent in corrections that I will
get to them in a timely fashion.
Third, people who wish to submit now should follow the format in the
site or for more clarity go to the "Guidlines" section o the site.
For those who missed it, the Max Resource Guide is located in scenic
Geocities at:
As usual,
Tommy DOG


End of MAX Digest - 1 Jul 1997 to 2 Jul 1997