Subject: MAX Digest - 15 Apr 1997 to 16 Apr 1997
Date: Sun, 9 Nov 1997 23:05:57 +0100
From: Automatic digest processor  (by way of dudas)
To: jonwitte@CYBERNEX.NET

There are 10 messages totalling 277 lines in this issue.

Topics of the day:

  1. Max crashing w/ sysex dumps
  2. check failed: t_newptr in overdrive
  3. Max crashes
  4. send different MIDI sync out multiple ports?
  5. Max 3.5 seems to crash when I open files from the Finder.
  6. MAX Digest - 14 Apr 1997 to 15 Apr 1997
  7. detonate object on a 68000...
  8. MAX Guide
  9. Max and MacOs 7.6
 10. Midi Setup Problems

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

Date:    Tue, 15 Apr 1997 22:52:15 -0700
From:    David Zicarelli 
Subject: Re: Max crashing w/ sysex dumps

Greg Laman <3a5ctl4@CMICH.EDU> writes:

>I've been having trouble with Max crashing when I send it large sysex dumps
>from my Ensoniq DP/2 effects processor.  I'm trying to record these sysex
>dumps into a seq object.  It works if I just send one preset at a time, but
>if I send a whole bank I run into problems.  First OMS will report a serial
>overrun error and then sometimes Max will crash with either an
>"unimplemented trap" error or type 28 error.  I think the problem is
>somewhere in OMS or Max because I am able to receive and send the same
>sysex dumps just fine if I use an application that records midi files
>without going through OMS.

The seq object was never designed to record large sysex dumps. Although
I don't know how large you're talking about, in principle, you should
use an object that has preallocated the space needed to receive your
dump. The table object is a good candidate. You can use its "load"
message (documented in 3.5 but available in all versions) that
puts the object in a state where each successive value that comes
in the left inlet is written to a successive index. The "dump"
message will send out the contents of the table, or you can use a
counter. Before sending the sysex message to Max, you'll need to
change the table size to the expected message length. The only
problem with table is that it allocates four times as much memory
as is needed to store your dump, because it handles 32-bit values
at each index.

For more efficient temporary storage of dumps, you can use the
capture object.

seq is designed for real-time recording of small bits of data;
i.e., MIDI messages like note-on and note-off or small sysex
messages such as parameter changes.

David Z.

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

Date:    Wed, 16 Apr 1997 08:25:47 +0200
From:    "David K. Mason" 
Subject: check failed: t_newptr in overdrive

What does the message
=80 check failed:  t_newptr in overdrive
in the MAX window mean?

Best regards, Dave Mason
music@tempo.s.shuttle.de
http:/www.s.shuttle.de/tempo/

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

Date:    Wed, 16 Apr 1997 09:51:35 +0200
From:    Jeffrey Burns 
Subject: Max crashes

This may be a banal tip but still of use to some great artists and
absent-minded professors, among which I immodestly include myself. Have you
forgotten to raise the RAM allocation of Max 3.5.1 after installing it???

Jeff

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

Date:    Wed, 16 Apr 1997 01:17:01 -0700
From:    James Reynolds 
Subject: send different MIDI sync out multiple ports?

i'm new to the list, so i apologize if this issue has already been
addressed...

i have an opcode studio 64x four-port interface running with max 3.0 and
oms 2.31, and i'm having trouble sending MIDI sync at different frequencies
out each of the four ports (i.e., sending the value 248 at different rates
simultaneously to midiout a, midiout b, etc. in order to create
polymetrical textures with looping delay devices).  no matter which port i
send the sync to, devices on all ports receive the sync.

the midiout objects with port arguments seem to function independently
(except for the sync).  i can send program change messages (as an integer
list) into a midiout object with a port argument, and the message is sent
only to the specified port.

it would seem as if the interface itself is making the decision to route
the sync to all ports (logical for most situations, but problematic for
illogical music...).  so my question is, do all multiport interfaces
automatically send sync and other non-channel-specific data to all ports,
or is this an unwanted feature specific to the studio 64x?  can anyone
recommend a multiport interface that doesn't exhibit this behavior?

thanks in advance,

james

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

Date:    Wed, 16 Apr 1997 11:47:11 EDT
From:    Tom Ritchford 
Subject: Re: Max 3.5 seems to crash when I open files from the Finder.

Jens Jacobsen  wrote:
>Max 3.5 crashes - not every time,
>but perhaps every one out of 5 - when I open or save a file. Also when
>it´s done from within Max.

This is a worse problem than mine.  As long as I open from
within Max, I don't get crashes on opening.

I do occasionally get sporadic crashes, but never when I'm
just running patches.  OTOH, I've not run something fast and
long in Max 3.5.

Just another probably dull data point.

    /t

Tom Ritchford                        tom@mvision.com

    Verge's "Little Idiot" -- Music for the mentally peculiar.
1-800-WEIRDOS                       http://www.weirdos.com/verge

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

Date:    Wed, 16 Apr 1997 15:33:29 +0100
From:    Terry Nigrelli 
Subject: Re: MAX Digest - 14 Apr 1997 to 15 Apr 1997

> ------------------------------
>
> Date:    Tue, 15 Apr 1997 12:29:02 +0200
> From:    Le Quan Ninh 
> Subject: Re: Powerbook 520
>
> >If I were to buy a second-hand PowerBook 520 for MAX (3.0), OMS (1.2.3),
> >Vision (2.0.8), Galaxy (1.2.9), MIDI Manager (2.0.2), would I regret it?
>
> No, you wouldn't. I use it since 2 years and now with Max 3.5.1 and OMS
> 2.3.1 and it works perfectly. The only thing I hardly regret is that I
> cannot succeed in using Studio 3. OMS cannot recognize it because the
> serial/modem port I think...
>
> Ninh
>

Ninh,

I use a PB520 to run MAX with a Studio 5LX. It should run a Studio 3
also.
Check the "OMS MIDI Setup" It should have an X in the modem port box.

Terry Nigrelli
--
my home page: http://home.earthlink.net/~terryn/

Bay Shore Schools home page: http://www.bayshore.k12.ny.us/

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

Date:    Wed, 16 Apr 1997 13:28:04 PDT
From:    "Patrick T. Rost" 
Subject: detonate object on a 68000...

Now I know that MaX 3.5 is supposed to want a 68020 or better, but I thought
that the w protocol and the detonate object were supposed to be portable
enough
that they could be installed in 2.5.2 (or 3.0 for that matter)...
I am perfectly happy running Max 2.5.2 on my powerBook100, SE or Plus...I
have
moderate automation needs, and so the slow processors don't normally bother
me.
The problem is editing in the detonate object.  As soon as I double click
on it,
I get either an Address Error (Type 2) or a Bus Error (Type 1).  This has
happened on every 68000 machine I've tried it on ('100, SE, Plus) but not on
my IIci at work (68030) or my PowerMac 7200/75 (PPC601).  Any answers out
there?
David?

The upshot is that I'd really like detonate, but I'd settle for an object
that
can read and write type 1 standard MIDI files.

Thanks.
Sorry about the excessive ramble.
Patrick T. Rost
Studio and Technology Assistant
University of California, San Diego

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

Date:    Wed, 16 Apr 1997 20:23:32 -0400
From:    "Tommy \"Uncle Max\" DOG" 
Subject: MAX Guide

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
     The MAX Guide R E M I N D E R & UPDATE

The submissions are coming in a couple of times a day, which is pretty
amusing so don't stop. So far there is a pretty good mix of people in
various areas of discipline as well as experience level.
There are a couple of you who have not sent in your vitals, I'm gonna
start contacting people very soon -so be afraid.
I want to remind people; if you don't here back from me within three
days, you're probably are using AOL and I didn't get the E.
Another thing, please DON'T just send your URL, if you are really that
lazy, REQUEST a questionnaire and I'll E you one..... Now that I said
that I think I should probably type one up.
As usual,
TD

A NEW & less ugly info page is here:
http://www.panix.com/~jjprinz/max_guide_lines.html

Once you've looked at that, E me here:
unclemax@iname.com

"The more submissive you are, the easier my job is"
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

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

Date:    Wed, 16 Apr 1997 21:52:57 +0100
From:    "Frédéric Murray" 
Subject: Max and MacOs 7.6

Excuse my english, I am a french speaker.  I would like to know if someone
test Max 3.5 with MacOS 7.6  Do you meet some trouble?  Thank you for
answer.

Frédéric Murray
aae052@agora.ulaval.ca

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

Date:    Wed, 16 Apr 1997 23:01:53 -0500
From:    "Frank L. Thiel" 
Subject: Midi Setup Problems

I just subscribed to the listserv, and thought I would ask a question
about a problem I am having with MAX 3.5.  My setup is as follows:

   MAX 3.5
   OMS 2.3.1
   PowerCC PowerWave 604/120
   MOTU Midi Express XT
   Several pieces of MIDI gear

The problem is as follows: after setting up my studio document in OMS,
I launch MAX and select File -> Midi Setup...  All of my gear appears
in both the "input devices" and "output devices" column, including
the Midi Express XT (for which OMS chose the "Midi TimePiece" driver).
When I try to choose a letter assignment in the "output devices" column
for the device connected to Port 1 of the Midi Express XT (MEXT), MAX
insists on explicitly linking the MEXT itself with the device, making it
have whatever letter assignment the Port 1 device has.  This essentially
renders Port 1 useless under MAX by sending all Port 1 data out all of the
8 ports on the MEXT.

I have tried throwing out and recreating the studio document in OMS
with different devices on Port 1.  I have also tossed the MAX Preferences
and made it recreate them.  The problem is always there.  I would appreciate
any insight anyone has on this.

Additionally, whenever I try to do a "Save as...", the "Old Format" radio
button is always grayed-out (regardless of how simple the patch is).
Again, any insight would be appreciated as I am writing some patches
that will be used on an old system.

Thank you very much, and I look forward to being part of this listserv.

Sincerely,

Frank Thiel

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

End of MAX Digest - 15 Apr 1997 to 16 Apr 1997
**********************************************