Recently got the Matriarch and using it with Studio One (with Quantum 2626 and MOTU midi express XT) . I can record/play Matriarch via midi just fine into Studio One. BUT if I send Midi Clock to the Matriarch (to control sync on Arp/Seq) it triggers erratically and makes garbage.
Anybody using this combo that might know the culprit? I’ve been trying process of elimination with no luck : (
I just tried to sync my Matriarch via usb midi from a Hermod sequencer. It responds to start/stop, but timing is garbage. It can play a few beats in time, but then throws in erratic stutters.
The really odd thing is that I found a combination of patch cords (in positions that has NOTHING to do with arp timing) that miraculously fixes the sync. Seems to me like it could be some weird grounding issue with the midi.
(If you now are wondering if I have any clue what I am doing: Although I just walked into this forum, and I received my Matriarch yesterday, I have worked with midi synths since 1986 and with modulars since 2000.)
I just made a little video of the weirdness, - will post a link.
Here is a link to a short video demonstrating the problem: https://youtu.be/jH0WEh7REts
(It is unlisted on youtube, so you can only see the vid with this link.)
I can add that the problem is the same whether I use usb midi or din midi.
Using a good ol’ analog clock from my modular is rock solid though, so I am using that for now.
For me, these are basics that are not met.
I never understand, why the cutoff isn´t available via Midi. The most time I work with a DAW (Studio One 5.5) and my other synth vintage stuff works fine with midi.
Also I wait for other open midi topics, see here the forum posts
→ Matriarch Velocity via MIDI
→ Matriarch-midi automation on cutoff filter
Well, to be absolutley fair, Moog never promised that parameters such as filter cutoff could be controlled via midi.
However, it is clearly their intention that the sequencer should be able to sync via midi, but as the above video shows, there are some very serious issues with that.
I have A matriarch connected with a MOTU Express XT on iMac 2020 with cubase 11
Don’t have the sync problems you are talking about.
No problem at all with the arp getting steady clock from the motu thru cubase.
My experiences are the following:
It only goes out of sync when I press stop and play(rapidly) and if the note(chord) was still on
The matriarch then needs one bar to get in sync (4/4 @ 128 bpm)
If a stop cubase and press play when the marker starts at the beginning of bar or note its in sync
If a let cubase start at the middle or near the end of a note the arp isn’t playing(usual arp behavior for me)but perfectly in sync when the next note(chord) hits
The Matriarch is on latest firmware V 1_2_3
And has its own ports on the motu
I’m having same issue with a MIDI DIN clock coming from a hardware drum machine. What I’ve noticed is that the issue occurs when I have the Stereo Delay “SYNC/TAP” enabled (like the patch the video does). I’m wondering if the delay timing and the arp clock are somehow coupled when the Delay SYNC is enabled?
Hi - I just joined the forum here to bump this thread in hopes that Moog will address this(not sure if they read their forums here). I’ve had my Matriarch for some time and keep coming back every few months in hopes that I can get it to sync properly with MIDI. My entire studio (Prophet Rev 2, Juno, large modular setup, etc) is all clocked via MIDI with an Elektron Digitakt as the main clock. The only piece of the setup I cannot get to clock correctly is my Matriarch and it’s incredibly frustrating.
I’m having the exact same erratic clock behavior as shown in LDT’s video above. The light is green indicating MIDI sync, but flickers red and jumps around in the same way.
I had weird behaviour similar to this last night. I realised that with me it was related to me having something patched to “Time 1 In” (I think some attenuated noise), and also having Sync enabled on the delay. I notice that this is also the case in the video that LDT posted above. And actually I notice that jjiitter posted similar findings, although doesn’t mention whether “Time 1 In” is patched. If I remove that patch cable, then sync and arp seem to work fine for me.
I’ve had this issue since I got the Matriarch. My steup: UA LUNA sending master clock to Matriarch via USB. Moog than forwarding the clock to other devices.
I’ve had the weird behaviour like on the video countless times, but restarting the computer with the Matriarch on and USB plugged would solve the issue.
This isn’t the case today, that being the reason why I ended up in the forum.
I’m not sure what to do now.
I’ve restarted 5 times and the Matriarch is still not receiving MIDI correctly.
The MIDI lamp in the back is off and the RATE/DIV led lamp flashes weirdly mostly red and sometimes green, but super shortly.
Here too. Just got a Matriarch. The midi sync is appalling for a flagship synth. It’s the most basic of requirements, even for a £100 box. Sort it out Moog!!
I’ve registered an account here specifically to post about this. My Matriarch has this same exact issue that has been referenced a few times in this thread. The problem being that when you patch a signal into the Time inputs of the delay, it affects the ARP/SEQ clock!! Why is this the case? Is there only one clock and the delay is operating on subdivisions? The delay should basically be its own module and not affect the ARP/SEQ timing.
Can this be fixed in a firmware update or is this a problem with the design?
Bumping this thread because this is a major issue for me and renders the synth almost unusable. It’s truly shocking and very unpredictable. I’ve got £50 boxes that are rock solid sync-wise. It should be a no brainer for the Matriarch. Very close to returning it here as it’s not fit for purpose. I’ve got a DFAM and that’s bullet proof.
It kills any creative vibe and I don’t even want to switch the thing on. MOOG! FFS! it’s 2023!!!
Same problem here with the newest firmware (1.3). I was hoping the newest firmware would solve it!
I have tried:
Sending a 24PPQN clock directly from Ableton via a 3.5mm patch cable
Syncing it via MIDI cable with my Squarp Hermod
Syncing it with a 3.5mm patch cable into the clock-in with my Pamela’s New Workout
Syncing it directly from my PC via a USB cable
Syncing it with an iConnectivity MIO USB to MIDI converter
I didn’t have this issue when syncing via my Squarp Pyramid via a MIDI cable, at least I didn’t notice it. I sold my Pyramid and it’s been a pain trying to sync this thing since then. All my other gear syncs perfectly.
Using Reaper, I have had problems with Matriarch receiving arp sync (USB midi clock) It seemed to be in time but like running with some random offset time. Very fustrating. Sometimes switching arp mode back and forth would suddenly lock it to correct time, sometimes not.
Today I noticed that if my song structure is built in Reaper not in the start of timeline but like 1500 bars away from bar 1 (don’t ask why) the Matriarch’s arp will be off time (running with offset) but if I delete the first empty 1300 bars and try again somewhere more in the beginning of timeline the Matriarch is perfectly in sync right away!
So in the other words, it seems to not handle long or late song / timeline positions?
Same here, really disappointed, spent hours building a killer patch, no chance to record it or play anything which resembles what is should. Just Awful
Ableton Live + USB Sync + Matriarch = nothing musical
I post this only to try to be helpful, but I don’t have an issue with Midi Clock Sync. My Matriarch is conected via USB to Mac via Ableton. I have whatever the latest firmware is.
Like if I press the play seq and hold button on the Moog, then press a note (either in Seq or Arp mode), it runs at speed set by knob and has red LED. Once i hit play in Ableton the sync LED turns green and the clock adjusts to the Ableton BPM and the rhythm locks together. Delay sync seems to work normally as well with and without something plugged into one of the time inputs.
Feel free to ask me anything to try to get to the bottom of this. It’s not that i didn’t have major problems setting the Moog up with Ableton, but it was more about double triggering, hold button issues, etc. (i made a thread). Somehow i was spared from this issue. I feel for yall because my problem caused me so much headache.