[Scarab]

Hi All,

I am trying to chain the 4 sequencers together to achieve a 64 step sequence.  I am using Logic to send MIDI clock.  MIDI clock is sent to the first sequencer and then patched down the chain so they are all synced. All four sequencers are in one-shot mode and are triggered by EOS->Start. 

The problem is: there is a slight delay from one sequencer to the next however, meaning that the 64 step cycle does not align to project, with each 16 steps being either a bit behind or ahead of the tempo.  

I have experimented with both lit and unlit for EOS mode and this doesn't correct it. 

I hope I have explained this clearly; am I missing something, or is this a Logic-Komplex MIDI clock issue?

[Jackieflipflop]

Hello Scarab.
can you give a look to this thread?
https://community.koma-elektronik.com/thread-432.html
there is a screenshot posted from Quolcat that shows how to perform what you want to do.
That might help i think.
JJ

[Scarab]

Hello Scarab.
can you  give a look to this thread?
https://community.koma-elektronik.com/thread-432.html
there is a screenshot posted from Quolcat that shows how to perform what you want to do.
That might help i think.
JJ

Hi Jack, thank you for your reply.  I did search and find that thread, and after your link I went through and carefully read it again to make sure I didn't miss something, but I believe having read it again that my issue is separate from the one described in that thread.  When running a 64 note sequence, when the pattern moves from one sequencer to another, it does not slow down or change tempo in any way.  What happens is that there is just a slight pause before the next sequence starts, so the 64 steps don't align to the tempo of the project.  In other words, there is a little space ever 16 steps.

[Scarab]

Just wanted to bump this; can anyone account for the slight gap between each 16 steps?

[CalvinMooney]

geometry dash lite

Drive all sequencers from the master MIDI clock in loop mode, and use Reset pulses to line them up every 64 steps.
Instead of EOS chaining, use a clock divider (÷16) from Logic to “select” which sequencer should be active, so they all run in sync but only one outputs at a time.

[ortedtweed]

Hi All,

I am trying to chain the 4 sequencers together to achieve a 64 step sequence.  I am using Logic to send MIDI clock.  MIDI clock is sent to the first sequencer and then patched down the chain so they are all synced. All four sequencers are in one-shot mode and are triggered by EOS->Start. 

The problem is: there is a slight delay from one sequencer to the next however, meaning that the 64 step cycle does not align to project, with each 16 steps being either a bit behind or ahead of the tempo.  

I have experimented with both lit and unlit for EOS mode and this doesn't correct it.  ragdoll hit

I hope I have explained this clearly; am I missing something, or is this a Logic-Komplex MIDI clock issue?

It sounds like the issue might be related to MIDI clock transmission timing between the sequencers, especially when chaining multiple devices. Even though you’re sending the clock from Logic, there could be a small latency introduced at each stage of the chain. This might cause the slight delay you're hearing between sequencers. One thing you could try is adjusting the buffer size in Logic or looking into whether each sequencer is receiving MIDI clock at a slightly different rate due to how the signal is routed. If you’re able, testing with a direct connection between just two sequencers might help pinpoint whether it’s the chain causing the drift, or if it’s something to do with Logic’s handling of the clock signal.

[noahharold]

Hi All,

I am trying to chain the 4 sequencers together to achieve a 64 step sequence.  I am using Logic to send MIDI clock.  MIDI clock is sent to the first sequencer and then patched down the chain so they are all synced.  All four sequencers are in one-shot mode and are triggered by EOS->Start ->rice purity test

The problem is:  there is a slight delay from one sequencer to the next however, meaning that the 64 step cycle does not align to project, with each 16 steps being either a bit behind or ahead of the tempo.  

I have experimented with both lit and unlit for EOS mode and this doesn't correct it. 

I hope I have explained this clearly; am I missing something, or is this a Logic-Komplex MIDI clock issue?

It sounds like you're facing a common challenge with chaining sequencers and MIDI clock synchronization. One thing to consider is the latency introduced by each sequencer in the chain; even slight delays can add up. Have you tried adjusting the MIDI clock settings in Logic or using a dedicated MIDI splitter to ensure a more stable signal? Sometimes, experimenting with the clock resolution or using a different clock source can also help improve synchronization. Good luck!

[hootalliance]

Hello Scarab.
can you  give a look to this thread?
https://community.koma-elektronik.com/thread-432.html gorilla tag
there is a screenshot posted from Quolcat that shows how to perform what you want to do.
That might help i think.
JJ

Chaining sequencers and MIDI clock synchronization seem to be prevalent problems for you. The latency that each sequencer in the chain adds is one factor to take into account.

[Kubiak21]

Hi All,

I am trying to chain the 4 sequencers together to achieve a 64 step sequence.  I am using Logic to send MIDI clock.  MIDI clock is sent to the first sequencer and then patched down the chain so they are all synced.  All four sequencers are in one-shot mode and are triggered by EOS->Start Slither io. 

The problem is:  there is a slight delay from one sequencer to the next however, meaning that the 64 step cycle does not align to project, with each 16 steps being either a bit behind or ahead of the tempo.  

I have experimented with both lit and unlit for EOS mode and this doesn't correct it. 

I hope I have explained this clearly; am I missing something, or is this a Logic-Komplex MIDI clock issue?

Alright, MIDI clock woes, sounds like a rhythmic nightmare! Ever feel like you're chasing your own tail? Sequencing stuff can be trickier than herding cats, especially when timing is paramount. My first thought is always latency, but you seem to have considered that. Remember that time I was trying to sync up audio tracks for a short film and the drift was driving me crazy? I had to manually nudge each clip, a process as tedious as trying to get good at Slither io while avoiding those massive snakes. Eventually, I just re-recorded everything with a click track and solved. I hope you find a solution.