I am able to convert Midi from Logic through the Mother 32 and send CV and Gate info to my modular. But when I try the same thing on the Matriarch, it does not work. Is there a Global setting i am missing? Anyone able to do this with their Matriarch and can advise?
I have exactly the same problem. Can anyone help? Ist the Matriarch working as Midi>CV interface somehow?
I believe the CV jacks are hardwired to the dedicated physical controller circuit output - not the summation point of the midi derived signal and the physical controller.
I’m guessing this could be modified in hardware but again, just guessing at this point.
Aftertouch seems to work properly (the CV output responds to MIDI Channel Aftertouch), but none of the others do (velocity, pitch, mod wheel). Hopefully this means that the others could be enabled with a firmware fix, but who knows what’s actually going on inside. Aside from using Matriarch as a MIDI-to-CV converter, this also makes playing the Matriarch from an external sequencer or controller fairly useless if you want to do any patching at all.
I wrote to Moog support about this a couple months ago, but never heard back.
I had to delete my initial response after realizing my controller was assigning modwheel to AT pressure. You are correct and it leaves me thinking the same. If AT can effect the CV output jack over midi then velocity and the modwheel should work the same way. Hopefully it is just a firmware fix.
While they’re at it I wish they would add volume CC7 and going the other way I wish the pedal would send a CC like expression CC11). That may be asking for too much.
Same problem here. Resulting in the fact, that patches I made using the Matriarch Keyboard can’t be played back properly from my DAW, which is very important for me as working for film. Some patches sound totally different ( different oscillator levels ), some of them which use CV out as a mod source don’t work at all via Midi… I hope this can be fixed somehow.
Best,
Ralf
I’m distraught. What a horrible thing. I guess they targeted modular people who are DAW-less? Here I go looking for non-moog solutions…
Anyone here who has experience on how to get a reaction / statement from MOOG music about this?
If we buy an instrument in this price range, they should at least inform us about the possibilities of future firmware fixes…
I had sent an email to support months ago, but have not heard back like many others.
After reading your post today I tried the chat one more time and after leaving it open for 45min I got a reply: 
“There is a bug on the latest firmware revisions that prevents the Matriarch from sending MIDI data through some of the rear panel CV jacks. There is no ETA at this time, but our engineers are aware of the issue and working hard on the future firmware update that corrects this behavior.
In the meantime, I can send you an older firmware version and instructions on how to update your Matriarch if you’d like to drop the firmware down.”
According to Moog firmware 1_1_0 (zip attached) does not have this issue. (I have not tested this.)
Matriarch_Firmware 1_1_0.zip (589 KB)
Uff… WOW, that’s great news!!
Thanx for your persistence, cmoog!
xxx,
Ralf
cmoog, I can confirm this downgrade solution works. Thank you for sharing! Moog had better take time to fix this as it’s a pretty major bug. 
Nice to hear, but: MOOG!!! The first post on this issue is already 10 months old. We need an update! 
I just spoke to a tech at Moog and he said that he is not expecting a fix for the MIDI-to-CV issue unfortunately, and that many people have requested it. He also said that it wasn’t something that was working in older firmware versions, either. Weird! Maybe he misunderstood what I meant – I’m a bit confused.
Does what you’re saying here mean that I won’t be able to patch the CV MIDI outputs from the Matriarch into my Eurorack and get any signal? Or that MIDI coming into the Matriarch doesn’t get passed through to the CV MIDI outputs? Either would be a major issue for me, and I’d need to sell the synth if they aren’t going to be fixed since those are a very significant part of why I bought it – I’m currently building a Eurorack.
Hi Headlands,
yes, hard to believe, but that´s really my problem. I bought the Matriarch as the basis for a Eurorack system. Apart from that I love it therefore, and the possibilities are great. Send a Mutable Oscillator in the Matriarch Mixer, turn it up… beautiful…
I can: Play the Matriarch Keys or it’s Sequencer and patch it’s CV outputs to the Eurorack an add an oscillator from the ER.
I can’t: Play this sound via Midi from my Logic DAW!! Cause the Matriarch doesn’t pass the Midi signal.
Feels very retro, 70ties before Midi. Sometimes I like the restriction, cause it forces me to play live on the keyboard or work with the sequencer. But most of the time I hate it. And it’s really sad, that I still haven’t got any reply from Moog about this!
I bought an extra Midi to CV interface from Doepfer for the Eurorack, and send the same Miditrack twice, to the Matriarch and the ER…
This is one of those things that defy logical explanation for me if there’s no fix for it or they won’t make a fix for it. It’s massively limiting for anyone who uses a DAW and a Eurorack, as we’re talking about, or other situations. I’m feeling a bit pissy about it, but it’s in part because it’s a very expensive synth.
Unless we can get a definitive answer from Moog I will need to buy a MIDI to CV converter like you did. You’re saying in that case I can’t just use the regular MIDI 5-pin out/thru from the Matriarch and plug it into the MIDI to CV converter in order to get MIDI notes from my DAW to go to both? Instead I need to send MIDI out from my DAW to both the Matriarch and the ER converter?
Uups, yes, there was something called Midi through! Totally forgot this. 
But yes, this should work…
Best,
Ralf
It works!!!
Finally I made the firmware downgrade to V 1.1.0. as mentioned above.
Now everything works as expected.
So far I haven’t experienced any bad behavior due to this old firmware.
Anyway, I would feel better to have an updated firmware with this issue fixed.
Best,
Ralf
Reviving this old thread to say that I also had success getting MIDI>CV to work by downgrading to firmware 1.1.0.
Now that the new 1.3.0 firmware is out, I’m hesitating to install it because I’m not quite sure after reading the release notes whether the functionality has been re-implemented successfully. It’s a shame since there seems to be a lot of other bug fixes and additional features, but to lose MIDI>CV functionality again would be a complete dealbreaker for me.
Please let us know if you do so!
I can’t risk it in the moment, due to my live setup.
But I also would feel more convenient with a new firmware version…
Best,
Ralf