quantize with metro
Hello !
I do not quite get it when I use @quantize in a metro. What is it
made for ?
I understand this is like having a speedlim after a metro but I'd
love to see an example showing what it is made for.
metro 4n @autostart 1 @autostarttime 0 @quantize 2n
OliveR
If you have a [metro 4n], and you don't quantize it, then it will output a bang every quarter note starting from the moment the metro is turned on. But this will not necessarily be on the beat, because you might have turned on the metro in the middle of the beat.
If you want to make sure the metro is on the beat, then you use quantize. It will send the first bang at the next quantize point, and then every quarter note after that.
If you use timepoints to start a metro on the beat, then you probably don't need to worry about this. If you let the user start and stop metros, and you want to keep everything in sync, you should use quantize.
Probably dumb question, but how do you "unquantize" a [metro] after having quantized it ? "quantize 0" doesn't seem to work.
EDIT : yep, it was dumb, as the metro remains "in sync" until it's banged.
I've been trying to make my own little example patches of this to learn it.
My interest would be to have multiple metros running at different clock divisions to run different sequencers at different rates, and be able to do things like ratchets.
I know about phasor as a clock, I'm just doing tests to figure out which is the most appropriate before getting too deep into the project.
@quantize does seem to permanently speed limit the metro, so you can send new arguments, but only ones slower than the @quantize clock rate take effect.
What I've also found strange is that with two metros with the same @quantize value will stay in sync, even if receiving separate note value messages, but if they have different @quantize values to begin with, they can fall out of phase even when receiving the same note value message, and even when stop/starting the transport.
Please let me know if I've made a silly mistake here and there's a way to get them completely sync'd.
I've also had strange behaviors when trying to send a series of quick updates to the metro interval inlet. Sometimes it felt like certain input values had no effect, or sped/slowed in the wrong direction.