10-23-2021, 04:38 PM
(This post was last modified: 10-23-2021, 05:01 PM by ipassenger.)
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.
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.
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.