Internal clock stability

[interpolate]

Hi all,

 Nerdseq but wondering how stable is the internal clock?

I recently started a song using Nerdseq as the primary clock. Basically recorded a live jam into Ableton and I noticed a significant amount of clock drift. 

• I had both Nerdseq and Ableton set to 150 bpm.
  
• I was only using 2 of the primary Nerdseq channels and 5 channels from 16 more triggers expander
  
• I was not sending a clock from Ableton to Nerdseq but I did have Midi input plugged into the io expander
  
• Over the course of 4 minutes it seemed to drive forwards and backwards almost a full beat.
  

Am I doing something wrong?

[XORadmin]

Which version?

The clock is suppose to be very stable, directly derived from a crystal oscillator. The only thing i can imagine is that 150 bpm are never 150 bpm. There is always some slight difference between systems.

[interpolate]

Thanks for the fast response.

I am using 1.20 firmware on the Nerdseq and the 16 trigger expander says 1.10 I believe.

I will try another test soon where I will record a hi hat for a few minutes and see if it drifts again. I was having trouble lining things up after 32/64 measures.

[XORadmin]

Thanks for the fast response.

I am using 1.20 firmware on the Nerdseq and the 16 trigger expander says 1.10 I believe.

I will try another test soon where I will record a hi hat for a few minutes and see if it drifts again. I was having trouble lining things up after 32/64 measures.

I can for sure imagine that it would drift as i said. But then minimal and only into one direction.

[Marizu]

Any two sequencers will always drift relative to each other when set to the "same" BPM.
This is why you need te use thing slike MIDI time code or MIDI clock. In the analogue world, you often send clock and reset signals to keep things in sync.
Nerdseq can definitely send clock. You will need to set Ableton to listen for it. In this setup, Nerdseq will be the master controller and Ableton will be the slave and follow it. It might suiot your needs to do it the other way around, but I haven't ever slaved Nerdseq over MIDI.

[interpolate]

Hey guys, this ended up being an issue with the drivers on my audio interface (L-20 v1.0). I updated the drivers and the issue seems to have gone away.

I appreciate all the insight! The next time I do this work flow, I will have a MIDI clock one way or another.

Cheers!

[XORadmin]

: Dancing Banana :

:-) Nice that it is solved!