I think this is fixed now. 
http://www.moogconnect.net/downloads/minitaur/Minitaur_firmware_v2_0_13.syx
in v2.0.13:
My apologies for all the long waiting and incremental improvements… getting closer now.
Work continues on the new editor, as well.
Sorry Amos but this one doesn’t work at all for me…
i return to 2.0.12
in Mode 2, Release switch stays locked “light on” and there’s no other way to light it off than switch in mode 1. Decay is not functionnal.
and while i’m writing, the minitaur freezed on a release/note on.
(about the “freeze” problem, do there is a shortcut that i can do in live situation in case of ? )
As every other MIDI gear, you can send a panic message (CC#120 or CC#123) on the current MIDI channel.
(i meant, physical shortcut)
Fixed! Added a physical shortcut for panic/all-notes-off.
http://www.moogconnect.net/downloads/minitaur/Minitaur_firmware_v2_0_14.syx
New in v2.0.14:
Default global settings are:
Knob Mode = Relative
Note Priority = Last Note
MIDI In/Out channel: 1
MIDI input transpose: none
MIDI CC filter: off
14-bit MIDI: off
Load Preset Volume: off
Load Preset Mod Wheel: off
Enjoy,
Amos
What controller are you using to send notes to the minitaur? just curious if this is maybe a factor…
this time it was my MPC1000, midi, in loop mode on… maybe 8 bars. but sometimes it occurs while playing a whole song, sometimes in USB from my computer. i think, more often in loop mode.
it’s not happening like 10 times in an hour, but enought to be afraid of live troubles and needs a panic button (lack of possibilities associated just with switches ? 
doing this with one hand (the other is still on the guitar or the piano) would be nice… but guess it’s complicated, so much combinations…)
i use a midisolutions quad out of my mpc, for several machines, included the Minitaur. all of them have Program changes, Cc’s and other message send on their respective channel. Minitaur is 01. sometimes i think it’s maybe a Cc destinated to another machine that makes the minitaur fault, but it’s happening when it’s alone with no other channels too. sometimes. Always the same trouble… like a long release (or a note off miss ) where you can ear a few note that are still playing behind in legato, until the decay fall to 0. switch off/switch on (or Cc 123 from a DAW)
GLIDE button is directly next to Amp SUSTAIN knob… I have only ever used one hand to do the new “all notes off” shortcut; one finger on the GLIDE button, and a thumb to turn the SUSTAIN knob. I am right-handed, I suppose with the left hand you would use thumb on the GLIDE and a finger to turn the SUSTAIN knob… but it should work much the same.. I hope this is not too much to do while playing another instrument.
I’ll do some further investigation of the underlying issue, as well…
edit: I could do something else for all notes off… Hold Glide + tap three times on the RELEASE switch? Would that be better?
Any other suggestion?
-Amos
I think the glide and sustain works just fine. It’s a keeper if you ask me.
yes it’s cool ! works great, i didn’t figured, i wasn’t in front of the minitaur
Sorry again, but the Decay/release mode still doesn’t work for me AT ALL in 2.0.14, same as 2.0.13
mode 1 is working, but when switching to mode 2 (that should be the one and unique mode in my modest opinion) the release switch stays “light on” and is unusable… → return to 2.0.12 to work this afternoon
cheers
^^ that’s odd, I don’t have this problem at all. Mode 2 works for me as it should; the RELEASE toggles on/off reliably, and maps the Decay/Release knobs to Decay when off, and Release when on.
Did you try a Factory Reset after loading the latest firmware?
(http://www.moogconnect.net/downloads/minitaur/_Minitaur_Factory_Restore_Cmd.syx)
I am not exactly sure why you should see a different behavior than I am seeing, but maybe the state of the global variables is different on your unit than on mine… I’ll look at this some more, but I definitely am not seeing the same problem, which makes it a bit harder to fix. 
cheers,
Amos
OK, I changed the switching on/off logic to be more robust, it should work even if there is some funny starting value in memory (as I suspect is the case in your unit). This will put it right, I am almost certain.
http://www.moogconnect.net/downloads/minitaur/Minitaur_firmware_v2_0_15.syx
changed in v2.0.15:
Thank you Amos for all your hard work!
Well, for me in this version, Release button does change the behavior of the Decay knob as you had explained, but it does not turn on or offf the Release mode of the envelope. For me its always on now.
The rest of the buttons are simply not working in this version
That is the trade-off… in Release Mode 1, the Release button turns on/off the release section of the envelope, and that’s its only function.
In Mode 2, the Release button controls the behavior of the Decay/Release knob (and that’s its only function).
As for the other buttons not working… my apologies! I will test further before my next update.
hi guys. Could someone explain me how saving/storing/scroll presets works actually on the minitaur? I am a little bit confused
thanks in advance
Unread postby spin » Fri Oct 04, 2013 2:09 pm
hi guys. Could someone explain me how saving/storing/scroll presets works actually on the minitaur? I am a little bit confused
(start at page 01, we’ll talk about the editor in a few days… 
)
(sorry for the joke, but actually it’s just doesn’t work at all. you can save, but the sound will maybe slightly change so you’ll have to save it manually again on the machine using shortcut after the “save to computer → store somewhere in the machine” hard manipulation. then, the name will change with strange letters, and your preset may be one step higher or lower on the preset list. without the name you gave. easy way, no ?
so: do not record presets one after one, let space between them, like 2 empty programs… and recall them via Program Change, finding them with your ears, not with the list… that’s my advice)
cheers
(by the way, i didn’t know how to make a “quote” on a forum… sorry)
And for our concern Amos, i’ve just apdated to 2.0.15 and it’s working fine, actually. COOOOOOL
i’m working on it all day today, so i’ll tell you if there is troubles, and maybe i’ll have the “oportunity” to test the ALL NOTE OFF shortcut 
it was a short breath ! 
first bug of the day: pitch is not working correctly. trying to set it to +12/-12 (as it should be as default at my opinion…) and it sets itself lower than it should. like: +12 on the iditor is +7 on the machine, etc…
but, the most problematic thing (that may help for your diagnostic) is that the two osc are not following the same pitch… for ex. when i turn the wheel up, (set to +24 to have +12) osc. 1 is at +12, and osc2 is at… +10… nearly.
it happened before, but when i was swhiching on/off the machine, reboot the editor,tweak the pitch pots on the editor it came back… not this time.
a sysex command to reset pitch mode and set everyone to +12 for example ?
cheers
Hi everyone… v2.0.15 was a nice effort but it did indeed have a new problem with the oscillator and glide buttons, where my fix for the Release button was incomplete… I fixed it this morning.
http://www.moogconnect.net/downloads/minitaur/Minitaur_firmware_v2_0_16.syx
ALB: I can pitch-bend +/-1 octave, +/- 2 octaves, and oscillators are tracking OK.
I recommend you install the new firmware from this post, and then run a Note Calibration, then try your pitch bend again.
(note calibration sysex: http://www.moogconnect.net/downloads/minitaur/_Minitaur_Note_Cal_n10-n72_Cmd.syx)
Another thing I discovered today is that the old editor does not always send consistent MIDI CCs from its pitch bend amount selection controls. The new editor can’t get here soon enough… 
I am getting lots of updates from the editor developers though; progress is good.