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.
Only problem here is, since the OT is the master, I need it’s clock to be on so everything works in sync.
Anyone with a similar set up having issues? Any solves?
I don’t have an M-32 but it puzzled me why you would want to send MIDI clock to the M-32 if you want to sequence it from the OT? Or have I misunderstood what you want to do?
Next, is there anything else in your setup that is sending MIDI clock to the M-32 by some route? Did you try with just the OT and M-32 connected?
It’s because I have the OT going into a RYTM going through into Monomachine thou into the M32 (at the end as it has no midi out/thru). For the other devices I need the clock so they all run in sync.
I’m fairly sure I tried a direct connection, but will try again to make sure.
Not a loop. Just more than one sequencer sending to the m32. You have OT and M32 sequencers (maybe more) running and feeding input to the m32. OT midi clock / transport runs the M32 sequence and you get MIDI chaos.
Solutions:
a. Switch off transport and midi clk in OT. stick to OT completely for sequencing. If you need synced LFOs, sequence them from the OT using CCs.
B. Sequence from m32 but no midi notes and ccs from OT (transport and midi clk: on)
Ps. And go for a direct connection. The MD might also be adding notes and ccs to the midi stream.
I use a four way midi thru to get 4 direct master slave connex.
OK - found the solution. It was the iConnectAudio4+ and specifically the setting “Enable Running Status on DIN ports”. I had that enabled, once disabled things worked as expected.
It’s a real buzzkill - but I’m glad everything is working now. Only gripe I have with the M32 is there’s no way to disable the sequencer so everytime I press play on the OT I have to press stop on the M32 so that the OT’s sequence can override.
Hopefully this will be a fix from Moog at some point.
[quote=“” OH/EX/OH""]
OK - found the solution. It was the iConnectAudio4+ and specifically the setting “Enable Running Status on DIN ports”. I had that enabled, once disabled things worked as expected.
It’s a real buzzkill - but I’m glad everything is working now. Only gripe I have with the M32 is there’s no way to disable the sequencer so everytime I press play on the OT I have to press stop on the M32 so that the OT’s sequence can override.
Hopefully this will be a fix from Moog at some point.
Thanks all for the help.
[/quote]
If you disable send clock and transport on OT, the mother should not run its own sequence, it will not play unless it gets midi notes from OT. So you having to press stop is a sign you have forgotten a midi sync setting on OT somewhere, i’m afraid.
Ps. I’m getting tight sync and sequencing with both methods… Not using any intermediary interfaces though, just direct midi.
Yeah, I know that switching off clock & transport will not trigger the M32 but the OT is the centre of my rig so other bits of gear rely on it to start / stop & keep tempo.
MIDI is a world of weirdness… And every new piece of kit often throws a spanner into my set up. A great GAS antidote for sure
[quote=“” OH/EX/OH""]
Yeah, I know that switching off clock & transport will not trigger the M32 but the OT is the centre of my rig so other bits of gear rely on it to start / stop & keep tempo.
MIDI is a world of weirdness… And every new piece of kit often throws a spanner into my set up. A great GAS antidote for sure
[/quote]
I see, could you filter out the transport message on certain midi channels with the iconnect?
That’d fix it nicely.