[NO BUG] Clock Timing Behaviour

[XORadmin]

Doesn't seem to be tempor related, tried much lower (like 25bpm) and much higher (270bpm) tempo and the sequencer trigger latency seemed the same.

---

I did have more complicated sequences (!!   ) at first but after I started digging into the issue started simplifying things to narrow down on what was happening.

---

I've sussed it... well sort of.

• As am on the new firmware have tried sending the clock out pulses using a modular track to rule out anything related to the modular track delays or anything and the issue remained.
  
• Connected gate outs straight to es6 in from (the synced pattern on the er101) and a modular gate output on the nerdseq.
  
• If you use the auto gates, it adds the negative gate pulse to trigger the next note, this delays the pulse by 8-9ms.
  
• So it's the auto gates that are causing this issue, am guessing you would need some kind of read ahead to avoid it?
  

---

Also just checked the trigger outs on the trigger expander and they behave properly.

So am 100% sure it is auto gates that is doing this.

Yes you can lower the autogate timeout in the settings.
But the autogate is just a function to let a note retrigger if the note changes(if you want that). And some sources need a longer timeout to detect a new trigger/gate.
I wouldn’t use it at all. Use either note on/off or the trigger column for your triggers /gates. No delay there. And no surprises :-)