This version contains many bug fixes, probably more than we can list. We are going towards a release candidate, which we hope to publish soon. This is the time to report anything unusual that you may encounter, and any issues that you think are important and which haven’t been treated yet.
Please download, install, and let us know your feedback.
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.14. If it says anything other than 2.1.14, 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.
If you are using Cubase 9.0.10 64 bit, the new editor does not work! It is loaded (vst 2.4 & VST 3), but it can not connecten to the editor although all the settings are in it! With the editor version Minitaur-Editor-3.2.0b8-WINDOWS.zip worked without problems. In the standalone version, however, it works with the new editor.
I could imagine that maybe the new plugin sentimental ligt is what’s new in Cubase 9
I have the latest firm and editor installed. I have tried standalone, VST, AU, VI VST versions and in all of them my LFO Rate knob no longer works.
I’m sorry I dropped out of the conversation for a while, I had also been having a preset saving issue where the HARD SYNC button would not save when triggered. I am happy to report this issue was resolved in the latest release! LFO rate knob is a big one that must be fixed before the official release. Interestingly, while the knob has no effect on the LFO rate, presets and editor type (VST, VI VST..) do.
I’ll try a reinstall & reset MTRE tonight and report back ASAP. I do not use a controller with a mod wheel, I use my Maschine Mikro.
Last Night
I did experience a glitch where I had to install the 2.1.14 firmware twice to get it to reboot. The first time I attempted to send the firm update the c6 window showed it loading but the Minitaur kept acting as though it were in fully erased standby mode. A few minutes later I tried to reboot the Minitaur myself while it still had the “Glide” blinking. I can’t positively say I started the whole process over with an erase command but I believe I went through steps 1-8 from your instructions.
I checked the editor as soon as the Minitaur booted up in the editor “settings” window and it did in fact list 2.1.14 as the current firmware.
The knob worked for two 2hr sessions over the last few days before I updated. With HARD SYNC the LFO rate knob and LFO VCO Pitch knob get much more attention from me.
I added nothing new to my set up during or after the update. I do have another editor running Pigtronix Echolution 2, but as stated both pieces of gear meshed perfectly for multiple sessions before update.
I reinstalled the firmware and also reinstalled the editor per the instructions. The issue is still there, however, I am only getting the issue in Maschine when using MIDI sync on the LFO.
I do not have this issue with standalone our in Bitwig 1 or Bitwig 2 Beta.
This issue did not exist before I updated the editor and firmware to the latest. I went back to software beta 9 and I got the same issue.
If you share the firmware files back a ways I am willing to test each one to isolate the update that caused the issue.
Yes, I only have the issue when all of the following are true:
Using VST or AU in Maschine
LFO MIDI Sync is engaged
The behavior is that the LFO rate is stuck and can not be adjusted. I can’t tell which update the issue started because I was disengaged for a few over the holidays (sorry).
Maschine is not officially supported on this release so as long as LFO Rate control works when MIDI Sync is On on “regular” DAWs, I think we’re ok. When Sync is engaged, Rate should change the clock division based on the DAW’s tempo.
I’m getting stuck notes when using the au editor in logic pro x! Have to restart the DAW for it to stop… Seems to happen when I change presets in the editor.
