From:
                                                             8/3/97 11:00 PM
Subject: MAX Digest - 2 Aug 1997 to 3 Aug
1997To: Recipients of MAX digests 

There are 7 messages totalling 215 lines in this issue.

Topics of the day:

  1. Your own Preferences File
  2. Fat Object Problems (68K CW Development)
  3. Grouping objects (Was: coloured patch cords)
  4. PB 540 and Max
  5. AIFF/SD2 headers
  6. multitasking
  7. Max and mtc

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

Date:    Sun, 3 Aug 1997 09:19:56 -0700
From:    Christopher Dobrian 
Subject: Re: Your own Preferences File

>>>I was wondering how I can have the app be able
>>>to save out a 'preference' file that will get
>>>loaded and read whenever the app is started.
>
>>Max 3.5 can do this. See p. 62 of the 3.5 Addendum manual.
>
>Not really.  All this does is allow you to have a uniquely named "Max"
>Preferences file, which remembers things like the last setting of
>OverDrive, etc.  You can't write your own data to it, such as the last
>settings of various menus in your app.

True. The preferences file is for storing Max preferences. Max has no way
of knowing what other "preferences" you may devise in your own program. You
have to devise your own storage scheme for data of your own that you want
to save, using a table, a preset, or whatever.

--Chris

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

Date:    Sun, 3 Aug 1997 21:32:33 +0200
From:    Peter Castine 
Subject: Re: Fat Object Problems (68K CW Development)

pseudo wrote:

>It is very frustrating.  I have a suite of externals which have been
>extensively tested under PPC and work fine.  Now I need to demo my tools
>on a 68K machine.
>
>Absolutely nothing works!  I've got all my project settings correct.  I'm
>adding the right libraries.  I do all the A4 mumbo jumbo.
>
>It seems that the CW 68K compiler is much more finicky about automatic
>type conversions than the PPC compiler.  I've had to go in and rework
>almost every macro and inline I've used in order to make them work under
>68K.

Thing is, the entire API on 68k consists of untyped macros; on PPC you
#include a header with function prototypes. So, the PPC compiler can
automagically typecast all your shorts to longs (and vice versa). The 68k
compiler just blindly puts what you give it onto the stack and does a JSR.
If Max wants a long and you've given it a short, well, things aren't gonna
work too well.

Once upon a time I re-wrote a version of the macros with all the
appropriate typecasts built in (well, I only got as far as the macros I
actually use myself). Saved some trouble, but it got zapped on an upgrade.

Anyway, the aside from Preparing, Entering, and Exiting callbacks,
typecasting is the biggest potential for mistakes in Max externals on 68k.

Hope this helps,

Peter

-------------------- http://www.prz.tu-berlin.de/~pcastine/
-------------------
Dr. Peter Castine          | 'Just the place for a Snark!' I have said it
twice
pcastine@prz.tu-berlin.de  |   That alone should encourage the crew.
                           | Just the place for a Snark! I have said it
thrice
Have Mac, Will Travel      |   What I tell you three times is true.'

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

Date:    Sun, 3 Aug 1997 21:33:46 +0200
From:    Peter Castine 
Subject: Re: Grouping objects (Was: coloured patch cords)

> GROUPING objects... to group objects and the patch cords associated with
them

Not to be pedantic, but there *is* a way to group objects -- Sub-Patchers.

I've seen an aweful lot of messy patches that could have been tidied up
immensely by packing a couple of things into sub-patchers.

OK, so I've gotten pedantic. Yeah, a command to group a bunch of objects
together would be cool, but until David gets around to implementing it, we
might as well make the most of the tools that we do have.

Gelle?

Cheers,

Peter (and apologies for the German colloquial rhetorical question)

-------------------- http://www.prz.tu-berlin.de/~pcastine/
-------------------
Dr. Peter Castine          | 'Just the place for a Snark!' I have said it
twice
pcastine@prz.tu-berlin.de  |   That alone should encourage the crew.
                           | Just the place for a Snark! I have said it
thrice
Have Mac, Will Travel      |   What I tell you three times is true.'

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

Date:    Sun, 3 Aug 1997 22:48:48 +0200
From:    Oeyvind Brandtsegg 
Subject: PB 540 and Max

Hello

I posted a question some days ago regarding system crash doing calculatio=
ns with floats.
Since then I've been trying to track down the problem, but I've just foun=
d more and more ways to crash my computer. Not 100% consistent
crash-proof, but close to it. I'm not shure if it's the Max program, the =
System or the hardware. I recall there was some discussion of Max and
Powerbooks some months ago, and I now want to ask:

Anyone have experience running Max 3.5 on a PB 540 ?
Is there any known problems with OMS 2.3.1 and Max ?
Would it make any difference what Midi-interface I use ? (currently: Stud=
io 64X)
Which version of the Mac OS would be considered the most reliable for Max=
 ? (currently: System 7.5.1)

When running disk checks I oftentimes find files with damaged recource fo=
rks. What is this ?
I also sometimes get reports on some problems with the "catalog B-tree". =
What is that ?
I always choose to fix these disk problems, but they keep re-appearing. T=
he computer was infected by a MBDF-virus, but I got rid of it I
think.
Could these thing be connected to instability with Max in any way ?

Well, OK
I understand that I ask too many questions, but I do not demand answers d=
o I ?
I can just plea for help. So pleeease ?

BTW. David: is the rapid-clicking-on-number-box bug fixed by now ?
Thanks

=D8yvind Brandtsegg (Composer/Vibraphone)
Nedre Bakklandet 47 A
7014 Trondheim
Norway
mailto:obrandts@sn.no

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

Date:    Sun, 3 Aug 1997 23:17:44 +0200
From:    pottier 
Subject: AIFF/SD2 headers

*-*-*-*-*-*-*-* Hello,*-*-*-*-*-*-*-*-*-*-*

In English
        I just want to know if somebody has few lines of code in C to read
a soundfile header (aiff or SD2) and put it in a structure.

en Francais
        Je cherche quelques lignes de code en C permettant de lire
l'en-tete d'un fichier son aiff ou SD2 et stocker les infos dans une
structure. C.

(PS. grand bonjour =E0 Richard.)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

-------------------------------
    Laurent Pottier
   d=E9part. Math-Info
   UPV - Rte de Mende
 34199 Montpellier Cedex 5
pottier@bred.univ-montp3.fr
 -----------------------------

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

Date:    Mon, 4 Aug 1997 08:52:07 +1000
From:    David Rodger 
Subject: Re: multitasking

David Z wrote:

> Indeed, the "multithreading" that allows the Finder to
> copy a file in the background has always been possible; it's called
> asynchronous file i/o, and you couldn't do hard-disk recording
> without it.

Presumably, though, it's not part of any standard file I/O and Digidesign
and others had to figure it out for themselves.

Regards, David
musdr@lure.latrobe.edu.au
http://farben.latrobe.edu.au/d_rodger/

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

Date:    Mon, 4 Aug 1997 02:48:28 +0100
From:    Eirik Lie 
Subject: Re: Max and mtc

>I've just put together a tutorial on mtc for my fall class (geatly expanded
>from something I posted here last winter). I will happily send a copy in
>Word 5.1 format to the first 5 people who ask. If more than 5 ask, I'll
>post it somewhere.
>
>Peter Elsea

Please post it somewhere.

Eirik Lie, Bjornerabben 9, N-0383 Oslo, Norway
Email: eirikli@notam.uio.no   -   Tel +47 22 50 23 14
Check out my CD "12 Bilder": http://home.sn.no/home/eiriklie/Visual.html

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

End of MAX Digest - 2 Aug 1997 to 3 Aug 1997
********************************************