Octatrack MKII Vs Matriarch Midi

Elektron Gear Octatrack
1

So I picked up a Moog Matriarch this week and have come into an issue controlling clock/midi from the Octa. Moog’s global parameters I THINK I’ve set correctly by pressing Hold/Sync Enable at the same time, C#2, A#0, then C0. That in theory sets it to receive midi clock and start/stop commands from the octatrack. I hit “1” on the octa and it triggers the matriarch so it’s definitely connected but when I hit play, the moog doesn’t start playing and the clock isn’t synced up at all.

Annnnnd I somewhat solved part of this while typing it. Basically I want to hit play on the octatrack and have the matriarch start playing in sync with the octa that’s sending clock.

Does anyone have both of these synths that can help?

2

The midi channel perhaps?
its the first thing that pops in my mind because you didn’t write it down here so :wink:
On what midichannel is the octa sending its midiclock and the matriarch receiving?

Also check if your matriarch has the latest firmware, with the old firmware I had a lot of midi hick ups but those are all gone with the new firmware .

3

MIDI clock and transport messages are not transmitted on any MIDI channel.

This is excellent advice. @Sesshomaru should ensure that the Matriarch is running v1.2.0 or later, and preferably v1.2.3.

2 Likes
4

On the OT are you sending both transport and clock, and on the moog have you set it to receive transport and clock?

2 Likes
5

exactly

What was I thinking :zipper_mouth_face:

1 Like
6

from the manual of the matriarch (not the latest version)

image
image716×218 3.99 KB

or perhaps this

image
image716×115 1.74 KB

7

That is what @Sesshomaru was describing in the first post.

8

I know :wink:

9

So in midi, the matriarch is set on channel 1 and triggers when I hit 1 on the octa but does nothing when I hit start/stop on the octa. In midi settings, clock is set to send, prog ch is set to send. I have NOT however updated the firmware for the matriarch. So maybe that’s something causing the issue. Firmware is frustrating :pensive:

10

To get the transport to work, as pointed out by others above, you need to ensure that TRANSP SEND is activated on the OT.

PROG CH is irrelevant for your stated needs.

This is irrelevant for your current needs.

2 Likes
11

Sorry for the late response. I think that did the trick. I didn’t have TRANSP SEND activated. Thank you so much @PeterHanes and everyone else!

2 Likes