Page 1 of 1

Grandmother and re-triggering ENV : Issue

Posted: Sat Jun 29, 2019 10:08 am
by liviou2004
Definitely there's an issue with the Enveloppe Trigger In :

I did a try with an external MIDI Gate module : my Behringer Neutron wich has a MIDI Gate output. So the Grandmother MIDI out is connected to the Nuetron MIDI In.
Each time I'm pressing a key on GM, I can see the MIDI In led blinking and triggering the Neutron Env.

I have connected Neutron MIDI Gate output into GM Trigger In, normally it should trigger the GM Env each time I'm pressing a key, even on legato playing. But it's not the case.

If the GM had been right, the Env Trigger input should had priority on the Keyboard. But the Keyboard has priority so Trigger Input will never work that way.

I don't know if that could be solved by a software upgrade ?

Re: Grandmother and re-triggering ENV : Issue

Posted: Wed Jul 10, 2019 1:31 am
by le__rien

You totally right, this is a general issue with the GM. here is the answer of the support on this topic:

"What you are encountering is due to a known bug in the Grandmother firmware. Pressing the HOLD button while turning the Glide knob should change the legato setting however this bug is preventing that functionality from working at this time. Our engineers will be addressing this issue, in addition to some other bugs, in the next firmware update for the Grandmother. As for when this update will be available, I cannot say for certain. When new firmware becomes available, we will make an announcement through the Moog website and to all registered Grandmother owners."

I hope the firmware update will be released soon, because this is very annoying...


Re: Grandmother and re-triggering ENV : Issue

Posted: Wed Jul 10, 2019 12:31 pm
by liviou2004
Thank you very much. Knowing the staff is working on that issue is a fisrt good news.

Re: Grandmother and re-triggering ENV : Issue

Posted: Tue Sep 10, 2019 8:52 am
by liviou2004

Two months since you've got a response from Moog about this issue. For the moment, no update has arrived.
Hope Moog engineers are going on solve this problem !