change quantize on metro
Is it possible to change the @quantize value of a metro by sending it a message ?
Basically, i need to make a synced metro which could (quickly/permanently) change its synced time but keep perfectly synced to Live.
Using a single metro does fit to Live tempo but is not synced...
thanks a lot raja
but now that i learned this, i realize it doesn't solve my problem ....
I need to make a changing metro, but as i said before, the "metro" object always fits to live's tempo but doesn't stay perfectly in sync with Live's own metronome... Don't really know how to do this. I tried to use transport, plugsync~, but they don't have their 'own' tick and are only dependent on live's one.
Any idea ? thanx again
hi tep, i dont use M4L, but you may want to consider simply using milliseconds rather than quantize messages. If there is a way to get Live's BPM (which there absolutely has to be), then you can find out how long a quarternote is n milliseconds through the object [!/ 60000]. Then you can divide that by any value for subdivision MS values.
here's an example that demonstrates this along with quarternote quantization, useful for changing metro values in a live performance setting:
metro 4n @quantize 4n @active 1
Is the same as Live's metronome.
Hopefully that should be enough to get you going.
-A
thank you people,
i know i am not very clear about what i'm trying to achieve (though the example of Comfortable works in Max, but doesn't stay synced in M4L)
The idea is : let's say in a bar i want a metro to jump from 8n to 4n to 1n to 16n to .... and always be sync with Max.
Dunno how to do it ... Once i change a value in metro, the sync is lost. I mean, the metro follows Live's tempo of course, but it doesn't fit to the metronome anymore. There's an offset.
Sorry to insist !
Hello,
you don't say if you link your metro object to a transport object, to get Live's timing. Or d'you use another mean?
I'm away from my testing computer right now so I can have a look at this in the morning.
In the meantime
Why not have a bunch of metros running at different rates, and switch between them.
What you'll actually end up with in the long run is a step sequencer, have a look at the internals of the Step Sequencer device.
-A
for those like me who find this thread more than 7 years later... here's the answer, which I copied from the mono sequencer.
edit: it turns out that it is better to just have separate metronomes, though... with one metro, you can decrease the subdivision immediately, but it takes time to increase the subdivision.
So... another 7 years ahead... Why would I be wanting to send messages containing "interval" and "quantize" through the left inlet of a metro object, when sending plain integers through the right inlet would suffice? The answer to that question is that both methods do not seem to work in exactly the same way. Or something like that. I'm hoping someone could send me to an explanation that offers some definitive clarity.