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

There are 10 messages totalling 260 lines in this issue.

Topics of the day:

  1. check failed: t_newptr in overdrive
  2. detonate object on a 68000...
  3. Midi Setup Problems
  4. detonate object on a 68000
  5. studio3 and powerbook
  6. send different MIDI sync out multiple ports?
  7. MAX Digest - 14 Apr 1997 to 15 Apr 1997
  8. Presets and overdrive
  9. Memory trouble (2)

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

Date:    Wed, 16 Apr 1997 22:40:51 -0700
From:    David Zicarelli 
Subject: Re: check failed: t_newptr in overdrive

"David K. Mason"  writes:

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

This usually happens when you are doing something that tries to
allocate a chunk of memory at interrupt level that is too large.
This might happen if you are doing something like building up a
large list in a process triggered from a clock object or MIDI input.

The solution is usually to keep your clock-driven process from getting
out of hand memory-wise, or use an object that has its memory
pre-allocated, such as table.

David Z.

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

Date:    Wed, 16 Apr 1997 22:52:08 -0700
From:    David Zicarelli 
Subject: Re: detonate object on a 68000...

"Patrick T. Rost"  writes:

>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.

Let's assume that Patrick purchased Max 3.5 and he just wants to use
the externals that come with it in conjunction with an older version.
That's fine, but if we assume that new externals are a major part of
the value in an upgrade, someone who acquires the externals and
uses them with a previous version without buying the upgrade would
be getting something for free that others, such as Patrick, paid
money for. I could easily take my Powerbook 100 off the bookshelf
it's on and try to fix the detonate object to work with a 68000
machine, but I have a hard time motivating myself to do so. I hope
that doesn't come off as greedy or insensitive.

David Z.

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

Date:    Wed, 16 Apr 1997 23:03:23 -0700
From:    David Zicarelli 
Subject: Re: Midi Setup Problems

"Frank L. Thiel"  writes:

>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.

I can't answer Frank's question about the MIDI Express but I am sending
him e-mail to try to clarify the nature of the problem. But to answer
the question he asked above about old format files, the "Read Me"
document that comes with Max 3.5 explains that the PowerPC version of Max
cannot save Old Format files. This is due to the Old Format's use of
a 68K-specific floating-point format used in these files that is not
supported on the PowerPC. However, you can install and run the
68K-only version on a PowerPC machine and you'll be able to save
in the old format. Alternatively, all versions of Max can read
files saved in Text format.

Why anyone needs to use the Old Format at this point is a bit of a
mystery. The newer format ("Normal") was introduced in Max 2.2, released
in 1992. In Max 2.5, it was optimized to read in up to six times faster
than the older format.

David Z.

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

Date:    Sat, 16 Mar 1996 03:26:20 -0600
From:    =cw4t7abs 
Subject: detonate object on a 68000

>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?

dz!e 68000 mikroprocessor will generate an error if a word or l.word is
written to an odd address. 68020\30 allows 4-this [it will run slower]

aRt aboliTion kommiTTex2 .960[inft]
hTTp://www.tezcat.com/~antiorp.
_||- p!ano[koncErt4||4]handz.
anTi_s!g-naTure_kampa!gn.10-62.kode_1

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

Date:    Thu, 17 Apr 1997 10:08:29 +0200
From:    Le Quan Ninh 
Subject: studio3 and powerbook

Terry Nigrelli wrote :

>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.

and Guenther Albrecht sent me this :

>concerning your studio3 (i had one for years, now i use
>the 5lx), you will find the explanation on the opcode web site:
>www.opcode.com/support/faqs/midi_interfaces_faqs/studio3_powerbook.html
>
>It reads:
>Studio 3 Interface does not work with most PowerBooks
>The Studio 3 Interface was designed before the PowerBook series of Macs
>and is not recognized when doing an OMS search with most PowerBooks. Our
>later multiport interfaces, the Studio 4 & 5 do work with the PowerBook
>series. If you need an interface with the same capabilities as the
>Studio 3, our Translator Pro Sync  offers the same features and number
>of MIDI In's (2) and Out's (6) as the Studio 3 and does work with
>PowerBooks. The Translator Pro Sync lists for $249.95 and is housed in a
>plastic case (rack mounting tabs are an available option).

Ninh

-----------------------------------------------------------
l                      ninh@hol.fr                        l
l  http://ourworld.compuserve.com/homepages/Le_Quan_Ninh  l
-----------------------------------------------------------

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

Date:    Thu, 17 Apr 1997 15:10:50 +0100
From:    Nick Rothwell 
Subject: Re: send different MIDI sync out multiple ports?

>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...).

This is certainly true of the Studio 4, due in part to its derivation from
MOTU's MIDI Time Piece. Beat clock bytes are global, and system common
messages like song pointer are routed in some unobvious way which
temporarily escapes me.

I think the Studio 5 is more flexible in this regard - maybe - but probably
not illogical enough for your purposes.

         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, 17 Apr 1997 15:11:04 +0100
From:    Nick Rothwell 
Subject: Re: MAX Digest - 14 Apr 1997 to 15 Apr 1997

>I use a PB520 to run MAX with a Studio 5LX. It should run a Studio 3
>also.

Studio 3's are odd in some way. I think Opcode suggest the Translator Pro
to people who want two-port SMPTE functionality because of known S3
problems.

         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, 17 Apr 1997 15:11:14 +0100
From:    Nick Rothwell 
Subject: Presets and overdrive

I'm currently implementing another back of externals, and it occurs to me
that (AFAIK) the documentation doesn't explain much about presets, viz.:

If an object's state is stored into a preset (say, via a "store "
message coming into the preset object at interrupt), does the preset
message come into the object at interrupt? (I'm wondering about the
binbuf_insert stuff as well.)

If a preset is sent an integer at interrupt, does it restore the object's
state at interrupt?

My guess is no and yes respectively. Do I get any points?

         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, 17 Apr 1997 20:06:21 +0100
From:    "Frédéric Murray" 
Subject: Memory trouble

Please help me!
Excuse my english, I am a french speaker.  Opcode tech support refer me to
this list. When I load MAX 3.5, memory for system folder (in window About
your Macintosh) pass to 4000k at 11000k!!  I can't open anything when MAX
is loaded. When I close MAX, the memory don't come back, I have to restart
for retreive all my memory.  What's that? Is this OMS?  I have try this
without extension but the memory pass to 2500 at 9000.  I have a Performa
6200, 16 M of RAM and system 7.5.3.    I have also try this with Max 3.5.1
but I get no success.  Help!!!
Thank you for answer.

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

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

Date:    Thu, 17 Apr 1997 22:06:46 -0400
From:    DPALKOWSKI@AOL.COM
Subject: Re: Memory trouble

make sure 32 bit addressing is enabled, for one thing!

dp

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

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