i'm working on a new set of clocks based on audio rate, since the last 

discussion we all had about, and i'm testing your metro~.

Please, REPLACE the fe.typecheck object by any typechecking object you 

This is really impressive how we got a steady irregularity (every 8 

f.e chanfrault | aka | personal computer music

> >>>>>> |sublime music for a desperate people|

i'm working on a new set of clocks based on audio rate, since the last 
discussion we all had about, and i'm testing your metro~.

print: 1001.360544
print: 1001.360544
print: 998.458050
print: 998.458050
print: 998.458050
print: 998.458050
print: 998.458050
print: 998.458050
print: 998.458050
print: 998.458050
print: 1001.360544
print: 1001.360544
print: 1001.360544
print: 1001.360544
print: 1001.360544
print: 1001.360544
print: 1001.360544
print: 1001.360544
print: 998.458050
print: 998.458050
print: 998.458050
print: 998.458050

Please, REPLACE the fe.typecheck object by any typechecking object you 
usually use (tap.typecheck or ej.route).

This is really impressive how we got a steady irregularity (every 8 
bangs) ! Any explanation ?

f.e
-- 
f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


about-metro-again

> This is really impressive how we got a steady irregularity (every 8 

The scheduler interval in your measurement is around 2 ms. It pretty 

stable compared to your vector size. Its pretty much what I would 

expect. sometimes 500 scheduler intervals, and if it drifts of more than 

half a scheduler interval it will switch to 501 scheduler intervals 

which corrects it into the other direction - till its half off...

If you switch into the scheduler world the resolution of events is 

smaller, but over a long period it will be pretty exact.

f.e schrieb:
> This is really impressive how we got a steady irregularity (every 8 
> bangs) ! Any explanation ?

The scheduler interval in your measurement is around 2 ms. It pretty 
stable compared to your vector size. Its pretty much what I would 
expect. sometimes 500 scheduler intervals, and if it drifts of more than 
half a scheduler interval it will switch to 501 scheduler intervals 
which corrects it into the other direction - till its half off...
If you switch into the scheduler world the resolution of events is 
smaller, but over a long period it will be pretty exact.

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


about metro~ again