Ah that sounds like a clever solution! Thanks for taking the time on this! I guess loosing transport does not have many drawbacks except for the need of sending the exact note length for the desired duration (which I think is great!) and remember: we do these things not because they are easy, but because we thought they were going to be easy

yes! I did try this, the option is called MIDI Control Mode iirc. With a combination of Live Play = ON and MIDI Control Mode = OFF It works at first, but it desyncs eventually.

Thanks Chris, I understand what you mean and it definitely makes sense. And I agree that timing is the highest priority. However.... while performing it might be tricky to think in this kind of things, and it soooo easy to mess up and ruin a performance. Its a workflow killer! With the digi there are some things I can try: 1. Record unquantized consciously ahead of the beat. 2. Set Microtimings after quantized recording (tried this without success but need to do more tests, ie how much "ahead" of the beat I need to be, does this work for midi notes on the digi) 3. live record quantized one step before the beat. This gets tricky for arps with high subdivisions 4. Try the "no transport sync" idea but send a chord every 1/16 step to "simulate a clock" 5. Try the same sequence with other arpegiators to see how they behave. Will do some tests and report back. Another thought: if we could potentially send up a chord with 1 or 2 CC messages instead of notes (root and mode), would this also have the same timing issue? Thanks for your time!

Thanks for the further comments. I can summarize a little workflow idea based on my experience 1. Make a drum beat on the digitakt. 2. Play with a fixed chord on the ARP to get some nice patterns on the 4 channels. 3. jam along with the keyboard, find a nice chord progression. 4. play the chord progression on the notes channel (in my case CH16) 5. 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!

Thank you for the quick reply! Tried with the delay approach and kinda works but it seems that different delay settings are needed for the tracks and it arp mode / time divisions seems to affect it as well. overall the behaviour feels a bit... random 😂 The other approach definitely feels cumbersome. I think this might a real issue for including ARP to play nice with the rest of the studio. I might be missing something obvious! how are people triggering precorded chord progressions? I assume this behaviour would be reproducible with other sequencer, ie, Keystep Pro, Ableton Live, etc. going off the grid might be too much hassle! On the other hand... why live inputting notes does not have the same issue?, I'm probably sending note data after/before the clock (due to human nature) and I never need to wait 2 ticks for the change! Any other Ideas I could try or any potential future fix? Thanks! PS. This device is AMAZING ans so inspiring. Thanks for all your work!