Moog Music Forum

Have anyone else noticed that when enabling latch mode on only the Amp envelope it will also latch the filter envelope (locking the filter envelope in sustain mode). So when playing the keyboard the filter envelope will not retrigger. Is this a bug or intended behaviour?

Petur wrote:Have anyone else noticed that when enabling latch mode on only the Amp envelope it will also latch the filter envelope (locking the filter envelope in sustain mode). So when playing the keyboard the filter envelope will not retrigger. Is this a bug or intended behaviour?

Wow! Interesting find, Petur.
I was instantly able to reproduce it, just like you said.

With AMP EG's LATCH ON lit (but with the FILTER EG's LATCH ON dark) the Filter Envelope stays at its SUSTAIN level after key release.

The FILTER EG should be falling to zero at its[ b]RELEASE[/b] rate. Instead, turning the FILTER EG's SUSTAIN knob (after key up) proves that it's still in that portion of the envelope.

_DemonDan_ wrote:

Petur wrote:Have anyone else noticed that when enabling latch mode on only the Amp envelope it will also latch the filter envelope (locking the filter envelope in sustain mode). So when playing the keyboard the filter envelope will not retrigger. Is this a bug or intended behaviour?

Wow! Interesting find, Petur.
I was instantly able to reproduce it, just like you said.

With AMP EG's LATCH ON lit (but with the FILTER EG's LATCH ON dark) the Filter Envelope stays at its SUSTAIN level after key release.

The FILTER EG should be falling to zero at its[ b]RELEASE[/b] rate. Instead, turning the FILTER EG's SUSTAIN knob (after key up) proves that it's still in that portion of the envelope.

Yup! I have reported it to Moog and they have confirmed it is a bug. They also said it is in in the patch list for the next firmware release.

Is the latch bug fixed? I haven't been able to try it out.

klay wrote:Is the latch bug fixed? I haven't been able to try it out.

Seems fixed in 1_0_13!

I don't have the old OS loaded anywhere to compare to the broken behavior.

But, based on the text description, I think it has been corrected correctly