czesc.list

metronome

The problem is that metro is not really a metronome. It is an alarm clock.

The ms time parameter tells metro how long to wait until the next bang.

Updates to the right inlet take effect when the previous time period

expires. If you are going from fast to slow this may not be evident but

slow to fast certainly is. At the point where you change from mm = 160 to

80 this will be quite obvious. Unfortunately waiting for a bang doesn't to

the trick since the next time delay has already begun. The remedy is the

tempo object. You might also try metro~. I looked at it but I'm not sure

The problem is that metro is not really a metronome.  It is an alarm clock.
The ms time parameter tells metro how long to wait until the next bang.
Updates to the right inlet take effect when the previous time period
expires.  If you are going from fast to slow this may not be evident but
slow to fast certainly is.  At the point where you change from mm = 160 to
80 this will be quite obvious.  Unfortunately waiting for a bang doesn't to
the trick since the next time delay has already begun.  The remedy is the
tempo object.  You might also try metro~.  I looked at it but I'm not sure
how it works.

Cheers,
Gary Lee Nelson
TIMARA Department
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson


On 12-Jun-2006, at 17:41, Gary Lee Nelson wrote:

> The problem is that metro is not really a metronome. It is an 

Thinking outside the box, it occurs to me that a solution could be 

found in the Litter Power object lp.frrr~. I know that when I built 

the object, I added code to specifically deal with the issue of the 

user increasing the speed of pulses. Instead of waiting for the next 

"alarm" to ring before adjusting tempo, frrr~ calculates what 

percentage of time-between-pulses has passed and adjusts the 

scheduled time of the next alarm proportionally, based on the new 

pulse rate. So whenever you change pulse rate, frrr~ responds with a 

If metro~ or tempo does this, then fine. But if you're still looking 

for a solution, someone (maybe even li'l ol' me) could look into 

Peter Castine +--> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|

Interface Building for |bei uns | i nostri|

On 12-Jun-2006, at 17:41, Gary Lee Nelson wrote:
> The problem is that metro is not really a metronome.  It is an  
> alarm clock.

Thinking outside the box, it occurs to me that a solution could be  
found in the Litter Power object lp.frrr~. I know that when I built  
the object, I added code to specifically deal with the issue of the  
user increasing the speed of pulses. Instead of waiting for the next  
"alarm" to ring before adjusting tempo, frrr~ calculates what  
percentage of time-between-pulses has passed and adjusts the  
scheduled time of the next alarm proportionally, based on the new  
pulse rate. So whenever you change pulse rate, frrr~ responds with a  
slower or faster tempo immediately.

If metro~ or tempo does this, then fine. But if you're still looking  
for a solution, someone (maybe even li'l ol' me) could look into  
building an example with lp.frrr~.

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter

> The problem is that metro is not really a metronome. It is an alarm clock.

One workaround could be, to do it as in the Midi spec: Midiclock is a 

clock wich is 24-times faster than the beat...

metro's resolution might not be good enough for that though...

Gary Lee Nelson wrote:
> The problem is that metro is not really a metronome.  It is an alarm clock.

One workaround could be, to do it as in the Midi spec: Midiclock is a 
clock wich is 24-times faster than the beat...

metro's resolution might not be good enough for that though...
(In that case move to MSP...)

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


An easy hack I've used is this situation is to restart the metronome by sending it a '1' to the left inlet each time you change the speed. A [trigger 1 i] works well.