Hoping some other T/T+ users can test this before I submit a bug.
I had my T+ and another device set to exactly the same tempo. Pressed play on the T+ and then hit play on the other device (Model:Cycles) to manually ‘sync’ them. They played in sync for a while and then they started to drift apart. Thinking it was odd I tried the same test with T+ and Roland P6. Same thing happend - after a while the T+ starts to drift out of sync. Seems the internal clock on the T+ isn’t stable?
I wouldn’t say the subject never comes up, but it’s usually a configuration issue. I think we’d be hearing about it non-stop if it was an issue with the Tracker.
For the Model:Cycle, do you have it set up to take Type B MIDI? I’ll set up my Tracker to Drive some of my synths later to day and let it run for an hour or so. I’ll check back in later and share my results.
I think the main issue is that hardly any device out there has a stable clock.
So drift will always happen, regardless of which device you use, when they aren‘t clocked to eachother.
It‘s the nature of MIDI really. There is no standard as to how clocks are calculated so most manufacturers use their own implementation or run at different PPQ‘s and ticks. This inevitably leads to drift over time.
If you want to prevent that i would suggest you sync them. If all you want is for the clock not to start transport on the other device as well, most devices allow to enable/disabled Transport In.
Hope that helps 
Perhaps I didn’t explain properly. I don’t have the T+ connected via MIDI to the M:S (or the P6) I’m just pressing play on the M:S as the T+ is playing to make them play in time. Eventually they drift out of time which, if both devices are set to exactly the same BPM, shouldn’t happen.
There’s no MIDI sync involved, just seems like the T+ internal clock is off very slightly.
Got it! In that case, Sandroid pretty much said it all as it is perfectly normal. 120bpm is an average, where most machines run at this tempo, there’s usually a deviation of +/- .002 bpm on average.
