External midi transport not starting sequence

Hello, I am trying to utilize an external midi controller to stop and start my Keystep Pro.

The Keystep Pro seems to be responding to midi transport commands via sysex but when started, it does not play my sequences. It just sits with the Play button activated and no steps advance. I have tried all sorts of Sync and Clock settings on the KSP itself and within MCC software but nothing gets things going other than utilizing the onboard controls on the KSP.

I could very well be missing something. Has anyone else run into something similar or perhaps know what I may be doing wrong?

Thanks much!

HI @rjaneshek and welcome to The Sound Explorers Forum!

From memory, as i don’t use the sequencer on my KS37 very often, i think it’s a case of having to press a key or send a midi note to trigger the sequence… the old memory is a little hazy there though…

HTH!

Hello and thank you so much! I will give this a try the next time I am back at the Keystep Pro. I can of course experiment but the next obvious question would be what note to send. Does it have to relate to the sequence? If so what if the first step is a rest and no notes are played on the first beat?

I will report back once I’ve given this a try.

Thanks again for the fast and friendly reply.

1 Like

So, was able to get the KSP playing via midi sysex. It required sending a sysex message of FA (start) followed by midi clock.

My issue now is that the external clock is wildly unstable, drifting all over the place. I would really like to be able to utilize the internal clock of the KSP as the master clock for everything since it is the heart of my midi system but once it is started via an external transport source it expects the external clock to be in command.

It would be really great if there were some CCs that could be sent to trigger the Keystep Pro’s internal transport and clock so that the KSP remained the master device.