Minitaur firmware update soon - your requests here please

[bichuelo]

Hey Amos,

I'm hooking up the Minitaur to the voyager ext input and playing it via midi from the voyager, I'm running into some issues where I'll change a parameter in the voyager and it will change something else on my minitaur. Is there any fix for this? Plus, when I change the midi out oct to -2 on the voyager the Minitaur doesn't recognize it for some reason. It only works if I change the main octave setting.

Thanks.

I suggested previously that the unit could have a command to turn on and off Program Change reception. I think this could be applied as well to CC values...

[bc3]

I updated to 2.0.8 from 2.0 and now am experiencing the "all notes playing at the same pitch" syndrome. Wish I would have just stayed on 2.0 now until the new firmware was "officially" released. Looking through other posts on the forum it appears that this problem is common and my Minitaur most likely needs the Pitch CV input calibrated? Are there instructions available from Moog on how to perform the calibration? I called tech support and they did not even mention it and told me just to send the unit back for repair. I have a show in a few weeks and am worried it will not be returned in time. Ugh!

[Amos]

Happy Friday, Minitaur fans!! Here's some new firmware.

firmware v2.0.9:
http://www.moogconnect.net/downloads/mi ... v2_0_9.syx

recent-ish update instructions:
http://www.moogconnect.net/downloads/mi ... README.txt

Now, some new sysex "command" files:
(these will only work after you update to v2.0.9 firmware)

Reset Pitch-CV Calibration to Default:
(only use this if your Minitaur is playing the same high pitch no matter what note you play)
http://www.moogconnect.net/downloads/mi ... ET_Cmd.syx

Turn OFF Program Change (Minitaur will not receive or send MIDI Program Change messages):
http://www.moogconnect.net/downloads/mi ... ge_OFF.syx

Turn ON Program Change (Minitaur will send and respond to MIDI Program Change messages):
http://www.moogconnect.net/downloads/mi ... nge_ON.syx

_______________

So What Else Is New:

True (constant) Beat-Frequency adjustment is back... with "compatibility mode" for older presets.
Basically: if you load an old (pre-v2.0.9) preset, the Beat control will behave as before, like a very tiny detuning of VCO2 Freq. So, old presets will play and sound as they used to. HOWEVER, if you change the Beat setting at all, it will update the preset to the new format and you will now have constant-beat-frequency detuning behavior. You'll then need to save the preset if you want this new behavior to persist.

So... if the old sound of your presets is important, leave their Beat setting alone, and they'll keep sounding the same. If not, tweak away and enjoy the improved Beat setting.

ALSO... you can now adjust Beat from the front panel. Just press & hold the GLIDE button while turning the VCO2 Freq knob. VCO2 Freq while holding glide = VCO2 Beat. The only downside is it's sorta hard to do one-handed. It works, though!

Have a great weekend,

Amos

[snailbirdfish]

TRANSPOSE PLEASE!!!!

My Xylosynth is only in range from 29 - 101 and it wont budge.

Minutar is 0-72 and wont budge.

I am seriously missing the bass.

Please please please please please

[Chef]

- VCA output level is not stored/recalled to/from the Preset Memory of the Minitaur.

Volume knob cannot be saved. It's a purely analog control.
There is a "MIDI volume" response (CC7) which digitally scales the volume envelope to a reduced maximum amount... and I don't remember if this is saved or not, I think not. I'll have a look.

Hi Amos,

Any luck with the Midi Volume?

[Amos]

Any luck with the Midi Volume?

Yes, it turns out it's been saved as a part of the preset the whole time.

Only thing is, this value is not used when you load presets.
I'm now adding a global option to "load preset volume level" or not. That should do the trick.

[Amos]

OK, here's new firmware. Lots to enjoy.

http://www.moogconnect.net/downloads/mi ... 2_0_10.syx
http://www.moogconnect.net/downloads/mi ... README.txt (update instructions)

I promise a full sysex documentation when this firmware is officially released.

For now, here are some sysex "command" files to turn the new features on and off.

New features in this build include:

- MIDI Note transposition; transpose incoming MIDI notes up to 24 semitones up or down.
http://www.moogconnect.net/downloads/mi ... inus12.syx (down one octave)
http://www.moogconnect.net/downloads/mi ... inus24.syx (down two octaves)
http://www.moogconnect.net/downloads/mi ... e_Zero.syx (no transpose)

- Ignore MIDI CCs (except for Mod Wheel, Pitch Bend); for the fellow who wants to control Minitaur from a synth and turn knobs on the controller synth without the Minitaur sound being affected:
http://www.moogconnect.net/downloads/mi ... se_OFF.syx (Minitaur won't respond to CCs)
http://www.moogconnect.net/downloads/mi ... nse_ON.syx (Minitaur will respond to CCs)

- Load Preset Volume; MIDI CC7 sets a volume scale, prior to the (always-active) VCA Volume pot on the front panel. You can load this saved volume scale when loading presets, or not. Default = not.
http://www.moogconnect.net/downloads/mi ... ume_ON.syx
http://www.moogconnect.net/downloads/mi ... me_OFF.syx

I also made a small fix in this version to the "legacy mode" for the VCO2 Beat parameter; I'm not certain it was working in v2.0.9 but it should work now.

[FuzzyController]

please can you fix saving panel settings. they never seem the same once saved and then returned too via the editor.. its usually lfo or cut off that is affected.. the whole saving of presets could be expanded on and may be a user patch section with all my own sounds in it...

How about releasing a new set of presets, if saving my own wont work ...

Minitaur still freezing on my mac running logic x same as it did in logic 9... ableton seems more stable though


great product , please make it easier to recall all the work that i do on the machine ...

i'm sure you'll come up with the goods!

Regards

Guy

[xnenuphar]

Hey fellow moog lovers, hey amos (you are a true hero btw, my band is pondering carrying a yet to be received picture of you in our respective purses):

thanks for the hard work on the bug fixing etc.
my request: please please please fix the preset saving/recalling problems the editor has, still going so well after the latest patch thingy.
I cannot bear to lose a single one of the AMAZING FANTASTIC sounds this precious diamond of a synth allows us to create any longer. we need to grasp the fame and fortune soon or I have to go back to the social work and saving the world stuff! save us from this! please fix those preset issues.

from somewhere in middle of europe with loooooove.
xnenuphar.

[FuzzyController]

Any idea when the Minitaur REV 3 will arrive ?

[spin]

I don't know why, but with the new firmwares i can't get minitaur to work in both directions using CTRLR minitaur vst editor with 14 bit midi resolution. For me it works only with v2_0_4 firmware. With the others the minitaur will respond from 14 bit cc from the editor but the editor doesn't respond when moving minitaur knobs.

Anybody else got the same issue?

[Amos]

did you manually re-enable 14-bit midi output after updating to the new firmware? perhaps that setting reverted to its default state, which is 7-bit output.

http://www.moogconnect.net/downloads/mi ... bit_ON.syx

^^ that sysex command should turn on 14-bit output; see if it helps. The stand-alone editor can turn this setting on and off as well.

[spin]

yes i have tried with 14 bit on message but it didn't work. I have to say that with the standalone editor (and with every firmware i've tried) i never get it respond to minitaur knobs. It works only when sending CCs to minitaur. Any solution?

[TffShtt]

2.0.10 didn't work for me at all...I got the dreaded high-pitched-constant-note problem on both oscillators before playing a single note. Reinstalled...using the erase sysex then sending 2.0.10: same dreaded high-pitched-constant-note problem on both oscillators. Decided to revert to 2.0.8.

2.0.9 gave me the dreaded high-pitched-constant-note problem on oscillator 2 after playing for a while. Before this happened, I didn't really believe in the dreaded high-pitched-constant-note problem because I never experienced it.

2.0.8 seems to be working fine and have had no sticky LFO experiences that I had on a regular basis before this update

@spin I could never really tell if 14 bit was working at all... on several occasions I tried setting up 14 bit CCs on my remote SL, sending them to the editor (with 14 bit switched on in the editor) or directly to the minitaur (first sending the 14 bit on sysex command) and in both cases got no reaction from the minitaur to knob tweaking. I am probably missing something.

[Chef]

Hi Amos,

Thank you very much for the Update and the quick response to my request (_Minitaur_Load_Preset_Volume_On)! I am now able to use the Minituar for my liveset, knowing that I have a balanced Bass Level throughout the set. It is working really nicely.

Just for sake of documentation: Is it correct that you need to upload this Sysex command to the Minitaur Bootloader mode? When I tried it first it didn't seem to work but after loading it up to Minitaur in the Bootloader mode it was ON.

Best Regards,
Stef