Im using an Octatrack Mk2 and a Moog Mother 32.
In my MIDI settings I have Send and Recv checked under Transp.
And for Clock I have Recv checked.
The channel I have selected for the M32 is channel Two, and the midi channel is properly formatted for Midi Channel two. When I hit play, the Midi LED on the M32 lights up with the corresponding midi notes… But no sounds are heard… When I press Start/Stop on the M32 sequencer… Then voilà all is working. But I have to press Start Stop on the M32 sequencer whenever I want it to play? When I sequencer my Korg MS20 everything works just fine. Maybe its because the M32 has its own sequencer? IDK but its pretty annoying that I have to do that. Any suggestions on whats going on?
Also-- I have gotten this to work a random times of changing settings, and turning things on and off a bunch. But it feels pretty random at this point.
Hope this makes sense.
TLDR; I have to hit start stop on my Mother32 in order to play the midi notes I am sending from the octatrack.
That is not clear. Is that OT settings?
In that case, why Receive? (if you want to sync M32, transport and clock send should be enough)
Did you plug OT midi out to M32 midi in only?
Did you try disabling midi sync Send / Receive from OT? (sending notes only)
Ah! Sorry. I am sending clock from Ableton. My Midi cable is going fromMidi OUT into a MIDI Solutions Quadrua Thru. Where one of the MIDI cables goes out into the M32. When you press FUNC + MIDI, those were the midi settings I was describing. The MIDI Sync settings. Hope this helps.
I don’t have an M32 but if you send it Clock only maybe it waits for Transport? I’d send nothing or send both Clock and Transport to check.
Also check M32 sync / clock setting in its manual.
The Ableton Clock (nor an OT derived clock will reach the M32) with that setup - the Ableton clock will appear at the OT Thru - if you want the Ot to send clock (necessary if you expect the Transport to work) then you’ll have to enable clock too - I also don’t know the M32 - but i know this isn’t a ‘bug’ so i changed the title, this is just basic connection issues
@avantronica is correct as far as the clock routing is concerned, but you’ll still have an issue with the midi start command because it is issued by Ableton’s transport, not by the OT which is slave to Ableton. When the OT is slave, it can generate a clock on it’s output but will not echo out any received transport commands on the midi output (I might be wrong but I’m almost sure: I have used this “feature” in the past to “filter out” the start/stop/continue commands IIRC). I have no details of your set-up but if you want Ableton to remain the master clock, then Ableton should command the thru box, OT and M32 connected to two thru-ports, clock and transport rcv on, clock and transport snd off; the output of the OT into Ableton and route it back out again so your notes for the M32 sequencer will be merged with the clock inside Ableton. No tracks set to receive on ch2 on the OT. That should work. You now created a midi loopback on the OT: this opens up lots of creative possibilities (check out @sezare56 's posts) but you need to be extra careful not to create havoc. (Disclaimer: I don’t have Ableton but every software sequencer I’ve ever used is able to perform such a simple routing)