Subject: MAX Digest - 26 Feb 1999 to 27 Feb 1999 (#1999-67)
Date: Sun, 28 Feb 1999 00:00:14 -0500
From: Automatic digest processor 
Reply-To: MAX - Interactive Music/Multimedia Standard Environments
     
To: Recipients of MAX digests 

There are 4 messages totalling 147 lines in this issue.

Topics of the day:

  1. looping with line~ and play~
  2. FUTURE MAX?
  3. play~, groove~ and loops
  4. max manual prominantly (?) displayed

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

Date:    Sat, 27 Feb 1999 00:03:24 -0800
From:    David Zicarelli 
Subject: Re: looping with line~ and play~

groove~ attempts to be sample-accurate in its loops. I have
long admitted however that it has some problem with clicking
when looping that I have not been able to fix.

The following is a patch that demonstrates how to do sample
accurate looping with variable speed playback using the count~
and play~ objects. If you want to play back the loop at the
original speed only, this patch can be simplified
by using count~ and index~.

A sample-accurate "line~ sequencer" is something I was
planning on attempting to convince everyone to pay for in
an MSP upgrade, but you never know, I might fall into a
generous mood.

max v2;
#N vpatcher 50 43 621 437;
#P comment 175 44 59 196617 begin (ms);
#P comment 239 44 50 196617 end (ms);
#P newex 316 75 40 196617 t b b f;
#P newex 176 104 27 196617 / 1.;
#P newex 235 104 27 196617 / 1.;
#P flonum 316 53 35 9 0 0 0 3;
#P newex 248 272 108 196617 *~ 1.;
#P button 176 60 15 0;
#P toggle 209 307 15 0;
#P newex 248 338 29 196617 dac~;
#P flonum 176 79 54 9 0 0 0 3;
#P flonum 235 78 54 9 0 0 0 3;
#P newex 235 125 64 196617 mstosamps~;
#P newex 247 171 52 196617 pack 0. 0.;
#P message 247 192 79 196617 set \$1 \$2 \, bang;
#P newex 193 145 64 196617 mstosamps~;
#P newex 248 210 38 196617 count~;
#P newex 248 239 64 196617 sampstoms~;
#P newex 248 310 50 196617 play~ foo;
#P newex 384 167 59 196617 buffer~ foo;
#P message 384 136 28 196617 read;
#P comment 57 41 107 196617 send left-hand number click button \, or move
speed control to trigger loop. A better interface is left to the reader as
an exercise.;
#P connect 19 0 11 0;
#P connect 14 0 11 0;
#P connect 11 0 18 0;
#P connect 19 2 18 1;
#P fasten 18 0 6 0 181 133 198 133;
#P connect 19 1 10 0;
#P connect 10 0 17 0;
#P connect 17 0 9 0;
#P connect 6 1 8 0;
#P connect 8 0 7 0;
#P connect 7 0 5 0;
#P connect 5 0 4 0;
#P connect 4 0 15 0;
#P connect 15 0 3 0;
#P connect 3 0 12 0;
#P connect 13 0 12 0;
#P connect 19 2 17 1;
#P connect 9 1 8 1;
#P connect 16 0 19 0;
#P fasten 19 2 15 1 351 182 351 182;
#P connect 1 0 2 0;
#P pop;

David Z.

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

Date:    Sat, 27 Feb 1999 16:46:15 -0500
From:    sean paul zitello 
Subject: FUTURE MAX?

Just wondering, those who are in a position to know: Is MAX done as far as
Opcode/IRCAM are
concerned or is it still a product with a life cycle.  Clearly DSP is its
future, but amatuer
MidiMultiMedists like myself, who took on faith that MAC was a superior
graphics platform,
well, we're just trying to figure out if its time to cut our losses and move
on from the
distant hope that anyone really wants to make it a MMM product.  So is it
still a product or
shall I bury it under a brown heavy 256 color palette?

sean paul zitello

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

Date:    Sat, 27 Feb 1999 20:51:41 EST
From:    Bob Ostertag 
Subject: play~, groove~ and loops

Hi Maxers,

This discussion of looping is very useful to me.  I have studied all the
proposed patches, but, at least to my understanding, none solve the problem
I
have.

My objective is to be able to, on the fly, modulate the loop start point
with
one controller, the end point with another, whether it is looping forward,
reverse, or for/rev with another, and, finally, the pitch with another.

I don't think this can be done with line~ and play~.  Trying to generate
line
segments with constantly updated start and end points would be a real mess.
Also, if you wanted to generate smooth pitch bends, you would have to send a
new list for line~ for each increment of the speed parameter in the list.
These lists would have to have start points that reflected not the loop
point
you wanted, but the current sample point being played back in the buffer~,
otherwise you would retrigger the loop.

If someone could eductae me as to why I am incorrect, I would be delighted.
But I see no way around these problems.

What is frustrating is that groove~ already does everything I want to
accomplish, EXCEPT the for/rev looping.  As I said earlier, I have
accomplised
this with groove~, but to make it work reliably, while modulated on the fly
all the parameters I mentioned, means that there is a lot of Max stuff
hanging
around which bogs down the whole system.

An addition to groove~ which involved a flag for for, rev, or for/rev
looping
would be so sweet...

Thanks for your time,
Bob

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

Date:    Sat, 27 Feb 1999 20:08:35 -0600
From:    William Sethares 
Subject: max manual prominantly (?) displayed

I was looking at the pictures in this months Keyboard
magazine (April 99) and saw on page 34 a photo of Jeff
Rona's studio. I was thinking what a great collection of electronics,
when I observed the only book visible - the MAX manual.

So Jeff, did you put it there specially for us?

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

End of MAX Digest - 26 Feb 1999 to 27 Feb 1999 (#1999-67)
*********************************************************