It’s a new year and 2022 seems like a wonderful year to iron out any final matriarch bugs. What say you Moog? lets do dis!
any plans for more updates of any kind or is the matriarch in its final form? Not a huge deal at all. but some kind of state of the union on further matriarch plans if any would be aces.
I don’t think anyone from Moog visits here that often. It’s best if you want something in particular to be looked at to contact Moog directly via their support page. The more people that request that something needs to be fixed the more likely they are to fix it.
Have to say it’s criminal that moog still haven’t addressed this issue.
Isn’t it ? I can understand that they don’t give a f"ck of people like you and me, but how comes that the influencers (you know, people that count) don’t talk about this ? Or ‘real famous artists’ if such a thing exists. Anyway, shame on you Moog.
pointless bump.
Please someone in the US call them by phone(as it’s the only way to reach support). I did twice, it cost me like 30€ and they were so arrogant.
Just got off the phone with Adam at Moog Music. I had to get ungrounded PSUs and am having trouble with what seems to be the same gate issue, so I’m sending him a video of the problem and a link to this thread.
Hi, Adam! I hope we get more Moog reps reading the forum. 
Fingers crossed. Hard.
I’m filming my video now. In the interest of being scientific, I decided to measure the internal gate lag. Assuming normal gate operation has near-instantaneous release — ±5ms or so, similar to the main VCA attack and release — we should be able to assess how long the lag is.
I sent MIDI notes from Logic: a 5-second C1 and C2, with two one-second holds on C4 and E4 every other second. I recorded Matriarch’s output and analyzed it in iZotope RX. I zoomed in carefully to get as close to the actual notes as possible, but consider human margin of error at ±1ms for my numbers.
You’ll notice that my selection is 1.128 seconds long. Yes, internal gate releases have 128 milliseconds of lag. Even if they’re not instantaneous, they should be at most 5 ms, the same as the VCA, no?
I’ve provided a wav and midi (120 bpm) in a zipped folder if you want to replicate this experiment or analyze my file yourself, if you have better metering tools. I think Logic may have compensated for latency since the onset of the first note appears just before 1s.
Matriarch gate test.zip (855 KB)
Thanks for doing this !
I really hope they’re working on an update for this as it’s been almost 2 years since the last one. There are quite a few bugs that need to be ironed out.
Just got a response back. Fingers crossed they tackle this in the next release:
“There is an update coming in the next few weeks, it focuses primarily on CV and MIDI to CV improvements. The behavior you describe is still documented on our bug report/feature request shared with engineering. I’ll put an extra note in that entry so that it might be investigated in the next revision. Please let me know if you have any other questions.”
I wonder what the CV and MIDI to CV improvements are?
Let’s hope they’re going to do something about the note delay. It worked fine in v1.0.1
Damn, I sincerely hope it will be fixed.
I just can’t believe that such a defect can last that long without being corrected. I mean, some people actually play this synth, right ?
I’m glad they’ve finally given some kind of ETA, but still shocked at how long it’s taken. The most frustrating part is that, knowing a lot of fellow neurodivergent people who do coding stuff strictly because they’re passionate about it, I don’t think it would have taken this long if Moog had bothered to find people who wanted to do it “for fun” instead of putting this on the to-do list for paid employees. Knowing the way the community is, if Moog would release the source code and appropriate documentation, there would be a patch next week. Incredibly frustrating, then, that they have dragged their feet for literal years.
Yeah it’s unbelievable how long they take to fix things what, well, would make this instrument simply useable !
Meanwhile, GREAT news, since today, you can effectively protect your useless Matriarch : https://www.moogmusic.com/products/matriarch-dust-cover
Bumping this.
Not because I’ve got hope, mainly because I’m pissed off.
Supposedly there’s a new firmware update coming very shortly. And it’ll fix the rear facing CV outputs not responding to midi too.
But, yeah, I’ll not be holding my breath until it arrives.
Which reminds me, I must badger them about the filter tracking not working properly on certain glide modes and the delay CV input not working correctly.
I think I’ve always had 1.2.3 flashed on my Matriarch, but I gotta say, I went down to 1.1.0 and the response and articulation is SO much better. Moog should absolutely fix 1.2.3, but I’m not going to let buggy firmware prevent me from enjoying the sound of this synth.
I also finally reverted to a playable firmware.
But it’s so frustrating, as the additions of 1.2.3 are very nice.
And I just can’t believe how much Moog support sucks. They simply don’t reply. And when I pick up the phone to call them 10000km from home, that act in a very condescending way…
I just got my Matriarch. I am quite musical so I need perfect response from the keyboard. I found it totally unplayable in paraphonic mode. It was sluggish and I couldn’t do fast nice crispy runs and chords.. I have had a Behringer Poly D before this and the matriarch didn’t play nearly as well.. So I figured.. I try to downgrade to firmware 1.1.0. Lo and behold! The synth played perfectly and responded as well as it could. Even other bugs reported like stuck notes and filter go crazy wasn’t there. It just felt less buggy and much more stable when playing advanced and fast. I just tell you: moog team knew what they did when they did this synth and it is perfect. But with firmware over 1.10 I would exchange it for my former Behringer no time, it just isn’t playable in paraphonic mode.
The thing I miss most from newer firmware is the hold / latch / note. It only latches arps and seqs now. But man what a beautiful synth and how responsive with the fatal keyed.. I do not exaggerate. I think moog has messed up the later firmwares. Just comparing file size 800 kb vs 3 mb tells me that the newer firmware is unnecessary complex and introduce many errors. IMHO. I think moog definitely needs to hire good musicians (not only patch-tweakers) that would react to such errors immediately and stop it. But hey.. the synth is not about the digital side / the firmware. Firmware 1.1.0 sounds as good! So just revert and be happy is my advice.. (note: you also miss the editor function since param changes via sysex was introduced later). I feel I don’t miss something real out. Do you know any important changes since 1.1.0 that really are ESSENTIAL (I haven’t discovered them yet),