Repeatable Bug with MIDI Clock at 24 PPQN

[WubWuber]

I've ran across a problem with MIDI Clock (24ppqn) on the latest firmware 2.2.4.

I'm using a NerdSeq sequencer supplying clock at 24 PPQN via MIDI to the Micro. I am triggering a loop via gate/trigger (20ms).

100% of the time when starting the sequencer, the Micro will play the loop at 120 BPM and not the sequenced BPM. If I quickly stop and restart the sequencer it will playback at the correct BPM. However, if I stop the sequencer and give it a few seconds before restarting, it will always start playing at 120BPM and not the actual BPM. Sometimes this will result in the Micro skipping several triggers and starting mid-sequence. I'm monitoring the triggers via an oscilloscope, so I know they are being sent accurately.

Pam's Workout correctly reads the CV clock from the NerdSeq at the correct BPM (24ppqn) at all times. MIDI clock to my TR8S from the NerdSeq is rock solid and works without issue.

I'll post a video of the problem ASAP.

Thanks,

[Steve]

Please post a video of this along with your MIDI settings and connections. Are you sending Analog clock to the MIDI in port?

[WubWuber]

Please post a video of this along with your MIDI settings and connections. Are you sending Analog clock to the MIDI in port?

No, I'm using TRS A MIDI sending 24ppqn. After lots more testing, it appears the Micro can't determine the midi clock quick enough and defaults to the internal clock. Quicky restarting via midi transport will restart the clip loop at the correct BPM. If stopped for more than a few seconds a restart will resume at this "default" 120bpm. Often the Micro won't immediately respond to the midi start, and will sort of "hang" for a bar or two starting mid sequence. This seems to depend on whether the internal clock "beat counter" correctly resets or not over the stop & restart.

Clocking with analog 4ppqn 1/16 works fine but that really limits the usefulness of midi for me. I tested 4ppqn over midi, but it didn't improve anything.

Midi transport control is also very important for me, but stop doesn't appear to work with loops.

[Steve]

Thanks. I was confused because you said "MIDI clock at 24PPQ. But that is the MIDI spec, so I asked if you were connecting things properly. MIDI stop will not stop clips. I do not have a NerdSeq (cool device though). Does it offer Play and pause via MIDI? If you can send a short video of this I would like to see it. Thanks

[pixfoil]

I confirm the bug on the midi clock, I tried with beatstep arturia, out midi RME audiocard, but always the same thing. at first it doesn't clock then you restart it and it seems to work fine, but on Ableton live it doesn't take the BPM changes in arranger mode; he doesn't hear the stop sign, in short, it's really a mess, it should be fixed. Thanks

[Steve]

please share more details, firmware version as a number, settings, external gear, etc.

[Steve]

Please share specific steps to reproduce. A video is helpful.

[Olivier Biron]

I am new to the device so I might be missing something but so far.
i see that the clock reset what I start an external sequencer ( Midi ) that the tempo does not follow and that the loops will keep running even when the external sequencer stop.
Westlicht or ableton live same result

[Steve]

Clips do not stop from external 'stop' messages.

[Steve]

From four different controller (different manufacturers), I am having only success syncing Micro.

To continue this discussion, please post the actual steps to reproduce. Please (aside from the OP) share your firmware version as a number. Please do not use PPQN when talking about MIDI. Make sure to include the device that is sending MIDI clock to Micro. Also, be aware that Clips do not respond to external stop messages. Use the Stop button in the upper right corner of the pads screen.