While programming and testing a midi-synced LFO on an Arduino, I noticed syncing my LFO to the sub37 Midi-clock and sequencer was not as thight as syncing to Cubase.
I did some testing with MIDIMonitor to see what happens.
My conclusion:
The internal sequencer is not in phase with the midiclock the sub37 sends out.
The tempo is correct but the notes are not timed on midiclockpulses, but in between.
So syncing an external sequencerdevice to the sub37, will result in a small time shift between the notes played from both machines.
Every time you start te sub37 sequencer you get a different shift in time between midi clock pulses and sequencer notes.
This makes the sub37 less usable as a midi clock master, at the moment. (could be useful, in rare occasions. )
Shouldn’t the sequencer and arpeggiator notes be quantised to the midi clock?
Yes, MIDI clock should properly be in phase with the internal sequencer. I will definitely try to tighten this up at my next opportunity!
I can’t work on this before the next official v1.2.0, which is basically done, but I will flag it for immediate follow-up. Thanks again.
Edit: actually, it could be as simple as one missing thing: to hard-sync the (internally-generated) MIDI clock phase to the sequencer start. If this is not happening, then it would act like this description, with a different phase-error on every start…
Edit: actually, it could be as simple as one missing thing: to hard-sync the (internally-generated) MIDI clock phase to the sequencer start. If this is not happening, then it would act like this description, with a different phase-error on every start..
To me, it seems this is exactly what is happening.
)