[MTRE] Minitaur Editor 3.2.0b11 is available !

Hello beta group,

Minitaur Editor v3.2.0b11 is now available.

This version contains bug fixes, including Cubase 9 connection issues reported by some users on 3.2.0b10, please confirm if possible.

Please download, install and report your feedback on the forum.

Editor Download:
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0b11-WINDOWS.zip
http://www.moogconnect.net/downloads/minitaur/Minitaur-Editor-3.2.0b11-OSX.zip

Firmware Download (unchanged):
http://www.moogconnect.net/downloads/minitaur/Minitaur_Firmware_Beta_v2.1.14.zip

Windows Drivers Download (unchanged):
Driver v3.30.0 (Windows 7 and up): http://www.moogconnect.net/downloads/minitaur/Moog_Minitaur_USB_DriverSetup_v3.30.0.zip
Driver v2.23.0 (Vista or XP): http://www.moogconnect.net/downloads/minitaur/Moog_Minitaur_USB_DriverSetup_v2.23.0.zip

  • 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:

  1. 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.
  2. 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.
  3. Load the C6 sysex program and configure C6 midi ports so they point to Minitaur In/Out (“CONFIG”)
  4. Load the ‘Erase Firmware’ file provided in the firmware zip, into the C6 program (“LOAD”)
  5. 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.
  6. 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.
  7. 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.
  8. Restore settings to defaults by clicking on “Restore Default Global Settings” on the Editor’s Settings page.

Installing the driver (Windows only):

  1. Power off your Minitaur and disconnect its USB cable.
  2. 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.
  3. 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.
  4. Restart your computer.
  5. 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.
  6. 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.
  7. Restart your computer.
  8. 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.
  9. 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.

Thanks for your cooperation !

Just loaded this; havent had time to do a complete test drive, but one thing I noticed:

The LFO tempo indicator ‘LED’ on the GUI never flashes…dont know if this is an actual ‘bug’… ( dont remember noticing it before, but I assume it should be flashing like the one on my hardware Minitaur )

on Mac OSX 10.11.6

It’s there for future support, currently inactive. Thanks for the heads-up.

I can now confirm that the connection problems were solved under Cubase 9.0.10 were the VST 2.4 64 bit version and the VST 3 64 bit version! The standalone editor was somehow not installed with others also the problem that they have no standalone version? Thanks for the quick cooperation Gill and Salvator :slight_smile: you make very good work :slight_smile:

Thanks djkey,

Do you mean that you do not get the standalone installed in your system ?

Have you recently moved the app from the Applications folder to trash or somewhere else ?

I have uninstalled the old version. And the new version installed

Hello Gil,
Salvator and I have found the error I have a custom installation made only vst 2.4 64 bit and VST 3 64 bit selected then the standalone version is grayed out and you can not install it! If you make a full installation everything is as it should be!

Thanks for the heads-up. Please recheck once 3.2.0b12 is up, should be fixed.

yeah, cannot install only 64bit plugins and standalone, stand alone gets unchecked and cannot be checked again.
Also, i got a stuck note playing with the standalone editor and the lfo shape parameter on screen. not a big issue, but a panic button for all notes off on the editor wouldn’t hurt.
other than that seems to be working good and stable.

Not sure I understand.

Did you get this more than once ?

just once. i was messing with the knobs on screen with the mouse and at the same time was playing the minitaur via midi din in with an external keyboard. may be that dual midi in caused the problem.
i got a stuck note on and missed a panic button on the editor to shut it up. had to reset the minitaur for it to turn off.

Let me know if it ever happens again,

Thanks!

Hi Gil,

I have a strange one: I have 2 Minitaur’s, one “older” black one and one “newer” white one. For some unknown reason, the older unit will suddenly go completely out-of-tune to the point that the fine tune adjustment does nothing. It’s almost as if the 2 oscillator’s don’t stay in tune with each other and drift independently. I had a similar issue awhile back on one of the earlier beta versions that got corrected, but it’s back now and much worse. I was about to send the older unit back to Moog for a checkup when I tried one last time to send a preset to it and this time, the writing of the preset corrected it. Note that both units have the same firmware, attached to the same PC, running the same ME, etc. I had also previously tried re-flashing the firmware several times on the older unit and it didn’t fix the problem.

I just got it “fixed” a couple of days ago and haven’t played much since, so I’m not sure yet if the fix stays.

Let me know if this does sound like a hardware issue, and if so, I’ll send back to Moog.

Thanks, Ben.

How did you get it fixed ?

“Fixed” as in sent the Minitaur a MIDI preset from ME that got the oscillators back in tune (just the standard Taurus Bass III preset).

After I posted the above last night, I went to play the Minitaur and upon first turning it on, it was terribly out of tune again. I re-sent the Taurus Bass III preset and it went back into tune.

Could the software be causing this or does this seem more like a hardware issue?

Seems like you were the only person reporting this, so I guess this is hardware related (and specific to your unit).