Hello I'm having a weird issue, I have a keystep connected to the digitakt and midi out to the ARP.
If I live play the chords it works as expected, but if I record the chords on digitakt I get the chord changes with 1 or 2 steps of delay. The strange thing is that the ARP gets the new chord information immediately (green leds change) but the sound of the tracks change after (i believe) 2 steps. Digitakt tracks are quantized.
Im on the latest firmware.
Thanks for the further comments.
I can summarize a little workflow idea based on my experience
Make a drum beat on the digitakt.
Play with a fixed chord on the ARP to get some nice patterns on the 4 channels.
jam along with the keyboard, find a nice chord progression.
play the chord progression on the notes channel (in my case CH16)
ok this sounds good, lets live record that progression (midi notes on ch16) to free up hands to jam along on another channel. --> This is where its failing, either live recording (quantized) or just adding the steps manually brings the before mentioned issues.
Another thing I have tried is to record full bar note length on the digi and prevent te ARP to sync clock and use the notes from the digi to simulate "live play". This kinda works but the arpegiator sounds a bit out of sync, like it driffts a bit. I suppose it is expected as we don't have a shared clock this way. BUT the notes trigger at the exact step.
I'm also curious to research how other arps deal with a similar situation. I have a microfreak which has some arp patches, I could do some tests if you feel it would be of any value.
Also, the lights for the notes DO change immediately so maybe there is some hope to make this work somehow?
Thanks!
The issue is that the chord data is sent on the same clock tick as the step should play. The clock message is recieved and ARP plays the step, then the chord notes are received and ARP updates it's global scale.
It has to be this way a timing messages must take priority in the MIDI message stream.
If you can shift the chord change 1 clock tick earlier on digitakt, ARP then has time to update its global scale before playing the next step. Alternatively, use ARP's Delay parameter to push ARP's steps back by a clock tick. That should help.
I hope that makes sense. Let me know how you get on.