Analogue-sequencer

You guys are confusing timestamping with an actual time reference.

OK, so MTC is sending an arbitrary clock to reference the two machines
- it is not sending the EXACT interval of the tempo - you are
assumming that each and every one of your devices are individually
calcualting the tempo IDENTICALLY.

All that I am saying is that, when running with MTC, if the individual
machines do not output the exact tempo as the next, and they do not
run together, you are SOL, even if you believe that MTC provides
'absolute lock".  (Which I don't).

The Wilkopedia articles discuss how often MTC outputs data to provide
"sync".  Once again, this is the generator's speed to announce where
it is - how quickly it sends data to the display.

This isn't the issue - it is how often the slave checks the master
code.  Most all of MTC devices list parameters about how often the
device should look at the master MTC, and how slop there should be in
the case of error. 

gary


Nick Rothwell <nick@...> wrote:
>
Assuming maths of  
> sufficient accuracy, two devices with the same tempo figure should be  
> able to stay locked by constantly doing the frames-to-beats  
> calculations; they aren't free-running.