sync transport to external clock
hi, any hingst on how to sync transport to Incoming mtc or midi clock ?
thx
hints ....
Here is an example of syncing transport to midi clock (start, stop, tempo).
thanks ;-)
Hey guys I have used this and it works wonderfully for a LIVID Block Step Sequencer I built about a year ago and still use. I am currently documenting my build process and was wondering @BROC if you could explain what this sub-patch is doing to actually accomplish the result I am so glad works? haha
I am kinda confused on why the arguments are '248 250 252' and how the math works the way it does in the 'expr' object (60000/(24 * $f1))
Thank you!
you read "exprs" from inside to out... what has more brackets is processed first.
expr (60000/(24 * $f1))
is the same as
[* 24.]
[!/ 60000]
248, 250, 252 is the decimal representation of F8, FA, FC
in combination with [rtin], 284 is the ticks of incoming midi beat clock.
which is not the same as midi time code.
if your device can send that, too, this is the easiest way to sync stuff.
Hi Austin, I'm glad the patch is useful for you.
Re the expr (60000/(24 * $f1)):
According to the MIDI standard there are 24 clock messages per beat. The [timer] object measures the time interval ($f1) between them. So the time of one beat can be calculated with 24*$f1, and the tempo (beats per minute) is 60000 divided by the beat time.
BROC. Thank you for this info. I'm serious you really helped me out here. I hope you live forever.
BROC, i've not yet read the rest of the thread beyond Mickey242's last reply, so i can't say whether you helped me out here, yet still I can say that I, too, hope you live forever 💙
Hi, any idea where to find this [mtc] external these days? :)
mtc - midi time code is a midi message.
needs no external.
sounds like peter elsea... but you really don´t need it.