Minitaur firmware update soon - your requests here please

[Amos]

OK, here's v2.0.28:
http://www.moogconnect.net/downloads/mi ... 2_0_28.syx

now we are getting somewhere!

Fixed in this version:

- Good old tuning (you will need to do Note Calibration if updating from 2.0.25/.26, but probably not if updating from v2.0.21)
- fixed Knob Mode behavior; Relative knob mode should work consistently now.
- new panel knob function: Hold GLIDE + turn FILTER ATTACK knob to select TRIGGER MODE (legato on, legato off, reset).
- fixed Save Preset behavior... see below

To save a preset in place, it's the "older" way again (although a little faster)... first press GLIDE, then while holding GLIDE press RELEASE; hold for half a second, done. The GLIDE and RELEASE button lights start to pulsate, then they go back to normal and the MIDI LED blinks to confirm preset is saved.

To save a preset to a different location, it's simplified similar to your suggestions... Press GLIDE + RELEASE and then let go, instead of holding for half a second. You'll see the GLIDE and RELEASE button lights pulsating... while it's in this mode, you can scroll up/down through the presets by pressing the OSC 1 and OSC 2 waveform buttons. When you get to a preset you want to save over, press GLIDE + RELEASE again to finish saving. If you want to exit this mode without saving, press the RELEASE button by itself.

To output all parameter values as MIDI CCs, this is the same as before: while holding the GLIDE button, double-tap the RELEASE button. This only sends MIDI CCs and does not save the preset to internal memory.

A note about saving presets "in place" -- the Minitaur always boots to Preset 0 and preset 0 always gets the real knob positions from the panel, instead of using the saved values for the panel knobs... so if you turn on the Minitaur and tweak up an amazing sound, you might want to save it to a different location rather than saving it to Preset 0, because your saved sound won't always sound the same in that particular location. You may have already discovered this.

I added a global setting for this (preset 0 behaves like all other presets, or preset 0 always gets the panel settings)...
here are a couple sysex "commands" for turning this on and off. "preset 0 is static" is the new setting where preset 0 acts like any other preset. "preset 0 is dynamic" is the default behavior, where the MInitaur uses the real knob positions any time you switch to Preset 0. (the Minitaur always loads preset 0 when you first power it on)
http://www.moogconnect.net/downloads/mi ... static.syx
http://www.moogconnect.net/downloads/mi ... ynamic.syx

[misterpete]

I downgraded back to 2.0.26 after 2.0.27 because of a weird 'time lag' i.e. every preset and setting had a super slow attack like playing a pipe organ, or being out of sync on a primitive DAW... i forgot the word for that...
strangely, on my machine tuning is fine and 2.0.26 is running quite smoothly!

[CleverConQueso]

Is it too late for a two or three button note panic? I know I'm supposed to be able to send one but sometimes you just can't. It's particularly an issue because it seems like my Minitaur, anyway, is particularly prone to sticking on a drone.

[Amos]

I downgraded back to 2.0.26 after 2.0.27 because of a weird 'time lag' i.e. every preset and setting had a super slow attack like playing a pipe organ, or being out of sync on a primitive DAW... i forgot the word for that...

The word is "Latency" -- and I added a hidden parameter for it in v2.0.27, although on my presets it was set to zero by default. I'll tinker with that some more this afternoon.

Why add a latency parameter, you might ask? I have a good reason, actually. Note Sync.
The idea is, Note Sync resets the VCO phase to zero the instant you get a Note On.
If you want to play with the phase relationship between the oscillator and the envelopes, you need to reset the oscillator first and then add a little latency to the envelopes so that they start at a different phase relative to the VCO.
You could do it the other way (envelopes, then phase reset) but then you'd get a reset-glitch at the start of the note and it wouldn't sound right.

So, that's the deal... It will be a really useful parameter I think... but it looks like I'll need to ensure that its default value is set to zero for all presets.

Is it too late for a two or three button note panic? I know I'm supposed to be able to send one but sometimes you just can't. It's particularly an issue because it seems like my Minitaur, anyway, is particularly prone to sticking on a drone.

There's already a panic -- hold GLIDE button while turning the Amp EG SUSTAIN knob to zero.

[misterpete]

Cool!
Thanks Amos!
Is there a good reason for leaving the CV Filter IN static as opposed to mapping it like GATE, VOLUME, PITCH?

[Amos]

Here's v2.0.28, with no latency.
http://www.moogconnect.net/downloads/mi ... 2_0_28.syx

-- This new latency thing I described in my previous message is not ready for release, so it's better to take it out entirely for now.
It's something I am working on in response to an individual user's request, but it's a cool idea... just needs more work and we are trying to get to a stable release build at this time.

So, I've updated the link in my previous message as well... v2.0.28 is the version to test at this time.

Cheers,

Amos

PS)

Is there a good reason for leaving the CV Filter IN static as opposed to mapping it like GATE, VOLUME, PITCH?

Yes, the filter CV is purely analog. It's not scanned by the processor, so it can't be mapped to anything.

[misterpete]

Thanks Amos ~ I guess most people only post when things DON'T work but want to confirm everything is running well for me with this fixed Minitaur_firmware_v2_0_28.syx

about the analog Filter CV is that the same as selecting "Cutoff" via a mapped input or is there something else going on there?

best, Pete

Here's v2.0.28, with no latency.
http://www.moogconnect.net/downloads/mi ... 2_0_28.syx

Is there a good reason for leaving the CV Filter IN static as opposed to mapping it like GATE, VOLUME, PITCH?

Yes, the filter CV is purely analog. It's not scanned by the processor, so it can't be mapped to anything.

[tagirov]

updated to 2.0.28, works stable so far

[CleverConQueso]

Say, I think the V2 editor has an audition feature under the bleep key. Any chance on getting that replicated in the new editor or in the hardware?
Thanks for the tip on the panic feature (glide+ampSus->0)
-CCQ

[confused machine]

hi amos

first just want to say thanks for your efforts on the minitaur, i had one of the early ones so all this extra functionality since v1 has been a great bonus

one quick question, is there any possibility of being able to assign the various cv mappings via midi cc instead of the editor?

[tagirov]

Say, I think the V2 editor has an audition feature under the bleep key. Any chance on getting that replicated in the new editor or in the hardware?
Thanks for the tip on the panic feature (glide+ampSus->0)
-CCQ

+500 agree
Audition or external keyboard routing + virtual keyboard audition

[CleverConQueso]

Bleep? Not sure how or why that happened in my post but it's the shift key. Maybe speech to text on input, I don't remember.

[CleverConQueso]

In the save routine, how about the oscillator buttons display the patch number you're on in the same way the firmware version is displayed? Also, any chance at an audition via button press or perhaps, keyboard press?
.Thanks,
-CCQ

[EMwhite]

Bleep? Not sure how or why that happened in my post but it's the shift key. Maybe speech to text on input, I don't remember.

It's called a typo followed by censorship

[tatobox]

I updated to 2.0.28. It's really stable.
Thanks Amos