Moog Music Forum

This may be due to my lack of knowledge of MIDI. I'd like to understand what's happening here if anyone can explain.

The Mother 32 seems to ignore MIDI clock events until it receives a start event at which point the tempo LED will turn green until it receives a stop event. I have a device that's continuously broadcasting clock messages, whether start has been sent or not, but the M32 (and a couple of other devices) seem to ignore those messages. The M32's tempo LED remains red even as those events are being broadcast (confirmed by MIDI monitor).

What's the correct implementation? Is there any way to get the Mother 32 to recognize the non-sequence clock events?

I'm resurrecting this thread as I'm having the same issue. I'm a bit frustrated as I got it to work one time the first night I set it up but I don't know how I did it and now I cant get it to work again.

I am running an Oxygen 49 into a Disaster Area Smartclock into the Mother 32. I can confirm that the connections work because I can play notes on the mother with the Oxygen. The smartclock is in tap tempo mode and the light is blinking, which according to the manual indicates the clock is running. I know it is possible for this to work as I accidentally got it running the other night but I have no idea how I did it.

Any advice on what would cause the M32 to not recognize a midi clock signal while it is recognizing midi notes would be great, or if anyone happens to know the smartclock. If I figure it out in the meantime I will post my solution here.

Just as an added note, I can confirm the smartclock is sending midi clock as I can get it to control the tempo of a delay pedal I have which can be synced to midi clock.

Even further added note, in the preset mode of the smartclock, if you stop and start the clock it sends a midi start/stop message, which is also having no effect.

Turned out to be a firmware issue with the clock pedal. It was not sending midi start/stop when it claimed to, confirmed via midi monitor. Rolling back to the previous firmware on their website restored this function, then once a midi start message was sent to the mother 32 it recognizes the clock from then on.

Wondering if anyone is having the same trouble I am. I have the M32 hooked up to the OT which is acting as the master for a bunch of other pieces of gear. I want to program the M32 via the OT as there's more flexibility with the OT's step sequencer. But, when I have Midi Clock Out switched on, on the OT the M32 becomes really unresponsive and glitchy. As soon as I switch off the Midi Clock everything works ok.