We’re posting the final release candidate for minitaur Firmware and Editor, which are 2.2.0RC4 and 3.2.0RC4.
Please install, test and use extensively, and report any issues on the forum.
We won’t be able to add any new features unfortunately, but will try to address any real blockers.
Thank you all for your precious time and great support during this phase,
Much appreciated!
IMPORTANT: Please DO NOT link this version to anyone outside this beta forum and group. It is still confidential and may result in different firmware versions carrying the number of 2.2.0 to exist on-line. We will release it officially once approved.
The driver allows DAWs to use Minitaur’s Midi ports and an Editor plug-in at the same time.
NOTES:
Drivers haven’t been changed since the last version, so no need to reinstall if already present.
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.2.0. If it says anything other than 2.2.0, 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.
Following is a list of changes added in this version.
Firmware:
Fixed: CV inputs work only once making an assignment
Fixed: Modulation corrupt when playing specific preset in Ableton, synced to DAW
Fixed: LFO AMT not recalled with a saved Ableton project
Fixed: KEY TRIGGER doesn’t seem to function when MIDI SYNC is on
Fixed: Restore Globals doesn’t work correctly
Editor:
Fixed: Sort by Category broken
Fixed: PT12 project loaded with no MTRE preset menu and sound wasn’t recalled
Fixed: Selecting top presets, the mid-pane should scroll to make selected preset show
Fixed: off-by-one on Clock Div display in response to CC from hardware
Fixed: Release button doesn’t affect hardware when not it Linked mode
Fixed: Make two parts of Sync warning message in one line in OSX
Fixed: Selecting a category from top list doesn’t always work
Fixed: Hardware list empty once canceling GET
Fixed: Getting “Hardware Disconnected” or/and blank list once GET completed
Fixed: Remove the balloon appearing on start, when MTR is not connected
Fixed: Broken link to standalone when installing on a clean Home 32bit Windows 7 + no AAX/RTAS listed
Fixed: Top category list may present items which don’t exist on the list
Fixed: Hardware Presets list shows as empty once GET is completed
Added: Perform GET whenever hardware presets list is not synced
Added: Don’t ask for GET if location 000 is double-clicked and the name is not “Panel Settings”
When I send to the minitaur the CC 82 with value before 63 or after 64, there is no change…
CC 82 is given in the MINITAUR_MANUAL_3_16_15… Is it still that number ?
Do you manage to change the LFO key trigger with CC in this version ?
Here, the light of the midi in light on when I send the CC but nothing happen…
n°1:
-In editor click on MIDI SYNC
-move the LFO rate knob on the hardware
-the values in the editor are only “4 bars - 1/2 - 1/8 - 1/32T - 1/64T”
-impossible to have the others ones…
-but it’s working with arrows in the editor.
n°2:
When I send the sysex message “F0 04 08 1B 00 00 F7”
(Causes the Minitaur to output MIDI CC values for all internal sound parameters.)
The LFO clock divider is not the good one.
-In Editor, click “MIDI SYNC” on
-move the LFO rate knob on the hardware until a value.
-the LFO clock divider indicator in the Editor is moving (but gives only value of issue n°1)
-Send the Sysex F0 04 08 1B 00 00 F7
-The Editor change the LFO clock divider to 4 bars (sometimes it’s an other value).
Is it a regular behaviour ?
thanks all! Looking at schlam issue #1, I think it’s an Editor problem… if I monitor the MIDI CC output from the hardware, it’s putting out correct values as I turn the LFO Rate knob… and in fact I hear the hardware LFO stepping through its correct sync values… but the Editor in response to this MIDI CC is showing a wrong clock division in its UI.
I’m beginning to wonder if firmware v2.2.0RC4 was sent out as the correct file… I’m making a new version today.
In any case, I have verified on my side that CC 82 is the correct CC for LFO Key Trigger… verified that the hardware changes LFO Key Trigger setting correctly (any value 0-63 = OFF, any value 64-127 = ON), and verified that the LFO resets in response to MIDI notes when LFO Key Trigger is On.
update again: Looking at the raw MIDI CC output in response to “F0 04 08 1B 00 00 F7”
it appears the LFO Clock Divider (CC 86) is being output correctly.
Seems to me that the reported issues #1 and #2 are both caused by Minitaur Editor not updating its “Clock Divider” UI display correctly in response to this MIDI CC.
