I’m having problems with the Minitaur Editor again
Today I noticed a strange behaviour when using the velocitiy sensitivity and keyboard tracking settings.
For example if I set the velocity sensitivity (VCA and VCF) to zero and save the preset, the next time I load it it’s velocity sensitive again (even though the parameter in the editor shows zero). If the VCA vel.sens. is set to some other value than 0, the next time I load the preset there is no sound at all until I edit the parameter! Also the keyboard tracking setting is not always loaded correctly.
Can anyone confirm this or is there something like a default value for these parameters that I have to set?
If I try dealing up velocity to amp or filter and save the patch (on Mac or in onboard preset), when I load the patch there’s no sound until I touch the same velocity control on the editor.
The editor is obviously not storing these values correctly.
I have noticed this exact same behavior - Velocity settings are not being saved. I’m not sure if they are being saved using hardware or not. I cannot get a preset to recall that shows anything on the velocity knobs. They always show up as zero, as far as I can find. I don’t think any of the factory presets have velocity anyway, but this is a bug regardless.
I can change the velocity response using the behind the scenes panel - that definitely works, the data is being sent to the hardware, but the setting is not saved with the preset, at least using the editor to save it.
I also experienced the “no sound” problem. I did not realize it was related to the velocity control, but that would make sense.
I stopped using the velocity in general because of this. The Minitaur kicks ass without velocity response anyway, and performs sort of like a classic MiniMoog, where you can get responsive espression by varying the attacks on the ADSRs. Having the Release option on the Minitaur is really great as well.
Anyway, I wanted to jump in on this thread because I see elsewhere that the newest update of the editor and firmware may be coming soon and I’d like to make sure this bug is looked into.
