If it’s slaved, try playing with the MIDI latency compensation and see if you can make the result better. I’m pretty sure you can.
Yes, the compensation is for receiving clock only but since Tracker sequences its own sounds, this should be enough to get everything airtight.
And please make sure you’re on beta 5 
@7C Check all your setting (these recent updates have been changing some default settings throughout the tracker) and triple check that the update took and your tracker is showing beta 5 in current version. So far everything seems ok…
Tracker as master…I built a few patterns with a good mix of internal sounds and midi notes then hooked up a few pieces of gear to slave (minilogue xd, nts1, Mpc One, microfreak)… In these instances of the trackers sequencer triggering midi notes in external gear alongside its own sounds, I found no issues.
Still testing tracker as slave and will update soon.
Pm me if you want to send a project file that highlights what you’re experiencing or more specifics on your setup and issue for reproduction purposes.
yup, on beta 5, tried every single delay from 10 to minus 50 to plus - it’s always the same, tracker is 15 to 30ms late with everything. the newest addition now is a clock glitch after each (32steps) cycle, with longer patterns sometimes somewhere in the middle. this has been giving me one of a headache today.
it shows beta 5 and all the settings are correct, it’s been like that since day 1. in fact what you could try and this should be fairly quick - open the demo barker polystarff and just record the whole output with midi out clocking a drummachine. i can pm you the mess it’s making here and vice versa, thx for your help!!
Works perfectly on beta 5 for me.
Didn’t even have to adjust the settings.
Had an rd8 (latest beta which resolves clock issues) and tracker slaved to squarp pyramid (in turn slaved to ableton but I didn’t turn ableton on) and all sync perfectly.
Nice one polyend. Studio is now T I G H T as the meth dealer from breaking bad might say
Well at least bèta 5 seems Far more stable than bèta 3. Been testing whole evening, no crashes so Far 
0b5 came out immediately and it is fine. Apart from the pleasure of the tracker workflow. Program change for each midi channel, chords, polyphonic aftertouch, sidechaining and many others make it powerfull sequencing machine. Bitimbral mode on Micromonsta 2 works well. Great!
I am seeing problems with the midi latency compensation and have opened a bug for it: https://github.com/polyend/TrackerIssues/issues/559
Did you try resetting to -49.5? Just tested with Model:cycles as master clock… tracker ‘clock in’ set to midi in… sequencers in tracker and ms running parallel for 10 minutes with no audible drift. I’ve kept my clock sync delay at -49.5 (default).
Holy shit, I just managed to get myself a Tracker as a an Xmas/Early birthday present to myself! I got a load of pay today upfront instead of receiving it spread out in a couple weeks. Being born on New Years Eve means as a kid you kinda get fucked about and only get half the presents, and when you’re older it’s all about going to a ton of parties with your friends and get mashed, meeting new people, and all that good stuff…so since that is absolutely not happening due to living on the so called “Plague Island” - the UK atm I thought fuck it man, treat yourself to the one thing you’ve actually had total GAS for all year, and instead of slicing up lines on a coffee table in some randoms flat on New Year’s Day, get to slicing up some breakbeats and stay relatively level headed.
The reason I’m so excited is that I’m still sorta drunk at 06:45 am, and should probably just go to bed…but this is like a Christmas miracle to me and I would normally never have the dollar to actually afford it out-right at the moment at least. so my current philosophy is fuck it, basically. All I wanna do this Holiday season, make some Drukqs era Aphex Twin inspired breakcore, on my brand new Tracker, and have my own Party, soundtracked by the Tracker and the rest of the gang in my flat/studio.
It’s nice to finally be part of the club.
lol great post
Well that was quick!
1.3.0b6 just dropped with some fixes, if y’all were experiencing anything wonky.
*The Amount parameter in Instrument Automation could get stuck ([#554]
*MIDI clock drift on external clock sync ([#559]
*Record quantization ([#561]
*Delay compensation setting wasn’t respected after a cold restart.
Welcome to the club. The first rule of the club is: you do not talk about the club.
Correction: If there were such a thing as a club, it would surely at this point welcome you and kindly request that it’s own hypothetical anonymity be respected.
These PolyEnd guys are really amazing, the updates come faster than flashing them. Respect!
Time to explore this little instrument over the Christmas break 
the developer must be trying to avoid xmas , locked in his/her office/bedroom knocking out firmware updates to avoid turkey/pork/quorn or whatever food is eaten at xmas.
Shhhhhhhh!
(Also thank you for the unofficial non-welcome )
It’s getting delivered tomorrow my lawd. I’m slightly more sober at the moment but not sure how much longer that will be the case but I’m even more excited now!!! It’s been some time since I used a tracker, but this seems to have just the right amount of tools to glitch up my drum sequences, and hopefully sync well with my modular, OT and OB6 via midi. As much as I love making percussion on the octatrack, would great free up those sample tracks for interesting tonal ideas along with the modular. My set up is fairly modest and I’m sure it’ll slide right in.
so for everyone having trouble with latency or clock / sync issues - with the new beta (6) it’s history. glitches and wonky clock gone, audio latency gone! finally enjoying (all) the shit out of this box now heureka! thx to Lukasz, Piotr and whoever else does all this wonderful work, ace!!!
1.3 is out !!!
Polyend are relentlessly efficient
And the games are fun
