• To get the Nerd's Sequences to be in time with my computer, am sending a negative delayed clock (-8.5ms) to the nerdseq clock inputs (with the clock in mode set to mod.clock24).  
  
• I then use the clock out on the nerdseq to send this clock to onwards to my ER101/102.  
  
• When I do this the ER101/102 is 8.5ms in front of the nerdseq.
  
• So am assuming the clock the nerdseq receives is being echoed straight out again. 
  
• Would it be possible to account for this within the nerd in some way.
  

(10-23-2021, 04:03 PM)ipassenger Wrote: Hi,

When clocking the Nerdeq from another source (ES3+5) and using the clock out and reset to trigger another sequencer am getting around an 8-9ms delay between the sequences generated by the nerd and my other sequencers.

To be more specifc;

• To get the Nerd's Sequences to be in time with my computer, am sending a negative delayed clock (-8.5ms) to the nerdseq clock inputs (with the clock in mode set to mod.clock24).  
  
• I then use the clock out on the nerdseq to send this clock to onwards to my ER101/102.  
  
• When I do this the ER101/102 is 8.5ms in front of the nerdseq.
  
• So am assuming the clock the nerdseq receives is being echoed straight out again. 
  
• Would it be possible to account for this within the nerd in some way.
  

I also tested a similar situation using the internal clock on its own, so the nerdseq set to internal but sending its clock to the er101/102 and am seeing a similar 8.5ms delay between patterns generated in the nerd vs those from the er101/102 with the Er being in front of the nerd.

Furthermore am seeing the same behaviour if the nerd is set to midi for its clock in source... seems like the latency for the internal sequencer in the nerd to spool up is around 8.5ms.

So I think what I am asking is could we have a setting to account for this on the clock outputs?

(10-23-2021, 04:24 PM)ipassenger Wrote: lol, had to look that up to check, as I didn't know about trigger delay but no it is off for the track.

---

Even tried creating a new pattern, to clear the memory etc

---

That being said it could well be a setting I am missing somewhere, the nerd is a complex beast!

(10-23-2021, 04:33 PM)ipassenger Wrote: Yeah doesn't seem to be project related, will try some different tempos.

"How does your sequence look like that you compare with the output?" Sorry, I don't follow this?

For comparison in sequence performance, was sending the same note/trigger pattern from the two seqs (er101 / nerd)

• 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?
  

(10-23-2021, 04:38 PM)ipassenger Wrote: 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.