Subject: MAX Digest - 28 Jan 1999 to 29 Jan 1999 (#1999-35)
Date: Sat, 30 Jan 1999 00:00:00 -0500
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
     
To: Recipients of MAX digests 

There are 7 messages totalling 235 lines in this issue.

Topics of the day:

  1. fiddling with fiddle~ (3)
  2. Authorization Codes on new Macs (2)
  3. USB Mac MIDI solution
  4. corrupted patches

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

Date:    Thu, 28 Jan 1999 21:34:20 -0800
From:    dudas 
Subject: fiddling with fiddle~

Dan Trueman writes:

>I've been having great fun and getting good results from fiddle~. I am
>running several interfaces that use it, and I've noticed that if I open a
>second interface that uses it (closing the first, without quitting MAX in
>between), when I
>close that second interface, MAX crashes. This is quite consistent. If I
>quit MAX in between, I don't have this problem. I'm wondering if anyone
>else has had this experience, and if there might be an easy fix.

I know that several people here at CNMAT have been using fiddle~ and were
getting regular crashes.  I do not know if these people found any rhyme or
reason for the crashes, however.

In the end, they had to go back to using the pt~ object that is part of
Ircam's ISPW compatibility lib, to do some crude monophonic pitchtracking.
Too bad, because apparently fiddle~ worked SO much better when it was
working...

-R

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

Date:    Fri, 29 Jan 1999 01:30:21 -0500
From:    Dan Trueman 
Subject: Re: fiddling with fiddle~

I have noticed that when I open the second interface, the object does not
post its "fiddle~ 1.0" message in the MAX window, which reminds me that
it is not unloading and reloading the object. I wonder if this could have
anything to do with it; perhaps some of its buffers get screwed up. Is
there a way in MAX to tell it to unload and reload a specific object?

tak,
dan

On Thu, 28 Jan 1999, dudas wrote:

> Dan Trueman writes:
>
> >I've been having great fun and getting good results from fiddle~. I am
> >running several interfaces that use it, and I've noticed that if I open a
> >second interface that uses it (closing the first, without quitting MAX in
> >between), when I
> >close that second interface, MAX crashes. This is quite consistent. If I
> >quit MAX in between, I don't have this problem. I'm wondering if anyone
> >else has had this experience, and if there might be an easy fix.
>
>Dudas:
>
> I know that several people here at CNMAT have been using fiddle~ and were
> getting regular crashes.  I do not know if these people found any rhyme or
> reason for the crashes, however.
>
> In the end, they had to go back to using the pt~ object that is part of
> Ircam's ISPW compatibility lib, to do some crude monophonic pitchtracking.
> Too bad, because apparently fiddle~ worked SO much better when it was
> working...
>
> -R
>

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

Date:    Fri, 29 Jan 1999 16:17:19 +0100
From:    sven erga 
Subject: Authorization Codes on new Macs

Hello all!
I am about to buy one of the new G3 macs, and I wonder about how to
install MAX and other software without the seemingly obsolete 3,5"
diskette drive. How can I cope?
Best wishes
-sven

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

Date:    Fri, 29 Jan 1999 13:54:35 -0500
From:    Bob Gluck 
Subject: USB Mac MIDI solution

I have continued to research USB Mac MIDI solutions and finally found one.
Apple was uninformed and unhelpful, but Opcode sent me in the direction of
Griffin Technology (although they didn't have the phone number; I found
Griffin on the web). Apparently, Griffin will be releasing the "G Port" in
2-4 weeks. They have already released an "I-Port" for the iMac. When I
spoke with Griffin sales, they wouldn't be specific about what exactly the
"device" is or how it works, except to say that it is not a PCI card (good
news) and that it addresses the issue of serial clocking data that the USB
to serial adapters don't touch. They had the MIDI market in mind when
developing this board or whatever. The price will be $59.00. The sales
number is (615) 255-0990.

Of course, sending and receiving MIDI data doesn't address the copy
protection problem which has now only worsened with the new G3s lacking a
floppy drive. Hopefully this additional log in the road will put more
pressure on Opcode to move away from the authorization disk copy protect
scheme.

Bob

New web site: http://www.rpi.edu/~gluckr/home.html

Semi-comic words of the month: "I'm from the House, you know, the working
class..."  -Rep. Henry Hyde, R-MI

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

Date:    Fri, 29 Jan 1999 15:24:05 -0500
From:    Stephen Kay 
Subject: Re: fiddling with fiddle~

>I have noticed that when I open the second interface, the object does no=
t
>post its "fiddle~ 1.0" message in the MAX window, which reminds me that
>it is not unloading and reloading the object. I wonder if this could hav=
e
>anything to do with it; perhaps some of its buffers get screwed up. Is
>there a way in MAX to tell it to unload and reload a specific object?
> dan

The way most max objects are written, they only post a message the
very first time an instance is created.  Imagine if you use 400 gates
in a patch and had to watch a "gate 1.0" message appear 400 times
while loading the patch.

The first "instance" actually loads the code necessary to create
the object.  The 2nd through nth instances simply replicate what
was already loaded.  =

While I don't know what is going on with the fiddle~ object, the
fact that it's not posting a second message doesn't mean anything.

Stephen Kay
---------------------- The MegaMAX Collection ----------------------
 Over 30 Max objects for the creation of more professional looking, =

         feeling, and functioning patchers and applications.
           http://www.musikinetix.com/MegaMax/MegaMax.html
------------------------ Free Max objects! -------------------------
       http://www.musikinetix.com/MaxCorner/PublicDomain.html
--------------------------------------------------------------------

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

Date:    Fri, 29 Jan 1999 12:56:19 -0700
From:    Alex Stahl 
Subject: Re: Authorization Codes on new Macs

At 8:17 AM -0700 1/29/99, sven erga wrote:
>Hello all!
>I am about to buy one of the new G3 macs, and I wonder about how to
>install MAX and other software without the seemingly obsolete 3,5"
>diskette drive. How can I cope?

Coping is the operative verb.

You can:

-- get a SCSI card for your new G3, authorize an external SCSI hard drive
on an old computer, then attach that drive to the new system;
-- buy a new Max/MSP bundle from cycling74 and authorize via
challenge/response codes
-- wait (how long???) for a solution from PACE and Opcode.

You cannot:

-- buy an external USB floppy drive and use it to authorize. At least, not
yet you can't.

You might be able to:

-- find someone with a Performa or some other older Mac that has both a
floppy drive and an IDE/ATA hard drive, boot the Performa off the internal
drive from a standard SCSI-less G3, authorize it, and reinstall it in the
G3.

All this drive swapping isn't quite as bad as it sounds given the ease of
access inside the new G3's, but it's still pretty silly. I needed SCSI
anyway so I went the first route.

http://www.userfriendly.org/cartoons/archives/99jan/uf000222.gif

-Alex S.

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

Date:    Fri, 29 Jan 1999 19:56:16 +0000
From:    Michael DeMurga 
Subject: corrupted patches

I've opened up patches today and, out of the blue, their cords are all
scrambled.  Objects are connected improperly, cords have multiple
segments aiming in random directions, etc.

I remember hearing about problems like this before, but can't seem to
track down any information on a solution.

Is there a way to correct this problem and restore the patches to their
pre-scrambled state?

Many thanks,

Mike

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

End of MAX Digest - 28 Jan 1999 to 29 Jan 1999 (#1999-35)
*********************************************************