Hello, this is may appears really simple to some of you but I was wondering something about tempo division. What is the best from a cpu and/or coding point of view?
For the moment when I want to divide my tempo I do something like that :

[metro 200]
[f][+1]
[mod 12] this one is sent to some stuff
[sel 0]
[f][+1]
[mod 6] for example, every 12 steps, 1 of 6 event is triggered

this seems really ugly and I was wondering if there were another way to do that?

I have thought about different metros at the good speed rate also...
thanks a lot

decide your fastest possible speed and set your metro to that. so maybe even [metro 1]

then instead of

[f ]x[+ 1]

you just do something like:

[f ]x[+ 0.01]
|
[int]
|
[change]

and then just vary the value going into the +0.01 to change speed

cool, thanks. I will try soon.
Isn't [metro 1] CPU consuming?
And, so you say (or maybe not) that it's better for me to have just one metro instead of several, just for the clarity of the patch? or is there any other reason...?

if you have just one metro, it's foolproof with timing, more elegant, easier to debug, you only need one receive input for the rate value, etc.

[metro 1]
|
[f ]x[+ 0.01]
|
[int]
|
[change]

would use very minimal CPU,

i just checked and i could make about 400 copies before spiking the CPU of my old mac.

thanks, i can see better now.
A 0.01 tempo definition would maybe be too much for my simple patches but I keep that in mind for another time.