Subject: MAX Digest - 23 Aug 1999 to 24 Aug 1999 (#1999-253)
Date: Wed, 25 Aug 1999 00:00:09 -0400
From:
Automatic digest processor <LISTSERV@LISTS.MCGILL.CA>
Reply-To: MAX - Interactive Music/Multimedia Standard Environments <MAX@LISTS.MCGILL.CA>
To: Recipients of MAX digests <MAX@LISTS.MCGILL.CA>


There are 8 messages totalling 325 lines in this issue.

Topics of the day:

  1. Starting detonate
  2. More on that SoftStep thing (2)
  3. timing (2)
  4. USB Midi Harware...
  5. USB midi
  6. to mute~ or not to mute~

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

Date:Tue, 24 Aug 1999 00:46:54 +0000
From:Jeff Mann <jefman@UTCC.UTORONTO.CA>
Subject: Re: Starting detonate

You missed the discussion on this a few weeks ago...

Frederic Murray <aae052@AGORA.ULAVAL.CA> wrote:
> is it possible to start detonate (not from the beginning) with another
> message then startat ?

No.

Unless... you know the event number you want, and you use an Uzi to send
that number of "next" commands to advance detonate to that note. This
doesn't seem very practical if you have a dense/long sequence, but it
might work in some cases. I haven't actually tried it so I can't really say.

>
> is it possible to start detonate with the starting time of a note ?

No.

Unless... you send a stream of "nth" commands until you find the nearest
note after the time you want, then do the above. Haven't tried this
either; let me know if you do.

Hopefully there will be a "locate" command added to detonate in the
future. In the mean time, you might want to try putting your sequences
into QuickTime movies using MoviePlayer, or you could try the sequencer
patch that Jeff Burns posted to the list a week or two ago (it doesn't
read MIDI files though).

<Jeff
--
Jeff Mann - Information Consumer ___O___O__= -- >
mailto:jefman@utcc.utoronto.ca||http://www.interlog.com/~jefman
Visit the Art & Robotics Group site: http://www.interaccess.org/arg

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

Date:Mon, 23 Aug 1999 22:29:29 -0700
From:Tim Thompson <tjt@NOSUCH.COM>
Subject: Re: More on that SoftStep thing

> Basically it's a slick but very simplified subset of Max optimized for
> sequence generation. It reminds me of Interactor more than Max actually.


> Seems similar to but less powerful than KeyKit, from what little I've seen
> of that.

There is virtually no resemblance between SoftStep and KeyKit,
unless you're counting the number of rectangles that appear in the GUI.

...Tim...

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

Date:Tue, 24 Aug 1999 09:45:52 +0200
From:Jeffrey Burns <jeff@BERLIN.SNAFU.DE>
Subject: timing

>How about using the train~ msp object for driving metronome related
>objects for a
>more steady/accurate timing pulse? Has anyone experimented with this?

Absolutely brilliant idea!

Here is a train-based clock that gives a signal every 2 ms. which is
accurate to 1 ms. and whose accuracy over long periods is equal to that of
the hardware's quartz timing.

max v2;
#N vpatcher 50 40 341 278;
#P toggle 20 167 15 0;
#P newex 20 193 42 196617 adc~ 1;
#P message 182 40 76 196617 \; max interval 1;
#P newex 49 119 35 196617 1000;
#P newex 134 119 26 196617 2;
#P newex 20 40 50 196617 loadbang;
#P newex 185 193 72 196617 noteout;
#P newex 185 143 29 196617 60;
#P newex 185 167 72 196617 makenote 60 5;
#P newex 20 96 39 196617 train~;
#P message 164 73 50 196617 clock real;
#P toggle 185 96 15 0;
#P number 225 96 35 9 0 0 0 3;
#P newex 185 119 50 196617 metro;
#P newex 49 143 95 196617 setclock real interp;
#P newex 20 73 35 196617 1000.;
#P comment 39 167 100 196617 dsp on/off;
#P comment 78 40 85 196617 This is the Clock!;
#P connect 17 0 16 0;
#P connect 14 0 3 0;
#P connect 13 0 3 1;
#P connect 12 0 2 0;
#P fasten 12 0 13 0 25 64 139 64;
#P fasten 12 0 7 0 25 64 169 64;
#P fasten 12 0 15 0 25 64 169 64 169 37 187 37;
#P connect 10 0 9 0;
#P connect 9 0 11 0;
#P fasten 9 1 11 1 252 188 221 188;
#P connect 8 1 14 0;
#P fasten 7 0 4 0 169 115 190 115;
#P connect 6 0 4 0;
#P connect 5 0 4 1;
#P connect 4 0 10 0;
#P connect 2 0 8 0;
#P pop;

Jeff Burns

http://www.snafu.de/~jeff

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


Date:Tue, 24 Aug 1999 09:57:57 -0400
From:Neal Farwell <nfarwell@FAS.HARVARD.EDU>
Subject: timing

I mentioned this a while back though it wasn't picked up...


Apple claim that their new Open Firmware on the G3 Series powerbooks (and
blue G3s?) yields vastly reduced interrupt latency times over all the
previous ROM-based models. If each interrupt task is simple, that should
mean the total time from receiving-an-interrupt to finishing-its-task
should be substantially reduced. I've been wondering:

- does this in principle or in fact improve MAX timing jitter?

- would it enable Apple to allow shorter Sound Manager buffers, so that
audio latency could be reduced?

Knowledge and guesses welcome...


By the by, I used to have access to a Silicon Graphics Indy for audio work
- very fast, but the unix-like OS would periodically go and do arcane
system management tasks, not ideal for audio smoothness. So it's not just
the Mac.

Neal

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

Date:Tue, 24 Aug 1999 11:54:53 -0400
From:Timothy Andrew Holt <tholt@STETSON.EDU>
Subject: USB Midi Harware...

I've heard a lot of people having problems with usb midi hardware on this
list. I only have experience with the opcode midiport, but it has been
rock solid so far. It hasn't flinched at controller data that has made a
studio 5 choke (not a single overflow error message so far). So if you
need a recomendation then get it instead of the midiman. I'm running oms
2.3.7 on a 333 mhz imac. In theory the usb interfaces offer so many
advantages over their traditional serial counterparts that it's a shame
there are so many problems with them. But I'm sure that will be better in
the future.
Tim
http://www.stetson.edu/~tholt

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

Date:Tue, 24 Aug 1999 12:44:42 -0400
From:Stephen Kay <sk@COMPUSERVE.COM>
Subject: More on that SoftStep thing

If you're interested in "MAX like" things that run on the
PC, you might want to check out Algorithmic Composer at:

http://users.hunterlink.net.au/~maaaf/

Stephen Kay

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

Date:Tue, 24 Aug 1999 10:47:49 -0600
From:Adam Schabtach <nebulous@EARTHLINK.NET>
Subject: Re: USB midi

>I also wonder what kind of sign it is, that Opcode just sent me a message

>exclaiming
>" MIDI for the Blue and White G3! ", and it's an ad for the Stealth Serial
>Port made by geethree, not one of the USB interfaces made by Opcode.

Actually the point of using the Stealth port in a B&W G3 is that it
lets you use existing serial-port MIDI interfaces, such as Opcode's
Studio 4 and Studio 5. This is good news for those of us with
substantial investments in serial-port-based equipment that we'd like
to continue using with newer host computers.

--Adam

Adam Schabtachnebulous@earthlink.net
see me: http://home.earthlink.net/~nebulous/adamcam/

"If it ain't broke, break it!"
--Name withheld to protect the mischievous

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

Date:Tue, 24 Aug 1999 20:51:13 +0300
From:Tom Mays <tmays@HOL.GR>
Subject: to mute~ or not to mute~

David Z. said that R. Dudas said:

>Richard Dudas pointed out to me recently that mute~ does not
>mute DSP objects in subpatchers of the patcher you're muting.
>For this you would want to send the enable 0 1 message to
>pcontrol and to reenable, enable 1 1. The second 1 argument to
>the enable message denotes a "deep" enable/disable that
>reaches all MIDI and DSP objects in all subpatchers of the patch
>you are enabling/disabling.

With all due (and possibly overdue) respects to Dr. rD Xoaz, further
laboratory verification has re-concluded that when mute~ receives
1 1 and 0 1 messages it TOO mutes and unmutes subpatchers - at least
with cycle~s and send~s. See patcher as text that follows.


Je vous prie d'agr=E9er l'expression de mes salutations les plus r=E9spectue=
uses.

tmz;-)

max v2;
#N vpatcher 50 40 323 237;
#P toggle 59 30 15 0;
#P message 59 48 29 196617 \$1 1;
#P newex 59 67 35 196617 mute~;
#P toggle 17 127 15 0;
#P newex 56 143 29 196617 dac~;
#N vpatcher 335 40 561 237;
#P outlet 55 123 15 0;
#P newex 55 102 71 196617 receive~ hghg;
#N vpatcher 50 265 706 398;
#P newex 565 82 55 196617 send~ hghg;
#P newex 565 61 51 196617 *~ 0.001;
#P newex 565 40 59 196617 cycle~ 440;
#P newex 504 82 55 196617 send~ hghg;
#P newex 504 61 51 196617 *~ 0.001;
#P newex 504 40 59 196617 cycle~ 440;
#P newex 443 82 55 196617 send~ hghg;
#P newex 443 61 51 196617 *~ 0.001;
#P newex 443 40 59 196617 cycle~ 440;
#P newex 382 82 55 196617 send~ hghg;


#P newex 382 61 51 196617 *~ 0.001;
#P newex 382 40 59 196617 cycle~ 440;
#P newex 321 82 55 196617 send~ hghg;
#P newex 321 61 51 196617 *~ 0.001;
#P newex 321 40 59 196617 cycle~ 440;
#P newex 260 82 55 196617 send~ hghg;
#P newex 260 61 51 196617 *~ 0.001;
#P newex 260 40 59 196617 cycle~ 440;
#P newex 199 82 55 196617 send~ hghg;
#P newex 199 61 51 196617 *~ 0.001;
#P newex 199 40 59 196617 cycle~ 440;
#P newex 138 82 55 196617 send~ hghg;
#P newex 138 61 51 196617 *~ 0.001;
#P newex 138 40 59 196617 cycle~ 440;
#P newex 77 82 55 196617 send~ hghg;
#P newex 77 61 51 196617 *~ 0.001;
#P newex 77 40 59 196617 cycle~ 440;
#P newex 16 82 55 196617 send~ hghg;
#P newex 16 61 51 196617 *~ 0.001;
#P newex 16 40 59 196617 cycle~ 440;
#P connect 0 0 1 0;
#P connect 1 0 2 0;
#P connect 3 0 4 0;
#P connect 4 0 5 0;
#P connect 6 0 7 0;
#P connect 7 0 8 0;
#P connect 9 0 10 0;
#P connect 10 0 11 0;
#P connect 12 0 13 0;
#P connect 13 0 14 0;
#P connect 15 0 16 0;
#P connect 16 0 17 0;
#P connect 18 0 19 0;
#P connect 19 0 20 0;
#P connect 21 0 22 0;
#P connect 22 0 23 0;
#P connect 24 0 25 0;
#P connect 25 0 26 0;
#P connect 27 0 28 0;
#P connect 28 0 29 0;
#P pop 1;
#P newobj 79 59 42 196617 patcher;
#P inlet 26 24 15 0;
#P connect 2 0 3 0;
#P pop 1;
#P newobj 59 92 42 196617 patcher;
#P comment 111 32 128 196617 10 to 12% when mute off \; around 3.5% when
mute on;
#P comment 128 76 100 196617 Try duplicating row of cycle~s in sub/sub
patch for more dramatic results...;
#P connect 4 0 3 0;
#P connect 7 0 6 0;
#P connect 6 0 5 0;
#P connect 5 0 2 0;
#P pop;

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

End of MAX Digest - 23 Aug 1999 to 24 Aug 1999 (#1999-253)
**********************************************************