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

There are 8 messages totalling 227 lines in this issue.

Topics of the day:

  1. Syncing MIDI ports independently (2)
  2. Mexico
  3. PCI Serial Port Cards
  4. Libswitch problem in 3.5.1
  5. FAT Aiffplayer?
  6. Nintendo Power Glove
  7. 68K vs. PPC

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

Date:    Mon, 21 Apr 1997 02:03:37 -0700
From:    James Reynolds 
Subject: Re: Syncing MIDI ports independently

Nick Rothwell wrote:
Nick Rothwell wrote:
>I could have sworn I posted a reply to this, but I've looked through my
out
>box and don't see one...

yes, you did, nick - thanks for the info.

>AFAIK they all work
>this way. After all, who would want to run different ports with different
>clocks, right? Not your average pop producer. They don't call it "global
>sync" for nothing.

hmmm... some of us who aren't the "average pop producer" might prefer
something like "continental sync"?

>you could try using
>discrete serial ports on the computer for differing sync values.

using discrete serial ports seems to be the only way to have devices
receive discrete sync.  it works, but it means i can only get two different
sync resolutions going simultaneously, rather than the three or four i was
hoping for.

in case anyone's curious, my goal was to have looping delay devices (each
individually fed with improvised effected sounds) layering polymetrical
textures - for example, one device looping a 4/4 measure, one looping 5/4,
and one 6/8 (eighth note constant duration for all three).  the result
would be a sort of steve reich phasing effect, where all the parts would
start together, get out of phase, and eventually reconverge.  the sample
held in each device can be modified and relayered in realtime, and by
varying individual sync rates, one time signature could be "morphed" into
another.

well, it was just an idea...

james

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

Date:    Mon, 21 Apr 1997 13:24:14 +0200
From:    Le Quan Ninh 
Subject: Mexico

Hello,
Does anybody on this list involved in improvised interactive computer music
in Mexico city ?

Le Quan Ninh

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

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

Date:    Mon, 21 Apr 1997 08:34:38 -0300
From:    Alex Noyes 
Subject: PCI Serial Port Cards

I have a feeling this was recently discussed here, but I was temporarily
unsubcribed and lost the info. Does anyone know of any serial cards for
PCI based macs? Is anyone using one? I'm hard at work modifying an
installation that needs to control 2 Laserdisc players, 1 Video
switcher, and mucho MIDI. I was using a quadralink card, but now need to
switch to PPC/PCI.

Alex

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

Date:    Mon, 21 Apr 1997 07:16:56 +0000
From:    Tod Fiste 
Subject: Libswitch problem in 3.5.1

David Z,

I'm having some problems with the libswitch object in 3.5.1.
Specifically, I can't seem to get libswitch to work from any patcher
other than the one designated as the editor in the libscript (which
I'll call the "correct" patcher).  It used to be (3.5) that when you
placed a libswitch object in a patcher other than the "correct" one a
message would come up in the Max window saying "warning: libswitch:
can't be in a subpatcher", but using the libswitch in that patcher
worked anyway.  Now it doesn't.  I understand if that's not the right
way to go about things, but I can't figure out any way to get the
libswitch object in the "correct" patcher to recognize messages I send
it from the "wrong" patcher.  (By the way, the "wrong" patcher in this
case is opened by sending a link message to the lib object - it's not
really a subpatcher of the "correct" patcher.)

To get around the problem I tried creating a bpatcher object in the
"wrong" patcher that points to the "correct" patcher, with an inlet in
the "correct" patcher that feeds into the libswitch object and a print
object.  Sending messages to the bpatcher object causes the print to
happen, so I know that the message is getting through, but the
libswitch ignores it!  (This part is true in both 3.5 and 3.5.1).

So what's a guy to do?  It's apparently illegal to put a libswitch
object in any patcher except the one specified as the editor, but I
can't get the libswith object in that patcher to recognize messages
sent from other patchers.  If I can only do libswitch operations from
the editor patcher, it means I must effectively do my whole librarian/
editor application in that one patcher.  So much for modularity!  Say
it ain't so, David!

Thanks,

Tod

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

Date:    Mon, 21 Apr 1997 12:35:40 -0400
From:    Eric Singer 
Subject: Re: FAT Aiffplayer?

Hi, Karl,
I hope you don't mind me CC:ing the list on my response....I do plan to
make FAT versions of all of my objects.  However, it won't have time until
the summer to do this.  When I do, I will announce it on the list and my
web page.

Eric

On Mon, 21 Apr 1997, Dr. K@rlheinz Essl wrote:

> Dear Eric!
>
> If someone else already asked you the same question, please forgive the
> redundance. I am just wondering if it is possible that you or someone else
> will FATten your wonderful "AiffPlayer" - I think it is not only me who
are
> interested.
>
> Cheers,
>   --- K@rlheinz
>
>
> Dr. K@rlheinz Essl
> SAMT - Studio for Advanced Music & Media Technology
> Bruckner-Konservatorium Linz / Austria
> www:   http://www.ping.at/users/essl/index.html
>
> ________________________________________________________________________
>      Visit the MindShipMind - an interactive multimedial Web Oracle
>           http://www.ping.at/users/essl/works/mindshipmind.html
> ________________________________________________________________________
>
>
>

**********************************
*                                *
*          Eric Singer           *
*    Media Research Laboratory   *
*       New York University      *
*   email: esinger@cat.nyu.edu   *
*  web: http://cat.nyu.edu/eric  *
*                                *
**********************************

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

Date:    Mon, 21 Apr 1997 11:35:44 -0700
From:    David Zicarelli 
Subject: Re: Nintendo Power Glove

>The only thing at this stage which would make me even contemplate a
>PPC-based machine and MAX 3.5 is if the timing jitter is much improved.
>
>(Cue for David Z. to come along and tell me that it is...)

Something that might reassure Nick even more is for someone who
has a fast PPC machine to tell him that Max 3.0 runs better on it
than a 68K machine.

David Z.

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

Date:    Mon, 21 Apr 1997 21:49:04 +0100
From:    Nick Rothwell 
Subject: 68K vs. PPC

>Something that might reassure Nick even more is for someone who
>has a fast PPC machine to tell him that Max 3.0 runs better on it
>than a 68K machine.

You mean, like a testimonial...?

Roland Hemming is already trying to persuade me along these lines with 3.5.
I thought that 3.0 wasn't at all PPC-native? I don't even want to think
about whether I'd need to recompile all my own THINK C externals...

Anyone know whether the PB520 PPC upgrades are still available? Just
curious at this stage.

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

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

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

Date:    Mon, 21 Apr 1997 18:22:43 +0100
From:    Nick Rothwell 
Subject: Re: Syncing MIDI ports independently

>hmmm... some of us who aren't the "average pop producer" might prefer
>something like "continental sync"?

What you're after is the infamous "kitchen sync" facility. Unfortunately,
most modern music products these days seem to offer everything but the
kitchen sync.

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

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

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

End of MAX Digest - 20 Apr 1997 to 21 Apr 1997
**********************************************