Matriarch: Known bugs In firmware 1.3 on release - will they ever be fixed?

I came across this bug in the Matriarch yesterday, where when you set the arpegiator to be sent via midi, and you engage the hold button, it will keep the arpeggiation locked/latched, but it will also sustain the notes indefinitely. Making Usng the matriarch as an arp generator for third party synths, especially polyphonic ones, not possible.

To my surprise, i found that in the bottom of the release notes of Firmware 1.3 this bug was already mentioned and known!

Especially given the changes in the company, is it likely these bugs will ever be solved or adressed?

In the Moog Matriarch Manual
p65.
Global Parameters. Group 2
Section 2.6. Sequence keyed restart

Bug
The sequencer operation is not affected by the changes made in Global Settings.

So another year has passed, and here i am again. The issue still has not been resolved. Please Moog, if you have no intention of fixing this, at least open source the firmware or something. I would really like to use my matriarch more as a master keyboard. Below is a screenshot of Moog’s own release notes

1 Like

bump bump bump bump bump this thread

The Sustain/Hold button function is definitely messed up and is the one that frustrates me most. In my case the problem is that both the Hold button and Sustain pedal only send a MIDI CC64 value of 64 when pressed instead of 127. I’ve had to work around it several times over the past couple years. Theres several issues when you try to use it w local control off and want to incorporate the arp/sequencer.

So surprising…. Sold my Matriarch, bought a Messenger… Even more bugs… Moog is dead. Buy something else!

It’s disappointing they listed the bug but didn’t fix it. With the company changes, legacy gear like this often gets neglected, so don’t get your hopes up.