Following are new firmware version v2.1.18 and Editor v3.2.0RC1. This version was supposed to be our release candidate, but we also plan a v3.2.0RC2 following later this week. Please download, install, and let us know of anything unusual. We really wish to get this released in a couple of weeks.
Changes in this version
Editor:
Fixed: Trying to save to a different disk results in error
Fixed: VCO2ONLY state not recalled, saving using Cubase v3.1, loading using v3.2
Fixed: CV MAPPING section not populated upon instantiation
Fixed: Second instance of plugin in DAWs should be blocked from use
Firmware:
Added: Changing “Wrap Up” mode by holding GLIDE and turning GLIDE knob. GLIDE knob below mid-position = octave wrap OFF; GLIDE knob above mid-position = octave wrap ON. When top octave wrap is on, then notes above C5 will repeat the highest octave; when octave wrap is off, then all notes above C5 will play C5.
Fixed: Tilde chars are added to preset name when overwritten
Fixed: VCO1 plays C instead of C# when going above top C
Fixed: VCF EG Delay Time made longer so it’s easier to notice the change in sound
Fixed: Changing the destinations of CV mapping sometimes has no effect
Fixed: Sound may change when performing note calibration
Fixed: When Midi Sync is ON, changing LFO rate should affect Clock Divider field
Fixed: CV issues mentioned on some public forums
Fixed: EG HOLD params don’t send MIDI values
Fixed: “GET” may end up with “Invalid Sysex” error message
Fixed: POLY VOICE NUMBER resets to default once powering MTR off.
Fixed: Restore Globals doesn’t work correctly
Fixed: CV Mapping doesn’t function since 2.1.17
Fixed: Misc Midi Sync issues
Fixed: Pitch-CV input now goes to maximum when mapped to non-default parameters. Editing the global “CV Start Note” is now implemented. Users who want to change the default starting pitch for CV-only use, will need to send a sysex command to the Minitaur. Example sysex: F0 04 08 23 18 00 14 F7. the last byte before the F7 sets the value; in this example it’s 0x14 (MIDI note 20). Value range is 0 to 7F (MIDI note 0 to 127).
Tested and fixed note calibration issues:
Verified that Pitch CV Calibration really does work if instructions are followed properly (sending 1V when calibrating 1V, sending 4V when calibrating 4V). Note that if the Pitch CV source doesn’t track linearly, Minitaur also can’t track linearly, but given a linear Pitch CV source, the Minitaur behavior is correct and in-tune.
Addressed issues of “can’t play lowest note via CV” / “sending a C via CV gives a G#”, by removing an internal pitch offset that was loaded at startup (setting “CV Start Note” to zero by default). Unit now plays lowest possible C with 0V pitch CV, up to highest possible C with 5V pitch CV.
The driver allows DAWs to use Minitaur’s Midi ports and an Editor plug-in at the same time.
NOTES:
Driver and firmware weren’t changed since the last version/s, so no need to reinstall if already installed.
Users must first update the Minitaur firmware, and only then install the driver.
With the new dedicated driver for the Sub Phatty, there is no need anymore for the generic moog USB driver and it should be removed. Uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel) and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64.sys” in “Windows\system32\drivers”, before continuing.
No driver is needed on OSX.
Updating the Firmware:
Enter bootloader mode: Press and hold VCO1 Wave and VCO2 Wave switches, and while keeping them both pushed plug the power cord into your Minitaur unit. Keep holding the two switches and press the Release switch, then release all switches. You should see the Glide switch LED blinking slowly, which indicates that your Minitaur is now in bootloader mode.
Connect your Minitaur to your computer using a USB cable. Please connect it directly and not using any hub. If Windows starts an automatic driver search, let it install the default drivers.
Load the C6 sysex program and configure C6 midi ports so they point to Minitaur In/Out (“CONFIG”)
Load the ‘Erase Firmware’ file provided in the firmware zip, into the C6 program (“LOAD”)
Click SEND. VCO1 Wave switch LED should blink as the old firmware is being erased. Once completed, VCO1 Wave LED should go dark and Glide LED should keep on blinking slowly.
Load the firmware sysex file into the C6 program and send it to the Minitaur (“SEND”). As the syx file is being transferred, you should be able to see the Midi LED blinking rapidly, and VCO2 Wave LED blinking slowly. Once the firmware update is completed, the Minitaur should reboot automatically. Your Minitaur is now updated with the new firmware.
Run the Minitaur Editor and check for the firmware version by clicking on “Settings”. It should say 2.1.18. If it says anything other than 2.1.18, it means that the beta firmware has not been updated successfully, and you should repeat the process again from the first step.
Restore settings to defaults by clicking on “Restore Default Global Settings” on the Editor’s Settings page.
Installing the driver (Windows only):
Power off your Minitaur and disconnect its USB cable.
If you haven’t done so already, uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel), and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64.sys” from Windows\system32\drivers.
If case you are also using a Sub Phatty, install its new dedicated driver, posted here: http://forum.moogmusic.com/viewtopic.php?f=20&t=25828
Same goes for Sub 37. Use the production driver provided with the Editor 1.0.0 / Firmware 1.2.0 release package.
Restart your computer.
Power the Minitaur On, connect the USB cable and let Windows auto-detect and install the default Minitaur driver. This may take a few minutes so please be patient.
Once detected, install the new Minitaur driver. The installer should load two popup messages, asking to confirm the new driver. Mark the checkboxes and let it complete. If asked by the installer to disconnect and reconnect the cable, please do so.
Restart your computer.
Check your Device Manager settings. There should be a separate entry for MTR, SPH and S37 (in case they are present is your system). The entries should appear under the root, with no exclamation mark placed on them.
Open the Editor, click the Setting button and select “moog Minitaur In/Out” from the Midi Input and Output menus. To sync all preset, click the GET button.
Looking and sounding really good so far, noticing a few things:
VCO2 Only mode for LFO isn’t working.
The text for Preset Category, Preset Name and LFO Clock Divider look fuzzy on the edges, and there is some distortion to the letter causing “0” to look like “D”. Perhaps there is a different type weight which can be more legible at smaller sizes?
Preset LFO depth amount is not sent until after the touching the control in the editor.
The indicator for Midi in/out doesn’t seem to be lighting up, not sure if it’s meant to light in the same way it does on the HW.
The indicator for LFO rate doesn’t light.
Preset Name list expanded view can cover the current Preset Name, feeling jarring especially if it was mis-clicked.
VCO2 Only mode does work for me
Correct, the zero looks like a D
The MIDI In/Out in the editor indeed never lights up like the hardware does
I understand you mean the LFO rate on the hardware? In mine it works fine
Can’t confirm right away the rest of your report
I am using it with Live, whose MIDI clock is synced externally, from the OP-1. When this function is on, the envelopes on the Minitaur do not trigger properly. The sustain stage dissapears while the playback is stopped and works fine during reproduction. I wonder if this is the expected behavior
After the USB lost connection accidentally, the Editor kept receivin the Minitaur’s controls, but it stop sending them to the unit. I would expect an error message from the editor when something like this happens
The CV inputs seem to work fine with my EW+ even when mapping them, altough I haven’t tried every parameter yet. The EP-3 however, does move the parameters, but in the opposite direction. When it’s in the highest position, the parameter is in zero and vice versa
LFO RATE Led in GUI is a dummy and will not light up. It’s just the way the GUI was made (so it matches the actual interface).
Midi In on Editor will light up, if Echo DIN → USB is ON, and MTR is receiving Midi from an external source via it’s MIDI In port.
Midi Out on Editor will light up whenever the GUI is tweaked, having the Editor sending out Midi messages.
VCO2 ONLY doesn’t work as expected here as well. Thanks for noting about it.
LFO VCO/VCF AMT work correctly when tweaked from hardware here.
I’m not sure I understand the 0 vs D issue you’ve noted about.
I should have mentioned all of my feedback is based on using the editor only. Loading presets which have LFO modulation don’t reflect that in the audible sound until “touching” the VCO or VCF depth amount in the editor.
-“Glide+EG FIlter Attack” never send a 0 value, the range is only “1 to 127”
-In Editor choose “panel setting preset”, then, still in editor, increase preset number with the narrow, move in the hardware the Cutoff knob then come back in the pannel setting preset with the editor, the sound is changed but the value is not taken in the editor… (it’s the same with some other knobs..)
-In the panel setting preset, change the LFO shape (with editor or with “glide+FLO rate”), then choose another preset (with editor or hardware glide + OSC1/2) and when you come back in the panel setting preset, the LFO shape will always be the triangle one… (I think it’s the same with all the Glide + X function), the changes are not taken in the editor if you don’t save them before, is it a normal behavior ?
I have an other question..
The behavior of the “GLIDE + Sustain Amp” is very annoying.
If you want to let a sound always open, you can’t, because you have to cut it before.
Because to let the gate open you have to do “GLIDE+ SUS amp from 0 to 127” but “GLIDE + SUS amp 0” is the Panic shortcut… =(
So, is it possible to have the following behavior :
glide + SUS Amp 0 = Gate off
glide + Sus Amp 127 = Gate On
?
Last question : could we expect in the next version that all the under the hood function will be accessible with a GLIDE + XXX shortcut ?
And, in the same manner, could we expect that all the functions will be editables in the editor (there is no knob in the editor for EG Delay/EG Hold…) ?
Here is the “0” vs “D” illustrated, on closer examination the LFO clock divider, preset category and name labels all appear to be italicized. Changing the font to a regular typeface could potentially help with the legibility.
Can’t reproduce using 2.1.19, can you try this again using latest firmware?
Please see Amos’s note: For LFO Shape or any “under the hood” parameter, this change must be saved to the hardware while Preset 0 is active (to be clear, “this change must be saved to hardware preset 0”) before switching presets, or the change will be discarded. Same as making a change to any other preset and then switching presets without saving; non-saved changes will be lost. The panel knob position is different; preset 0 should definitely load the current knob positions every time.
Will post as a request. However the chances there will be any change made on this release are really slim, sorry.
