From:
                                                             1/23/97 7:28 PM
Subject: MAX Digest - 22 Jan 1997 to 23 Jan 1997 - Special
issueTo: Recipients of MAX digests 

There are 13 messages totalling 541 lines in this issue.

Topics in this special issue:

  1. 68020 requirement (2)
  2. standard midi files
  3. Max3.5 size, OMS?, older objects FAT? (4)
  4. chords
  5. video disc player
  6. Crashes with 3.5
  7. looking for graphics externals
  8. Steve E's objects...
  9. Chord Recognition

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

Date:    Wed, 22 Jan 1997 23:31:44 -0800
From:    David Zicarelli 
Subject: 68020 requirement

The requirement for a 68020 (or 030 possibly) for Max 3.5 is
not set in stone. I'm not sure whether the copy protection
works on a 68000 processor (and Nick makes me doubt it does)
but the program can certainly be made to do so. That would
mean a version of Maxplay 3.5 that runs on a PB 100. It's not
an immediate priority but I'll try to do it in the near future.

Just to clarify: irrespective of the copy protection, Max 3.5
does currently require at least a 68020, maybe a 68030. It
crashes on my PB 100, which I dug out of the closet for this
test.

David Z.

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

Date:    Thu, 23 Jan 1997 12:01:20 +0100
From:    Dominic Robson 
Subject: Re: standard midi files

Im trying to read 'standard' midi files created in cubase into the MTR or
SEQ objects, so far to no avail. Have i missed a trick here or is it not
possible. If so are there any clever ways around the problem. Any tips much
appreciated.

                                Dominic Robson

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

Date:    Thu, 23 Jan 1997 18:33:12 +0100
From:    Eirik Lie 
Subject: Re: Max3.5 size, OMS?, older objects FAT?

>>Max 3.0 = 885K
>>MaxFat3.5 = 1125K
>
>Hmm, another 300K down... It is getting VERY tight on my PowerBook 170. I
>take it that the 68020 requirement rules out my PowerBook 100 as well?

So, if Max 3.5 requires a 68020, does that mean that compiled standalones
will not run on 68000 machines?

Eirik Lie, PB 6820 Elgeseter, N-7002 Trondheim, Norway
Email: eirikli@notam.uio.no   -   Tel +47 73 52 80 30
New CD: http://home.sn.no/home/eiriklie/Visual.html

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

Date:    Thu, 23 Jan 1997 12:48:34 -0500
From:    Kenneth N Babb 
Subject: Re: chords

>Amanda Pehlke says:
>>I made a chord-recognition
>>utility in Max (to plug into a larger endeavor, and because I need it!),
and
>>I'm looking to compare it with any others that people have done.
>

Peter Elsea writes:

>.... We are going to convert this into a *pitch set*, a
>list that always has twelve numbers, which will be one if a pitch is
>present and zero if it is not. The pitch set for a C major chord looks like
>this:
>[1 0 0 0 1 0 0 1 0 0 0 0]
>Position 0 (the first one) is one, representing the presence of a C. There
>are also 1s on 4 and 7 for E and G. Notice the postition numbers corespond
>to the pitch classes

>... You might also want to look at the Fuzzy
>Logic paper, which takes this set business a whole lot further.

An article titled *Combinatorial Music Theory* by Andrew Duncan may be of
interest to some MAX users . It is published in the Journal of the Audio
Engineering Society Vol 39, No. 6, June 1991. It is along the line of the
above thread with an emphasis on applying the technique to the Guitar
fingerboard.

Regards,
Kenneth Babb
kbabb@escape.com

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

Date:    Thu, 23 Jan 1997 12:49:08 -0500
From:    Jeffrey Krieger 
Subject: video disc player

In a message dated 1/23/97 12:06:21 AM, you wrote:

<<> Has anyone had any success with the video disc player object in MAX?

I've been working on a project with Toni Dove for a while that involves
interactive control of 2 Video Disc players and a switcher as part of an
installation. Is there a specific problem you are experiencing?>>

No, I'm debating the pros and cons of image quality, reliability and
portability.  I am trying to turn my e-cello into an audio/video sampler.  I
was originally thinking of just triggering QT movies within MAX but the
resolution doesn't sound very good. However, I love the portability of doing
this on my 5300cs Powerbook.  With the video disc player I'm sure the
imagery
quality is fantastic.  Is MAX and the VDP object reliable?  What machines
does it work with?

Thanks for your input!
Jeff Krieger
http://www.xenonarts.com

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

Date:    Thu, 23 Jan 1997 13:01:04 EST
From:    Roland Hemming <100414.2220@COMPUSERVE.COM>
Subject: Max3.5 size, OMS?, older objects FAT?

>Just in case anyone's interested why I'm interested in upgrading: I'm not
>really, but I only have a single key disk for 3.0 with one of the installs
>buggered, and sooner or later I'm not going to be able to get a replacement
>for it as newer versions come along. While sticking with old software is a
>good philosophy a lot of the time, with MAX we don't have the option...

Good news Nick, TSC (our UK distributor) have a stock of 3.0 install disks.
These are ones with no serial number so can only be given to registered
users.
Just send Lars L5.

>Fine, so long as OMS 1.2.3 and MIDI Manager are both still supported.

MAX3.5 seems to work fine with OMS1.2.3.

Out of interest what are your objections to OMS 2.x?

Roland

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

Date:    Thu, 23 Jan 1997 13:43:37 -0500
From:    Bob Gluck 
Subject: Crashes with 3.5

Thanks to those who sent me advise regarding books from which to learn C.

I've been experiencing a fair number of system crashes since installing 3.5
and OMS 2.3.1. I'm running System 7.5.0 and wondering whether there is a
problem that might be correctable by upgrading to 7.5.x. Any ideas? Have
others been having this experience?

Bob Gluck
Sheffield, MA

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

Date:    Thu, 23 Jan 1997 20:21:26 +0100
From:    Jeffrey Burns 
Subject: looking for graphics externals

Before firing up CodeWarrior, I wonder if anybody already has some
externals for graphic purposes that I need:

1. versions of "rect" and "oval" in which the pen pattern can be varied (I
want to use dithers of various density to make my sprites fade in and out.)

2. sprite objects using the polygon and/or region QuickDraw calls

3. version of "movie" in which the display window can be set to a desired
place by means of arguments and its title bar can be removed (just as in
the "graphic" object)

4. an object to drive the "LanBox-LC II" MIDI to DMX 512 convertor (Does
anybody have good or bad experience with this hardware?)

offer FREE BEER by snail mail

Jeff Burns

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

Date:    Thu, 23 Jan 1997 20:04:13 +0000
From:    Nick Rothwell 
Subject: Re: Max3.5 size, OMS?, older objects FAT?

>Good news Nick, TSC (our UK distributor) have a stock of 3.0 install disks.
>These are ones with no serial number so can only be given to registered
users.
>Just send Lars L5.

Ah, great.

Is that L5 per disk or L5 for a whole pile of them? (I'll give him a call
tomorrow.)

>Out of interest what are your objections to OMS 2.x?

See previous message. Basically: it's too big and too bloated.

         Nick Rothwell, CASSIEL        contemporary dance projects
         http://www.cassiel.com        music synthesis and control

             years, passing by, VCO, VCF, and again, and again

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

Date:    Thu, 23 Jan 1997 19:45:00 +0000
From:    Nick Rothwell 
Subject: Re: 68020 requirement

>I'm not sure whether the copy protection
>works on a 68000 processor

"MAX 3.5 requires a 68000. Its copy protection requires a 68020." Sigh...

>That would
>mean a version of Maxplay 3.5 that runs on a PB 100. It's not
>an immediate priority but I'll try to do it in the near future.

I'd be reasonably happy with that, actually; it gives me a MAXPlay-only
backup PowerBook for performances, which is the main thing.

>Just to clarify: irrespective of the copy protection, Max 3.5
>does currently require at least a 68020, maybe a 68030. It
>crashes on my PB 100, which I dug out of the closet for this
>test.

I believe MAXPlay 3.0 is fine on a PB100 - I think I tried it. I cannot
install MAX 3.0 on the PB100 for reasons I'm sure you can recall.

         Nick Rothwell, CASSIEL        contemporary dance projects
         http://www.cassiel.com        music synthesis and control

             years, passing by, VCO, VCF, and again, and again

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

Date:    Thu, 23 Jan 1997 19:45:19 +0000
From:    Nick Rothwell 
Subject: Re: Max3.5 size, OMS?, older objects FAT?

>Is OMS 1.2.3 truly more reliable or faster than later rev's?

I fetched 2.0.x from Opcode sometime last year. I tried to install it on my
PB100 and it failed, reporting that it needed a 68020. Nowhere did it say
that in the documentation I had. I brought it up on my PowerBook 170. It
took loads of memory. It had enormous splash screens and icons. It tried to
do an "auto-configure" and gave me a window full of question marks, and
then crashed.

>I've always stuck to AMMgr because I use the printer port with _serial
>to do 57k baud and I despised the parasitic style of OMS' hegemony
>over my ports.

OMS (1.2.3 anyway) will only use whatever ports you tell it to: there's a
dialog during the "setup" procedure to tell it what ports to examine.

         Nick Rothwell, CASSIEL        contemporary dance projects
         http://www.cassiel.com        music synthesis and control

             years, passing by, VCO, VCF, and again, and again

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

Date:    Thu, 23 Jan 1997 15:41:04 -0700
From:    Steve Ellison 
Subject: Steve E's objects...

>>So how exactly does backward compatability work?  For instance, Steve
>>Ellison's _sense object.  In 3.5 can it be used in a Fat standalone?
>
>Steve, the offer still stands...  I don't have time to do all of yours, but
>I will do the ones I use:
>
>sense
>modifiers
>installed
>
>Stephen Kay
>

en route...  Sorry I haven't had the time to dig into this myself.

_____________________________________________________
Steve Ellison                ellison@LCSaudio.com
Level Control Systems        http://www.LCSaudio.com

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

Date:    Fri, 24 Jan 1997 01:28:40 +0100
From:    dudas 
Subject: Chord Recognition

OK, OK, Dearest Maxers,

Finally, in response to Amanda Pehlke's wish to compare chord recognition
methods, I'm posting my commented (perhaps also demented) Chord recognition
patch.  It needs to be cut out and pasted into a text document before you
can open it up in Max, obviously.

This patch is rather rough, although I cleaned it up and added comments,
etc...
The window is probably far too big for those using a Powerbook or Mac Plus.
Sorry.
I'll leave it up to all of you to copy and paste the desired bits into your
patches, and use them as you like.  I can't seem to locate any examples of
how this thing ever got used in a practical situation, so it remains rather
abstract.

This patch uses the "thresh" object to collect notes into a chord, but in
the original patch I used my "quickthresh" object instead.  Quickthresh
comes with the unsupported objects on the Max3.5 cd Rom (it's both 68k and
PPC compatible), and is also available on the IRCAM ftp. (If anyone at
uiowa wants to copy it to the kahless server, be my guest -- do whatever
you want because you will anyway.)

At first it might seem a bit twisted to do all that strange number packing
and bit shifting to reduce the chords to a single cryptic integer.  This
is, however, a very handy trick indeed, since each chord is thus associated
with a unique number (not a list) that can serve as an index for a funbuff
or coll. The cryptic number trick can also be useful to identify a chord
progression using a simple "match" object.  As you see, most everything has
been done with standard Max objects... please note though, that:

*** James McCartney's "sort" object is the only "unsupported" object used.
***
(It's also on the 3.5 CD RoM, or at the FTP site nearest you!)

"Basta, Riccardo, out with it," you say.  OK. Capito. Ecco il max-patch:

-------------------------------------------------
max v2;
#N vpatcher 9 40 794 554;
#P newex 72 130 27 196617 sort;
#P newex 72 156 43 196617 t b l b;
#P newex 72 293 43 196617 accum;
#P newex 105 208 66 196617 counter;
#P newex 105 230 27 196617 * 7;
#P newex 88 254 27 196617 <<;
#P newex 88 179 25 196617 iter;
#P message 104 274 14 196617 0;
#P newex 313 130 27 196617 sort;
#P newex 313 156 43 196617 t b l b;
#P number 313 316 135 9 0 0 0 3;
#P newex 313 360 45 196617 == 1856;
#P newex 313 109 52 196617 thresh 50;
#P newex 313 65 40 196617 notein;
#P newex 313 89 49 196617 stripnote;
#P toggle 313 385 15 0;
#P message 1 123 50 196617 67 72 76;
#P message 1 140 50 196617 72 76 79;
#P message 1 106 50 196617 64 67 72;
#P message 1 89 50 196617 60 64 67;
#P newex 72 109 52 196617 thresh 50;
#P newex 72 89 49 196617 stripnote;
#P newex 72 65 40 196617 notein;
#P number 72 316 135 9 0 0 0 3;
#P newex 329 209 35 196617 % 12;
#P newex 368 210 66 196617 counter;
#P newex 368 232 27 196617 * 4;
#P newex 313 295 43 196617 accum;
#P newex 329 256 27 196617 <<;
#P newex 329 181 25 196617 iter;
#P message 345 276 14 196617 0;
#P comment 288 402 224 196617 this recognises a C Major triad in root
position \, 1st and 2nd inversions respectively \, regardless of their
octave transposition.;
#P comment 2 44 222 196617 recognise chords made up of specific midi notes;
#P toggle 359 385 15 0;
#P newex 359 360 41 196617 == 116;
#P toggle 401 385 15 0;
#P newex 401 360 45 196617 == 1031;
#P message 244 109 50 196617 55 60 64;
#P message 244 92 50 196617 52 55 60;
#P message 244 126 50 196617 60 64 67;
#P message 244 143 50 196617 64 67 72;
#P message 244 177 50 196617 72 76 79;
#P message 244 160 50 196617 67 72 76;
#P number 593 333 135 9 0 0 0 3;
#P newex 609 196 40 196617 change;
#P newex 593 152 43 196617 t b l b;
#P newex 609 175 25 196617 iter;
#P message 625 293 14 196617 0;
#P newex 609 273 27 196617 <<;
#P newex 593 312 43 196617 accum;
#P newex 648 249 27 196617 * 4;
#P newex 648 227 66 196617 counter;
#P newex 593 46 40 196617 notein;
#P newex 593 69 49 196617 stripnote;
#P newex 556 68 25 196617 iter;
#P newex 593 89 35 196617 % 12;
#P newex 593 109 52 196617 thresh 50;
#P newex 593 130 27 196617 sort;
#P comment 539 20 173 196617 recognises a chord regardless of inversion \,
octave \, or whatever;
#P newex 677 355 27 196617 >> 4;
#P toggle 593 402 15 0;
#P newex 593 379 45 196617 == 1856;
#P newex 642 379 32 196617 % 16;
#P number 642 402 30 9 0 0 0 3;
#P newex 677 379 32 196617 % 16;
#P newex 711 379 27 196617 >> 4;
#P number 677 402 30 9 0 0 0 3;
#P number 711 402 30 9 0 0 0 3;
#P newex 539 426 203 196617 match 1856 2384 1856 2930 46930 2657;
#P comment 393 155 105 196617 V 4 3 (C)/ Aug 6 (F#);
#P comment 464 173 33 196617 I (F#);
#P message 499 171 50 196617 58 61 66;
#P comment 465 104 11 196617 I;
#P comment 465 121 32 196617 IV 6 4;
#P comment 465 138 32 196617 V 6 3;
#P comment 465 53 24 196617 I (C);
#P comment 465 70 32 196617 I 6 3;
#P comment 465 88 32 196617 I 6 4;
#P message 499 120 50 196617 60 65 69;
#P message 499 137 50 196617 59 62 67;
#P message 499 154 65 196617 59 62 65 67;
#P message 499 86 50 196617 67 72 76;
#P message 499 103 50 196617 72 76 79;
#P message 499 69 50 196617 64 67 72;
#P message 499 52 50 196617 60 64 67;
#P comment 583 449 173 196617 this "match" recognises the chord sequence CM
\, FM \, CM \, GM \, G7 \, F#M in any inversion!;
#P button 539 449 40 0;
#P toggle 72 394 15 0;
#P comment 71 412 162 196617 toggle is on if a specific C Major triad (60
\, 64 \, 67) is recognised.;
#P newex 72 369 65 196617 == 1105980;
#P comment 83 338 152 196617 ***big numbers limit maximum chord size to 4
notes...;
#P message 244 196 50 196617 63 67 70;
#P comment 193 198 38 196617 Eb Maj;
#P comment 193 93 49 196617 CMaj 6 3;
#P comment 193 110 49 196617 CMaj 6 4;
#P comment 193 145 49 196617 CMaj 6 3;
#P comment 193 163 49 196617 CMaj 6 4;
#P comment 193 127 31 196617 CMaj;
#P comment 193 180 31 196617 CMaj;
#P comment 7 15 255 196626 Richard's Chord Recognition;
#P comment 270 34 167 196617 recognise a specified inversion of a chord
regardless of octave;
#P comment 463 210 132 196617 This last example using "match" should
explain the usefullness of my strange number packing instead of list
comparing... remember: these cryptic numbers can be used as funbuff or coll
indexes (whereas lists...)!;
#P comment 4 73 48 196617 C Major:;
#P connect 20 0 48 0;
#P connect 48 0 47 0;
#P connect 68 0 69 0;
#P connect 62 0 93 0;
#P connect 66 0 67 0;
#P connect 60 0 93 0;
#P connect 61 0 93 0;
#P connect 21 0 48 0;
#P connect 102 0 101 0;
#P connect 101 0 100 0;
#P connect 101 1 96 0;
#P connect 101 2 95 0;
#P connect 101 2 99 2;
#P connect 100 0 79 0;
#P connect 79 0 13 0;
#P connect 13 0 15 0;
#P connect 23 0 48 0;
#P connect 99 0 98 0;
#P connect 98 0 97 1;
#P connect 97 0 100 1;
#P connect 96 0 97 0;
#P connect 96 0 99 0;
#P connect 95 0 100 2;
#P connect 82 0 102 0;
#P connect 80 0 81 0;
#P connect 80 1 81 1;
#P connect 81 0 82 0;
#P connect 83 0 101 0;
#P connect 63 0 93 0;
#P connect 88 0 90 0;
#P connect 89 0 88 0;
#P connect 89 1 88 1;
#P connect 90 0 94 0;
#P connect 72 0 75 2;
#P connect 73 0 78 0;
#P connect 73 0 77 0;
#P connect 74 0 75 1;
#P connect 64 0 93 0;
#P connect 91 0 87 0;
#P connect 92 0 91 0;
#P connect 92 0 68 0;
#P connect 92 0 66 0;
#P connect 75 0 92 0;
#P connect 93 0 75 0;
#P connect 93 1 73 0;
#P connect 93 2 72 0;
#P connect 93 2 77 2;
#P connect 94 0 93 0;
#P connect 76 0 74 1;
#P connect 77 0 76 0;
#P connect 78 0 74 0;
#P connect 45 0 57 0;
#P connect 46 0 45 0;
#P connect 50 0 49 0;
#P connect 50 1 49 1;
#P connect 49 0 47 0;
#P connect 47 0 46 0;
#P connect 51 0 52 0;
#P connect 52 0 54 1;
#P connect 53 0 59 0;
#P connect 59 0 34 0;
#P connect 59 0 41 0;
#P connect 59 0 40 0;
#P connect 59 0 43 0;
#P connect 41 0 42 0;
#P connect 54 0 53 1;
#P connect 55 0 53 2;
#P connect 56 0 58 0;
#P connect 57 0 53 0;
#P connect 57 1 56 0;
#P connect 57 2 55 0;
#P connect 57 2 51 2;
#P connect 58 0 54 0;
#P connect 58 0 51 0;
#P connect 40 0 39 0;
#P connect 43 0 38 0;
#P connect 43 0 37 0;
#P connect 38 0 36 0;
#P connect 37 0 35 0;
#P connect 34 0 16 0;
#P connect 86 0 101 0;
#P connect 19 0 48 0;
#P connect 18 0 48 0;
#P connect 85 0 101 0;
#P connect 84 0 101 0;
#P connect 65 0 93 0;
#P connect 24 0 48 0;
#P connect 22 0 48 0;
#P connect 31 0 48 0;
#P connect 11 0 93 0;
#P pop;
------------------------------------------------------
Have fun!

-Richard

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

End of MAX Digest - 22 Jan 1997 to 23 Jan 1997 - Special issue
**************************************************************