[NO BUG] Clock Timing Behaviour

[XORadmin]

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?

Hey, are you sure you didn't have just the trigger delay turned on?

The clock should be very stable normally and act within the microsecond area.