Metro Synced to Transport
as far as i can tell, metro has two conditions to meet to sync to transport. interval has to be in a note tempo format, ie n, 4n, etc. and @ active 1. Im also asuming that just using @active in this case is default synced to the global transport, but name the tranport with @transport will sync to another transport? alos, is quantize necessary as well? if anyone can answer or confirm these, id appreciat eit.
others should correct me if wrong, but i'm pretty sure:
everything you said is true(@active can work with or without sync to transport: it's the same as tracking a toggle state you'd pass into the first inlet, or a bit like having @autostart but with a time that starts instantly)... except quantize is only necessary if you want many metros and other timing/clock critical objects to be exactly in sync with each other as they're all driven by the same transport(if you only ended up using one single metro and splitting off all your clock needs from there, but still have that metro sync to a transport(either just for tempo control or for external sync to another transport, etc.) , then you don't need quantize because you can setup your own quantization based on that main metro - another reason, other than synchronizing multiple metros, to need quantize is when using a single metro synchronized to a phasor~ with @lock). basically, 'quantize' is best when using multiple timer/clock/timing-critical objects all synchronized to the same transport, otherwise, they can all keep the same tempo-based interval, but might all be started at different times so might appear out of phase with each other by varying degrees.
hope it helps 🍻
that certainly helps. Im learning RTT toolkit and one of the example videos was comparing with metro and i realized how woefully little i knew about metro. I would want to sync several metros and quantize them on beat as well (although i believe RTT ignores or negates the need for this). Thanks!