Using Minibrute (Firmware 1.0.3.23) with Modular V (3.1).
When I patch the keyboard aftertouch (AT socket) into filter frequency modulation in Modular V, I get following response:
When I start to apply aftertouch on the Minibrute keyboard, there seems to be a threshold value of pressure after which the AT value switches to
'full voltage' and it maxes out. Even setting the CV attenuation to a tiny amount, you still get max modulation.
When I then let my finger rest lightly on the key, the aftertouch value still seems to remain maxed out for about 0.5 to 1.0 seconds, then it decays
back to a value of zero over the course of about 0.5 seconds.
Aftertouch from the Minibrute works well for all other devices in V-Collection 7 (for example CS-80 V). It's only with Modular V that I am seeing this
strange behaviour. Minibrute also works correctly with native devices in Reason.
When I make aftertouch automation curves in Reason, I sometimes get this strange behaviour too with Modular V, however it works correctly about 50%
of the time. With the combination of Minibrute and Modular V, it ALWAYS does this strange thing, 100% of the time.