Hello,
just uploaded the new firmware beta (2.1.9) and testing standalone editor 3.1.0.
new lfo waves are not working, when changing them with the editor the midi led light up, so the message is being send, but the waveshape remains a triangle.
also vco2 mod only is not working either.
finally, i tried to install the latest midi driver and it got stuck at about 90%. i needed to restart to uninstall.
been playing around with new firmware (2.1.10) and editor and it seems to be working as described.
preset saving and recalling working well for both, vst’s and hardware shortcuts.
what’s the difference between vst editor and editor-vi? both working with no issues here anyways though (64 bit version)
vst screen take a while to load when restoring (live 9), probably due to graphics?
takes longer than other vst’s i have. no issues so far but could be too much resourse consuming, will try with more things happening on the live project later.
will keep on playing and report back if anything strange happens.
hey. first tests with new firmware (2.1.13) and vst 64 bits (3.2.0b6).
GUI runs a lot faster now on the vst, thanks for that.
had a situation with midi connection though:
i was scrolling through presets by hardware (glide + release mode on) and after some preset switching the vst stopped to actualize.
changed to settings screen and a popup telling about lost midi communication with minitaur showed up (All this in ableton live 9)
i closed live, re connect the minitaur usb and run all over again and wasn’t able to reproduce the crash. worked solid after that.
on another subject: is it possible to add a velocity sensitive configuration via hardware shortcut? like with glide + sustain knobs for filter and vca respetively? i often use the mtr in an otb setup and really miss that control.